Hello. When I try to open weath-lab without logging in to Fidelity, I get an unhandled exception box before the program opens. Below are the first several lines. I also get the same sometimes when trying to save an optimization using Net Profit as the highest parameter. I've tried everything I've found in the forum (re-installing .net, removing .xml files), but can't seem to resolve. Thanks.

System.NullReferenceException: Object reference not set to an instance of an object.
at WealthLabPro.ChartForm.a(BarDataScale A_0)
at WealthLabPro.ChartForm.w()
at WealthLabPro.ChartForm.GoButtonPressed(String symbol, Boolean force)
at WealthLabPro.ChartForm.p(Object A_0, EventArgs A_1)
at System.Windows.Forms.ToolStripButton.OnCheckedChanged(EventArgs e)
at System.Windows.Forms.ToolStripButton.set_CheckState(CheckState value)
at System.Windows.Forms.ToolStripButton.set_Checked(Boolean value)
at WealthLabPro.ChartForm.LoadWorkspaceItems(IList`1 items, Int32 version)
at WealthLabPro.MainForm.b(String A_0)
at WealthLabPro.MainForm.cu(Object A_0, EventArgs A_1)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Hi,

Based on the stack trace I believe the issue can be caused by corrupt default workspace. Please enable hidden file visibility (if required) and delete your saved workspace's file: it's called Default.ws and can be found under:

c:\Users\your Windows account\AppData\Roaming\Fidelity Investments\WealthLabDev (or WealthLabPro)\1.0.0.0\Data\Workspaces\

Afterwards you'll have to re-create the default workspace.

QUOTE:
I also get the same sometimes when trying to save an optimization using Net Profit as the highest parameter.

It's unlikely that the exception is the same. An "Object reference not set..." error message can be thrown by different routines. It's not necessarily a connected event.

Great, thank you, you were correct on the default workspace corruption.

You're welcome.