I have a v12.1 client which was not connecting to a SEPM because of a duplicate id. I corrected this by running the RepairClonedImage.exe fix. After the "fix" I noticed the status doesn't show any components. I have removed the client, reinstalled, still, no luck. I also have a bunch of SideBySide errors in the event log. I reinstalled Visual C++ 2008 SP1 and had a somewhat cleaner reboot, but I tried clearing out the client again, reboot and reinstall, but have the same symptom all over again. I only got one hit (and now I can't find it) with a graphic of a client in this state, but the note was an SEPM upgraded from 11. to 12.1 with a client deployment package of an 11.0.6 install. Not the case here. Anyone else see anything like this?
I also get a DCOM error after a restart:
Evenit ID: 10000
Source: DistributedCom
Unable to start a DCOM Server: {1CDDD0B9-03AA-4442-9A5B-AC98086513E1}. The error: "14001"
Happened while starting this command:
"C:\Program Files\Symantec\Symantec Endpoint Protection\12.1.1101.401.105\Bin\SmcGui.exe" -Embedding
Details of the SideBySide error:
Event ID: 35
Source: SideBySide
Frequency: This is logged 9 times after each restart.
Activation context generation failed for "C:\Program Files\Symantec\Symantec Endpoint Protection\12.1.1101.401.105\Bin\ProtectionUtil.dll".Error in manifest or policy file "C:\Program Files\Symantec\Symantec Endpoint Protection\12.1.1101.401.105\Bin\Microsoft.VC90.ATL.MANIFEST" on line 4. Component identity found in manifest does not match the identity of the component requested. Reference is Microsoft.VC90.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.30729.6161". Definition is Microsoft.VC90.ATL,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.30729.4148". Please use sxstrace.exe for detailed diagnosis.