Jump to content
The simFlight Network Forums

Problem with WideFs


ducaud
 Share

Recommended Posts

I have been using FSUIPC V 3,98a and WideFS 6.78 with my FS2004 running on a Windows 7 64 bit machine.

I use the WideFS utility to connect to FS Commander V8.6 , to see the rolling map and the AI planes. I never had problems with connection before.

Lately I have noticed that after a while of running fine, My plane icon and the Ai planes stop moving on the FS Commander screen, and I see that the Wide FS says "waiting to connect" then when it does I get a connection error #14 message on FSCommeander. Volker told me that it was a WideFS connection issue and not related to his software.

I also found a WideServer log file on the FS9/Modules folder which shows some disconnections , I am adding the text at the end of this message.

I appreciate if somebody can help me sort this out.

Thanks

Juan

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

Blocksize guide = 4096 (double allowed)

Date (dmy): 25/09/10, Time 15:39:17.141: Server name is DUCAUD-PC

117750 Initialising TCP/IP server

117750 Initialising IPX/SPX server

117750 IPX/SPX socket() failed [Error=10044] Socket type not supported

117750 Failed to start IPX/SPX Server

117750 Initialising UDP/IP server

118842 Broadcasting service every 1000 mSecs

120371 Incoming connection Accepted ok (skt=2620) TCP

120651 Connected to computer "JGD-VAIO" running WideClient version 6.780 (skt=2620) TCP

3495483 Client socket unused for too long: removing (skt=2620) TCP

12601075 Incoming connection Accepted ok (skt=2620) TCP

12601340 Connected to computer "JGD-VAIO" running WideClient version 6.780 (skt=2620) TCP

12637095 Error 10053: client socket disconnected at Client: removing (skt=2620) TCP

12696095 Incoming connection Accepted ok (skt=11720) TCP

12696407 Connected to computer "JGD-VAIO" running WideClient version 6.780 (skt=11720) TCP

14573052 Retried 21 times: sends blocked for over 5 secs! (0 of 920 sent), Error=10035 (skt=11720) TCP

14578060 Retried 19 times: sends blocked for over 5 secs! (0 of 925 sent), Error=10035 (skt=11720) TCP

14583036 Error 10035: sends blocked for too long! Removing client (skt=11720) TCP

14603254 Incoming connection Accepted ok (skt=12748) TCP

14603566 Connected to computer "JGD-VAIO" running WideClient version 6.780 (skt=12748) TCP

14622707 Retried 21 times: sends blocked for over 5 secs! (0 of 113 sent), Error=10035 (skt=12748) TCP

14624220 Incoming connection Accepted ok (skt=12752) TCP

14624486 Connected to computer "JGD-VAIO" running WideClient version 6.780 (skt=12752) TCP

14627949 Retried 20 times: sends blocked for over 5 secs! (0 of 121 sent), Error=10035 (skt=12748) TCP

14632660 Error 10035: sends blocked for too long! Removing client (skt=12748) TCP

14642769 Retried 20 times: sends blocked for over 5 secs! (0 of 134 sent), Error=10035 (skt=12752) TCP

14648011 Retried 20 times: sends blocked for over 5 secs! (0 of 150 sent), Error=10035 (skt=12752) TCP

14652987 Error 10035: sends blocked for too long! Removing client (skt=12752) TCP

14714264 Incoming connection Accepted ok (skt=11720) TCP

14714342 Connected to computer "JGD-VAIO" running WideClient version 6.780 (skt=11720) TCP

14784387 Client socket unused for too long: removing (skt=11720) TCP

14825243 Incoming connection Accepted ok (skt=12748) TCP

14825368 Connected to computer "JGD-VAIO" running WideClient version 6.780 (skt=12748) TCP

14884960 Client socket unused for too long: removing (skt=12748) TCP

14935255 Incoming connection Accepted ok (skt=12748) TCP

14935349 Connected to computer "JGD-VAIO" running WideClient version 6.780 (skt=12748) TCP

15005799 Client socket unused for too long: removing (skt=12748) TCP

15032257 Incoming connection Accepted ok (skt=12788) TCP

15032537 Connected to computer "JGD-VAIO" running WideClient version 6.780 (skt=12788) TCP

15106201 Client socket unused for too long: removing (skt=12788) TCP

15141301 Incoming connection Accepted ok (skt=12788) TCP

15141410 Connected to computer "JGD-VAIO" running WideClient version 6.780 (skt=12788) TCP

15162252 Incoming connection Accepted ok (skt=12744) TCP

15162330 Connected to computer "JGD-VAIO" running WideClient version 6.780 (skt=12744) TCP

15186495 Client socket unused for too long: removing (skt=12788) TCP

15206697 Client socket unused for too long: removing (skt=12744) TCP

15250284 Incoming connection Accepted ok (skt=12756) TCP

15250580 Connected to computer "JGD-VAIO" running WideClient version 6.780 (skt=12756) TCP

15271266 Incoming connection Accepted ok (skt=12748) TCP

15271484 Connected to computer "JGD-VAIO" running WideClient version 6.780 (skt=12748) TCP

15307052 Client socket unused for too long: removing (skt=12756) TCP

15322247 Incoming connection Accepted ok (skt=12788) TCP

15322325 Connected to computer "JGD-VAIO" running WideClient version 6.780 (skt=12788) TCP

15327208 Client socket unused for too long: removing (skt=12748) TCP

17340557 Error 10053: client socket disconnected at Client: removing (skt=12788) TCP

17668564 Close signalled to clients

17669672 Closing down now ...

Memory managed: Offset records: 314 alloc, 314 free

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

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

Throughput maximum achieved: 53 frames/sec, 8370 bytes/sec

Throughput average achieved for complete session: 3 frames/sec, 485 bytes/sec

Average receive rate from "JGD-VAIO": 0 frames/sec, 16 bytes/sec

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

Link to comment
Share on other sites

I also found a WideServer log file on the FS9/Modules folder which shows some disconnections , I am adding the text at the end of this message.

I appreciate if somebody can help me sort this out.

Yes, you certainly have some serious connection problems. The data is blocking up as shown by these errors:

14573052 Retried 21 times: sends blocked for over 5 secs! (0 of 920 sent), Error=10035 (skt=11720) TCP

14578060 Retried 19 times: sends blocked for over 5 secs! (0 of 925 sent), Error=10035 (skt=11720) TCP

14583036 Error 10035: sends blocked for too long! Removing client (skt=11720) TCP

14622707 Retried 21 times: sends blocked for over 5 secs! (0 of 113 sent), Error=10035 (skt=12748) TCP

14627949 Retried 20 times: sends blocked for over 5 secs! (0 of 121 sent), Error=10035 (skt=12748) TCP

14632660 Error 10035: sends blocked for too long! Removing client (skt=12748) TCP

14642769 Retried 20 times: sends blocked for over 5 secs! (0 of 134 sent), Error=10035 (skt=12752) TCP

14648011 Retried 20 times: sends blocked for over 5 secs! (0 of 150 sent), Error=10035 (skt=12752) TCP

14652987 Error 10035: sends blocked for too long! Removing client (skt=12752) TCP

However, the WideServer log is only half of the story. Maybe the Wideclient log will show something more helpful? You always need to look at both ends of the connection, not just one.

Last time I saw errors of this type I found I had a failing Network Adapter. Replacing it fixed it. Another possible cause is real memory becoming overfilled on either PC, such that the TCP/IP driver in Windows cannot get enough buffer space. Maybe something you are running has a memory leak?

Pete

Link to comment
Share on other sites

Hello Pete, thanks for your reply, here is text of the Wideclient log file.

I believe you are correct when you mention the possibility of a memory leak. In a couple of occasions I have got a message in FS9 telling me that I have run out of available memory and it takes me out of the program. How can I find out what is causing it ?

Thanks

Juan

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

Date (dmy): 26/09/10, Time 13:58:54.268: Client name is JGD-VAIO

1779 Attempting to connect now

1950 Server = DUCAUD-PC

2262 Trying TCP/IP host "DUCAUD-PC" port 8002 ...

2262Okay, IP Address = 192.168.1.103

2262 Connection made okay!

9953 New Client Application: "FSC" (Id=2468)

3770326 Timed out response: connection assumed lost!

3770342 Ready to try connection again

3770435 Timed out response: connection assumed lost!

3772385 Attempting to connect now

3773399 Trying to locate server: Need details from Server Broadcast

3779140 Server = DUCAUD-PC

3779452 Trying TCP/IP host "DUCAUD-PC" port 8002 ...

3779452Okay, IP Address = 192.168.1.103

3779452 Connection made okay!

5978552 Timed out response: connection assumed lost!

5978552 Ready to try connection again

5978614 Timed out response: connection assumed lost!

5980611 Attempting to connect now

5981406 Server = DUCAUD-PC

5981718 Trying TCP/IP host "DUCAUD-PC" port 8002 ...

5981718Okay, IP Address = 192.168.1.103

5981718 Connection made okay!

6066801 ****** End of session performance summary ******

6066801 Total time connected = 6050 seconds

6066801 Reception maximum: 66 frames/sec, 5961 bytes/sec

6066801 Reception average whilst connected: 42 frames/sec, 316 bytes/sec

6066801 Transmission maximum: 8 frames/sec, 222 bytes/sec

6066801 Transmission average whilst connected: 0 frames/sec, 18 bytes/sec

6066801 Max receive buffer = 5323, Max send depth = 2, Send frames lost = 1

6066801 **************** Individual client application activity ****************

6066801 Client 2468 requests: 192269 (Ave 31/sec), Data: 33215063 bytes (5490/sec), Average 172 bytes/Process

6066801 ********* Log file closed (Buffers: MaxUsed 5, Alloc 442939 Freed 442938 Refused 0) *********

Link to comment
Share on other sites

Hello Pete, thanks for your reply, here is text of the Wideclient log file.

Okaythat seems to confirm that the problem is at the Server end. And the fact that it takes a while to bog down indicates either a memory leak, as suggested, or a hardware problem being caused by heat or something which gets worse with time like that.

I believe you are correct when you mention the possibility of a memory leak. In a couple of occasions I have got a message in FS9 telling me that I have run out of available memory and it takes me out of the program. How can I find out what is causing it ?

The only way I ever found was by a process of elimination. Stop every add-on on the same PC, only use default aircraft. If it then runs okay, add things back one at a time. If it doesn't, then it's probably to do with scenery. Fly somewhere else or eliminate add-on scenery (make a safe copy of your SCENERY.CFG file and remove all of the entries past the default stuff. If that fixes it, add half back. If it is still okay, half the rest, etc, else take half of what you added back offetc. Eventually you find the one entry causing the problem).

The only time this process of elimination fails is when there's more than one thing causing it. Then you are in a bit of a mess, unfortunately.

If the problem only started happening recently, work out what you've added, recently, and start with those additions. It might speed things up.

Regards

Pete

Link to comment
Share on other sites

I have the same problem the WideFS has worked great for many years now suddenly it does not recognise the server, and creates a bogus IP address - I have loaded everything again and it continues to do this

It is NOT WideFS creating a "bogus address"!! The address is usually the Internet address of your ISP, or related to it, and when Windows supplies this to WideClient it is always a result of a wrong setting in your Router. If you cannot set your router up to work correctly then just override it by giving the explicit IP address in the INI file, as documented!

Pete

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

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