Reproduceable Exception Dialog When Running App in 2.1.6

[Kraggy]

I have a seemingly reproduceable problem with a new 2.1.6 installation.

 

As I mentioned in a separate post I made some minutes ago I have some tools that require process elevation and the problem I'm having seems to always happen after one of those apps has run.

 

The sequence of events is this:

 

1) I use the RUN button to launch a command-line tool called TCC which requires process elevation, so I get the dialog my other post is complaining about.

2) I click OK and TCC runs normally.

3) Back in MO2 I then, say, run LOOT.

4) The console window for usvfs_proxy_x86 opens.

5) An ERROR dialog appears saying "Unhandled USVFS proxy exception (line 110): The system cannot find the file specified."

6) I click OK and LOOT opens normally.

 

I assume line 110 means something to the programmer who wrote this, sadly I'm not he so I have no idea what it's referring to, also It'd be nice when an error like this occurs if name of the file which is a problem was actually included in the error message, it helps users try to fix problems. 

 

Right now I have zero idea what the problem is or how to proceed, having never seen this with 2.1.5.

 

I have uploaded the log files I could find from MO2.  Note that in one there's a message saying it failed to spawn TCC.EXE, this is bogus, TCC DID run.  Because the tools seem to run I'm not sure if this is a real problem or not, but given problems with the VFS could corrupt game save files I'm leery of using MO2 in this state.

 

 

As extra information, after the error occurs every attempt to run tools will get the exception dialog, only exiting MO2 and restarting makes them stop, until that is I run another elevated process and the dialog start happening again.

logs.7z

[Kraggy]

I changed MO2's logging to DEBUG in case that provides more info, the attached logs relate to a sequence of tools being run: LOOT, TCC, LOOT

 

As expected, the exception dialog occurred when LOOT was run the second time.

logs.7z

[TechAngel85]

Have you reported this on Discord or github?

[Kraggy]

Er, no.  I don't have an account on Github and the one time I tried to report on there I couldn't without one and I don't know how I'd report a technical fault like this on a VOIP system like Discord.

 

[edit]

 

So I created a Github account and found my way to: https://github.com/ModOrganizer2/modorganizer

 

I see nowhere to actually post an error report.

 

It says "Issues should be reported to the GitHub page " which completely fails to explain where this is, I thought I was ON the Github page.

Edited December 23, 2018 by Kraggy

[Greg]

I seem to recall this may be a known issue and the interim solution is to restart Mod Organizer after running a process with elevated permissions. I'd report it on Discord or github anyway just in case I'm not remembering this correctly.

Er, no.  I don't have an account on Github and the one time I tried to report on there I couldn't without one and I don't know how I'd report a technical fault like this on a VOIP system like Discord.

Discord is a text-based chat system that also supports voice chat on some channels. Find the link to the Mod Organizer 2 discord channel on the MO2 page on Nexus, click it, and it should drop you into the text chat.

[TechAngel85]

Yeah, you can point the devs to these forums for more information and logs (you can post logs in Discord too). The devs don't frequent these forums.

[Kraggy]

I've found where to open an 'issue' but then go 'techied' when I read this:

 

"Create a [GIST](https://gist.github.com) which is a paste of your USVFS logs,"

 

WTF does that mean? (Rhetorical, I'm not asking you but Github is a typical techie playground where 'normal' users aren't expected to join in).

 

I'll take your suggestion and post a link to this thread.

 

Cheers.

 

[edit]

 

After battling with the 'create ticket' function I eventually managed to create one.

 

/sigh, why do techies like to make normal users jump through hoops to report bugs in the software they write?

Edited December 23, 2018 by Kraggy

[Kraggy]

LOL, what a typically arrogant developer, LostDragonist closed my ticket with this comment:

 

"Duplicate of #218. This is a known issue. Previously, MO2 would have failed silently. Now it warns they user that they're doing something wrong."

 

So it's the USER's fault if they do something the software allows them to do and then the software breaks!!!

 

Well at least there's an alternative to MO2, albeit less than ideal, clearly the MO devs treat users with problems with contempt.

Edited December 23, 2018 by Kraggy

[LostDragonist]

Sorry about that.  I didn't mean to imply it was the user's fault.  I'm sorry my prescription sleep drug ramblings came off as arrogance.  It is a problem with MO2.  We're looking into getting it fixed.

 

Literally the only reason I even do anything with MO2 is to make it better for people trying to use it.  I really hope I'm not secretly hating everyone. 

[TechAngel85]

LOL, what a typically arrogant developer, LostDragonist closed my ticket with this comment:

 

"Duplicate of #218. This is a known issue. Previously, MO2 would have failed silently. Now it warns they user that they're doing something wrong."

 

So it's the USER's fault if they do something the software allows them to do and then the software breaks!!!

 

Well at least there's an alternative to MO2, albeit less than ideal, clearly the MO devs treat users with problems with contempt.

A post like this would normally get you a warning. I'm going to give you the benefit of the doubt that you're just frustrated. Please be kind when posting.

[Kraggy]

Indeed TechAngel I was frustrated but that wasn't a justification to be rude .. LostDragonist replied to an e-mail very quickly and explained what he was intending to say.

 

I apologise to you both, my comment was unacceptable.

Edited December 24, 2018 by Kraggy

[Sumarianhaze]

Just for clarity the issue is that MO is not being run as an administrator, to resolve this find ModOrganizer.exe , right mouse and choose properties then the compatibility tab, tick run this program as an administrator and save.