Error Logs don't show

[bhaas]

When I run Reports>View Errors nothing happens. I also don't see an error report in the Reports folder. I'm running V17.

[jovivier]

Hi,
The first thing to check is if the Errorlog.txt file is present in your IRRICAD folder. The location of your IRRICAD folder will be
C:\Program Files (x86)\Irricad\Irricad Pro 17 for a new install or C:\Program Files (x86)\AEI Software\Irricad Pro 16 (or similar) if you upgraded an existing version to V17.

If the Errorlog.txt is present open it in a Notepad, write something and then save it. Did it let you save?
If not, then the issue is a permissions issue and it is not letting IRRICAD write to the Errorlog.txt. Follow the steps in our forum post "Changing File Permissions in Windows 7" viewtopic.php?f=17&t=523&p=1196&hilit=write#p1196 . Note that this will also work in Windows 10.

If the Errorlog is not present please also check for a Report.TMP file. Are both of these files missing?

Note that if you can't see the file extensions in Windows Explorer (e.g., txt, tmp) you can turn these on by following the steps in our forum post "How to Enable Hidden Folders on Your Computer" - viewtopic.php?f=18&t=610#p1423 , and unchecking the Advanced Settings option "Hide extensions for known file types".

The IRRICAD Team

PS. with priority support you can contact your local distributor, closer to your time zone, for more timely assistance.

[bhaas]

I am able to open and save text into the ErrorLog.txt file and the Report.Tmp is present.

[Dan Crosby]

Hi,

Another thing to check is that ReportViewer.exe is present and you can run it. We have had some instances of anti-virus software quarantining this file. If your anti-virus software has grabbed this file, you'll need to release it and configure an exception to prevent future problems. Could you also let us know which AV software you use?

Thanks

Dan

[bhaas]

The ReportViewer.exe was not present in the Irricad folder. I whitelisted the Irricad installation folder then did an installation repair, and it fixed the issue. We are using Security Manager AV Defender.