Navigation
 


CRM 3.0: Import of Customizations fails with unspecific error

The Role "System Customizer" has been modified or deleted in the CRM installation. An import of customizations fails with an unspecific error. With tracing enabled, there's an error message like the following in the MSCRMServices log,

>SOAP Request failed:
>Url:http://crm/MSCRMServices/ImportXml.asmx
>MethodName:Import
>Response:
><?xml version="1.0" encoding="utf-8"?>
><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> <soap:Body>
> <soap:Fault>
> <faultcode>soap:Server</faultcode>
> <faultstring>System.Web.Services.Protocols.SoapException: Server was unable to process request. ---&gt; System.NullReferenceException: Object reference not set to an instance of an object.
> at Microsoft.Crm.NativeInteropProxy.CRMInteropCRoleTClass.AddPrivileges(CUserAuth&amp; Caller, UInt32 iCount, CRolePrivilege[] Privileges, String sessionToken)
> at Microsoft.Crm.Metadata.SecurityHelper.CreateEntityHelper(EntityDescription entityDescription, OwnershipTypes ownershipTypeMask, ExecutionContext context)
> at Microsoft.Crm.Tools.ImportExportPublish.ImportEntityHandler.CreateEntityAndAttributesFromNode(XmlNode entityNode)
> at Microsoft.Crm.Tools.ImportExportPublish.ImportEntityHandler.ImportItem()
> at Microsoft.Crm.Tools.ImportExportPublish.ImportHandler.Import()
> at Microsoft.Crm.Tools.ImportExportPublish.RootImportHandler.RunImport(String[] ImportEntities, ImportMask Mask)
> at Microsoft.Crm.Tools.ImportExportPublish.ImportXml.RunImport(String parameterXml)
> at Microsoft.Crm.WebServices.ImportXmlWebService.Import(String parameterXml, String customizationXml)
> --- End of inner exception stack trace ---</faultstring>
> <detail />
> </soap:Fault>
> </soap:Body>
></soap:Envelope>
>

So - what's going on here? Microsoft CRM tries to grant the System Customizer Role privileges on the newly created entity. If that Role is missing, the CRM fails to do so. This is a known bug in Microsoft CRM. There is a solution availabe from Microsoft support.

References:

© customaze®