PMsystem lost connection

[jan737]

Hi Pete

I'm running pmsystem 67 via widefs650/fsuipc350 and fs2004.

But after a short period pmsystem lost the connection and report NOT connected.

Is this a widefs problem or........?

As attachment the widefs log.

Best regards

Jan Geurtsen

WideClient.zip

WideClient.zip

[Pete Dowson]

Is this a widefs problem or........?

Why are there two WideCliient logs and no WideServer log? There are always two ends to a connection.

407766 New Client Application: "pmSounds" (Id=3780)

413329 New Client Application: "pmsystems" (Id=3476)

413782 New Client Application: "MCP" (Id=3000)

2978563 New Client Application: "FSInterrogate2std" (Id=3820)

3478688 READSTATEDATA received with bad data size!

3478688 0 ReadLocal: Offset=10001, Size=31E40000

3570297 Shutdown request received!

Looks like you are running a LOT more than pmSystems -- you have pmSounds, the PM MCP and the new FSInterrogate there too!

This error occurred after 50 minutes from the FS connection being started not, as you say, "a short time".

After that you closed down and started again (but not WideClient), but you seem to be then getting errors from one of the programs:

3660985 Connection made okay!

3661016 C:\MCP\MCP.EXE

3661141 C:\PMSOUNDS\PMSOUNDS.EXE

3661266 C:\PMsystems\PMSystems.EXE

3662266 New Client Application: "pmSounds" (Id=2948)

3715922 READSTATEDATA received with bad data size!

3715922 0 ReadLocal: Offset=10001, Size=31E40000

3729125 0 ReadLocal: Offset=10001, Size=31E40000

3838422 0 ReadLocal: Offset=10001, Size=31E40000

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

3844704 Connection closed by server!

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

3844704 Ready to try connection again

3844750 Attempting to connect now

3844782 Connection made okay!

3871094 READSTATEDATA received with bad data size!

3871094 0 ReadLocal: Offset=10001, Size=31E40000

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

3987688 Connection closed by server!

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

3987688 Ready to try connection again

3987704 Attempting to connect now

3996657 Connection made okay!

4332422 READSTATEDATA received with bad data size!

4332422 0 ReadLocal: Offset=10001, Size=31E40000

4346032 0 ReadLocal: Offset=10001, Size=31E40000

4632047 New Client Application: "pmsystems" (Id=236)

4678344 READSTATEDATA received with bad data size!

4678344 0 ReadLocal: Offset=10001, Size=31E40000

6629766 0 ReadLocal: Offset=10001, Size=31E40000

6632813 New Client Application: "FSInterrogate2std" (Id=3188)

7080704 READSTATEDATA received with bad data size!

7080704 0 ReadLocal: Offset=10001, Size=31E40000

7364594 0 ReadLocal: Offset=10001, Size=31E40000

7444360 0 ReadLocal: Offset=10001, Size=31E40000

7597704 Shutdown request received!

Those "READSTATEDATA" errors indicate bad requests actually being received from one of the programs -- one of MCP, PMSOUNDS and PMSYSTEMS. Sorry, I can't tell which one. I suggest you report this to PM support -- that isn't a Network problem, it is data corruption in one of the programs.

In the other log there was this:

407766 New Client Application: "pmSounds" (Id=3780)

413329 New Client Application: "pmsystems" (Id=3476)

413782 New Client Application: "MCP" (Id=3000)

2978563 New Client Application: "FSInterrogate2std" (Id=3820)

3478688 READSTATEDATA received with bad data size!

3478688 0 ReadLocal: Offset=10001, Size=31E40000

3570297 Shutdown request received!

Again you are running FSInterrogate. However, the data error is exactly the same, and is consistent. If it is pmSystems which is hanging or gpoing odd, then it may be that which is responsible. Why not try it on its own, to prove it?

Regards,

Pete

[jan737]

Pete

I discussed this with Enrico and he uploaded a new version of pmsystem.

(version 68a).I'll try it in the next couple of days.

Thanks for your response.

Best regards

Jan Geurtsen.