New SSRS Report - Error on Creation - Help Needed

When copying an existing SSRS report and giving it a unique folder path, we get the following error when printing:

We can make a copy of the standard ssrs report and give it a unique file path. This prints successfully. We can also manually recreate our ssrs reports following this method with success but with the volume of custom reports we have this is not an acceptable path forward.

We have tried the following steps to speed up the process but get the same error as above:

  1. copy standard ssrs report with unique file path
  2. change rdd to the same as the report we are trying to recreate
  3. download the new ssrs report
  4. delete the files in the new ssrs report folder
  5. download the old ssrs report
  6. copy the files from the old ssrs report
  7. paste the files from the old ssrs report into the new ssrs report folder
  8. upload the new ssrs report back into epicor

Has anyone else run into this since the most recent update and have you had a means of fixing this without having to rebuild everything manually?

Thanks,
Dylan

1 Like

Maybe I’m missing something, but aren’t the 2 below the same thing ?

1 Like

Same action just copying different items. Copying the standard ssrs report style should “always work”

Copying already customized reports “may lead to more system breakages in the future”

Quotes are from epicor support.

3 Likes

Update:

This issue is related to reporting file paths on the server. Some time during the last update, many of our reports did not get the cut-over command:

You can double-check to see if you have similar issues by querying the Ice.CustomReportStoreHistory table.

In our case, support is working on a hotfix, but no date for its arrival yet.

just fix it yourself lol

How can we do that? We are in gov cloud and I don’t think I have access to the server in question.

Maybe I’m confused. Are the paths just wrong in your db, or the server itself?

Where would I see the full path for the DB? I see the partials listed in Report Style Maintenance:

I think I see the full path using the CustomReportStoreHistory table, but I don’t think modifying anything there would be useful.

You won’t see a full path, just a relative one.

Which ones are incorrect?

That I do not know. In the phone call with Epicor the tech said they didn’t know which path was right either. I’m still waiting to hear back on that.

The paths that have been causing me the most trouble with the “Cannot be found” issue were the ones that start with “SaaS”. But after looking at our system, I have job travelers that use that path and work just fine, even when copying them. This whole situation gets weirder the more I look at it XD

1 Like

Copy one of the SaaS ones, but use the new convention.
I bet it works after that.

1 Like

Error escalated to a problem in Epicor if anyone is interested in the read: PRB0297297