Closed Fuerte1 closed 2 years ago
While the error is happening, I can still open the RSLHelper.ini in Notepad++, for example. Perhaps RSLHelper is trying to open the file with incorrect options, so that reading the file is not allowed by other applications, and then it fails, if some other application is already reading it.
https://docs.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-createfilea FILE_SHARE_READ0x00000001 | Enables subsequent open operations on a file or device to request read access.Otherwise, other processes cannot open the file or device if they request read access.If this flag is not specified, but the file or device has been opened for read access, the function fails.
Just to be sure, you have startet helper with admin rights, started it at first and helper starts rsl?!? :D
Yes I start helper with admin rights. This is what I start: "C:\Program Files\RSL_Helper_X64\RSLHelper.exe" Sometimes I start RSLHelper first, and it starts RSL, but when RSLHelper stops working, then I just kill it in Task Manager, and start it again. It then works for a while, until problem starts again.
I used Process Monitor and it shows that it is using ShareMode: None, and this is causing this problem. It should use ShareMode: Read.
You have the ini on a one drive. So as the synchronisation with a cloud drive is happening, the ini is in use and the helper can't write into it. Thats the reason. We don't recommend the use of a cloud drive for the config,
Yes, that is the reason the problem is happening. But you could fix it by using correct share=read option when opening the file for writing.
Or you could write the config file to some other place, like you do with image files. If you can't enable the share=read option.
Still not fixed.
Operating system
Windows 11
Systemlanguage
Other windows language. (please specify in the description!) Finnish
Current Game-Version
2.16.2.4
Bug description
Steps to reproduce
This happens several times a day, usually after running helper for 30 minutes or so. If I close the error dialog, then it opens immediately again.
Relevant log output
No response