Sage 100

Upgrade from 4.4 to 2013 Custom report in Job Ops generates this ""report file not found"" error. Yesterday I deleted it in report Manager and added it back in, and it ran. Today the error has returned. The file does in fact exist and opens from Report Manager. @JobOps

Just a guess but is the path too long? I know we've had issues with that in the past.

Other custom reports with longer file names work.

Report has parameters - could that be it? I seem to remember an issue with parameters and custom reports but can't seem to find it in a search.

I have seen issues with converting reports to the v5.00b release (v2013, PU5) that give very similar error messages.

@JeffSchwenk - were you able to fix it, or did you have to recreate the reports?

I ran the mascrcw.exe utility, searched in all the various spots for the reports folders.

MY case it runs fine in 4.4, and gives the same error in 2013 whether the 4.4 version untouched, the version created by mascrcw.exe, or just doing verify database in crystal 2011. (the files changed a little, but not affecting fields used on the report).