Blog

Home > Event Id > Event Id 168 Symantec Mail Security

Event Id 168 Symantec Mail Security

No Yes logo-symantec-dark-source Loading Your Community Experience Symantec Connect You will need to enable Javascript in your browser to access this site. © 2016 Products Products Home Threat Protection Advanced Threat For example on a 32-bit system with 6.5 installed the key is:HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\SMSMSE\6.5\Server\DefsUpdateTimeInSecs. 3. b. Remove the user conditions from all enabled content filtering rules. have a peek here

Applies To This typically shows up on computers in which file system activity takes a long time. Don't have a SymAccount? Will the weather be sunny next month, what will next week’s lottery numbers or will you get stuck in traffic on the commute? The leading Microsoft Exchange Server and Office 365 resource site. http://www.eventid.net/display-eventid-168-source-Symantec%20Mail%20Security-eventno-4168-phase-1.htm

Click on Admin > System settings. 3. This causes a serial crash of IIS Admin and dependent services: IMAP, NNTP, MS Exchange Routing engine, and SMTP Your Event log will contain entries similar to these: Event Type: ErrorEvent Choose how long you'd like the scan to run before it will stop scanning, and select options for which messages to process. (Note: Selecting "Only scan items modified since last scan" Don't have a SymAccount?

For each content filtering rule, complete the following: a. Translated Content This is machine translated content Login to Subscribe Please login to set up your subscription. It has done this 1 time(s). The decomposer then loads the library MSVCP71.dll.

When content filtering rules are configuredSMSMSE issues a query to Active Directory using LDAP to determine the SMTP address associated with the X.400. Open the SMSMSE console. 2. To be precise: improperly configured file system antivirus software. Close Login Didn't find the article you were looking for?

The working folder that is used to store streaming temporary files that are used for message conversion. Enable all the rules you added to the list in step 4b and click Next . 11. Restart the following SMSMSEservice: Symantec Mail Security for Microsoft Exchange Workaround Configure LiveUpdate to update virus definitions at a time that the server has free resources. A review of the Application log in the Event viewer shows entries for Event ID: 5 with Event Source: Norton AntiVirus.

For each content filtering rule, complete the following: a. Supported Products A-Z Get support for your product, with downloads, knowledge base articles, documentation, and more. No Yes Products Products Home Threat Protection Advanced Threat Protection Endpoint Protection Endpoint Protection Cloud IT Management Suite Email Security.cloud Data Center Security Blue Coat Products Information Protection Data Loss Prevention Supported Products A-Z Get support for your product, with downloads, knowledge base articles, documentation, and more.

Submit a False Positive Report a suspected erroneous detection (false positive).

Information for: Enterprise Small Business Consumer (Norton) Partners Our Offerings: Products Products A-Z Services Solutions Connect with us: Support navigate here d. Education Services Maximize your product competency and validate technical knowledge to gain the most benefit from your IT investments. Submit a Threat Submit a suspected infected fileto Symantec.

You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The Exchange server antivirus will of course crash and sometimes even cause the Microsoft Exchange Information Store service to crash as well. Windows Application Event Log Contains Event IDs 110, 168, 68, and 167 When Copying Virus Definitions Takes a Long Time Did this article resolve your issue? Check This Out Event ID 68 - Unable to initialize scan engine.

Event ID: 103 with Event Source: Symantec Mail Security follows this entry. Recommend Us Quick Tip Connect to EventID.Net directly from the Microsoft Event Viewer!Instructions Customer services Contact usSupportTerms of Use Help & FAQ Sales FAQEventID.Net FAQ Advertise with us Articles Managing logsRecommended Navigate to Scans > Scheduled Scans. 6.

Event Type: Error Event Source: Symantec Mail Security for Microsoft Exchange Event Category: (3) Event ID: 401 Date: 12/01/2011 Time: 08:06:39 User: N/A Computer: XXXXXXXXXXX Description: The description

Here is an example of a procmon log from a working system: 14:12.6 SAVFMSESp.exe 6556 Load Image C:\Program Files (x86)\Common Files\Symantec Shared\definitions\Decomposer\Dec2LHA.dll SUCCESS Image Base: 0xec0000, Image Size: 0x14000 14:12.6 SAVFMSESp.exe Try these resources. During transport scanning, SMSMSE gets SMTP addresses of senders and recipients of mail items to be scanned, allowing it to evaluate this type of content filtering rules without the need to Submit a Threat Submit a suspected infected fileto Symantec.

Windows Application Event Log Contains Event IDs 110, 168, 68, and 167 When Library c:\windows\syswow64\MSVCP71.dll is Missing Did this article resolve your issue? Create a SymAccount now!' Symantec Mail Security for Exchange (SMSMSE) Processes Cannot Start. Fig 3: Normal response Fig 4: Response of a damaged SMTP service If you were unfortunate to run into situation like this, the only this contact form Perform a liveupdate to retrieve the latest virus definitions.

The virus definitions may be missing or corrupt. It has done this 1 time(s). If SMTP addresses /Active Directory groupsexist, remove them from the rule. Solution Reinstall SAV 10.xApplies To- Exchange 2003 SMS 6.5.1 - SAV 10.x - each server has its own console. - no proxy in the network. - certified definitions are used.

c. Note: The symptoms for this issue are very similar to multiple other root causes. Education Services Maximize your product competency and validate technical knowledge to gain the most benefit from your IT investments. These entries appear multiple times.The Symantec corporate edition product installed is one of the following:Norton AntiVirus Corporate Edition 7.xSymantec AntiVirus Corporate Edition 8.xSymantec AntiVirus Corporate Edition 9.xSolution:The presence of these entries

This results in the SMSMSEprocesses not being able to restart or reinitialize themselves.