Exception: Failed to rename 'log.txt' to 'logs\log-2012...
Posted: Tue Apr 13, 2021 10:19 am
I am getting a Windows error:
FahCore_a7.exe has stopped working
FahCore_a7.exe - Application Error
The instruction at 0x000000000... referenced memory at 0x0000.... The memory could not be written.
When I open the Windows Event Viewer, I see that this has been happening sporadically for 6 months but is now occurring every time I start FAH and seems to be:
Exception: Failed to rename 'log.txt' to 'logs\log-20yymmdd-hhmmss.txt': The process cannot access the file because it is being used by another process.
Looking in the Program Files (x86)\FAHClient folder, I do not see a log.txt file, and there was not a 'logs' folder. In an attempt to resolve the problem, I have created the logs sub-folder to see if this will resolve the issue.
I have also uninstalled and reinstalled the FAH client software, but I am still getting the error.
I am running FAH on two systems. The above error is occurring on a system based on an Intel Core i5-4570T with no GPU. I have not seen any errors on a system built on an i7-9700 with a GTX1050. Both are running Windows 10 Build 19041.867
FahCore_a7.exe has stopped working
FahCore_a7.exe - Application Error
The instruction at 0x000000000... referenced memory at 0x0000.... The memory could not be written.
When I open the Windows Event Viewer, I see that this has been happening sporadically for 6 months but is now occurring every time I start FAH and seems to be:
Exception: Failed to rename 'log.txt' to 'logs\log-20yymmdd-hhmmss.txt': The process cannot access the file because it is being used by another process.
Looking in the Program Files (x86)\FAHClient folder, I do not see a log.txt file, and there was not a 'logs' folder. In an attempt to resolve the problem, I have created the logs sub-folder to see if this will resolve the issue.
I have also uninstalled and reinstalled the FAH client software, but I am still getting the error.
I am running FAH on two systems. The above error is occurring on a system based on an Intel Core i5-4570T with no GPU. I have not seen any errors on a system built on an i7-9700 with a GTX1050. Both are running Windows 10 Build 19041.867