This is mainly a curiosity, as it very well could be the computer I'm working on has a lot of junk on it. Here we go:
Symptom: On login (arhoover@gmail.com) the app crashes. About 30sec after it goes out to logos.com's servers, the program crashes and a windows exception error is thrown.
Things I've tried: Uninstalled and Reinstalled, Held Ctrl, and checked "Run setup."
Log File Contents:
Program Version: 1.0 (1.00.0.0062)
Windows Version: 6.1.7600.0
Time: 2012-01-21 00:00:53 -05:00 (2012-01-21T05:00:53Z)
Installed memory: 4,095 MB
Install path: C:\Users\Andy\AppData\Local\Apps\2.0\024WWNRP.OHT\82QQGWO0.QCD\proc..tion_c830e69472a2fd73_0001.0000_09da1efa593fcd7e\Proclaim.exe
Free install space: 2,523 MB
Temp path: C:\Users\Andy\AppData\Local\Temp\
Free temp space: 2,523 MB
Error ID: 7909
Error detail: ArgumentNullException: Value cannot be null.
Parameter name: groupInfo
System.ArgumentNullException: Value cannot be null.
Parameter name: groupInfo
at Logos.Proclaim.Common.Model.Group.Create(GroupInfo groupInfo)
at Logos.Proclaim.Common.UserManager.DeserializeCurrentGroup(String currentGroupString, String currentGroup2String)
at Logos.Proclaim.Common.UserManager.GetCurrentGroup(Int32 userId)
at Logos.Proclaim.Common.AccountManager.<LoginWork>d__d.MoveNext()
at Libronix.Utility.Threading.AsyncWorkerTask`1.EnumMoveNext()
at Libronix.Utility.Threading.AsyncWorkerTask`1.ContinueExecution(Object unused)
at Libronix.Utility.Threading.GroupedThreadPool.ExecuteNextCallback(Object state)
at System.Threading._ThreadPoolWaitCallback.WaitCallback_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)
From the looks of this log, it seems something is wrong with my Group and username connection.
Let me know what you think,
Andy