SSRS BAQ Reports error after upgrade to K21.2.9

None of the upgraded SSRS BAQ reports are running in our migrated 2021.2.9 system. We get the message below on all of them whether the source is a BAQ or an External BAQ. The old system had the app and database on the same machine and they are split in the new scenario if that might make a difference.

If I create a new SSRS BAQ Report in the new system, it works fine.

I’ve filed a ticket but thought I’d do a shout out to see if others ran into this.

Thanks!

Mark W.

Program Ice.Services.Lib.RunTask raised an unexpected exception with the following message: RunTask:
Ice.Core.SsrsReportService.ReportExecutionSoapException: Exception of type 'Ice.Core.SsrsReportService.ReportExecutionSoapException' was thrown.
SOAP Fault: The report server cannot process the report or shared dataset. The shared data source 'dsBAQReport' for the report server is not valid. Browse to the server or site and select a shared data source. ---> Microsoft.ReportingServices.Diagnostics.Utilities.InvalidDataSourceReferenceException: The report server cannot process the report or shared dataset. The shared data source 'dsBAQReport' for the report server is not valid. Browse to the server or site and select a shared data source.)

We had the same issue and found the instance for the upgraded Epicor had a different name. So I had to go into each report and subreport to change the name of the Epicor Instance.

Thanks @Vinaykamboj! Where exactly are you changing the instance? I looked at the new RDL I created and a converted one and the datasources are identical.

I use Report Builder for SSRS reports. So I went to properties of the Data source and selected the SharedReportDataSource again manually with the new AppServer and Instance by browsing for it.

2 Likes

Ah, you mean the report server!

So the fix is:

Download the RDL

image

Open the RDL in Report Builder

Change the Report Server location

Save the RDL

image

Upload the RDL

image

Test the Report

image

Works great!

Thanks again @Vinaykamboj!

We are on prem, so do not have to download. I just went into the SQL server. In our case both the report server (due to new server) and the instance name were changed. Glad it worked.

Also on prem. From a Zero Trust security standpoint, we’re trying to keep developers like me off of the servers. :wink:

Also, downloading works for my cloud friends!