Lost Communications with Host error..

[imageworx]

Can't seem to fix this with FMPro Server running on Mac (G3) with OS 9.1.

 

Two to three clients accessing 12 dB files on server.

 

Around 6-7 hours of daily use, when clients get a Lost Communications error (squiggly arrow).

 

Server is hung.

 

LAN, HP4000 switches are fine. Wiring switched (ports and wall jack and drop cables/patch cord).

Still get error in middle of day.

 

Checked to see if anything was running on machine that was not supposed to. Negative.

 

Did find TCP/IP had "Load Only When Needed" checked so I unchecked it. (or should this be checked? I found it not checked on an ASIP 6.3 server and its been running 24/7 for 11 months...)

 

This started after upgrade to 9.1 and FMPro 5.5v1 (server) and FMPro 5.5v3 clients and our database worked on by IDS.

 

Thanks for any clues?

 

Ed-

[hairyjim]

Are you get any large cache hits?

 

What do your filemaker server logs say?

 

Plus check to see if that you are not logging people out if they are innactive for a while? Run a test on this, leave a machine for a while and then go back and try and do some work, see if you can recreate the problem.

 

Jim

[imageworx]

Originally posted by hairyjim:

[qb]Are you get any large cache hits?

 

What do your filemaker server logs say?

 

Plus check to see if that you are not logging people out if they are innactive for a while? Run a test on this, leave a machine for a while and then go back and try and do some work, see if you can recreate the problem.

 

Jim[/qb]

Jim, thanks for heads up!

 

Getting some large cache hits. Have it emptying hourly, should I reduce the time? Cache size at max.

Logs are blank hour before crash. Thought it ironic that cache emptying was done hour prior and that it could be related. (ie. log shows cache emptying and then next hour its same thing. Then hour later all is blank--when it crashed).

 

I turned off running any schedules, and the disabling inactive users is not active.

 

I am thinking it might be a combination of things. The other day, late in evening, a user ran a dB file and it hung. Next day, that dB was damaged and I had to do a recover. But the communication error wasn't present.

 

Likely, I am guessing it WAS the TCP/IP prefs having Load Only When Needed checked had caused the error.

 

Ed-