Monday, 23 April 2018

Issue with the 'CRM 2013 Outlook Plugin' crash when you try to open it from Windows Start


Faulting application name: Microsoft.Crm.Application.Outlook.ConfigWizard.exe, version: 6.0.0.819, time stamp: 0x57a8f98f

Faulting module name: KERNELBASE.dll, version: 6.1.7601.24094, time stamp: 0x5abee073
Exception code: 0xe0434352
Fault offset: 0x0000c54f
Faulting process id: 0x2db4
Faulting application start time: 0x01d3dae0b2f11adb
Faulting application path: C:\Program Files (x86)\Microsoft Dynamics CRM\Client\ConfigWizard\Microsoft.Crm.Application.Outlook.ConfigWizard.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: f4a0ee1b-46d3-11e8-8e45-b083feb17d38


Resolution:


Resolve by replacing the value(C:\Program Files (x86)\MSCRM\Client\) of 'HKEY_CURRENT_USER\Software\Microsoft\MSCRMClient\InstallPath' in registery, with 'C:\Program Files (x86)\Microsoft Dynamics CRM\Client\'.


Reboot the PC once and try to open the putlook client.


For your info, I have installed the following updates on top of the 'Microsoft Dynamics CRM 2013 for Microsoft Office Outlook' 


- Service Pack 1 for Microsoft Dynamics CRM 2013 (KB2941390)


- Update Rollup 5 for Microsoft Dynamics CRM 2013 Service Pack 1 (KB3122951)

Wednesday, 18 April 2018

Dynamics 365 - SQL Server Custom Report run issue

Trace Log:

Webserver!ReportServer_0-10!187c!04/17/2018-05:26:11:: e ERROR: Reporting Services error Microsoft.ReportingServices.Diagnostics.Utilities.RSException: An error has occurred during report processing. ---> Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing. ---> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for dataset 'DSMain'. ---> Microsoft.Crm.Reporting.DataExtensionShim.Common.ReportExecutionException:
Microsoft.Crm.CrmException: An unexpected error occurred.
System.ServiceModel.Security.SecurityNegotiationException: A call to SSPI failed, see inner exception.
System.Security.Authentication.AuthenticationException: A call to SSPI failed, see inner exception.
System.ComponentModel.Win32Exception: The target principal name is incorrect ---> Microsoft.Crm.Reporting.DataExtensionShim.Common.ReportExecutionException: An unexpected error occurred. ---> Microsoft.Crm.Reporting.DataExtensionShim.Common.ReportExecutionException: A call to SSPI failed, see inner exception. ---> Microsoft.Crm.Reporting.DataExtensionShim.Common.ReportExecutionException: A call to SSPI failed, see inner exception. ---> Microsoft.Crm.Reporting.DataExtensionShim.Common.ReportExecutionException: The target principal name is incorrect
   --- End of inner exception stack trace ---

Resolution:  

The error is due to a negotiate exception that is occurring with a fail to the SSPI.  Given the rsProcessingAborted and SSPI failure, we are looking at an SPN issue as none are registered under the domain account currently running the CRM AppPool. 

To check the list of spn's registered:
C:\>setspn -l <user running CRM app pool>

Run the following setspn commands on all CRM app servers which should resolve this reporting issue:

setspn -a HTTP/<CRM application server name> <user running CRM app pool>
setspn -a HTTP/<CRM application server FQDN> <user running CRM app pool>

Example:
setspn -a HTTP/CRM1 crmuser
setspn -a HTTP/CRM1.test.com test\crmuser

Do IIS reset and run the report.