SideBySide (SxS) error when running ModMgr.exe

I usually dig into Event Viewer to find and solve errors,
I've been seeing this error logged for a long time when running ModMgr.exe
now I decided to share to the public.

Everything works fine, no error messages displayed,
just an error entry - SideBySide - Event ID 80 - into Application Event Log

(saw an old thread about this, but no staff members replied)




Here is the error entry (italian)

Generazione del contesto di attivazione non riuscita per "D:\rf2\ModMgr.exe". Errore nel file manifesto o dei criteri "", alla riga . Una versione del componente richiesta dall'applicazione è in conflitto con un'altra versione del componente già attiva.

Componenti in conflitto:
Componente 1: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac.manifest
Componente 2: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest



xml detail follows:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="SideBySide" />
<EventID Qualifiers="49409">80</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-07-22T11:34:05.000000000Z" />
<EventRecordID>7707</EventRecordID>
<Channel>Application</Channel>
<Computer>PC</Computer>
<Security />
</System>
- <EventData>
<Data>C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac.manifest</Data>
<Data>C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest</Data>
<Data />
<Data />
<Data />
<Data />
<Data />
<Data />
<Data />
<Data />
<Data>D:\rf2\ModMgr.exe</Data>
<Data />
<Data />
<Data />
<Data />
<Data />
<Data />
<Data />
<Data />
<Data />
</EventData>
</Event>



running Win7 x64, anyone else could check their event viewer?

 

Interesting. I will look into it. My guess is the ModMgr and Mas tool are compiled with slightly out of date compiler.

 

Jeremy

There are problems with the manifest embedded in "MAS2.exe". Manifests can be verified with the "sxstrace.exe" diagnostic tool that is included with Windows Vista and newer.

Manifest embedded in b789 MAS2.exe ...

<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity version="1.0.0.0" processorArchitecture="X86" name="CompanyName.ProductName.YourApp" type="win32">
</assemblyIdentity>
<description>Your application description here.</description>
<dependency>
<dependentAssembly>
<assemblyIdentity type="win32" name="Microsoft.Windows.Common-Controls" version="6.0.0.0" processorArchitecture="X86" publicKeyToken="6595b64144ccf1df" language="*">
</assemblyIdentity>
</dependentAssembly>
</dependency>
<dependency>
<dependentAssembly>
<assemblyIdentity type="win32" name="Microsoft.Windows.Common-Controls" version="6.0.0.0" processorArchitecture="*" publicKeyToken="6595b64144ccf1df" language="*">
</assemblyIdentity>
</dependentAssembly>
</dependency>
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
<security>
<requestedPrivileges>
<requestedExecutionLevel level="asInvoker" uiAccess="false">
</requestedExecutionLevel>
</requestedPrivileges>
</security>
</trustInfo>
</assembly>

 

Here is my sxstrace. Have this sidebyside error since a long time.

 

Wow, Tosch - that was quick. Same result that I see. You must be familiar with sxstrace.

 

Googled a bit in the Microsoft support forums. I've seen this error for a long time in my eventlogs and yesterday I tried to figure out what's going on.