This is a recent issue, but for many of our crystal reports, we get the error in the System Monitor: ERROR: Run in preview mode from System Monitor for details. The report selected does not have any data to show. Yet, in the BAQ, there is plenty of data.
We virtualized our server, then we had to split Epicor into two separate servers and move the Crystal to the other server. So, I am wondering if in this process something got messed up. Ideas? Thoughts?
Thanks! For us it seems to be only the CR. Would this be a reinstall of CR on the local computer?
Not sure I under stand what you mean by “and move the Crystal to the other server”.
As far as I understand, a CR based report will make an XML file, which the CR Runtime viewer will read to render the report. Make sure client computers can access the location where the XML files are stored.
Follow-up …
After running a CR report (in preview mode), my System Monitor shows the report data stored at
\\usdcaapsXXXXX\EpicorData\Reports\manager\Job Pick List274723.xml
That first part \\usdcaapsXXXXX\EpicorData comes from the Client Data Directory setting in System Agent:
When we split our sever into two parts, App server and SQL server, I had to move all of our Crystal reports from the old, single server, to the new one. Like literally copy and paste from one folder on one server to at the new one. This was so Crystal reports would even work.
What is interesting though is, after running the report, they will show up as Complete in History tab, but show an error in Reports tab. However, if you hit Print Preview ti comes right up. Well, except for a couple that are not showing up in Reports tab at all but showing complete. So, I’m a bit confused. LOL!
@ckrusen Well, I got to looking at the info from where everything is stored, and I noticed that the EpicorData folder was not shared.
We have separate App server and SQL server boxes. All the CR stuff (the .rpt files) is on our App Server.
And we moved our app server to a different server, so I had to move everything with it. Long story why, but it was the easiest to do.
Since the RPT files are on a different server now, might want to double check that any custom RPT’s don’t have any references to the old server or its directory structure.
When we moved V8 (which only used CR reports) to a new server, I had to search every RPT to make sure it didn’t have any bad references - like the path to a sub-report’s location.
