I need help, FOMM crashes when trying to upgrade its files.

[Guest marieruth]

I think I know why it's crashing and I'm not sure how to fix it. I'm pretty sure it's due to this:

 

 

And the crash dump is this:

Thursday, July 17, 2014 - 8:24:43 PM
Fomm 0.14.10.8
OS version: Microsoft Windows NT 6.1.7601 Service Pack 1

System.Xml.XmlException: Data at the root level is invalid. Line 1, position 1.
   at Fomm.BackgroundWorkerProgressDialog.System.IDisposable.Dispose()
   at Fomm.InstallLogUpgraders.Upgrader.PerformUpgrade()
   at Fomm.InstallLogUpgraders.InstallLogUpgrader.UpgradeInstallLog()
   at Fomm.Program.Main(String[] args)

I tried using LOOT to organize the downloads so that Fallout3.esm would load first, but when I look at the data files list in the Fallout 3 launcher, it's below Broken Steel. :\

 

I'm not sure what to do.

[Guest endgameaddiction]

Click on settings on the right on FOMM. Un tick "Check for new FoMod version". That will stop the crash dump.

 

FOMM is no longer being updated by timeslip since he's been gone for some time.

[Guest marieruth]

Click on settings on the right on FOMM. Un tick "Check for new FoMod version". That will stop the crash dump.

 

FOMM is no longer being updated by timeslip since he's been gone for some time.

 

Is that setting named differently? I cannot see that in my settings at all. I use the most recent version from prideslayer on this website.

 

Only when I start up FOMM using New Vegas, and then switching over to Fallout 3 succesfully opens up FOMM. But when I open it from a shortcut on my desktop, I get a message saying that there is an upgrade required, and then it fails.

[Guest endgameaddiction]

Oh then nvm then, I never used that one. But there's many that do around here so someone will answer that for you. My mistake. :/

[jaam]

Use the updated FOMM from this site. The upgrade code is deactivated permanently.

 

[Guest marieruth]

Use the updated FOMM from this site. The upgrade code is deactivated permanently.

 

I just tried that, and that didn't change anything...

[prideslayer]

(redacted)

[prideslayer]

Gah nevermind, that error is in the installlog.xml upgrader.. which probably should not even be running, but FO3 doesn't get as much testing as FONV.

 

Did you by chance manage FO3 with NMM at some point?

[Guest marieruth]

Gah nevermind, that error is in the installlog.xml upgrader.. which probably should not even be running, but FO3 doesn't get as much testing as FONV.

 

Did you by chance manage FO3 with NMM at some point?

 

No, I used FNV with FOMM recently after using NMM for a while and I just started a new playthrough with Fallout 3, it was installed to my steam games, but I never actually ran the game until like a few days ago.

[prideslayer]

Well *something* screwed up the installog, maybe LOOT then. FOMM w/ FO3 is working fine here, just tested. That picture in your first post is not an FOMM screen I don't think, either.

[Guest endgameaddiction]

I believe that's from the launcher.exe which makes sense because you can't adjust the load order for those games unlike the skyrim launcher.

[Guest marieruth]

I took screenshots of everything that happens when I try to run FOMM for Fallout 3.

 

Here is the crash dump that was created after it failing to load:

 

 

 

Tuesday, August 12, 2014 - 11:19:59 AM

Fomm 0.14.11.9

OS version: Microsoft Windows NT 6.1.7601 Service Pack 1

 

System.Xml.XmlException: Data at the root level is invalid. Line 1, position 1.

   at Fomm.BackgroundWorkerProgressDialog.System.IDisposable.Dispose()

   at Fomm.InstallLogUpgraders.Upgrader.PerformUpgrade()

   at Fomm.InstallLogUpgraders.InstallLogUpgrader.UpgradeInstallLog()

   at Fomm.Program.Main(String[] args)

 

 

 

I guess I'll use BOSS to test and see if maybe that'll change anything.

 

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

 

After running boss and uninstalling LOOT, I still have the same issue. I downloaded the installer that was posted on the FOMM thread on here and installed it, then manually overwrote the installation with the Custom build version 0.14.11.9 zip

 

I am not really sure what else to try...

[Guest endgameaddiction]

Do you have NMM installed? Both NMM and FOMM do not like to hold hands. You need to use one or the other. And if you uninstalled NMM, not all the files were removed. I honestly forgot how to fix this because this happened to me when i used NMM at launch. But yeah, stick with FOMM and get rid of that NMM and stick with FOMM for Fallout.

[Guest marieruth]

Do you have NMM installed? Both NMM and FOMM do not like to hold hands. You need to use one or the other. And if you uninstalled NMM, not all the files were removed. I honestly forgot how to fix this because this happened to me when i used NMM at launch. But yeah, stick with FOMM and get rid of that NMM and stick with FOMM for Fallout.

 

Ah, okay. Then that may be the issue. I don't have them installed together, but I've had both on my computer. I manually deleted the leftover folders that were specific to NMM, and I ran CCleaner to see if that would help too, but I'll google to see how to go about removing any other residual NMM stuff. Thanks for the response!

[prideslayer]

FOMM knows how to 'undo' the NMM installlog.xml changes -- unless they changed the format again.

[Guest marieruth]

I uninstalled both Fallout 3 and New Vegas, as well as running CCleaner to hopefully clean out any other residual stuff that could still be on my computer. I started up FOMM (0.14.11.9) having only Fallout 3 installed so far, and it booted up normally. I guess I botched something really bad. Anyway, thanks to everyone who replied to this thread.

[RitualClarity]

Something similar happened to me with Steam. It ended that some remainder files were still in my computer. The programs and all other programs that accessed the files were "damaged" and caused constant issues. Now that I found and removed all remnants ( like you did when you deleted the files and started over) I haven't had a problem since.

 

Do a quick check to see if any files are installed elsewhere from FOMM,F03 and FNV to be sure. Also check for duplicates and such. That was my problem.