Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 327 Source: Symantec Mail Security for Microsoft Exchange
|Source: Symantec Mail Security for Microsoft Exchange|
The process SAVFMSESp.exe was forcibly terminated. Reason: SAVFMSECtrl process failed to communicate with SAVFMSESp process.
|English: Request a translation of the event description in plain English.|
From a newsgroup post: "I called Symantec and they said that the error that I was seeing was normal accept that it shouldn't happen repeatedly and bring the server to its knees. The program is designed to stop and restart the service if it hangs on a file that is unscannable. This seems to be the problem, except that it was caught in a loop of restarts. They thought that perhaps corrupted program files or virus definitions were causing the problem. Either way, they suggested uninstalling Symantec Mail Security for Exchange and Symantec Antivirus Enterprise, removing the Symantec shared folder from C:\Program Files\Common Files, and then doing a clean install of both programs. They also told me to disable the live update on the Mail Security because the Symantec Antivirus Enterprise gets the live updates and then shares them through the C:\Program Files\Common files\Symantec shared folder.
This seemed to do the trick. It only took an hour or so to do a clean install, although that was an hour or so that we had the e-mail server off line".
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated