Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Dear sir

I bought WideFS yesterday I wanted to use it on a program named PLAN-G that is a moving map on the second monitor.

When I open the wideclient on the client monitor I am getting 2 massages 1. The squawbox was unable to start because FSUIPC could not be initialized. 2. Autower 2.0 has been trying to connect the FSUIPC for some time now…

And when I try to connect the Plan- G – that why I bought the program the first place - I am getting the massage unable to connect to fs check if you have FSUIPC

********* WideClient Log [version 6.78] Class=FS98MAIN *********

Date (dmy): 24/08/10, Time 08:49:26.062: Client name is YAKOV2

640 Attempting to connect now

781 Server = YAKOV

890 Trying TCP/IP host "YAKOV" port 8002 ...

890Okay, IP Address = 10.0.0.1

890 Connection made okay!

1056812 Error on client post-Connection Select() [Error=10053] Software caused connection abort

1056812 Connection closed by server!

1056812 The connection was terminated due to a time-out or other failure!

1056812 Attempting to connect now

1057359 Server = YAKOV

1057406 Trying TCP/IP host "YAKOV" port 8002 ...

1057406Okay, IP Address = 10.0.0.3

1057422 Connection made okay!

1397297 New Client Application: "Plan-G" (Id=1868)

1517484 Error on client post-Connection Select() [Error=10053] Software caused connection abort

1517484 Connection closed by server!

1517484 The connection was terminated due to a time-out or other failure!

1517500 Attempting to connect now

1518500 Trying to locate server: Need details from Server Broadcast

1529531 Giving up server, looking for another!

1530281 Trying TCP/IP host "YAKO 1530265 Server = YAKOV

V" port 8002 ...

1530281Okay, IP Address = 10.0.0.3

1530297 Connection made okay!

Posted

781 Server = YAKOV

890 Trying TCP/IP host "YAKOV" port 8002 ...

890Okay, IP Address = 10.0.0.1

890 Connection made okay!

1056812 Error on client post-Connection Select() [Error=10053] Software caused connection abort

1056812 Connection closed by server!

1056812 The connection was terminated due to a time-out or other failure!

...

Seems it was quite happily connected for 1056 seconds (nearly 18 minutes!), but then:

1057359 Server = YAKOV

1057406 Trying TCP/IP host "YAKOV" port 8002 ...

1057406Okay, IP Address = 10.0.0.3

1057422 Connection made okay!

What's going on there? Your server PC, "YAKOV" changed from IP Address 10.0.0.1 to 10.0.0.3?!

There's something evidently wrong with your network setup. If your PCs randomly change IP addresses nothing can stay connected!

That connection lasted for a while, allowing PLAN-G to connect:

1397297 New Client Application: "Plan-G" (Id=1868)

but, again, and after 460 seconds (nearly 8 minutes this time):

1517484 Error on client post-Connection Select() [Error=10053] Software caused connection abort

1517484 Connection closed by server!

1517484 The connection was terminated due to a time-out or other failure!

1517500 Attempting to connect now

1518500 Trying to locate server: Need details from Server Broadcast

1529531 Giving up server, looking for another!

1530265 Server = YAKOV

1530281 Trying TCP/IP host "YAKOV" port 8002 ...

1530281Okay, IP Address = 10.0.0.3

the 10.0.0.3 reconnection failed and re-connected.

So, something very odd is going on at the Server end. Unfortunately you have not shown the WideServer.LOG corresponding to this client log -- all connections have TWO (2) ends, you see? Either end could have a problem.

Maybe it's a firewall? Have you disabled your firewalls, or at least allowed WideClient and FS through? Do your PCs see each other in Explorer?

Also show me the FSUIPC Log file please. Close FS and WideClient down BEFORE grabbing any logs, else the files won't be complete. Also please always state version numbers -- you don't even say if it is FS9 or FSX or CFS1 or what.

Regards

Pete

Posted

You are the man

Thanks for the quick answer

I see hope arising

Sorry I firstly using FS9

********* WideServer.DLL Log [version 6.78] *********

Blocksize guide = 4096 (double allowed)

Date (dmy): 24/08/10, Time 11:27:05.140: Server name is YAKOV

186547 Initialising TCP/IP server

186563 Initialising IPX/SPX server

186563 ServerNode=0.0.9216.8221.65248

186563 Initialising UDP/IP server

188266 Broadcasting service every 1000 mSecs

193141 Incoming connection Accepted ok (skt=6544) TCP

193407 Connected to computer "YAKOV2" running WideClient version 6.780 (skt=6544) TCP

4239578 Close signalled to clients

4240766 Closing down now ...

Memory managed: Offset records: 3032 alloc, 3032 free

Read buffer usage: 1839 alloc, 1839 free, max in session: 1

Write buffer usage: 141313 alloc, 141313 free, max in session: 1

Throughput maximum achieved: 64 frames/sec, 256081 bytes/sec

Throughput average achieved for complete session: 15 frames/sec, 42586 bytes/sec

Average receive rate from "YAKOV2": 0 frames/sec, 18 bytes/sec

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

********* FSUIPC, Version 3.90 by Pete Dowson *********

Running on Windows Version 5.1 Build 2600 Service Pack 2

Verifying Certificate for "C:\Program Files\Microsoft Games\Flight Simulator 9\MODULES\FSUIPC.dll" now ...

SUCCESS! Signature verifies okay!

Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL)

User Name="Yakov Kraus"

User Addr="yakovkraus@walla.com"

FSUIPC Key is provided

WideFS Key is provided

Module base=61000000

ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E

WeatherOptions(Orig)=4000B6A7[4000B6A7]

InitDelay: 0 seconds

WeatherReadInterval=4

LogOptions=00000001

DebugStatus=255

26687 System time = 12:43:27

26703 C:\Program Files\Microsoft Games\Flight Simulator 9\

26719 System time = 12:43:27, FS2004 time = 12:00:00 (00:00Z)

48672 FLIGHTS\OTHER\FLTSIM.flt

48781 AIRCRAFT\c172\Cessna172SP.air

49359 Aircraft="Cessna Skyhawk 172SP"

62359 \\YAKOV\Flight Simulator Files\UI generated flight.flt

62766 Clear All Weather requested: external weather discarded

82594 Advanced Weather Interface Enabled

5293359 System time = 14:11:14, FS2004 time = 14:10:03 (21:10Z)

5293375 *** FSUIPC log file being closed

Memory managed: 30 Allocs, 136351 Freed

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

Posted

********* WideServer.DLL Log [version 6.78] *********

193407 Connected to computer "YAKOV2" running WideClient version 6.780 (skt=6544) TCP

4239578 Close signalled to clients

4240766 Closing down now ...

Memory managed: Offset records: 3032 alloc, 3032 free

Read buffer usage: 1839 alloc, 1839 free, max in session: 1

Write buffer usage: 141313 alloc, 141313 free, max in session: 1

Throughput maximum achieved: 64 frames/sec, 256081 bytes/sec

Throughput average achieved for complete session: 15 frames/sec, 42586 bytes/sec

Average receive rate from "YAKOV2": 0 frames/sec, 18 bytes/sec

Well that looks okay. 64 frames per second is a little high -- don't you set an upper frame rate in FS9?

I don't think there's anything wrong with either the Server or the Client ends. The problem is your Registration for WideFS. You purchased this in 2010 but you are still using an old version of FSUIPC for which new Registrations simply are not valid.

Look:

********* FSUIPC, Version 3.90 by Pete Dowson *********

Version 3.90 is now 18 months old and has not been supported for 16 of those! Please review the list of supported versions in the Announcements. The oldest valid version is 3.98.

Regards

Pete

Posted
Pete I lived happily with the my version

You might, but you don't get any support if you don't keep up to date.

Anyway what should I do?

Download and install 3.98, of course! Then even possibly, optionally, get the very latest, 3.989 from the Updates announcement.

Pete

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.