Over the last few weeks, despite not making any changes to the materials subreport, we are getting an error message shown below with our job traveler report. Do we know why this might have happened? If we reupload the RDL file in Report Style maintenance it fixes it for the day, or sometimes for a few hours, but then the subreport will error out again.
That is rather unusual.
The Next time you get the error. I’d suggest download the RDLs and inspect them and confirm if anything has gone wrong with the shared datasource. Seems unlikely.
It could also be a permissions issue, once again unlikely.
It could also coincidently bad data. After you upload the the updated subreport, does the same job traveler work?
Yes if I reupload the same subreport as before it works for awhile, then eventually it breaks and prints an error. This will happen every day, sometimes more than once a day, but uploading the report always fixes it in the short term.
That’s really weird. Is this the base traveler or is it in the Custom Reports?
The top level Job Traveler is a custom report, but the RawMaterialComponents subreport is the one that comes stock
Right? I have been having so much trouble figuring out where to start looking for a fix.
The first thing I would do is to immediately download the subreport RDL as soon as it starts throwing the error. Then grab the RDL file that you use for re-uploading, and open both in a text editor to do a comparison. Sublime Text has a great tool for comparing differences in files, I’m sure there are a ton of tools you could use.
But if the RDL that is throwing the error is different from the other, then something is causing that RDL to change.
If the RDLs are the same, and re-uploading still fixes it, then that’s something you’ll probably need to contact epicor about. Are you in Cloud or on Prem?
1 Like
Here’s your problem 
Not really , but I thought the server name was funny, and this was just opening the default version of the subreport.
Einstein, Really
I’ve seen that in multiple cloud environments. There’s another one that comes up too, can’t remember the name of it.
For the same job though? I mean to say if you upload the subreport and rerun the job traveller for the job that it broke on previously does it work again?
If it does then I’d be taking @kve advice.
There has to be some issue with passing in the parameters