1
Vote

Windawesome Failing After .NET Upgrade

description

This week, my system administrator upgraded the .NET framework on my machine from the previous deployment of 4.5.2 to version 4.6. I was very unhappy to see this error when starting my previously functioning Windawesome configuration. I'm trying to debug myself, but I'll post the error here in case this is a common problem that others have seen.
Assemblies:
Windawesome, Version=1.4.2.0, Culture=neutral, PublicKeyToken=null
mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
System.Drawing, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Microsoft.Scripting, Version=1.1.0.20, Culture=neutral, PublicKeyToken=7f709c5b713576e1
IronPython, Version=2.7.0.40, Culture=neutral, PublicKeyToken=7f709c5b713576e1
IronRuby, Version=1.1.3.0, Culture=neutral, PublicKeyToken=7f709c5b713576e1
Microsoft.CSharp, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
 
OS: Microsoft Windows NT 6.1.7601 Service Pack 1
CLR: 4.0.30319
64-bit OS: True
64-bit process: True
Elevated: False
System.InvalidOperationException: Category does not exist.
   at Microsoft.Scripting.Interpreter.NewInstruction.Run(InterpretedFrame frame)
   at Microsoft.Scripting.Interpreter.Interpreter.Run(InterpretedFrame frame)
   at Microsoft.Scripting.Interpreter.LightLambda.Run8[T0,T1,T2,T3,T4,T5,T6,T7,TRet](T0 arg0, T1 arg1, T2 arg2, T3 arg3, T4 arg4, T5 arg5, T6 arg6, T7 arg7)
   at System.Dynamic.UpdateDelegates.UpdateAndExecute7[T0,T1,T2,T3,T4,T5,T6,TRet](CallSite site, T0 arg0, T1 arg1, T2 arg2, T3 arg3, T4 arg4, T5 arg5, T6 arg6)
   at Microsoft.Scripting.Interpreter.DynamicInstruction`8.Run(InterpretedFrame frame)
   at Microsoft.Scripting.Interpreter.Interpreter.Run(InterpretedFrame frame)
   at Microsoft.Scripting.Interpreter.LightLambda.Run4[T0,T1,T2,T3,TRet](T0 arg0, T1 arg1, T2 arg2, T3 arg3)
   at IronPython.Compiler.PythonCallTargets.OriginalCallTarget3(PythonFunction function, Object arg0, Object arg1, Object arg2)
   at System.Dynamic.UpdateDelegates.UpdateAndExecute3[T0,T1,T2,TRet](CallSite site, T0 arg0, T1 arg1, T2 arg2)
   at Microsoft.Scripting.Interpreter.DynamicInstruction`4.Run(InterpretedFrame frame)
   at Microsoft.Scripting.Interpreter.Interpreter.Run(InterpretedFrame frame)
   at Microsoft.Scripting.Interpreter.LightLambda.Run2[T0,T1,TRet](T0 arg0, T1 arg1)
   at IronPython.Compiler.PythonScriptCode.RunWorker(CodeContext ctx)
   at Microsoft.Scripting.Hosting.ScriptSource.Execute(ScriptScope scope)
   at Microsoft.Scripting.Hosting.ScriptEngine.ExecuteFile(String path, ScriptScope scope)
   at Windawesome.Config.PluginLoader.LoadAll(Windawesome windawesome, Config config, IEnumerable`1 files)
   at Windawesome.Windawesome..ctor()
   at Windawesome.Program.Main()
Inner Exception:
none

comments

steelet wrote Nov 5, 2015 at 4:51 PM

Any chance someone could debug this? I started using bug.n as a replacement and I'm worried I'm going to punch a hole in my screen soon.

Alien282 wrote Nov 11, 2015 at 3:25 PM

Hi,

Sorry for the late reply, I didn't get an email for the first post.

Google told me that the problem might be in the CPU/RamMonitorWidgets. Could you try removing them from your config file and see if that fixes the issue?

steelet wrote Nov 12, 2015 at 3:10 PM

Great Scott, you've done it!

Removing the CPU and RAM monitoring gadgets from my toolbar configuration solved the problem.

Windawesome is back up and running on my office workstation!

Thank you very much! I don't know how much longer I would have lasted using bug.n.

-Tyler