Check out the latest features available in Dynamics 365 for Customer Engagement, including LinkedIn Connect, Voice of the Customer and Universal Resource Scheduling.
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants.Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements.
ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
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,
How are your custom reports connecting to CRM ?
With CRM fetch connection or with SQL connection ?
It's a mix. The parent report is using a CRM fetch connection to utilize the filter, but the sub reports are SQL reports using the SQL connection.
Ok, this is definitely an environmental issue. The same report works perfectly fine on our Testing Environment and it has the same setup. The environments are structured as follows:
Things I have checked:
Ok, found a difference between the 2. The CRM App Pool on the test server is running under the context of NetworkService. The CRM App Pool on the dev server is running under the context of a custom account.
Anyone know what rights/groups this custom account should have (or might be missing) that would cause this problem?
The difference is only with the registering SPN an setting the trusted for delegation setting in Active Directory
• Trust For delegation must be set on Computer account
• setspn –a HTTP/crm
• setspn –a HTTP/crm.server.com
• Trust For delegation must be set also on User account
• setspn –a HTTP/crm Domain\User
• setspn –a HTTP/crm.server.com Domain\User
The CRM Fetch Reports require that you set correctly the SPN records.
Yes, this ended up being the problem. I thought having the Reporting Extensions installed meant you didn't need these SPNs, but apparently not!
If it's of help to anyone else I've written up about the different issues I came across on rsProcessingAborted error. It covers a lot of the issues I hit on this environment, so hopefully it saves somebody else 2 days of their life!
Business Applications communities