Jump to content

Question

Posted (edited)

First of all, before we go over troubleshooting procedures, Mod Organizer works just fine when I'm at home, but I get the error and Mod Organizer can't initialize when I try to open it at my office. I take my laptop back and forth between the office and my house.

 

Here is the error I'm receiving:

idlFrjO.png

 

Here is my log file:

15:31:59 [D] ssl support: 0
15:31:59 [D] Working directory: C:\Program Files (x86)\Steam\steamapps\common\Skyrim\ModOrganizer
15:31:59 [D] MO at: C:\Program Files (x86)\Steam\steamapps\common\Skyrim\ModOrganizer
15:31:59 [D] initializing core
15:32:51 [D] save C:/Program Files (x86)/Steam/steamapps/common/Skyrim/ModOrganizer/webcache/nexus_cookies.dat

Before you blow me up about my stuff being in a UAC folder, I have MO also installed in a folder that isn't protected by UAC and receive the same error when trying to run that installation. I also tried installing MO on a completely different drive, which yielded the same result. The log files from both other installations are the same, just with their respective paths.

 

Noticing that, based on the log file, the webcache activity is the last action resolved, I tried emptying that folder and retrying to no avail.

 

Now, I'd like to reiterate that, as soon as I get home with my laptop, Mod Organizer pulls right up with no issues. This fact most likely eliminates the possibility of many causes that most of you helpful people on this forum will want to suggest.

 

Full Control access has been given in regards to permissions.

 

The error saying something about the network, in addition to MO only working at home, led me to believe it might be a firewall issue, as firewall settings change based on my current internet connection. I tried adding exceptions to my firewall (Windows10 and Avast!), as well as turning them off completely and continued receiving the same error.

 

I've even tried connecting to my home network over a VPN to no avail.

 

 

Any input or additional troubleshooting procedure suggestions will be greatly appreciated.

Edited by DerpKat

8 answers to this question

Recommended Posts

  • 0
Posted

Welcome to STEP @DerpKat

 

We won't blast you for anything. This is a rather perplexing issue and one that is still currently ongoing for a few users, however your examination has highlighted a potential clue that may help resolve it. So what I'll suggest is you continue this in GitHub using the open issue (#533).

 

Be sure to highlight the fact that the differing network activity is linked, in some manner, to the issue showing up.

  • 0
Posted

Welcome to STEP @DerpKat

 

We won't blast you for anything. This is a rather perplexing issue and one that is still currently ongoing for a few users, however your examination has highlighted a potential clue that may help resolve it. So what I'll suggest is you continue this in GitHub using the open issue (#533).

 

Be sure to highlight the fact that the differing network activity is linked, in some manner, to the issue showing up.

Hi @GrantSP and thank you for the welcome,

 

I actually came across that post/issue/thread when researching my problem. The reason I made a new post instead of continuing on that one, was that his issue was an issue with the device not being ready (to accept reading/writing presumably). All of the procedures that were suggested that he follow were related to that, the device not being ready.

 

Should I comment on it regardless of the differences in our issues?

  • 0
Posted

I would, yes. Since @Tannin spends more time there than here, he is more likely to offer help if you continue the thread. I have been able to assist in the past with this matter but your investigation leads me to believe there is something internal to the code that needs addressing.

  • 0
Posted

@GrantSP

 

Thank you for suggesting I post on the GitHub open issue. I'm not sure Tannin has seen it yet, but another knowledgeable individual seems to think it will surface actionable information.

 

You mentioned that you may have been able to assist me, had the environment been slightly different. Have you any ideas, for the time being, that I could try to get this resolved (a workaround)?

 

Thanks,

DerpKat

  • 0
Posted

Ah, so, as it turns out, the problem might lie somewhere within my home network.

 

When I'm at home, connected to my wifi, I can run MO just fine. When I disconnect from my home wifi, thats when the error starts occurring.

 

None of my steam files, games, or game resources are on a network drive.

 

Any ideas?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.