E10.2 Error Editing ARForm SSRS

Anyone have any issues editing the AR Invoice form (ARForm) report?

I usually use Visual Studio for editing SSRS reports (I don’t like Report Builder). Last week I recreated our Quote Form without any issues, but now I’m getting an error with the ARForm report.

An error occurred during local report processing. The definition of the report ‘/ARForm’ is invalid. Error while loading code module: ‘CLSEpicor, Verison=1.0.0.0, Culture=neutral, PublicKeyToken=null,’ or one of its dependencies. The system cannot find the file specified.

I believe this has to do with the Reference of CLSEpicor.dll and class CLSEpicor.ReportFunctions.ARForm, but I can’t figure out resolve it.

I gave up and decided to use Report Builder, but I also get an error there too, but less informative.

An unexpected error occurred in Report Processing. (rsInternalError) Object reference not set to an instance of an object.

Any ideas would be extremely appreciated!

Same issue with the Customer Statement report too…

Shot in the dark, but did you double check the file path in your Report Style?

I should have said this is when I try to preview the report in Visual Studio (after pointing to the report GUID). If I make a change to the RDL and upload it to SSRS and print through Epicor it prints fine. But that’s a cumbersome way to fiddle with a report.

Thanks for the idea though!

Found the answer;

Copied the file the CLSEpicor.dll file from the client folder to: C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\PrivateAssemblies\ Apparently that is where Visual Studio is looking for it on some, but not all, SSRS reports.

I must have done this back when we moved from E9 to E10 and I was recreating these reports, but I completely forgot about it.

6 Likes

For anyone looking for a solution to this issue using Visual Studio 2019 Professional, try this path instead:

C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\CommonExtensions\Microsoft\SSRS

2 Likes

In case anyone else has this issue and the above solutions don’t fix the issue, I had to change the permissions of the folder “C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\ReportServer\RSTempFiles” on my SQL server. I found this by downloading the Microsoft Process Monitor onto the server then searching the log for which file was specifically getting the ACCESS DENIED.