FSUIPC isn't automatically loading upon startup

[CalCoastFlightSim]

So this product has been working just fine for me for several days but today it decided not to load. When I tried to connect my ACARS system for United Virtual it gave me this: FSUIPC Error #14: FSUIPC_ERR_RUNNING. FSUIPC not running. It doesn't show up in the addon bar btw.

and yes I've tried re-installing it and nothing has worked.

[Pete Dowson]

So this product has been working just fine for me for several days but today it decided not to load. When I tried to connect my ACARS system for United Virtual it gave me this: FSUIPC Error #14: FSUIPC_ERR_RUNNING. FSUIPC not running. It doesn't show up in the addon bar btw.

FSUIPC cannot decide whether to load itself. In FS9 and before it is loaded by FS itself, in FSX and Prepar3D it is loadedby SimConnect as a result of an entry in the DLL.XML file.

So, is this FS9, FSX or Prepar3D? What is the version number of FSUIPC please?

Check the Modules folder in FS. Is there an FSUIPC log (or FSUIPC4 log) file? If so please close FS down then see if the log is current and show it to me (copy and paste it into a message.here).

If this is with FSX or Prepar3D, then find the DLL.XML (it's inthe same folder as your current FSX.cfg or Prepar3D.cfg file). Copy and paste that here too. If that has been corrupted (and quite a few add-on installers seem to do this) then it can stop FSUIPC and other add-ons being loaded.

and yes I've tried re-installing it and nothing has worked.

Reinstalling rarely achieves anything as it is only replacing the DLL in the same place with the same DLL. Sometimes it can re-add FSUIPC to a DLL.XML screwed up by another installer, or even create a basic DLL.XML if the proper one has gone missing, but that's probably a long shot.

Regards

Pete

[CalCoastFlightSim]

It is FSX. The version number is 4.86. Here's the dll.xml: C:\Users\Michelle\AppData\Roaming\Microsoft\FSX\dll.xml (I think that's what you want me to copy)

-I have another question. I have this: FSUIPC4_Loader.dll in my modules folder. Should that be in there?

Here's the FSUIPC4 install log (note: I'm no computer whizz so I don't know if this was successful.):

Installer for FSUIPC4.DLL version 4.86

Looking in registry for FSX install path:

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

Parameter"SetupPath"

Not there, so looking in:

HKEY_CURRENT_USER\FSX

Parameter"AppPath"

... >>> 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

... No previous valid version 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\Michelle\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\Chris\AppData\Roaming"

... No FSX.CFG there

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\Michelle\AppData\Roaming"

Found FSX.CFG in "C:\Users\Michelle\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.

(for FSUIPC4, without Loader)

... FSUIPC4 section of DLL.XML written okay

Now checking for a SimConnect.XML file ...

... No SimConnect.XML file found. This is okay.

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

... No FSX.CFG there

"Modules\FSUIPC Documents" folder created okay!

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

Installed "FSUIPC4 Offsets Status.pdf" okay

FSUIPC4.DLL signature failed: trying GlobalSign Root fix ...

Problem! The signature check fails on the installed FSUIPC4.DLL. (Error ref 800B0111)

Deleted GlobalSign Root fix program ... no longer relevant

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

All installer tasks completed.

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

Many thanks!

Edited April 20, 2013 by CalCoastFlightSim

[Pete Dowson]

Here's the dll.xml: C:\Users\Michelle\AppData\Roaming\Microsoft\FSX\dll.xml (I think that's what you want me to copy)

Yes, that's what I need to see, but you forgot to paste it into your message!

I have another question. I have this: FSUIPC4_Loader.dll in my modules folder. Should that be in there?

It is not installed by the installer program, only provided in the ZIP (in case of specific difficulties). You must have copied that in yourself. It isn't a good idea to do things like that without at least knowing why. It is all clearly explained in the very short Installation guide, provded for you to read BEFORE doing anything!

Anyway, it seems you placed the Loader into the Modules folder AFTER you ran the installer, as this shows:

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

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

(for FSUIPC4, without Loader)

So, although it is currently not doing anything, please remove the loader from the Modules folder to avoid future confusion and problems. Also, please do read the little bit of essential documentation provided. It won't take long, really!

It's a little odd that the installer found that there was no previous version of FSUIPC4 installed in FSX itself, yet there was an existing entry for FSUIPC4 in the DLL.XML file. How did that happen? Did you delete FSUIPC4 from a previous install?

Was there no FSUIPC4.LOG file in the Modules folder?

Regards

Pete

[CalCoastFlightSim]

How do I paste the dll.xml into this?

I did delete FSUIPC4 from my modules folder and ended up re-installing it if that's what you mean. I has a member of my VA take a look at y dll.xml and give me a new one if that's how the existing entry complication occured. I can find my old one and post it here if you want.

The log I gave is the only one in there.

[Pete Dowson]

How do I paste the dll.xml into this?

It's only another text file, like the Log you posted. Just load it into Natepad or whatever and copy and paste as I assume you did with the install log.

I did delete FSUIPC4 from my modules folder and ended up re-installing it if that's what you mean.

Ah, that would explain the discrepancy between the DLL.XML and your Modules folder contents.

I has a member of my VA take a look at y dll.xml and give me a new one if that's how the existing entry complication occured.

Probably he changed it to stop FSUIPC4 loading.

I can find my old one and post it here if you want.

It it worked, why not use it? If it doesn't then it maybe just as bad as the current one, so post whichever one that doesn't work for me to look at and fix.

The log I gave is the only one in there.

Good. Then the problem is very likely to be a bad DLL.XML rather than something more serious preventing the Add-Ons-FSUIPC menu being added desptite FSUIPC running.

An alternative to posting it here is to simply delete the existing one and re-run the installer, so that it makes a new one from scratch with only FSUIPC4 being loaded. This is okay if you have no other add-on DLLs being loaded. If you are not sure, don't do this -- the fact that you got a member of your VA to even look at it does imply there's something more you are using. It is often the other DLL installers which mess up the DLL.XML, not thinking that there might be others needing entries.

Regards

Pete

[CalCoastFlightSim]

First of all, thanks for your time Pete,

I had him look at it after I noticed FSUIPC stopped working btw.

My old version:

<?xml version="1.0" encoding="Windows-1252"?>

<SimBase.Document Type="Launch" version="1,0">

<Descr>Launch</Descr>

<Filename>dll.xml</Filename>

<Disabled>False</Disabled>

<Launch.ManualLoad>False</Launch.ManualLoad>

<Launch.Addon>

<Name>FsPassengersX</Name>

<Disabled>False</Disabled>

<Path>FsPassengers\bin\fspassengersx.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>Object Placement Tool</Name>

<Disabled>True</Disabled>

<ManualLoad>False</ManualLoad>

<Path>..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>Traffic Toolbox</Name>

<Disabled>True</Disabled>

<ManualLoad>False</ManualLoad>

<Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>Visual Effects Tool</Name>

<Disabled>True</Disabled>

<ManualLoad>False</ManualLoad>

<Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>A2A Feel</Name>

<Disabled>False</Disabled>

<Path>Modules\A2A_Feel.dll</Path>

<DllStartName>module_init</DllStartName>

<DllStopName>module_deinit</DllStopName>

</Launch.Addon>

<Launch.Addon>

<Name>AccuFeelMenu</Name>

<Disabled>False</Disabled>

<ManualLoad>False</ManualLoad>

<Path>Modules\AccuFeelMenu.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>FeelThere ERJX Helper</Name>

<Disabled>False</Disabled>

<Path>FeelThere\Erj\E145XH.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>FSUIPC 4</Name>

<Disabled>False</Disabled>

<Path>Modules\FSUIPC4.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>FSCopilot</Name>

<Disabled>False</Disabled>

<Path>Modules\FSCopilot.dll</Path>

</Launch.Addon>

</SimBase.Document>

[Pete Dowson]

My old version:

That looks okay. Certainly FSUIPC4 should load. If something then went wrong I'd need to see the normal Log or something else.

What about the one you are using now?

Note that the "old version" loads these other DLLs as well as FSUIPC4:

FsPassengersX

A2A Feel

AccuFeelMenu

FeelThere ERJX Helper

FSCopilot

BTW I seem vaguely to recall there was some conflict years ago between FSUIPC4 and FSCopilot. One thing to check is that the latter is up to date.

It might be good to make sure FSUIPC loads AFTER FSCopilit. That can be done by moving this section to then end, just before

</SimBase.Document>

<Launch.Addon>

<Name>FSUIPC 4</Name>

<Disabled>False</Disabled>

<Path>Modules\FSUIPC4.dll</Path>

</Launch.Addon>

regards

Pete

[CalCoastFlightSim]

Still doesn't work. :(

[Pete Dowson]

Still doesn't work. :(

What exactly are the symptoms? No Addons menu, or just no FSUIPC entry in it? Still no FSUIPC4 log?

Are all of the other DLL entries running and working? i.e.

FsPassengersX

A2A Feel

AccuFeelMenu

FeelThere ERJX Helper

FSCopilot

Try, temporarily, renaming that DLL.XML, so it is ignored, and re-run the FSUIPC4 installer. If that works then there's some sort of conflict with one of those other Add-ons.

If it still doesn't work, and/or those other add-ons don't load, then you have a problem with the SimConnect installation. That gets very complicated ...

Pete

[CalCoastFlightSim]

Yeah, just no fsuipc in the addon bar.

Alright I will try that. Thanks for your help Pete.

[CalCoastFlightSim]

I'm afraid it didn't work. The installer created a new dll.xml file after I renamed my other one and I looked in that and everything seems fine. I opened up FSX and FSUIPC wasn't there.

Install log:

Installer for FSUIPC4.DLL version 4.86

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.860 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\Michelle\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\Chris\AppData\Roaming"

... No FSX.CFG there

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\Michelle\AppData\Roaming"

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

Now checking DLL.XML ...

... No previous DLL.XML found, creating new one (for FSUIPC4 only).

Now checking for a SimConnect.XML file ...

... No SimConnect.XML file found. This is okay.

Looking in "C:\Users\Public\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

Installed "FSUIPC4 Offsets Status.pdf" okay

FSUIPC4.DLL signature failed: trying GlobalSign Root fix ...

Problem! The signature check fails on the installed FSUIPC4.DLL. (Error ref 800B0111)

Deleted GlobalSign Root fix program ... no longer relevant

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

All installer tasks completed.

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

[Pete Dowson]

I'm afraid it didn't work.

Ah! Sorry, I failed to notice this in the original Installer log you posted:

FSUIPC4.DLL signature failed: trying GlobalSign Root fix ...

Problem! The signature check fails on the installed FSUIPC4.DLL. (Error ref 800B0111)

FSUIPC will not run if it beleives itself to be corrupted, which is what it assumes if the signature doesn't check.

If you right click on the FSUIPC4.DLL itself, select Properties - Digital Signature, then select the Simflight signature and Details, it should say the signature is okay. if it doesn't then either it isn't a good copy, or, more likely, your Windows installation isn't running the required decryption and signature checking services. You aren't stopping some default Windows services running, are you?

Googling Windows error finds things like "Trust verification failed" and "The certificate was explicitly marked as untrusted by the user.".

The FAQ subforum contains a couple of threadsa which might help. see

One solution for "My signature check fails on the installed FSUIPC4.DLL. (Error 80092026)"

and

Help with FSUIPC4 code signature problem

Again, apologies for not noticing this error earlier.

Regards

Pete

[CalCoastFlightSim]

No, I don't beleive I'm stopping any Windows services from running.

Ok so I tried the first FAQ thread you listed above and the signature still says: "A certificate was explicitly revoked by its issuer."

When do I rename the temporarily changed dll.xml file back to "dll.xml"?

[CalCoastFlightSim]

Paul, you're my goddamn hero.

So the pronlem with my post above was that I made simflight a trusted publisher, but I forgot to make sure it wasn't listed as an untrusted publisher. There lay my problem.

I'm back up and running and it's all because of you. Cheers!

[Pete Dowson]

Paul, you're my goddamn hero.

Which Paul is that? Can you point me to the helpful answer?

Pete

[CalCoastFlightSim]

How embarassing!

My bad PETE. lol