November 4, 200619 yr Hey all!I'm currently helping my father to set up his Flight Simulator 2004. I did not succeed regarding the discussion to buy a new computer (although he is an airline pilot and earns enough money - my opinion), so I have to install things like AS to another computer.My father was already using FSUIPC, I updated it to be 3.7.0.9 and installed widefs 6.7 according to the corresponding thread (WideFS / ASv6 - HOW TO) in this forum. Everything works fine, widefs gets connected and FS shows "1 Client connected", but AS 6.5 message is still "FS disconnected" in the title bar and "FS is not yet connected..." in the lower left corner.I've shared the "c$"-share of the FS computer to be Drive X: on the Widefs Client and vice versa, both share and NTFS settings are read/write (it is the same user in the NT domain).Now, when I've spend around 8 hours installing, deinstalling, updating, reinstalling and so on I'll give up. Can you please give me a hint which information you'll need to be able to help me out?Thanks in advance,Richard
November 4, 200619 yr Commercial Member Hi Richard,This indicates that AS is not receiving information from FSUIPC/WideFS interface. My best guess is that there are registration issues. A quick look at the wideclient and wideserver.log files should easily reveal the problem.Best, Damian ClarkHiFi Simulation Technologies
November 4, 200619 yr Hi Damian,thanks for your answer. As I couldn't find any hints in the widefs logs I'll post them here, hopefully is that okay with the board rules (did not read them very... ehhmm, extensive).Okay, here are the logs. The timeout errors on the client side are due to my used starting order: 1. wideclient (using Run1=... to start ASV), then starting FS. But what the #### are those errors: "88036 Block sequence error: expected 2 but received 1"?Thanks again for your help,Richard********* WideServer.DLL Log [version 6.70] *********Blocksize guide = 4096 (double allowed)Date (dmy): 04/11/06, Time 12:36:57.518: Server name is SCULLY 31000 Initialising TCP/IP server 31000 Initialising IPX/SPX server 31000 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family 31000 Failed to start IPX/SPX Server 31000 Initialising UDP/IP server 32109 Broadcasting service every 1000 mSecs 32109 Preferred protocol = UDP********* WideClient Log [version 6.70] Class=FS98MAIN *********Date (dmy): 04/11/06, Time 12:36:07.943: Client name is MULDER 1832 C:ActiveSkyModulesASv6 1832 C:ActiveSkyModulesASv6ASv6.exe 1882 Attempting to connect now 1962 Trying UDP/IP host "scully" port 8002 ... 1962 ... Okay, IP Address = 192.168.0.25 1972 UDP connectionless mode set up okay! 2133 New Client Application: "ASv6" (Id=904) 38164 Timed out response: connection assumed lost! 38174 Ready to try connection again 38235 Timed out response: connection assumed lost! 39246 Attempting to connect now 39246 UDP connectionless mode set up okay! 57512 Timed out response: connection assumed lost! 57522 Ready to try connection again 57582 Timed out response: connection assumed lost! 58564 Attempting to connect now 58564 UDP connectionless mode set up okay! 76870 Timed out response: connection assumed lost! 76880 Ready to try connection again 76930 Timed out response: connection assumed lost! 77882 Attempting to connect now 77892 Trying UDP/IP host "scully" port 8002 ... 77892 ... Okay, IP Address = 192.168.0.25 77892 UDP connectionless mode set up okay! 86644 Connection made: receiving okay! 88036 Block sequence error: expected 2 but received 1 90339 Block sequence error: expected 3 but received 2 92422 Block sequence error: expected 4 but received 3 95597 Block sequence error: expected 5 but received 4 96699 Block sequence error: expected 6 but received 5 97680 Block sequence error: expected 7 but received 6 98812 Block sequence error: expected 8 but received 7 101966 Block sequence error: expected 9 but received 8 103088 Block sequence error: expected 10 but received 9 104079 Block sequence error: expected 11 but received 10 105191 Block sequence error: expected 12 but received 11 108325 Block sequence error: expected 13 but received 12 109437 Block sequence error: expected 14 but received 13 110448 Block sequence error: expected 15 but received 14 111540 Block sequence error: expected 16 but received 15 114684 Block sequence error: expected 17 but received 16 115756 Block sequence error: expected 18 but received 17 116777 Block sequence error: expected 19 but received 18 117879 Block sequence error: expected 20 but received 19 121054 Block sequence error: expected 21 but received 20 122175 Block sequence error: expected 22 but received 21 123167 Block sequence error: expected 23 but received 22 124268 Block sequence error: expected 24 but received 23
November 4, 200619 yr Hey all,just tried to TCP again instead of UDP, and the block sequence errors are gone:The new logs read (shortend):********* WideServer.DLL Log [version 6.70] *********Blocksize guide = 4096 (double allowed) 27391 Initialising UDP/IP server 27484 Incoming connection Accepted ok (skt=2772) TCP 27750 Connected to computer "MULDER" running WideClient version 6.700 (skt=2772) TCP 28078 Broadcasting service every 1000 mSecs 28078 Preferred protocol = TCP********* WideClient Log [version 6.70] Class=FS98MAIN ********* 2114 New Client Application: "ASv6" (Id=2104) 3896 Attempting to connect now 38516 Connection made okay!^^ The protocol finished here. There is no more info. What to do now so ASV will find FS?
November 4, 200619 yr Commercial Member Hi,Assuming the networking issues are all resolved, we then need to look at the FSUIPC log file and see what it says. Enabling logging options for read and write should show specifically what info AS is requesting and/or setting and will verify registration is proper. Please enable logging as such after FS loaded then start AS, wait about 30 seconds then stop logging then post that FSUIPC.log file here. Thanks! Damian ClarkHiFi Simulation Technologies
November 5, 200619 yr Hi Damian,thanks for your assistance! Following is the log file, and as you expected there is an error indeed.********* FSUIPC, Version 3.709 by Pete Dowson *********Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL)User Name="Richard Ohl"User Addr="[email protected]"FSUIPC Key is providedWideFS Key is provided[Continuation log requested by user]Module base=61000000ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5EWeatherOptions(Orig)=C800372D[C800372D]InitDelay: 0 secondsWeatherReadInterval=4LogOptions=0000000D 27847515 System time = 02:26:49, FS2004 time = 06:57:39 (05:57Z) 27847515 LogOptions changed, now 0000000D (LogExtras=0) [strong]27870640 WRITEex(failed, read-only!) 330A, 2 bytes: 00 00 [/strong] 27955437 LogOptions changed, now 00000001 (LogExtras=0)So I think the error is not really in ASV, sorry! To check I just tried to move the installation of Flight Sim Commander to the WideFs Client - and he neither worked... What to do now, do you have any idea?Thanks a lot in advance,Richard
November 6, 200619 yr Hi, if I read this right, TCP works but UDP doesn't? Asuming WinXP on the FS server, when you opened the firewall port, 8002, did you choose TCP/IP or UDP? Any other firewall software running on either PC? ZoneAlarm, etc?Also, the WideFS.ini should ProtocolPrefered=UDP and the WideClient.ini should be Protocol=UDP. Also, make sure you can ping both boxes by machine-name without any packet-loss.The blocked content lines looks like a network problem whereby it's good enough for an initial connection but not enough to sustain heavy network traffic. Off the top-of-my-head, it looks like a network configuration or hardware issue. Regards, Al Jordan | KCAE
November 7, 200619 yr Commercial Member Hi,Al I think is right, there is a network configuration problem here. I highly suggest reinstalling wideFS/client following the instructions exactly per documentation and recommendations of using TCP/IP vs. IPX. Using the recommended configuration has worked for me numerous times in different environments, without any issues.Does this help? Damian ClarkHiFi Simulation Technologies
Create an account or sign in to comment