Share
ReportI am hoping this is the correct forum to post a problem that I am having
My Problem
When running a report, I am getting the following error
Am error has occurred during report processing (rsProsessingAborted)
Server Specifications:
-On premise setup Dynamic 365 9.xx
-Windows SQL Server 2022 in an Availability Group three nodes
-A single SSRS Server with one instance SQL SSRS 2022 extensions installed
-A single front end application server running Windows 2022
Back Story:
-I built the SQL Server, cluster and availability Group
-I built the SSRS and installed the additional extensions so that SSRS would work with Dynamic 365
-The report server is using the AG Listener and works find during failover
-We installed Dynamics 9 Organization, but we had to use a Server name and NOT the listener name because it kept failing during the creation of the Organization
-The plan was to install using the server name to create the organization and then convert to using the listener name after the fact.
-We did update the Org to use the listener name and the application works fine
Problem:
What Works
-The application works fine during SQL AG failovers
What does not work
-When I failover from node A to node B or C the reports stop rendering and I get the above error.
More specifically
When the server that we used to create the Org is primary in the AG I can open a report and it comes up with data. When I fail over to node b or C I get the problem.
What I think is happing
-I believe there is someplace in the application that is still using the server name and not the SQL Listener name and we cannot figure out were. We looked at SSRS management section and there are data sources, but the connection string box looks as if it pointing to the Application for the parameters. In the Type is says Microsoft Dynamics 365 SQL and the connection string only says MSCRM Data Connector Connection String
-On the server that was used to create the Org I am getting a connection error when its a secondary that says The target database, MSRCM_CONFIG is participating in an availability group and not accessible - as if something from the report server is still trying to access that one node A even after we failed over to node B.
My question
Where is the Report Server Data source getting the SQL Server connection string to render the report?
How can I update the server information for the reports
What we tried
-We found a web.config file and updated that - no luck
-We found some data sources in SSRS that had the full connection string to SQL Server we changed from server name to listener name - no luck
Your help is appreciated
Categories:
I have the same question (0)
All responses (
Answers (
120
