General Consultant Discussion

Has anyone been able to resolve the issue with this error : Error: ""Report file C:\ProgramData\Sage Software\Cache\MAS 200\<report name>.rpt is not found or does not exist. Load Report Fails"" I am receiving the error when I run a custom Crystal report from a custom report menu. The client had this report working fine, but they merged with another company so I modified the report with minor changes and then when I placed it back on the menu they receive this error. The report has a sub report. If I run the report in Crystal it works fine. If I remove the sub report, it works running it from the custom menu. I have tried recreating the report and the sub report from scratch, with a new name, no luck. I called Sage but they just pointed me to the KB ID:51884, which I have obviously looked at (and it did not help) and cannot find solution to it. Perhaps someone has been faced with this issue and has some insight ?

@Sage100Routine

Are you just _running_ the report or exporting to Excel? I know there was a Crystal 'export to Excel' issue a little ways back, but I don't recall offhand the exact issue.

Brett, I am just running the report. It does not load, simply comes up with the error (from the custom reports menu). If I run it from Crystal it works fine.

Similar issue from the way back machine. https://90minds-com.socialcast.com/messages/22317184?ref=stream

Nice, @JeffSchwenk. This still sounds somewhat familiar, and I'm kinda thinking the workaround might just be what you're aware of already: to just run the report from within Crystal. I did locate a note I had from a post-upgrade ""Load report failed"" error on a custom Crystal report, and I believe I resolved it by setting the Subreport Parameter ValueField to none. Probably a long shot but figured it couldn't hurt to try.

Brett, thank you, I will give that a try. Other thing I tried was to load the report and the menu entry on my workstation and I do not get the error. So it must be environmental, I think.

Brett, you are a genius! Setting the Sub report parameter value field to None did the trick! I would never have thought of that, thank you so much !!!