Jump to content


Photo

Wrye Bash Log Errors.


  • Please log in to reply
2 replies to this topic

#1 Tzunshun

Tzunshun

    Prisoner

  • Members
  • 2 posts

Posted 14 July 2018 - 10:30 AM

Hallo Step Project.
First i want to say thanks for this program i love it alot ^_^
But anyway. I reinstalled my Skyrim & all my mods with MO This time instead of NMM

Well i have slight problem. Everytime i close Wrye Bash i get a error

I can still build a patch tho and Wrye Bash does open when i Launch the EXE but every i close the program i get this error below

 

 

Traceback (most recent call last):
  File "bash\bolt.pyo", line 370, in initTranslator
  File "gettext.pyo", line 182, in __init__
  File "gettext.pyo", line 340, in _parse
  File "encodings\utf_8.pyo", line 16, in decode
UnicodeDecodeError: 'utf8' codec can't decode bytes in position 90-91: invalid continuation byte

I can still launch skyrim without problems.
I have tried few things.
Reinstall Wrye bash
Deleted Skyrim.ini (Because i heard it could be the problem)
Run Wrye bash on Admin

Im so lost now, no idea what the problem is or if it is a problem or i can ignore it.

Here is my mods/loadorder

Edited by Greg, 14 July 2018 - 11:41 AM.
Added spoiler tags

  • 0

#2 Sharlikran

Sharlikran

    Citizen

  • Mod Authors
  • Pip
  • 77 posts

Posted 15 July 2018 - 11:05 PM

This is the same error posted in about every Wrye Bash comment section. You simply have a non English language character that has to be removed. That error has been attempted to be resolved tens if not hundreds of times.

 

With that said though, the error is happening in a file that doesn't belong to Wrye Bash at all. So this error is more of a system issue.

 

It could be any one of these things:

 

1) A char in your User name
2) A char in your Downloaded file name
3) Contents of the zip/rar download may contain a file with non ASCII chars
4) Folder names of the zip/rar download may contain a file with non ASCII chars
5) Contents or TXT, INI, HTML, XML, CSV files of the zip/rar download may have non ASCII chars

 

I won't know where the char is and Wrye Bash can't help you find it either. Another thing you can try is changing your language settings if more then one variation of your preferred language is available from Windows. Sometimes you have only one choice, which in that case you won't be able to use Wrye Bash.

 

One last thing though. I really hate that really small abridged log file. Unfortunatly that's all the user gets. I wish there was a more automatic way to create a more complete debug log file automatically.  At the top of every Wrye Bash page is a link to a document for troubleshooting that asks you to run Wrye Bash in debug mode. For example then I would know what language you have, the version of Wrye Bash, the codepage, and so on. I would really appreciate it if users would follow the link. Here is a quick link to the section that pertains to the Standalone version. The guide says to change to "path\to\Mopy" which is telling you to change to the location where Wrye Bash is installed. Yeah you kinda need to know that. :;):

 

What that basically wants you to do is to run the Wrye Bash.exe with the -d command line parameter. If you ran the EXE installer there is also a Wrye Bash menu in the Windows Start menu that has a shortcut already that enables debug mode.

 

Once you have a BashBugDump.log in your mopy folder, post it here.


Edited by Sharlikran, 15 July 2018 - 11:12 PM.

  • 0

#3 Tzunshun

Tzunshun

    Prisoner

  • Members
  • 2 posts

Posted 16 July 2018 - 07:06 AM

This is the same error posted in about every Wrye Bash comment section. You simply have a non English language character that has to be removed. That error has been attempted to be resolved tens if not hundreds of times.

 

With that said though, the error is happening in a file that doesn't belong to Wrye Bash at all. So this error is more of a system issue.

 

It could be any one of these things:

 

1) A char in your User name
2) A char in your Downloaded file name
3) Contents of the zip/rar download may contain a file with non ASCII chars
4) Folder names of the zip/rar download may contain a file with non ASCII chars
5) Contents or TXT, INI, HTML, XML, CSV files of the zip/rar download may have non ASCII chars

 

I won't know where the char is and Wrye Bash can't help you find it either. Another thing you can try is changing your language settings if more then one variation of your preferred language is available from Windows. Sometimes you have only one choice, which in that case you won't be able to use Wrye Bash.

 

One last thing though. I really hate that really small abridged log file. Unfortunatly that's all the user gets. I wish there was a more automatic way to create a more complete debug log file automatically.  At the top of every Wrye Bash page is a link to a document for troubleshooting that asks you to run Wrye Bash in debug mode. For example then I would know what language you have, the version of Wrye Bash, the codepage, and so on. I would really appreciate it if users would follow the link. Here is a quick link to the section that pertains to the Standalone version. The guide says to change to "path\to\Mopy" which is telling you to change to the location where Wrye Bash is installed. Yeah you kinda need to know that. :;):

 

What that basically wants you to do is to run the Wrye Bash.exe with the -d command line parameter. If you ran the EXE installer there is also a Wrye Bash menu in the Windows Start menu that has a shortcut already that enables debug mode.

 

Once you have a BashBugDump.log in your mopy folder, post it here.

Looks like i got it. Im playing alot of Visual novels and i mostly on Japanese Locale & Time everything. Just changed it back i dont get any errors more  ^_^ i will be back if i get thanks for ya healp <3


Edited by Tzunshun, 16 July 2018 - 07:07 AM.

  • 0


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users