Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 168 Source: Symantec Mail Security
|Source: Symantec Mail Security|
The process <process> was restarted.
|English: Request a translation of the event description in plain English.|
In my case, I upgraded from SMSMSE 6.0.7 to 6.5.5 and then utilized the memory cap for SAVFMSESp.exe - see EV100272 (Symantec article TECH142829). The SMSMSEp process routinely starts over now, I'm guessing this is how the process regulates it's memory cap.
- Process: "SAVFMSESp.exe" - See "Symantec Support Document ID:2004062209101054" for information on this event.
- Process: "SMSESJM.EXE" - See "Symantec Support Document ID:2002011109535354".
- Process: "navesp" - See "Symantec Support Document ID: 2001022700100354".
As per Symantec: "This problem is resolved in Symantec Mail Security for Microsoft Exchange 4.0 build 461". See "Symantec Knowledge Base Document ID: 2003103013081854" for more details.
|Private comment: Subscribers only. See example of private comment|
|Links: Symantec Knowledge Base Document ID: 2003103013081854, Symantec Support Document ID:2004062209101054, Symantec Support Document ID:2002011109535354, Symantec Support Document ID: 2001022700100354|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated