I'm getting an error on our dev environment running custom reports. It doesn't happen with out of the box reports, just with reports I have uploaded. I've read a lot of sites and forum questions on this but none seem to yield a solution.
The following is the error I'm getting in the Reporting Services log:
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 --->
I have read the following post: http://support.microsoft.com/kb/811889 but it isn't exactly the same error message. All the same I checked if I needed to create SPNs etc. So using that support page I see that I can check the event log for MSSQL warnings, but there's nothing like the error they referenced: "Source: MSSQLServer EventID: 19011 Description: SuperSocket info: (SpnRegister) : Error 8344.". So for this reason I can only presume the account that the SQL and SSRS services runs under are set up correctly and can create any SPNs as required? Note that they both run under domain accounts, something like SSRS_Account and SQL_Account or something. For the record, the domain account that the SSRS context runs under is a member of both ReportingGroup and PrivReportingGroup.
Next, I installed Reporting Extensions on the SSRS server and it's up to the same UR as well. So I presumed we wouldn't need to configure SPNs? I'm open to correction on this one though. The initial problem we has was the reporting extensions wasn't installed so I installed UR6 and then upgraded it to UR8.
Any ideas much appreciated,
Conor.
