Support reference numbers are now provided to the user in CRM2011 when an exception is thrown where the details may contain sensitive information.
Initially we thought that they could be standard codes with corresponding meanings, however the code is a random code that is used to cross reference against the trace or application log. The message displayed is usually in the format:
"Reference number for administrators or support: #xxxxxx"
The section contains the Exceptions we have found using this method along with the resolution.
___________________________
System.Data.SqlClient.SqlException at Microsoft.Crm.Application.Platform.ServiceCommands.PlatformCommand.XrmExecuteInternal()
Cause: Occurred when executing a SDK Request during import/publish of Customisations.
Resolution: Wait until the import has finished and re-try. (V 5.0.9688.53)
___________________________
System.TypeInitializationException at Microsoft.Crm.Application.Platform.ServiceCommands.PlatformCommand.XrmExecuteInternal()
Cause: Occurred when a Plug In was executed after it had just been re-imported via a solution. The early bound proxy types were updated and I'm guessing the Proxy Types Behaviour was trying to load the old assembly.
Resolution: iisreset fixed the issue. (V 5.0.9688.53)
___________________________
System.Web.HttpUnhandledException Entity role must be specified for reflexive relationship <relationship name>
Cause: Occurred when trying to delete a N:N association where the relationship was defined as being between two entities of the same type.
Resolution: This is as yet unresolved (V 5.0.9688.53).
See http://social.microsoft.com/Forums/en/crm2011beta/thread/71ceaec4-a43b-494c-8518-a00e27f553cb for more information.
___________________________
System.Runtime.InteropServices.COMException (0x800703FA): Retrieving the COM class factory for component with CLSID {E5CB7A31-7512-11D2-89CE-0080C792E5D8} failed due to the following error: 800703fa Illegal operation attempted on a registry key that has been marked for deletion.
Cause: Occurred after a Plug In was re-registered using the Plug In Registration Tool.
Resolution: Re-booted fixed (V 5.0.9688.34)
___________________________
Microsoft.Xrm.Sdk.OrganizationServiceFault Plug-in assembly does not contain the required types or assembly content cannot be updated.
Cause: Plugin being registered does not have a public constructor with no parameters
Resolution: Add a public constructor
without any parameters in addition to the constructor public MyPlugin(string unsecure, string secure)