Jump to content


Photo

Mod Organizer Can't Run any FOMOD installer


  • Please log in to reply
6 replies to this topic

#1 TheFerries

TheFerries

    Prisoner

  • Members
  • 4 posts

Posted 29 October 2017 - 01:58 AM

So yeah this is quite a problem, so im following the STEP guide for fallout new vegas (Fear and Loathing) and everything was going fine until the point where I have to install Project Nevada

Everytime I tried to run the FOMOD installer, I just could not run it, it always gives the same error after it tries to load the fomod installer

I've attached a pic.
Incase you can't see the pic, the error says "The Type initializer for "SevenZip.SevenZipLibraryManager" Threw an Exception", then it says "installation Failed (errorcode 5)"

And it happens with every FOMOD installer, like the Flashlight mod and User Interface Organizer

At first i tought it was Winrar (cus it said Sevenzip) so i uninstalled and decided to install 7z, but nope, it fixed nothing
Later I decided to install them manually.. and everything was going well, until I reached Fallout Character Overhaul, and that is a whole different beast to treat manually!

So yeah, I Need help here

Any way to fix this?

Attached Files

  • Attached File  help.PNG   37.24KB   2 downloads

Edited by TheFerries, 29 October 2017 - 02:02 AM.

  • 0

#2 TheFerries

TheFerries

    Prisoner

  • Members
  • 4 posts

Posted 30 October 2017 - 06:53 PM

Double post!

And a little update, so somebody had this problem and tannin send a link about this same error, but in Fallout Mod Manager, where karbuke gave a solution:

https://sourceforge....hread/35b4171a/

but i'll be blunt, Since i have next to no knowledge about .net (apart from installing it), I dont know what to exactly do!

 


  • 0

#3 Helidoc

Helidoc

    Citizen

  • Mod Authors
  • Pip
  • 61 posts

Posted 31 October 2017 - 02:22 AM

In essence the discussion is about doing a repair on the effect .net installs. You may be able to open up program manager and select the effected .net installs and choose repair and see if that helps your issue or you could follow the directions from Microsoft, From an elevated command prompt run the following:

 

In the meantime, you should be able repair your install by running:
"%windir%\Microsoft.NET\Framework\v3.0\Windows Communication Foundation\ServiceModelReg.exe" /r /x
%windir%\Microsoft.NET\Framework\v3.5\WFServicesReg.exe /c

 

Each line is it's own command, Hope that helps
 


  • 0

#4 TheFerries

TheFerries

    Prisoner

  • Members
  • 4 posts

Posted 31 October 2017 - 01:58 PM

Thanks for the help, sadly its giving me another problem with the 2 commands

On the first command its giving me an error and telling me that: Web.Config. does not exists
and on the second command its telling me that: Machine.Config. does not exist

Since .Net framework 3.0 and 3.5 uses the configs from 2.0
when I see the config folder for 2.0 i have the following files (in the image attached):

As you can see I Have:

Web.config.default
Machine.config.default

But not the ones that the Commands are asking for.
Is there like, Any way to create the Web.Config and Machine.config file?

Attached Files


Edited by TheFerries, 31 October 2017 - 01:59 PM.

  • 0

#5 Greg

Greg

    Dragonborn

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 1,814 posts

Posted 31 October 2017 - 09:26 PM

You should have both machine.config and web.config in %windir%\Microsoft.NET\Framework\v2.0.50727\CONFIG. If this is the folder you took the screenshot from, you might try running a repair of the Microsoft .NET Framework 2.0 and 3.5 to see if this fixes the issue.



#6 TheFerries

TheFerries

    Prisoner

  • Members
  • 4 posts

Posted 01 November 2017 - 03:24 PM

The screenshot shows that folder indeed

I tried of course running the Framework 2.0, 3.0 or 3.5 installer, but since this is Windows 7, it doesnt work cus all those frameworks already comes with windows 7

Also ran the sfc /scannow command, and while it did fix some stuff the machine.config and web.config files are still missing


  • 0

#7 Greg

Greg

    Dragonborn

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 1,814 posts

Posted 01 November 2017 - 09:42 PM

In that case, run the .NET Framework Setup Verification Tool and follow the links near the top of the page to the .NET Framework Repair Tool if necessary.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users