Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2022 Release Wave 2Check out the latest updates and new features of Dynamics 365 released from October 2022 through March 2023
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
Up front, I am not a Dynamics person in any way. I work with SQL Server and SQL Server Reporting Services.
On the front end a collegue got the rsProcessingAborted error. She found a log entry in the SSRS log:
Microsoft.Crm.Reporting.DataExtensionShim.Common.ReportExecutionException: The user name or password is incorrect.
When I check the shared data source MSCRM_FetchDataSource that is of type Microsoft Dynamics CRM Fetch. The data source prompts the user for user name and password.
One thing that puzzled me was that the connection string was a single word (not a URL) that was an abbreviation for the company name. So I am not sure that that is the true reference to the CRM datasource. Could it be the actual reference? Where would I plug that connection string to test it (remember no Dynamics knowledge at all)? Or does this single word reference some configuration that is stored elsewhere?
The reports ran with that connection about a month ago and were run for the first time last week.
What should I suggest my collegue look into?
With that little of the messaging, I would say the best/easiest course of action is on the SSRS server, uninstall and then reinstall the SQL Reporting Extensions that are part of the CRM Installation media and then get them patched to the same level as CRM.
CRM has a custom reporting format that it uses for Fetch and the connection string is hard loaded based on the .dll build and some server info that is put into the reportserver.config file. Reinstalling the extensions should reset that info and get you back to functioning.
I forgot the most important phrase for consultants (besides "it depends"): "have you turned it off and on?" The client restarted their SSRS server and the connection came back.
Business Applications communities