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.
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
Last night I've applied some pending Windows Updates on our CRM 2015 environment. Although the patching process went perfectly fine, it seems that Reporting has been affected due to the Manual Failover switch from AG Node 1 - Primary to AG Node 2- Secondary(switched back AG Node 1 to Primary after boot).
While accessing Reports in CRM the following error is thrown:
Web service request SetDataSourceCredentials to Report Server http://ReportServer failed with SoapException. Error: An error has occurred during report processing. (rsProcessingAborted)
Reporting Log says that it cannot connect to the Datasource due to the following error:
System.Data.SqlClient.SqlException: Connecting to a mirrored SQL Server instance using the MultiSubnetFailover connection option is not supported. ---> Microsoft.Crm.Reporting.DataExtensionShim.Common.ReportExecutionException: Connecting to a mirrored SQL Server instance using the MultiSubnetFailover connection option is not supported.
I am pretty sure that this has been caused after the Manual Failover.
Can anyone with knowledge about this help me or point me to the necessary configuration to have this fixed?
Thanks in advance and Kind Regards,
Did you do an IISreset on the server after you reset the primary? Also to be clear, do u have CRM and SQL on the same box?
Hi Ray, thanks for your message.
No, CRM and SQL are on different VM. The SQL uses 2 VM, one is Primary and the other is a replica.
I will try an IIS reset and see if the issue will be fixed.
Business Applications communities