Application Event Log Source: SideBySide, Event ID: 35 Lync.exe.Manifest error
I resolved this by amending the manifest file reported in the error (C:\Program Files\Microsoft Office 15\root\office15\LYNC.EXE.MANIFEST
), changing the processor architecture of the UccApi DLL.
Before:
<assemblyIdentity type="win32" name="UccApi" version="15.0.0.0" processorArchitecture="*"></assemblyIdentity>
After:
<assemblyIdentity type="win32" name="UccApi" version="15.0.0.0" processorArchitecture="x86"></assemblyIdentity>
Related videos on Youtube
JohnLBevan
I work as a technical architect for an advertising company. Most of my day job revolves around ERP, Finance and Operations systems, though I also get involved with any technical issues which fall into knowledge gaps between the various IT teams' / people's roles. My (IT related) interests are more towards web applications, artificial intelligence, productivity utilities, and scripting. If you want to know more about me than that, just Google my username - it's a perfect example of how not to ensure personal privacy.
Updated on September 18, 2022Comments
-
JohnLBevan almost 2 years
I'm seeing an error in my Windows event log with the following signature:
- Log: Application
- Source: SideBySide
- EventId: 35
- Level: Error
- Description: Activation context generation failed for "C:\Program Files\Microsoft Office 15\root\office15\lync.exe.Manifest".Error in manifest or policy file "C:\Program Files\Microsoft Office 15\root\office15\UccApi.DLL" on line 1. Component identity found in manifest does not match the identity of the component requested. Reference is UccApi,processorArchitecture="AMD64",type="win32",version="15.0.0.0". Definition is UccApi,processorArchitecture="x86",type="win32",version="15.0.0.0". Please use sxstrace.exe for detailed diagnosis.
I've not seen any negative symptoms related; but like to keep my logs clear of errors where possible.
How can I resolve this issue / prevent this error?
-
Lucky Luke about 7 yearsThese errors can usually be ignored, but nice job fixing it. Thanks for posting the answer.
-
Leo Gurdian over 6 years@JohnLBevan - thank you for sharing the ACTUAL answer. It's better than Microsoft's suggestion to just "ignore" the problem as suggested here: support.microsoft.com/en-us/help/3077028/…