FSUIPC error when trying to connect with PIREP Programs

[ross744]

Hi All,

I appear to be having trouble connecting FSUIPC with my PIREP programs for different VAs.

With FS Flight Keeper, I get the following error message: "Error: IPC timed out all retries" and with GCP (Globe Cargo PIREP), I get the following: "Unknown FSUIPC Connection Error".

This happens with FSUIPC V3.80.

Any suggestions?

Thanks in advance :)

Ross Spargo

[ross744]

I got it sorted, but only by reinstalling FS9 :(

[scanman24]

Hi there,

I am having some troubles with pireps with the VA that I fly with. Their pirep system is FSACARS - an older system. I recently reinstalled all of my FSX setups after the game began to crash, perhaps triggered by me installing FSX SP1 & SP2. Prior to these reinstallations, FSIUPC and FSACARS worked in synchronization perfectly. Now however, after I install both programmes, FSACARS fails, and shuts completely. I have raised this issue in my VA forums, and they suspect it is a FSUIPC problem. I am using FSUIPC 4, and have not registered it (ie, 'free' version). I guess what I'm asking is: Can anyone who has experienced this help me? Is there something that I am doing wrong?

I have been following installations instructions to every detail.

My specs are as follows:

Win Vista Home Premium 32bit, SP1 and SP2

FSX Deluxe w SP1 (SP2 may not have reinstalled).

I have removed, re-downloaded and re-installed FSUIPC and FSACARS a few times to try and combat this problem (to begin with a clean system, so to speak).

Thanks in advance,

scanman24

[scanman24]

Hi there,

My complete FSX setup crashed recently, and so I have had to remove and redownload/reinstall virtually all of my FSX related programs; including FSUIPC and FSACARS, which is the PIREP program that my VA uses. I have since encountered many problems, the most major of which being that FSUIPC and FSACARS cannot synchronize with each other, and so I cannot submit any PIREPS. When I am using FSX, FSUIPC doesn't appear as an Addon under the tab like it use to, and doesn't "function" so to speak. When I try to begin a flight log with FSACARS, it freezes, as does FSX, and shuts down completely. Those at my VA are sure that this is a FSUIPC related problem (sorry) and not FSACARS. I guess my question is...Am I doing something wrong? Are there limits to the use of FSUIPC?

I have FSX Deluxe SP1, and use Vista Home Premium 32bit SP1 and SP2. I have the non-registered version of FSUIPC4, FSACARS is freeware. I have tried installing and running both programs as an Administrator and a regular user.

Thanks in advance,

scanman24

[Pete Dowson]

When I am using FSX, FSUIPC doesn't appear as an Addon under the tab like it use to, and doesn't "function" so to speak.

Does it generate a Log file in the FSX Modules folder? If so, show it to me please. If not, please show me the Install log file instead, in the same place. If there's no run-time log file produced then FSUIPC isn't even being loaded, so it is probably a DLL.XML problem -- though it sounds like a SimConnect problem.

FSX does not take kindly to re-installation -- it often seems to make a complete mess of the SimConnect part. The problem stems, I think, form the fact that the SimConnect side-by-side library doesn't get completely uninstalled, and this stops the installer re-installing correctly. In general it is better, if reinstalling FSX, to start with reinstalling Windows from scratch.

Of all the problems I hear of in SimConnect, they almost all occur after attempted re-installation of FSX. It's not a good move without also reinstalling Windows, especially on Vista or Win7 where there seems to be no work-around to fix SimConnect. On WinXP it is easier -- one can delete some WinSxS folders and reinstall just the SimConnect parts without too many problems. That doesn't appear to work, even if you could do it (which is difficult) on Vista or Win7.

When I try to begin a flight log with FSACARS, it freezes, as does FSX, and shuts down completely

Even if there is a SimConnect problem causing FSUIPC not to be able to connect to FSX (and the Log, if any, will show that), there is really no excuse for a separate program, as I assume FSACARS is, to 'freeze'. That cannot be directly to do with FSX or FSUIPC but more of a poor programmed response to non-connection. It should simply report that it cannot connect.

Regards

Pete

[767_Captain]

Hello.  I see that this is an old thread but thought it best to post my issue here.  I am running P3Dv4 on a laptop and as a member of Globe Cargo I am running their PIREP application.  It constantly crashes as it attempts to put together a file on its schedule.  It does point to an issue with FSUIPC.  I am running version 6and it is the current version as of this date.  It is registered.  As it tries to save periodically, I get an error #9 indicating that the connection to FSUIPC is not open.  This is what is generated when it crashes:

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
FSUIPC.FSUIPCException: FSUIPC Error #9: FSUIPC_ERR_NOTOPEN. The connection to FSUIPC is not open.
   at FSUIPC.FSUIPCConnection.Process(String GroupName)
   at GlobeCargoPIREP.Form1.Calculate_Distance_Flown_GPS()
   at GlobeCargoPIREP.Form1.Timer_GetPositionData_Tick(Object sender, EventArgs e)
   at System.Windows.Forms.Timer.OnTick(EventArgs e)
   at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9310.0 built by: NET481REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
Globe Cargo PIREP
    Assembly Version: 1.0.8376.30423
    Win32 Version: 
    CodeBase: file:///D:/Globe%20Cargo%20Virtual%20Airlines/Globe%20Cargo%20PIREP/Globe%20Cargo%20PIREP.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9256.0 built by: NET481REL1LAST_B
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9310.0 built by: NET481REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9032.0 built by: NET481REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9032.0 built by: NET481REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9297.0 built by: NET481REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9032.0 built by: NET481REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Accessibility
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.9032.0 built by: NET481REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
SandDock
    Assembly Version: 3.0.6.1
    Win32 Version: 3.0.6.1
    CodeBase: file:///D:/Globe%20Cargo%20Virtual%20Airlines/Globe%20Cargo%20PIREP/SandDock.DLL
----------------------------------------
AMS.Profile
    Assembly Version: 2.0.3181.20715
    Win32 Version: 2.0.3181.20715
    CodeBase: file:///D:/Globe%20Cargo%20Virtual%20Airlines/Globe%20Cargo%20PIREP/AMS.Profile.DLL
----------------------------------------
FSUIPCClient
    Assembly Version: 1.1.2397.13
    Win32 Version: 1.1.2397.13
    CodeBase: file:///D:/Globe%20Cargo%20Virtual%20Airlines/Globe%20Cargo%20PIREP/FSUIPCClient.DLL
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

I hope this is helpful.  Let me know if there is anything else I can provide.

Cheers,

David Rosenblum

Captain, Boeing 747-400 (Retired)

Atlas Air

[John Dowson]

13 hours ago, 767_Captain said:

I am running P3Dv4 on a laptop and as a member of Globe Cargo I am running their PIREP application.  It constantly crashes as it attempts to put together a file on its schedule. 

Then why not contact support for the PIREP application? The ecceptions/errors you posted are from that application, not FSUIPC - that doesn't mean anything top me.

13 hours ago, 767_Captain said:

It does point to an issue with FSUIPC.  I am running version 6and it is the current version as of this date.  It is registered.  As it tries to save periodically, I get an error #9 indicating that the connection to FSUIPC is not open.  This is what is generated when it crashes:

It does look like this program has an issue connecting to FSUIPC, but it should handle that gracefully an not crash. This is an issue for the app developers, not FSUIPC.

Note that the usual reasons for a third-party FSUIPC not being able to connect are:
   - the application is being ran at a different privilege level to FSUIPC. FSUIPC and all connecting programs must be ran at the same level.
   - firewall or antivurus software blocking the connection
   - not having an aircraft loaded and ready-to-fly

You can post / attach your FSUIPC6.log file here if you like and I can check that for errors, but you should really contact the support of the app  developers.

John

[767_Captain]

John, first, thank you for replying.  Yes, I understood that the issue was probably with GCP and not necessarily with FSUIPC.  I have reached out to them several times with this problem and for various reasons, not the least of which I suspect is that they are active professional pilots doing this as a hobby, they have been slow to respond and address it.  As you are the creator of FSUIPC and implicitly the expert on its idiosyncrasies I thought it prudent to at least reach out to you to see if you had a suggestion.  And when I was able to dialog with them they did in fact suggest that I contact you to see if you had any ideas to try.

I am running both P3D and GCP with administrator privileges.  Here is my FSUIPC6.log file.  Please let me know if anything jumps out as being not right and thank you again.

Cheers,

David

FSUIPC6.log

[John Dowson]

35 minutes ago, 767_Captain said:

I am running both P3D and GCP with administrator privileges. 

Double check this and maybe also try running with standard privileges to see if that helps. As I said, the main reason for 3rd-party connection issues IS the privilege level.

37 minutes ago, 767_Captain said:

Here is my FSUIPC6.log file.  Please let me know if anything jumps out as being not right and thank you again.

Nothing related to your issue. You do have a lot of USB device reconnection messages, which are strange, This could indicate either a USB power or connection issue unless you are disconnecting and reconnecting your Yawman Arrow.

John

[767_Captain]

Hmm... John, thank you.  I connect the Arrow to the USB port and an iPad to a USB-C port.  Running Duet on the PC and iPad I put Navigraph Charts on the iPad.  So it could be a power issue with either of those connections?  I will run this by the developers of GCP as well.  And I wonder if running a powered hub might address this?

Cheers,

David

[John Dowson]

6 minutes ago, 767_Captain said:

I connect the Arrow to the USB port and an iPad to a USB-C port.  Running Duet on the PC and iPad I put Navigraph Charts on the iPad.  So it could be a power issue with either of those connections?  I will run this by the developers of GCP as well.

If these reconnects are not causing any issues, it is nothing to worry about, just an observation from your log.

7 minutes ago, 767_Captain said:

And I wonder if running a powered hub might address this?

Properly powered hubs are generally always better/more reliable than unpowered hubs, but it really depends on the devices you are using.
If the disconnect/reconnect messages are just due to the iPad losing its connection/reconnecting, then this is nothing to worry about anyway as FSUIPC does nothing with that - it is just re-acting to a windows 'new HID device connected' message.

John