FAILED TO CONNECT FSUIPC

[RF-ODY]

help because I am with an error in FSUIPC.

Information of the error: IPC request contains bad data

[Pete Dowson]

help because I am with an error in FSUIPC.

Information of the error: IPC request contains bad data

That isn't an error from FSUIPC but an error reported by your application program. You don't even say what version of FS or FSUIPC you are using, nor whether you Registered FSUIPC or not!

The information needed will be in a complete FSUIPC log. Please run it again, then close FS down, and show me the FSUIPC Log file from the FS Modules folder.

Pete

[RF-ODY]

Then the record that has to be done, for the proper functioning.

AND HOW MADE THAT RECORD?

[Pete Dowson]

Then the record that has to be done, for the proper functioning.

AND HOW MADE THAT RECORD?

Sorry, I don't understand what you mean.

To find out why you are getting that error I need to see the FSUIPC.LOG file, which you will find in the FS Modules folder after running and closing FS. Please go and look. You can put the contents of that file in a message here. It is an ordinary text file.

Pete

[RF-ODY]

1.:After install and click the addons to run FSUIPC this message appears:

code signature does not verify! Please check that the cryptographic services are running, or try applying the supplied globalsign root fix. You'll then need to restart fs.

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

2.:ok,....its this:

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

Installer for FSUIPC4.DLL version 4.20

Looking in registry for FSX install path:

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

Parameter"SetupPath"

SetupPath="C:\Arquivos de programas\Microsoft Games\Microsoft Flight Simulator X\"

Checking version of FSX.EXE:

... Version 10.0.61472.0 (Need at least 10.0.60905.0)

Checking compatibility with installed SimConnect:

... Okay, Probe Manifest matches installed SimConnect 60905 (Original)

Found later build SimConnect 61242 (SP1 May07)

Found later build SimConnect 61259 (Acc/SP2 Oct07)

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

C:\Arquivos de programas\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL

... No previous valid version found.

FSX Modules folder already exists.

Okay -- installed FSUIPC4 into "C:\Arquivos de programas\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL"

Looking for the current user's Application Data path:

... found as "C:\Documents and Settings\user\Dados de aplicativos"

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

Looking in "C:\Documents and Settings\All Users\Dados de aplicativos"

No FSX.CFG there

Looking in "C:\Documents and Settings\Default User\Dados de aplicativos"

No FSX.CFG there

Looking in "C:\Documents and Settings\LocalService\Dados de aplicativos"

No FSX.CFG there

Looking in "C:\Documents and Settings\NetworkService\Dados de aplicativos"

No FSX.CFG there

Looking in "C:\Documents and Settings\user\Dados de aplicativos"

Found FSX.CFG in "C:\Documents and Settings\user\Dados de aplicativos\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.

Now installing additional files into the Modules 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

All installer tasks completed okay!

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

3.: new log create after install:

********* FSUIPC4, Version 4.20 by Pete Dowson *********

User Name=""

User Addr=""

FSUIPC4 not user registered

WIDEFS7 not user registered, or expired

FSUIPC4.DLL signature does not verify: running in failed mode!

... if the DLL has not been tampered with, then either the Cryptographic

Services in Windows are broken, or you need to run the Globalsign fix supplied.

Running inside FSX (SimConnect Acc/SP2 Oct07)

Module base=61000000

DebugStatus=0

359 System time = 13:54:56

359 FLT UNC path = "C:\Documents and Settings\user\Meus documentos\Flight Simulator X Files\"

375 FS UNC path = "C:\Arquivos de programas\Microsoft Games\Microsoft Flight Simulator X\"

1734 LogOptions=00000001

1765 SimConnect_Open succeeded: waiting to check version okay

14312 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0)

14312 Initialising SimConnect data requests now

14312 FSUIPC Menu entry added

14562 C:\Documents and Settings\user\Meus documentos\Flight Simulator X Files\SBGR-RNW.FLT

14562 C:\Arquivos de programas\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\B737_800\Boeing737-800.AIR

91593 System time = 13:56:27, FSX time = 13:55:11 (16:55Z)

92093 Advanced Weather Interface Enabled

[Log closed by user request, and continued in new file]

531734 System time = 14:03:47, FSX time = 13:55:15 (16:55Z)

531734 *** FSUIPC log file being closed

Average frame rate for running time of 4 secs = 10.4 fps

Memory managed: 6 Allocs, 5 Freed

********* FSUIPC Log file closed *** *******

[Pete Dowson]

After install and click the addons to run FSUIPC this message appears:

code signature does not verify! Please check that the cryptographic services are running, or try applying the supplied globalsign root fix. You'll then need to restart fs.

Aha! Another case of signature problems, interestingly also with an non-English version of Windows?

Please check this thread and follow the same course of action:

viewtopic.php?f=54&t=67502

Let's keep to one thread about this. It is quite a puzzle as after well over a year of FSX and FSUIPC4 this is only the second case of such a problem. Please use FSUIPC 4.211 (from the FSX Downloads Announcement) and perform the same steps as detailed towards the end of that thread.

Regards

Pete