Crash after update: dll.xml file gets corrupted?

[Eckhart]

Hi,

I really don't know what happened but all the sudden FSUIPC doesn't work anymore on my setting.

After connecting the Saitek Cessna trimwheel (the only element I changed in my perfectly working setting) and updating FSUIPC I get the three following screens starting FSX

Followed by

followed by

I forced FSX to accept the certificates of those elements including FSUIPC. I removed temporarily fsx.cfg to do this which forced FSX to read all the certificates which I approved. As a next step I put the old fsx.cfg back into its folder but I still continued to get those crashes.

As a next step I tried to follow your advice and just force perhaps Simmconnect to accept the update. I clicked yes several times to no avail. I changed the initdelay: no change.

I uninstalled the PDMG files. No change. I reinstalled the PDMG files. No change.

I modified the dll.xml file according to the PDMG recommendations http://support.preci...leshooting.aspx

THIS HELPED A LOT. The main element was to put

</SimBase.Document>

bled>False</Disabled>

at the end of dll.xml text.

This got FSX to start again and brought the 737 NGX back (now the 747 still doesn't work with this type of message: PMDG_747400_main.dll cannot find PMDGOptions.dllPMDG_747400_ACS.dll cannot find PMDGOptions.dllPMDG_747400_overhead.dll cannot find PMDGOptions.dll). However, FSUIPC still does not come up in the add-on menu. So I tried reinstalling FSUIPC to no avail.

I am at the end of my tether. Reinstalling FSX will be major work with all the add-ons to reinstall.

I hope you a solution for me...

Here is my install log:

Installer for FSUIPC4.DLL version 4.84

Looking in registry for FSX install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0

Parameter"SetupPath"

... >>> OK! FOUND FSX! <<< ...

Looking in registry for ESP install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft ESP\1.0

Parameter"SetupPath"

Not there, so looking in:

HKEY_CURRENT_USER\ESP

Parameter"AppPath"

... NOT found! ...

Looking in registry for Prepar3D install path:

HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D

Parameter"SetupPath"

Not there, so looking in:

HKEY_CURRENT_USER\Prepar3D

Parameter"AppPath"

... NOT found! ...

===========================================================

INSTALLATION FOR FSX:

SetupPath="C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X"

Checking version of FSX.EXE:

... Version 10.0.61637.0 (Need at least 10.0.60905.0)

Checking compatibility with installed SimConnect:

Found SimConnect build 60905 (Original)

Found SimConnect build 61242 (SP1 May07)

Found SimConnect build 61259 (Acc/SP2 Oct07)

Checking if there's already a version of FSUIPC4 installed in:

C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL

... Version 4.840 found.

FSX Modules folder already exists.

Okay -- installed FSUIPC4 into "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL"

Looking for the current user's Application Data path:

... found as "C:\Users\Chef\AppData\Roaming"

Now finding \Microsoft\FSX\FSX.CFG for all users, including this one

Looking in "C:\Users\All Users\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Chef\AppData\Roaming"

Found FSX.CFG in "C:\Users\Chef\AppData\Roaming\Microsoft\FSX\FSX.CFG"

Now checking DLL.XML ...

... There is a previous DLL.XML, checking for FSUIPC4 section.

... FSUIPC4 section already exists but will be replaced.

... FSUIPC4 section of DLL.XML written okay

Now checking for a SimConnect.XML file ...

... There is a SimConnect.XML, checking for "local" section.

... "local" section already exists, file not modified.

Looking in "C:\Users\Default\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Default User\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\Public\AppData\Roaming"

... No FSX.CFG there

Looking in "C:\Users\UpdatusUser\AppData\Roaming"

... No FSX.CFG there

"Modules\FSUIPC Documents" folder already exists.

Now installing additional files into the "Modules\FSUIPC Documents" folder:

Installed "FSUIPC4 User Guide.pdf" okay

Installed "FSUIPC4 for Advanced Users.pdf" okay

Installed "FSUIPC4 History.pdf" okay

Installed "List of FSX controls.pdf" okay

Installed "GlobalSign Root.exe" okay

Installed "FSUIPC Lua Library.pdf" okay

Installed "FSUIPC Lua Plug-Ins.pdf" okay

Installed "Lua License.pdf" okay

Installed "Lua Plugins for VRInsight Devices.pdf" okay

Installed "LuaFileSystem.pdf" okay

Installed "Example LUA plugins.zip" okay

Installed "Offset Mapping for PMDG 737NGX.pdf" okay

FSUIPC4.DLL installed and signature checked out okay!

Deleted GlobalSign Root fix program ... no longer relevant

===========================================================

All installer tasks completed.

Registration check for FSUIPC4 was successful! (result code 00)

*************** End of Install Log ***************

[Pete Dowson]

After connecting the Saitek Cessna trimwheel (the only element I changed in my perfectly working setting) and updating FSUIPC I get the three following screens starting FSX

It looks like something you installed before these things corrupted the DLL.XML file. That should be easy to sort out.

You said:

I modified the dll.xml file according to the PDMG recommendations http://support.preci...leshooting.aspx

THIS HELPED A LOT.

but you evidently did not fix the DLL.XML because you go on:

the 747 still doesn't work with this type of message: PMDG_747400_main.dll cannot find PMDGOptions.dllPMDG_747400_ACS.dll cannot find PMDGOptions.dllPMDG_747400_overhead.dll cannot find PMDGOptions.dll). However, FSUIPC still does not come up in the add-on menu. So I tried reinstalling FSUIPC to no avail.

All of which merely shows that the DLL.XML is in a mess. All those PMDG DLLs are loaded in the DLL.XML file.

I am at the end of my tether. Reinstalling FSX will be major work with all the add-ons to reinstall.

I hope you a solution for me...

Here is my install log:

No need for that, it is okay.

Just paste in your DLL.XML file and I can fix it for you. FSX is VERY fussy about XML files. It is possible you edited it with the wrong sort of editor. Only ever use either a proper XML editor, or something like NotePad. Never WordPad or any sort of Word Processor.

Regards

Pete

[Eckhart]

I am amazed Pete by your fast response. I edited the dll.xml file with notepad++ but I might have done something wrong. Many thanks for helping me with this issue!

DLL.XML

[Andydigital]

There were a couple of errors in it, the attached version should be OK now.

DLL.XML

[Pete Dowson]

There were a couple of errors in it, the attached version should be OK now.

Thanks, Andy ... you beat me to it!

Pete

[Eckhart]

Many thanks guys ! What a great community! Unfortunately this didn't settle the problem. Level-D came back into the add-ons (Ezdok is still there) but FSUIPC is still missing. Unfortunately the "detected a problem" FSX screens came back on with the order now inverted: FSUIPC comes first followed by PMDGOptions, PMDG Events and then PMDG Sounds as a new one. If I click on "No" for all those screens I get FSX back on but without FSUIPC and the PMDG 747 (no problem for the PMDG 737 NGX curiously).

I have no idea what to do now (I sent a request to PMDG too but for me the most important is to get my FSUIPC back...I use the VRinsight MPCombo by the way so I need it back :???: )

[Andydigital]

Have you run an FSX repair at some point recently by any chance? If you haven't definitely do NOT try that as it will ruin FSX and likely cause the exact same problem as you are having now.

Try the version of the xml below, in this version FSUIPC is the last module to load, sometimes changing the order that the DLL's load can help.

DLL.XML

[Andydigital]

Pete may have already mentioned this but another thing to try is to open up the FSX.cfg in Notepad++ and delete the whole section starting with the heading [Trusted] there will likely be quite a few lines starting with C:\ Program Files and ending with what looks like gibberish, just delete it all. Next time you load FSX you will have to allow all the gauges and modules again as FSX uses them, hopefully that will get around the bug in the trust mechanism is FSX.

[Pete Dowson]

Many thanks guys ! What a great community! Unfortunately this didn't settle the problem. Level-D came back into the add-ons (Ezdok is still there) but FSUIPC is still missing. Unfortunately the "detected a problem" FSX screens came back on with the order now inverted: FSUIPC comes first followed by PMDGOptions, PMDG Events and then PMDG Sounds as a new one. If I click on "No" for all those screens I get FSX back on but without FSUIPC and the PMDG 747

By answering "No" you are telling it not to run those programs, that's why they don't run. What if you said "Yes"?

It is starting to sound like a corrupted installation of FSX. Don't "repair" FSX, but try an uninstall and reinstall of the FSX SP2 update, or Acceleration (whichever it is you have).

Pete

[Eckhart]

I tried the new dll.xml. Now the error startup screens are back in the original order: PMDG options, events and sounds followed by FSUIPC. I followed your advice Andy and eliminated the trusted section in FSX.CFG. I confirmed everything on startup but unfortunately the error screens came back.

I was wondering about doing an FSX repair but thankfully I didn't. So I will try out Pete's advice and do a partially uninstall/reinstall

[Eckhart]

I made some significant progress! The PMDG error splashscreens disappeared after uninstalling/reinstalling FSX acceleration! The 747-400 loads now. The 747-400X-8i expansion pack still crashes but that should be solved by PMDG.

The main problem remains for FSUIPC. I still get the error splashscreen at startup. If I click "yes" the FSX clock turns and turns and turns (I waited one hour once) with no action on the process monitor (not responding). If I click "no" FSX loads but there is naturally no FSUIPC in the addon menu.

Do you have another advice for me at this point? Happily, I am making some progress but the essential item (=FSUIPC) is still not integrated into FSX. Many thanks so far and I really appreciate your help!

[Pete Dowson]

The main problem remains for FSUIPC. I still get the error splashscreen at startup. If I click "yes" the FSX clock turns and turns and turns (I waited one hour once) with no action on the process monitor (not responding). If I click "no" FSX loads but there is naturally no FSUIPC in the addon menu.

Does an FSUIPC4.LOG file get produced? If so show it to me. If not, then it is still the SimConnect trust bug which is occurring. Once FSX records that FSUIPC is trusted it will be okay. But apparently, on some systems, it takes some persistence. Please see the FAQ subforum thread entitled FSX fails to run after FSUIPC4 first installed .

BTW, Microsoft were aware of this bug long before they stopped FSX development. In fact it was much worse in the original release. They managed to reduce the risk of it occurring quite substantailly by the time SP2 and Acceleration was released, but it seems to occur on a few folks' systems very persistently. No one's ever got to the bottm of it. I have FSX installed on six completely different systems here and have never even had it occur once, let alone persistently. Weird.

Regards

Pete

[Eckhart]

Many thanks Pete for all your help! Same for Andy! It is amazing how fast you guys respond to a less computer savy flightsimmer.

Unfortunately I will have to sign out. I spent hours no DAYS trying to fix this and I am going around in circles. Most likely with all those freezes the FSX files are now corrupted and this is to no avail.

I will uninstall everything....I spent years to build up my little homecockpit and had quite some hours of joy with it. Unfortunately I spent more time with fixing things than with virtual flying.

Reading through all those emails of fellow simmers in the same situation I measure how much time we all wasted and time is the most precious thing down here... Therefore I will put a complete stop to this for the moment. Sad ending after having started with the wireframe MFS many years ago. Over and out...

Thanks for all Pete,

Cheers,

Eckhart

[Eckhart]

Hi Pete and Andy!

I am back and perhaps I found the solution... :razz:

As mentioned before I uninstalled everything regarding FSX (all those add-ons accumulated over all those years). I proceeded with a reinstall of FSX and FSUIPC (even bought a new version of FSUIPC in case mine got corrupted...meant as a support for Pete's work anyhow): no luck. I left it there for over 7 months now. I couldn't reinstall my whole computer because I had not enough time on my hand to do it...and I couldn't uninstall FSX and FSUIPC for sentimental reasons...

So one day roaming through the net I found a thread describing my problem where somebody proposed to search for a file called logbook.bin and to eliminate all occurrences of that file.

I did it and started FSX. The usual splash screen comes up immediately and I said "yes" once again......AND IT WORKED....from that point on, FSX started again without any problem and FSUIPC works like before!

A computer miracle... :razz:

So for all those souls in "simconnect" hell: search for logbook.bin and throw all files named like that in the trashcan....and VOILA!

Now I have to reconfigure everything and I need to get my FPS back...but I am as happy as can be!

[Pete Dowson]

I did it and started FSX. The usual splash screen comes up immediately and I said "yes" once again......AND IT WORKED....from that point on, FSX started again without any problem and FSUIPC works like before!

A computer miracle... :razz:

So for all those souls in "simconnect" hell: search for logbook.bin and throw all files named like that in the trashcan....and VOILA!

Thanks, I think Logbook corruption occurs sometimes when you have FSX crash on you mid-flight. However, such a corruption prevcents FSX starting up at all, irrespective of FSUIPC being installed. I've never known it to be related to the SimConnect timing bug.

Regards

Pete

[Eckhart]

I am certainly not as computer savvy as you Pete.

All I wanted to say is that it solved the problem I mentioned. All I had done since my last post was to remove all the add-ons which didn't change anything obviously(same FSUIPC incriminating start-up screen which never responded to a "yes" click). So I left everything alone for 7 months. Eventually I went back in with my OS-image disk ready to wipe everything clean and to start up from scratch. My last desperate move saved me from spending hours reconfiguring my computer and home simpit:

Just eliminating logbook.bin solved it immediately. How does this connect to the FSUIPC startup-screen and to the simconnect problem? I have strictly no idea.

But it worked immediately. Something to keep in mind for others who have the same problem and want to try a last trick before reinstalling Windows...

Thanks Pete for all your help!

What pleasure to be back...!

Cheers,

Eckhart

[Rose72]

Hi guys :-)

 

I'm new in here, but I think I have a problem with mine dll.xml as well, can you please take a look?

 

I've repaired FSX and reinstalled SP2. But ever since I have CTD (g3d.dll)  more often I select ENB.  Did I do something wrong here?

 

Kind regards

Frank

dll.xml

[Pete Dowson]

I think I have a problem with mine dll.xml as well, can you please take a look?

 

Looks okay, but I've not analysed every line. why do you think there's a problem with it? Is FSUIPC hetting loaded?

 

I note you are using the FSUIPC4 loader. Why? That's really not a good idea unless it is absolutely needed to solve a problem. You should remove the loader from the FSX Modules folder then re-run the FSUIPC4 Installer.

 

I've repaired FSX and reinstalled SP2. But ever since I have CTD (g3d.dll)  more often I select ENB.  Did I do something wrong here?

 

Why "repair FSX"?

 

G3D crashes are usually related to graphics -- sceneries and aircraft. They are nothing to do with FSUIPC. I think you are looking in the wrong place. Try a process of elimination on your graphics-related add-ons.

 

Regards

Pete

[Rose72]

Ok, thanks Pete.

 

I've removed the loader file from modules.

 

But what happen when you repair FSX, what will happen to the dll.xml file? and can I still use the old FSX.cfg file? without any conflicts?

 

Regarding G3D crashes, it happen often when I add ENB...

[Pete Dowson]

I've removed the loader file from modules.

 

You need to rerun the FSUIPC4 Installer, then.

 

But what happen when you repair FSX, what will happen to the dll.xml file? and can I still use the old FSX.cfg file? without any conflicts?

 

I don't think "repair" touches any of that. It's only looking at installed files ,ie. those in the FSX folder.

 

Regarding G3D crashes, it happen often when I add ENB...

 

Sorry, I don't know anything about ENB (and don't use it), but I have read about conflicts between ENB and other programs manipulating graphics. It does interfere with graphcs, which is where G3D comes in.

 

Your best bet is to check the relevant AVSIM forums.

 

Pete

[Rose72]

OK, thank you so much Pete for your service :-)

[lawrence737]

Hello Gentlemen,

 

Can anyone please help me out with my PMDG 747x,and MD11,they crash to desktop,I think Im faced with Eckhart's kind of issue.Someone please walk me out of this mess.

 Thanks a bunch.

 

Lawrence 737