Wrye Bash error "wxPython: stdout/stderr"

[Shayoden]

My Wrye Bash 306 Standalone Version gives me this error when I open it, opening a little window named "wxPython: stdout/stderr":

Traceback (most recent call last):
  File "bash\balt.pyo", line 1796, in _conversation_wrapper
  File "bash\basher\__init__.pyo", line 4101, in RefreshData
  File "bash\basher\__init__.pyo", line 4181, in _corruptedWarns
  File "bash\balt.pyo", line 1206, in Display
  File "bash\balt.pyo", line 2792, in __init__
  File "bash\balt.pyo", line 483, in listBox
  File "wx\_controls.pyo", line 1290, in __init__
TypeError: String or Unicode type required

 

 

The concequences are that my mod list under "Installers" does not update when I put a new mod in the Bash Installer folder, and the load order of the .esp files does not updates when I use Loot, and my fear is that the "Anneal All" command may not work properly.

I have Skyrim installed in C:\Steam Games\steamapps\common\Skyrim, and Wrye Bash is also installed there.
I have Windows 7 64bit.

Edited February 28, 2016 by Shayoden

[Greg]

I think the most common cause of this error is a corrupted mod.

[Shayoden]

A corrupted mod can compromise the working of Wrye Bash?
And how can I find out which mod is? Can I just deactivate some esps and reset Wrye Bash?

[Greg]

Assuming this is the case, just uncheck the mods in batches and run Wrye Bash until you find the culprit.

[Shayoden]

I have unchecked some esps but without results, and in the end I uncheck ALL the esps, but the problem persists.

Edited March 6, 2016 by Shayoden

[Nebulous112]

Have you tried deleting and re-downloading Wrye Bash? Maybe Wrye Bash itself is corrupted.

[GrantSP]

Navigate to \Steam\steamapps\common\Skyrim Mods\Bash Installers\Bash\ or where you installed WB on your system and make a copy of Installers.dat. Delete the original and see if the error persists. If not rebuild the installers tab either by answering "yes" when asked or by selecting 'Enabled' from the context menu on the Installers tab.

 

This file is a machine listing of every file seen by WB, and hence the game, and may take some time to generate. I do not believe doing this will adversely affect the already installed status of your mods but that is why you make a backup copy before proceeding.

[Shayoden]

It doesn't work!  :/

[PlukovnikPravda]

I got the same problem, but with a twist (or else I am dopey, which has often been true): I didn't find and installers.dat file in the Steam\steamapps\common\Skyrim Mods\Bash Installers\Bash\

folder. I did get something similar: WryeBash wasn't reading/seeing many of the .esm files I had loaded and present. It created the bashed patch without an issue (I think). Seems to work. But it's...uh, annoying? Vaguely worrying?

 

And I'm sure the strange noises and chanting in the basement are nothing at all.

[GrantSP]

You won't see that file unless you have first opened that tab in WB and refreshed the installer list.