Errors

SNFClient.exe.err only state: Could Not Connect!

When SNFClient cannot connect the SNFServer is either not accepting new connections, or it is down.

If it is down then restarting it helps by starting it again.

If it is not down then restarting helps by abandoning all of the existing connections -- many of them will re-try and succeed when the SNFServer is active again.

This "stalling" effect is seen only when you rename the folder that contains the message files.

It is probably not a good idea to rename the folder while there is any possibility of active scans in progress.

Instead, create a new folder with the correct name for new scans (perhaps by date) and then abandon the older folder in place. New scans would be done in the new folder and old or existing scans would continue in the old folder until they were complete. By the time you do anything with the old folder it will be several generations behind and safe.

A different approach --

Use a single directory for scans and have them always performed there. Then - depending upon the scan result move them into the appropriate directory. This way you could always be assured that the scanner is finished with a file before it is ever moved. This is an efficient process on ext3 and most other modern *nix file systems since it only requires the adjustment of a node and that operation will itself be journalized first.