Failed to open ErrorLog.txt on Start

[SteveLViss]

Hi,
I get this message on startup, Failed to open file, path to file, ErrorLog.txt

I've checked and this file is present, I can edit it and save to it manually.

This started to happen all of a sudden, Irricad had been running fine, I believe a patch was applied though and now this.

If I click OK in the message box Irricad runs normally, I haven't had to look for an error report as yet though, is there a fix for this?

[jovivier]

Hi Steve,

Please check for the presence of the Report.TMP and ReportViewer.exe. If the ReportViewer.exe is present double-click on it to see if it will run.
We have had some instances of anti-virus software quarantining the executable in the past. If your anti-virus software has grabbed the ReportViewer.exe you'll need to release it and configure an exception or exclusion to prevent future problems. Could you also let us know which AV software you use?

The IRRICAD Team

[SteveLViss]

Hi Jo,
Thanks for the reply, I can't find Report.tmp but ReportViewer.exe is present and runs but gives the message Report.tmp was not found when I run it. I've asked the Network Admin about AV Software but believe it is just Windows Defender.

[jovivier]

Hi Steve,

Can you please upload an image of the actual error message. This may provide a clue as to the underlying cause of the issue.

The IRRICAD Team

[SteveLViss]

See attached one for each message.

[phil]

Hi Steve

This looks like some sort of folder/file security issue. When IRRICAD is installed it sets up permissions on for the installed folder so that the Errorlog.txt file (and others) can be created and written to (I'm not sure how this would have changed). You can check this by simply right-clicking on the main IRRICAD folder and then "Properties/Security" the settings for "Users" should look something like this:-

Props.jpg

If the "full control" for "User" isn't ticked you could try setting this, by clicking the [Edit] button and reselecting "Users", and seeing if this fixes the issue.

If it does look like the above then it isn't the problem. You could try deleting the existing ErrorLog.txt as it will be recreated on startup.

Regards

Phil

[SteveLViss]

Hi Phil,
Thanks, the permissions were all good so I tried deleting (renamed the old file in case I need it for anything) and restarting and its generated a new one and the message is gone Thanks for that.