Event log error on Symantec Endpoint Protection Manager logged in Windows 2008 server.

Article:TECH185958  |  Created: 2012-04-06  |  Updated: 2012-11-26  |  Article URL http://www.symantec.com/docs/TECH185958
Article Type
Technical Solution


Environment

Issue



There are many "SidebySide" errors in the Windows Event Viewer Application logs in Windows 2008 server, caused by Symantec Endpoint Protection (SEP) trying to access files only present in updated builds of the Windows operating system (OS). 


Error



Event ID: 35
Event Source: Side by Side
Event Detail:
 

Activation context generation failed for "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection\12.1.1000.157.105\Bin\SDPck32i.dll".Error in manifest or policy file "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection\12.1.1000.157.105\Bin\Microsoft.VC90.CRT.MANIFEST" on line 4. Component identity found in manifest does not match the identity of the component requested. Reference is Microsoft.VC90.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8". Definition is Microsoft.VC90.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.30729.4148".


Environment



Windows 2008 64bit

SEP 12.1 RU1

 


Cause



 

Compatibility issue based upon the patching of the operating system where SEP is trying to access files that have been changed or are only present in updated builds of the Windows operating system. 

 


Solution



Upgrade Microsoft Visual C++ 2008 Redistributable Package to the latest version. It is also recommended to review Microsoft’s best practices for patching the OS.
 

Microsoft service pack best practices:
http://technet.microsoft.com/en-us/library/cc750077.aspx
 

Microsoft Visual C++ 2008 SP1 Redistributable download:
X86: http://www.microsoft.com/en-us/download/details.aspx?id=5582
X64: http://www.microsoft.com/en-us/download/details.aspx?id=2092
 


Supplemental Materials

SourceETrack
Value2406978
Description

internal investigation indicates this is not a Symantec issue.



Article URL http://www.symantec.com/docs/TECH185958


Terms of use for this information are found in Legal Notices