Fallout Mod Manager crashes every time I open package manager

[LostBeaver]

I am trying to open package manager but I am unable to. I am using this mod manager:

 

https://www.nexusmods.com/newvegas/mods/36901/

 

Every time I open the Package manager I get this:

 

Friday, December 1, 2017 - 5:33:43 PM

Fomm 0.13.21

OS version: Microsoft Windows NT 6.2.9200.0

System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Received an unexpected EOF or 0 bytes from the transport stream.

at System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count)

at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)

at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)

at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)

at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)

at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)

at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)

at System.Net.TlsStream.CallProcessAuthentication(Object state)

at System.Threading.ExecutionContext.runTryCode(Object userData)

at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)

at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)

at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)

at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)

at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)

at System.Net.ConnectStream.WriteHeaders(Boolean async)

--- End of inner exception stack trace ---

at System.Net.HttpWebRequest.GetResponse()

at WebsiteAPIs.NexusAPI.Login(String p_strUsername, String p_strPassword)

at WebsiteAPIs.NexusAPI.Login()

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)

System.IO.IOException: Received an unexpected EOF or 0 bytes from the transport stream.

at System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count)

at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)

at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)

at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)

at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)

at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)

at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)

at System.Net.TlsStream.CallProcessAuthentication(Object state)

at System.Threading.ExecutionContext.runTryCode(Object userData)

at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)

at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)

at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)

at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)

at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)

at System.Net.ConnectStream.WriteHeaders(Boolean async)

[dubiousintent]

From the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

Issue: FOMM crash trying to login to Nexus using Package Manager

• Cause: This feature has not worked in years, but just hasn't been disabled in the most recent updates. It is well documented in the comments section of the download page.

• Solution: Open FOMM, go to "Settings" and disable (uncheck) the box for "Check for new FOMod Version". This will prevent the login screen in FOMM from showing.

 

-Dubious-

[LostBeaver]

I tried doing that and it still says the same thing

[dubiousintent]

Don't have anything else to suggest. That is the known cause and solution. The API to the Nexus site changed, FOMM didn't, and that error report is saying the connection failed. Re-check that the setting box is no longer checked, and it should stop trying to connect.

 

If it isn't staying "unchecked", then you have a "permissions" problem preventing you from changing the settings. In that case it is most likely the location where you have FOMM installed (probably the same location as the Steam game).

 

Did you install Steam to it's default location? If so, please see the wiki "Installing Games on Windows Vista+" article for why the original default Steam behavior of installing games to the "C:\Program Files" folder tree was bad (they learned better, and don't do that any more); and why "disabling UAC and running as Administrator" is NOT sufficient, with instructions how to move it. This is the single most important thing you can do to fix and protect yourself against problems in the future. As much of a PITA as that is, it's never going to be any easier than now. Please see the 'Restoring to "Vanilla"' section of the wiki "FNV General Mod Use Advice" article as well.

If you did move Steam out of the default location, then likely the problem is one of "File and Folder permissions" on the parent "root" folder under which you installed the games. If this is not set correctly to allow at least "System", "Administrators", and "Users" to have "Full Control" then you can't overwrite other files or make changes. You then need to enable the "Properties | Security | Advanced | Change Permissions" setting of the parent folder to enable the box: "Replace all child object permissions with inheritable permissions from this object", so those changes get applied to the existing files and sub-folders.

-Dubious-

Edited December 3, 2017 by dubiousintent

[tsteele93]

UPDATE: Unchecking "Add missing info" or something like that worked. So, uncheck ALL the boxes in settings and it loads.

 

 

-----------------------------------------------------------------------

 

 

I'm getting the same error and tried the same thing - didn't fix it. I can start NVSE from FOMM but I cannot load or manage anything from there - I have to use NMM to do any installing or managing anything.

Edited July 23, 2018 by tsteele93

[dubiousintent]

Thanks for reporting back. Updated the Issue with that information.

 

-Dubious-

[langertown]

UPDATE: Unchecking "Add missing info" or something like that worked. So, uncheck ALL the boxes in settings and it loads.

 

 

-----------------------------------------------------------------------

 

 

I'm getting the same error and tried the same thing - didn't fix it. I can start NVSE from FOMM but I cannot load or manage anything from there - I have to use NMM to do any installing or managing anything.

 

This solved my problem three years later! Thank you mysterious internet stranger

Edited April 11, 2021 by langertown