Error message on lookup fields in MS CRM 2013 after FireFox patch 48.0
Our business users are receiving an error when clicking on any lookup fields in MS CRM 2013.
This started occurring in FireFox after the 48.0 update. The same web controls work fine on Internet Explorer.
We have experienced a similar problem with google Chrome in their 51.0.2704.79 m release.
Below is the generic exception:
Unhandled Exception: System.ServiceModel.FaultException`1Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=6.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35: System.NullReferenceException: Microsoft Dynamics CRM has experienced an error. Reference number for administrators or support: #9693EE1CDetail: <OrganizationServiceFault xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/xrm/2011/Contracts">
<ErrorCode>-2147220970</ErrorCode> <ErrorDetails xmlns:d2p1="http://schemas.datacontract.org/2004/07/System.Collections.Generic" /> <Message>System.NullReferenceException: Microsoft Dynamics CRM has experienced an error. Reference number for administrators or support: #9693EE1C</Message> <Timestamp>2016-08-05T15:50:58.7376015Z</Timestamp> <InnerFault i:nil="true" /> <TraceText i:nil="true" />
</OrganizationServiceFault>
Ñemoĩporã poravopyre
Found other community members that have experienced the same issue.
Microsoft KB: https://support.microsoft.com/en-ca/kb/3008160
Technical Explanation: http://www.crmanswers.net/2014/10/lookup-errors-with-google-chrome-38.html
Managed Solution that fixes the problem for both Chrome & FireFox: https://chrome38lookupfix.codeplex.com
Emoñe’ẽ ko mbohavái ejeregua reheve 👍 0Opaite Mbohovái (3)
That error message doesn't really seem to say anything... That's after a background request for HTML/text/xml in response to the click?
Is there any indication of an error message in Firefox's Browser Console? See: https://developer.mozilla.org/docs/Tools/Browser_Console
If there's no client-side error information, can you do anything on the server side to see whether a cookie, or HTTP header might be different between requests from Firefox 47.0.1 and Firefox 48.0? Checking the POST payload obviously is more difficult, but might be helpful.
If that doesn't flag up anything...
One standard approach to finding the specific change that triggers this problem is to find a "regression range" using nightly release of Firefox. It's an iterative process that would take some time and someone familiar with installing test versions of software with credentials to the application. Or in other words, I think you or someone at your company might need to roll up your sleeves for this one.
Some resources:
Ñemoĩporã poravopyre
Found other community members that have experienced the same issue.
Microsoft KB: https://support.microsoft.com/en-ca/kb/3008160
Technical Explanation: http://www.crmanswers.net/2014/10/lookup-errors-with-google-chrome-38.html
Managed Solution that fixes the problem for both Chrome & FireFox: https://chrome38lookupfix.codeplex.com
This change might get rolled back in Firefox 50, but your workaround is still needed for Firefox 49.