Unable to start: Early Log Initialization Failed
Moderator: Forum Moderators
Forum rules
Before reporting issues in this section, you must read the following topic:
Before reporting issues in this section, you must read the following topic:
-
- Posts: 6
- Joined: July 10th, 2014, 3:52 pm
Unable to start: Early Log Initialization Failed
Build: 1.14 Steam
OS: Windows 8
Message at startup:
"Early log initialization failed.
Runtime error: No such file or directory (2)
Log file path:
C:\Users\MSIUSER\AppData\Local\Temp\/wesnoth-20180509022552-6496.log
This may indicate an issue with your Wesnoth launch configuration. If the problem persists, contact the development team for technical support, including the full contents of this message (copy with CTRL+C)."
Attached latest game log.
OS: Windows 8
Message at startup:
"Early log initialization failed.
Runtime error: No such file or directory (2)
Log file path:
C:\Users\MSIUSER\AppData\Local\Temp\/wesnoth-20180509022552-6496.log
This may indicate an issue with your Wesnoth launch configuration. If the problem persists, contact the development team for technical support, including the full contents of this message (copy with CTRL+C)."
Attached latest game log.
- Attachments
-
- wesnoth-20180508-002146-7840.log
- (32.31 KiB) Downloaded 304 times
- Pentarctagon
- Project Manager
- Posts: 5564
- Joined: March 22nd, 2009, 10:50 pm
- Location: Earth (occasionally)
Re: Unable to start: Early Log Initialization Failed
Did it really say Temp\/wesnoth-20180509022552-6496.log(the "\/" specifically), or is that a typo?
99 little bugs in the code, 99 little bugs
take one down, patch it around
-2,147,483,648 little bugs in the code
take one down, patch it around
-2,147,483,648 little bugs in the code
-
- Posts: 6
- Joined: July 10th, 2014, 3:52 pm
Re: Unable to start: Early Log Initialization Failed
It literally said "\/wesnoth". Though issue may have resolved itself, I was unable to launch the application for a good few hours.
I did not power down my system in between the issue resolving itself within those few hours.
I did not power down my system in between the issue resolving itself within those few hours.