Reports erroring out after 10.1.400 => 10.2.100 upgrade

So, I probably missed something during the upgrade but I can’t figure it out (yet)…

SSRS reports are returning errors in my test environment following an upgrade to 10.2.100.11. The error message states that there is an “invalid object name ‘RptLabels_b16a4668cd474526958640ed64c8f3af’” but, depending on the report, the message will reference a different datatable_GUID. This leads me to check the report database and, sure enough, the objects are not being created.

Does anyone have any idea what I should be looking for to correct this? I’ve verified that the reporting services deployment is using the correct report database, but I’m not really sure what else could be causing this.

Weird, did you check the report data definition?

I looked at the RDD and everything looks the same as it is in my production environment; is there something specific I should be looking for?

My thinking is that it is not an issue with the RDD since it is not just one report, but I’ve been wrong before.

You could also go to the RDL file and in the Microsoft report builder, go to the Report Lbl data set and look the query. I have seen times that the query for the datasets get corrupted after upgrades. So I would make a backup for the one you have currently in your computer and then download the report again and compare the before and after.

Regards

Hey Joe,

Honestly, several people on the list have had issues with RDDs moving to 10.2, including us. You may want to cut bait now and just rebuild it. That seems to have fixed the issue for many.

Mark W.

2 Likes

The rebuild did the trick! Reports are running now and the testing can continue…thanks for the help.

1 Like

Hi Joe, I have a similar issue moving from 10.1.500 to 10.2.200 - I can’t seem to be able to edit SSRS reports like we used to, you know plugging in the report database table parameter (i.e. REPORT DATABASE: 120022947b0b4ca8827ed42622c8b8f6). How did you end up resolving the issue?