Posted by Barbara Brazil on October 29, 2018 at 13:51:21: Uploaded files: 1
In Reply to: Re: CAW Host weekend freeze...> posted by Tom Fulton on October 29, 2018 at 12:45:55:
Tom:
The reason I wanted to see the server logs was to look for an "orphan logout". If the Comet client stops pinging the servers at the expected interval, they will log that client out. I see this on your Security Server log, but the Security Server only checks for orphans when a new user wants to connect. There's no reason to do it sooner. In their case this didn't happen until this morning. The file server, on the other hand, checks for each client about every 60 seconds. It's important to log an orphaned file server client out as soon as possible so all their extracts, locks, etc can be cleaned up. I've attached a screen shot of the recommended file server logging settings. It would be helpful to set theirs up that way.
So, the next thing I would suggest is checking the Windows Event Viewer and Scheduled Tasks to see what else might have been going on around 4:38pm on Saturday. That's the time that CFAM detected a client/server disconnect had happened. I'm looking for either another application (such as shadow copy/backup or virus scanning) that could have interfered with Comet's connection to the server or for an indication that some piece of Comet crashed on the server. Look for anything involving CFileSrv.exe, CSecSrv.exe, or CFAMNetServe.exe.
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.