Home Dashboard Directory Help
Search

"Activation context generation failed" by adarshbhat


Status: 

Closed
 as By Design Help for as By Design


5
0
Sign in
to vote
Type: Bug
ID: 526027
Opened: 1/20/2010 7:47:34 AM
Access Restriction: Public
0
Workaround(s)
view
5
User(s) can reproduce this bug

Description

I see errors in my Windows Event Viewer that read as follows:

Source: SideBySide

Activation context generation failed for "C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\Remote Debugger\ia64\msvsmon.exe". Dependent Assembly Microsoft.Windows.Common-Controls,language="*",processorArchitecture="ia64",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0" could not be found. Please use sxstrace.exe for detailed diagnosis.
Details
Sign in to post a comment.
Posted by Robert Heinig II on 7/11/2011 at 5:08 AM
This one seems to be automatic when installing Visual Studio 2010 SP1 on x64 (in my case, may have wider impact - e.g. RTM or betas of VS2010). The original issue did not mention the Event ID nor chronological patterns - in my case Event ID 33, Source SideBySide and fingering the ia64 version of msvsmon.exe just like the original reporter had, and repeated once daily at 00:34 hours, starting precisely with the installation of VS2010 RTM.

I'm convinced this is a variation of the issue in KB article 2021839, and the passages concerning removing the exe in question and Scheduler Library\Microsoft\Windows\Application Experience\ProgramDataUpdater do apply. I have tested both exe deletion and disabling of the schedulked task, both prevent the messages and seem to work without negative side-effects so far.

The easiest workaround, of course, is to always shut down overnight.

I'd also like to say that this is a bug - W7/2k8r2 and the VS2010 installer are producing a bad configuration without needing user error or uncommon circumstances. True, ia64 code won't run on and is certainly incompatible to the common control libraries found on an amd64 architecture, but VS2010 places it automatically on an amd64 system (in the x86 folder no less), and the out-of-the-box scheduled task will pick it up though it's none of it's business... Either VS2010 chose a bad location or it should have installed the proper dependencies for the exe or the Job is missing some obvious checks. Status "Closed as won't fix" would have been preferrable over "Closed as by design".

For future readers I'd also like to point out that rlfranklin2's problem is most certainly a different one and more likely do be attributed to errors in Adobe and Nero installers (even improperly applied cracks can cause similar sxs issues).
Posted by rlfranklin2 on 4/13/2011 at 10:29 AM
Please note system is a configured as such;windows build 6002, processor 8 processor speed 2918 MHz, memory 12278MB
platform Vista Ultimate 64bit Hard drives
Posted by rlfranklin2 on 4/13/2011 at 10:16 AM
Hers' another one;
Activation context generation failed for "C:\Program Files (x86)\Adobe\Acrobat 9.0\Designer 8.2\FormDesigner.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6002.18305_none_1509f852f40ee5cd.manifest. Component 2: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6002.18305_none_5cb72f2a088b0ed3.manifest.
Posted by rlfranklin2 on 4/13/2011 at 10:15 AM
Any update to this? it's been a couple of months now.

Activation context generation failed for "G:\Program Files (x86)\Nero 9\Nero 9\Nero PhotoSnap\PhotoSnapViewer.exe.Manifest".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6002.18305_none_5cb72f2a088b0ed3.manifest. Component 2: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.6002.18305_none_1509f852f40ee5cd.manifest.
Posted by Microsoft on 2/5/2010 at 2:47 PM
Hello,

Are you reporting an actual bug here, or just an observed error in the Windows Event viewer? The issue in the event viewer is that remote debugger for the Itanium architecture can't run because it does not appear to be on an Itanium system.

Best Regards,
Visual Studio Product Team
Posted by Microsoft on 1/24/2010 at 9:55 PM
Thank you for reporting this issue.
But We are not very clear your question.How did this
happen? Could you please provide more detail steps/actions?
Posted by Microsoft on 1/24/2010 at 5:39 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.