Wide Client Connects then hangs!

[mhayling]

Hi, I'm having a problem with wide client. It connects, FS displays that it has connected, but it hangs and cannot be minimized or shut down! I have to shut it down with the windows task manager.

Ignoring the fact that it had hung I started the PM CDU software, however there is no data being transferred to the software, or so it seems.

My setup is this. I have three systems networked using a router/switch.

FS system is Win XP-PRO Service Pack 2

PMRJ system is Win 98 SE

PM CDU system is WIN XP-PRO Service Pack 1

I can read the files on any system from any system.

The PMRJ system is communicating with wide FS, no problems. The PMRJ Software is active.

The problem is with communication between the two WIN XP PRO systems. Im getting error 10054 in the "WideServer0" log.

Why are there two WideServer logs ??

If anyone has any idea what is going on, PLEASE Help.

Thanks.

[Pete Dowson]

I'm having a problem with wide client. It connects, FS displays that it has connected, but it hangs and cannot be minimized or shut down! I have to shut it down with the windows task manager.

Hangs? I've not had a case of it hanging for many years! There are separate threads in it for different things, so it is almost impossible.

It sounds like the process is being stopped down in the network drivers.

Don't you even have a WideClient LOG fragment for me to see? And I always need to know the version nmuber, always!

The problem is with communication between the two WIN XP PRO systems. Im getting error 10054 in the "WideServer0" log.

What's in the current log, and what version is WideServer?

Why are there two WideServer logs ??

Ah, you've not looked at the documentation then? When Wideclient and WideServer start they rename the PREVIOUS log to "0.LOG" before creating the new one as simply ".LOG. That way, if there's ever a need to restart Client or Server PCs you can do so directly without losing any useful information held in the Logs.

If anyone has any idea what is going on, PLEASE Help.

I need more information to start, please. Logs, INI files, version numbers at minimum.

Regards,

Pete

[mhayling]

Hi Pete,

I've checked the two WIN XP systems network settings. They seem to be the same.

I did a little experiment, the client system is my old FS system, the FS system is a new system. I still have FS on the client. so I ran FS on the Client and I ran Wide Client on the new FS system without FS running on that system. Wide client connecten and ran OK. So there does not seem to be any network problem.

Here are the Logs & INI Files.

I'm Using the latest files from your website.

Working Client.zip

Wide Server Logs.zip

Client Files.zip

[Pete Dowson]

Here are the Logs & INI Files.

Thanks. I cannot see anything wrong at all there. Seems that WideClient does connect, and even sends the first data block (that's how the Server knows its name and logs that, also making an entry into its INI file).

This is rather a puzzle. All I can do at present is ask you to log more data. Please edit the WideClient.INI file (on the problem Client only) with

Log=DebugAll

Edit the WideServer.INI with

Log=Debug

Start up the Server FS, do NOT run the working client (it will cloud the issues on the Server), then start the problem Client. Get as far as running an application on the Client to prove it isn't working, then close everything down.

Please ZIP up both logs (they may be very large) and send them to me at petedowson@btconnect.com.

I cannot say whether there will be enough information there, but it is all I can do at present. With those logging options, WideFS logs just about everything it does. If it is "hanging" I should be able to see where, and then maybe provide a version with yet more logging in that area.

This is the first time I've seen any problem like this in six or more years of WideFS so I am very puzzled by it.

Regards,

Pete