Sage MAS 90 and 200 Sage MAS 500 blogs Product Feedback Support Training
Reply
unidentified user
djustice
Posts: 3
Registered: 04-14-2011
0

Problem with ReportEngine

We are suddenly have trouble with one machine only getting this error when trying to view any report.

 

This is the Error message:

 

"There is a problem with directory ReportEngine at report form load time for.  This is where Crystal .RPT files should be stored."

 

Nothing has changed with the MAS500 server or this machine from yesterday, this began popping up this morning.

 

Hopefully someone has run across this before and can help.

 

Thanks!

Moderator Moderator
Moderator
Wei
Posts: 85
Registered: 10-28-2008
0

Re: Problem with ReportEngine

Could you check the ReportPath in the Application.Config file.

On a Windows 7, the Application.Config is located at C:\Users\[User]\AppData\Roaming\Sage Software\Sage MAS 500.

The default entry looks like this:

<ReportPath>C:\Program Files\Sage Software\Sage MAS 500 Client</ReportPath>

Sage MAS 500 Customer
JohnHanrahan
Posts: 207
Registered: 11-03-2010
0

Re: Problem with ReportEngine

Look at resolotion id 2562.  That will help you understand where to look (Wei's suggestion was for 7.3 and up).

 

Once you know "where" MAS is looking for the reports you can then figure it out.  Should be easy after that.

Contributor
hsanguino
Posts: 26
Registered: 11-01-2008
0

Re: Problem with ReportEngine

Hi,

 

Were you able to solve this issue?

 

Thanks,

Hugo

 

Sage MAS 500 Customer
fburnell
Posts: 11
Registered: 12-17-2009
0

Re: Problem with ReportEngine

[ Edited ]

For one of my users in Windows 7, they got this error but if I logged into the system, I was able to run reports.  Reinstalling the client had no effect.  I inspected their user profile and found that they had a copy of a single report in the AppData\VirtualStore structure.  I deleted the VirtualStore of the Sage software folder (C:\Users\USERNAME\AppData\Local\VirtualStore\Program Files (x86)\Sage Software\ ) and the user profile was then able to run reports again. 

 

Hope this helps others. 


Fritz