Hi @Hasara Dinu ,

Did u check whether all the existing .RDLC reports have been copied to the above folder. Since this is a version upgrade, there is a minimal probability to removing the existing .RDLC files from both folders.

Can you give it a try to upload the above .RDLC file via report admin screen and check whether the issue is occurring after that aswell.....

Thanks,

Induwari

@Induwari , 

Thanks for the reply.

Yes all the reports including baseline and custom reports are residing in the client reports folder(APP PARAM = CLIENT_REPORTS_PATH).

Regards,

Hasara 

Hi Hasara,

we had a similar issue after a Update going from 6.5 to 6.17 and it was due to  a custom client code that extended report printing functionality, which required adjustments in order to work with the new version. May be this is the same case for you? You can find more info in Case G2327157.

Best regards
Roman

The error thrown by custom reporting functionality in G2327157 is “Object reference not set to an instance of an object” which is different from “Report file … not found”

There was additional enhancement in U19 for AdHoc Reports Upgrade feature.

@Erin McQuestion As far as I remember the initial shown error message was the same as here “Report file...not found” but when the guys did debug the code they came to the actual root cause which was “Object reference not set...” :)

Best regards
Roman