Open Rails Logging file enabled causes open rails to crash to error report

[commec61]

Hello all. Whenever I check the log button on the main open rails screen it crashes to the error report screen. I know that it is a Windows security issue but I cannot remember how to get around this. I am using Windows 10 and updating to the latest testing version causes this problem. I've searched through the forums for the answer as I know that this was addressed in the past but I am unable to located the answer. Microsoft one drive has corrupted my files so that I don't have that answer available anymore (thanks alot Microsoft). Will someone please help me and I will store the response in a more secure place for the future. A.I (Artificially Ignorant is not my friend).

Thanks in advance,
Steve

[derekmorton]

No crash here with front screen logging ticked with version u2024.07.17-0722
route Tehachapi Pass II

Have you tried more that one route?
Have you tried more than one activity?

[commec61]

Hi Derek,
The real problem is not actually with Open Rails itself. The problem is it not having permission to write the log file to the desktop. If I uncheck the box it loads and runs fine. I just like having the log file so that I can see if something is causing problems. This happened before after an upgrade to Open Rails But I cannot remember how it was solved.

[derekmorton]

The activity runner needs to be run as administrator.

[R. Steele]

Steve manually delete any old OR log file from the desktop, start OR and let it generate a new log ..... see if that cures the problem. There is a way to make a registry entry to place the desktop log anywhere you want === I cannot find the how-to instructions at this moment.

[commec61]

Hello again all,
I tried running everything as Administrator but am still not having any luck. If I switch back to the previous update it runs with the logging checked just fine. As I said before I'm positive that this is a Windows security issue. I just can't remember how to get around it in Windows 10. It was quite some time ago when this happened to someone else, which is probably why I can't find the answer in the forums. If someone does remember the trick it will be greatly appreciated.

[derekmorton]

Can you post the error that you get please?

[commec61]

Hello all,

I was able to get this fixed by eliminating all references to Microsoft One Drive from my computer. After reestablishing the desktop to my c:\ drive, the logging file was able to write to the desktop and thus ending the crash error. As I stated at the beginning I knew that it had to be a Windows security problem. I am unable to give detailed instructions as this took quite some time to accomplish. Since I build desktops as a hobby, I wasn't afraid to get in the trenches and be ready to wipe everything and start fresh if necessary. Thank you all fro your time it is always appreciated.