FOMM Crashes at Package Manager

[gconeen]

My OS is Windows 7 64-bit. Whenever I click on Package Manager, if I try to login, it crashes and I get this

 

 

System.NullReferenceException: Object reference not set to an instance of an object.

at WebsiteAPIs.NexusAPI.get_LoginKey()

at Fomm.PackageManager.PackageManager.WebsiteLogin()

at Fomm.PackageManager.PackageManager..ctor(MainForm mf)

at Fomm.MainForm.bPackageManager_Click(Object sender, EventArgs e)

at System.Windows.Forms.Control.OnClick(EventArgs e)

at System.Windows.Forms.Button.OnClick(EventArgs e)

at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)

at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)

at System.Windows.Forms.Control.WndProc(Message& m)

at System.Windows.Forms.ButtonBase.WndProc(Message& m)

at System.Windows.Forms.Button.WndProc(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

And if I hit cancel and try to Add a FOMod, it crashes and I get this:

System.NullReferenceException: Object reference not set to an instance of an object.

at Fomm.PackageManager.FomodBuilder.FomodFromSourceBuilder.BuildFomodFromSource(String p_strPath, NexusAPI p_nxaNexus)

at Fomm.PackageManager.PackageManager.AddNewFomod(String p_strPath)

at Fomm.PackageManager.PackageManager.addFOMODToolStripMenuItem_Click(Object sender, EventArgs e)

at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)

at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)

at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)

at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)

at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)

at System.Windows.Forms.ToolStripItem.PerformClick()

at Fomm.Controls.SplitButton.OnClick(EventArgs e)

at Fomm.Controls.SplitButton.OnMouseUp(MouseEventArgs mevent)

at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)

at System.Windows.Forms.Control.WndProc(Message& m)

at System.Windows.Forms.ButtonBase.WndProc(Message& m)

at System.Windows.Forms.Button.WndProc(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Edited February 27, 2013 by gconeen

[BlackRampage]

Try reinstalling FoMM and see if that works. Or try the version one can find here: http://sourceforge.net/projects/fomm/files/

 

It's basically the same version, but that one doesn't requires one to login to anything.

[King Moloch]

I am having this same problem. Just reinstalled the FOMM from the link specified in this thread, Package Manager still just freezes up and never recovers.

 

What is causing this? It just started up one day and I have no idea how to treat it or troubleshoot it.

[M48A5]

Open FOMM, left click on "Settings", under "General" clear everything in the "Options" section.

[Aonghus]

One other note. FOMM has an issue when running inside the "Program Files" section on newer machines. If you haven't already, try installing it in a root directory.

[AxlDave]

Had the same problem as initial poster, the link above still requires you sign in to Nexus.

 

Open FOMM, left click on "Settings", under "General" clear everything in the "Options" section.

 

This solution somehow fixed it all. Cheers buddy.

[MasterObserver]

It's the combination of a connectivity issue with NM's servers and poor coding.

Examining the crash dump reveals that the error occuring is a pointer referencing a NULL object.

The object in question is part of an API used in FOMM to login to NM.

The method of the object being executed:

WebsiteAPIs.NexusAPI.get_LoginKey()

is failing, and thus the object that should be returned after successful execution is not.

This is poor error handling on the developer's part, plain and simple.

ALL object oriented programming languages have the capacity to catch exceptions and deal with them appropriately.

Turning the options off is a workaround but it shouldn't be necessary; A patch should be released.

The application's inability to connect to NM's servers is another issue entirely though; At least NMM traps the error appropriately.

From my experience, the inability to connect to their servers is a natural DoS. NMM even says so upon attempting login, essentially: "Could not reach blah blah server."

I've had maybe 2 successful logins in NMM, all other attempts failed thanks to server issues.

Whether it's a server capacitance issue or a ploy by NM to get users to buy access to their premium servers matters not.

PROBLEM SOLVED...

well, at least accurately identified. :pirate:

Edited January 15, 2014 by MasterObserver

[inahut]

Open FOMM, left click on "Settings", under "General" clear everything in the "Options" section.

 

This Works! for me. using fomm 0.13.21 with FO3, already logged in to my Nexus account. Whereas before doing what M48A5 recommended I could not login to Package Manager without inducing a crash, now I am able to log in to it without problem of crash. High praise and thanks to M48A5.

inahut

Edited February 24, 2018 by inahut

[AvoidableDoor]

Open FOMM, left click on "Settings", under "General" clear everything in the "Options" section.

f*#@ing god

[Hekw0n]

I know it's been years since the last post but I also encounter this problem. What I did was when I click "package manager" I click no to the next two pop ups asking about updating stuff and after that It work like a charm. Hope this helps someone in the future.