Getting SideBySide Event ID: 33
Original title: Microsoft Product: Windows Operating System; Version: 6.1.7600.16385; Event ID: 33; Event Source: SideBySide; ____
I must’ve uninstalled this. how can I find it again??
Replies (5)
Event ID 33 is logged in the Application log (Event Viewer) when you start an application that has versioning conflicts. This kind of error doesn’t affect the functionality of any application. You can safely ignore this. This may occur due to a program using Visual C++.
You can uninstall any existing Microsoft Visual C++ Redistributable Package and install the latest Microsoft Visual C++ 2010 Redistributable Package and check if it helps.
Step 1: To uninstall the package:
a. Open Programs and Features.
b. From the list, find Microsoft Visual C++ Redistributable Package and click on it.
c. Click Uninstall at the top of the list.
Step 2: Download and install the latest package and see if it helps.
Download details: Microsoft Visual C++ 2010 Redistributable Package (x86)
Hope this information is helpful.
Praseetha K
Microsoft Answers Support Engineer
Visit our Microsoft Answers Feedback Forum and let us know what you think.
If this post helps to resolve your issue, please click the «Mark as Answer» or «Helpful» button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.
Event ID 33 source side by side
I have upgraded my real player to real player 14 plus.Every time when i am launching the real player its generate an error log:-
Activation context generation failed for «C:\Program Files (x86)\Real\RealPlayer\plugins\rmxrend.dll». Dependent Assembly Microsoft.VC90.DebugCRT,processorArchitecture=»x86″,publicKeyToken=»1fc8b3b9a1e18e3b»,type=»win32″,version=»9.0.21022.8″ could not be found. Please use sxstrace.exe for detailed diagnosis.
SideBySide errors are typically caused by the current Microsoft Visual C++ version not being backward compatible with the application that failed. The Event ID 33 error message is typically: Activation context generation failed for “program name”..Please use sxstrace.exe for detailed diagnosis. There are other similar SideBySide errors with the same problem of backward compatibility. If the software works OK then you don’t have to fix it but if it does not or you want to get rid of this error here are two Fixes:
1) Reinstall or Repair (preferred if an option) the application. Often the installation package will have the version of Microsoft Visual C++ that it uses and will install it.
2) Try to figure out what Microsoft Visual C++ Redistributable Package version (available versions are: 2003, 2005, 2008, & 2010) the application needs (most likely the one that came out prior to the date that the application software was created; check the dates of the files in the package). . These are available through Microsoft’s Downloads.
Worse comes to worse you can just try installing a previous version to see if it works, if not then try the one before that. Though I don’t like it, you can have multiple versions of Microsoft on your computer and most people do because various install programs will install the one that they like.
Windows event 33 sidebyside
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Answered by:
Question
Let me say that I’m not really sure if this is the correct place to post this question, if that’s so, please move it accordingly
So, here’s my question. I have a few messages on the event log regarding sidebyside errors with ID 33, three are for visual studio components and another is for a vmware workstation component.
The errors I’m talking about read as such:
VMWare Workstation 7.0.1.11056
Activation context generation failed for «c:\program files\VMware\vmware workstation\vssSnapVista64.exe». Dependent Assembly Microsoft.VC80.CRT,processorArchitecture=»amd64″,
publicKeyToken=»1fc8b3b9a1e18e3b»,type=»win32″,version=»8.0.50727.762″ could not be found. Please use sxstrace.exe for detailed diagnosis.
Visual Studio 2010
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.
Activation context generation failed for «C:\Program Files\Microsoft Visual Studio 10.0\Common7\Packages\Debugger\X64\msvsmon.exe». Dependent Assembly Microsoft.Windows.Common-Controls,language=»*»,processorArchitecture=»amd64″,
publicKeyToken=»6595b64144ccf1df»,type=»win32″,version=»6.0.0.0″ could not be found. Please use sxstrace.exe for detailed diagnosis.
Activation context generation failed for «C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\Remote Debugger\x64\msvsmon.exe». Dependent Assembly Microsoft.Windows.Common-Controls,language=»*»,processorArchitecture=»amd64″,
publicKeyToken=»6595b64144ccf1df»,type=»win32″,version=»6.0.0.0″ could not be found. Please use sxstrace.exe for detailed diagnosis.
Now, I want to note that I haven’t had any problems using this applications, so whatever is reporting the event log doesn’t seem to be a problem for my use of the applications and I’ve also read several KBs and other online resources about even ID 33 related to sidebyside.
Another thing I want to point out is that my system is Windows 7 Ultimate 32-bits and what interest me about this errors is that with each one there are references to 64-bits platform components (x64 or ia64).
The fact that my system is 32-bits could be the reason I’m getting such messages in the event log or should I be looking for other things? Is there anything I could do to avoid such messages?
That’s it, thanks for reading. If you have any info about this please provide 🙂
Answers
Based on my further research, Event ID 33 is logged in the Application log when you start an application that has versioning conflicts. This kind of error doesn’t affect the functionality of application. You can safely ignore this. BTW, from your event log, it seems to be more related to Microsoft Visual Studio 2010. If you do would like to prevent event error from being logged, you may need to isolate applications and Side-by-side Assemblies to correct the DLL versioning conflicts, please visit the following site for reference:
All replies
Could you tell us the Source name of this event? Event ID 33 can be caused by different components. You’d better copy the whole Event information and paste here.
1) Click «Start», input «eventvwr» (without quotation marks) in the Start Search bar and press Enter.
2) Expand the «Windows Logs» node on the left pane, right-click on «Application» and click «Save All Events As»; in the pop-up window, click to choose the Desktop icon on the left frame, input «app» in the «File name» blank, and then click save.
3) Right click on «System», with the same method, save it as «sys».
4) Locate the two saved log files on the Desktop
Hello, thanks for responding 🙂
As I said previously, the Source name of the errors (for vs2010 and vmware7) is: SideBySide, or that’s what I see in every event on the Source field of the general tab, if that’s not what you’re asking, let me know.
I’ve created both evtx files as you requested, what should I do with those?
Regarding, copying the whole events, here they are:
I want to make clear that I’m not having problems while using the applications, but it intrigues me to see those event (which happen very times a day) so I’d like to know if I can do anything about it.
Also a thing I notice today, the vmware error happens even if I’m not using the application (no client app initialized and no service running), for instance, I have an event from today at 5:40 AM and I haven’t used vmware in days. Odd to me.
Thanks for reading,
Based on my further research, Event ID 33 is logged in the Application log when you start an application that has versioning conflicts. This kind of error doesn’t affect the functionality of application. You can safely ignore this. BTW, from your event log, it seems to be more related to Microsoft Visual Studio 2010. If you do would like to prevent event error from being logged, you may need to isolate applications and Side-by-side Assemblies to correct the DLL versioning conflicts, please visit the following site for reference:
Thank very much 😉
I’m reading right now the link since the primary interested in avoid those events is merely to stop noid in the logs.
I’ll keep investigating the issue but just to know why this version conflicts.
For now I think the question is answered so thanks a lot.
When diagonise side-by-side errors, start the SxSTracing using the below command:
SxsTrace Trace -logfile:SxsTrace.etl
Then run your application that is causing the problem.
When done, press Enter to stop the tracing and use the below command to generated a text formatted file of the output.
sxstrace Parse -logfile:SxSTrace.etl -outfile:SxSTrace.txt
Going through the generated text file should give details of each of the loaded modules and the bindings.
«A programmer is just a tool which converts caffeine into code» CLIP- Stellvertreter http://www.winvistaside.de/
When diagonise side-by-side errors, start the SxSTracing using the below command:
SxsTrace Trace -logfile:SxsTrace.etl
Then run your application that is causing the problem.
When done, press Enter to stop the tracing and use the below command to generated a text formatted file of the output.
sxstrace Parse -logfile:SxSTrace.etl -outfile:SxSTrace.txt
Going through the generated text file should give details of each of the loaded modules and the bindings.
«A programmer is just a tool which converts caffeine into code» CLIP- Stellvertreter http://www.winvistaside.de/
Thanks a lot! I’ll be checking that later today.
Have you made a SxStrace?
«A programmer is just a tool which converts caffeine into code» CLIP- Stellvertreter http://www.winvistaside.de/
I have but with no success it seems.
I start the trace, open up VS2010, open a project, made a simple change, rebuild the project, ran that project in debug mode, ran without debugging, stop the trace and parsed the file.
To my surprise the sxstrace.txt I set in the -outfile was empty (btw, I ran sxstrace from an elevated cmd). Another funny thing is that I went to the event log, and there’re SideBySide errors from this afternoon at 2:03 PM, but there was none at the time I was using sxstrace (
What I could made of this is that the SideBySide errors occur under certain conditions but not every time I build or run a project. Maybe is a project specific thing or maybe is something else, however, I would like to know now, should sxstrace provide output no matter if there were errors or not?
I don’t know yet what happened before but I manage to get the trace, however, didn’t get much from it.
I’ve paste the trace in the following link: http://pastie.org/947751
As I see it, there are no errors on that trace, beyond some manifest being searched for EN_US and EN cultures whatever that means.
Also, I think the lack of errors in that file is related to the fact that, once again, there are no SideBySide error on my logs beyond those from this afternoon.
I used the project I was working on this afternoon in case it was a really a project specific thing, but still no SideBySide errors.
I guess this is one of those times when you finally have something to dig deeper the error just doesn’t show 😛
Anyway, I’ll be keeping my eyes on the matter and try to catched.
I received an error message such messages since last update :
And those damn messages came at a time 13. Is this Idiotsoft stupid joke.
It seems that the update to be fully turned off ! :@ :@
Log Name: Application
Source: SideBySide
Date: 13.07.2011 23:21:55
Event ID: 33
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Martin-VAIO
Description:
Activation context generation failed for «C:\Windows\system32\conhost.exe». Dependent Assembly Microsoft.Windows.SystemCompatible,processorArchitecture=»amd64″,publicKeyToken=»6595b64144ccf1df»,type=»win32″,version=»6.0.7600.16823″ could not be found. Please use sxstrace.exe for detailed diagnosis.
Event Xml:
Log Name: Application
Source: SideBySide
Date: 13.07.2011 23:22:02
Event ID: 33
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Martin-VAIO
Description:
Activation context generation failed for «C:\Windows\system32\conhost.exe». Dependent Assembly Microsoft.Windows.SystemCompatible,processorArchitecture=»amd64″,publicKeyToken=»6595b64144ccf1df»,type=»win32″,version=»6.0.7600.16823″ could not be found. Please use sxstrace.exe for detailed diagnosis.
Event Xml:
WHAT THE FUCK. HOW FIX THIS JOKE. :@
we have the same errors after the last updates 🙁
Doesn’t work in our environment. all servers are affected.
Do you have rebooted the affected server after the update was uninstalled?
Best regards, Alexander Zirbes
I uninstall the KB2507938 and rebooted, but I have the same error, it appears to be calling an invalid version, in my case this is the error:
Activation context generation failed for «C:\Windows\system32\conhost.exe». Dependent Assembly Microsoft.Windows.SystemCompatible,processorArchitecture=»amd64″,publicKeyToken=»6595b64144ccf1df»,type=»win32″,version=»6.0.7600.16823″ could not be found. Please use sxstrace.exe for detailed diagnosis.
And it started whe I install the KB2507938 security update, this error is generated about 3 times on a minute, its getting my event log crazy.
I see another post out there stating that C++ may be corrupt and to uninstall and reinstall C++
Someon else posted this. It relates to Vista but may apply.
«The «side-by-side» component is associated with the Vista Windows Resource
Protection (WRP). You may have a corrupted file in the SxS folder.
To resolve this issue, use the System File Checker tool (SFC.exe) to repair
these files.
To do this, follow these steps:
1. Open an elevated command prompt. To do this, click Start, click All
Programs, click Accessories, right-click Command Prompt, and then click Run
as administrator. If you are prompted for an administrator password or for a
confirmation, type the password, or click Allow/Continue.
2. Type the following command, and then press ENTER:
sfc /scannow
(The sfc /scannow command scans all protected system files and replaces
incorrect versions with correct Microsoft versions.)
Activation context generation failed for «C:\Program Files\Microsoft Visual Studio 10.0\Common7\Packages\Debugger\X64\msvsmon.exe». Dependent Assembly Microsoft.Windows.Common-Controls,language=»*»,processorArchitecture=»amd64″,
publicKeyToken=»6595b64144ccf1df»,type=»win32″,version=»6.0.0.0″ could not be found. Please use sxstrace.exe for detailed diagnosis.
I’ve got exactly the same errors with Visual Sutdio 2010 Express installed. The reason is quite clear. Windows SxS basically makes sure that each binary is run with the desired version of a dependency library. So it tries to locate the right dependency (stored in %SystemRoot%\winsxs). In this case here it reads the dependencies from the manifest files of «msvmon.exe». Unfortunately Vistual Studio installs the 64-bit debugger in Packages\Debugger\X64 even on 32-bit system. This 64-bit version of the debugger depends on the Microsoft common controls library in version 6.0.0.0 for x64 platform.
As you’re running 32-bit Windows you won’t be able to install the common controls library for x64 platform. As a result I don’t think it is possible to make this error disappear. I currently even don’t know a way to prevent Windows from analyzing the manifest and then print this error.
In fact I have never launched msvsmon.exe. It seems to be analyzed (or launched) by Windows itself. I’ve also searched the registry but did not find any reference which could make it run automatically at any point in time. So I don’t know why Windows continuously scans this file (and a couple others I’ve have similar issues) again and again and keeps complaining. I thought about Antivirus (MSSE) but it shall actually not run the binary I guess.
So the only solution left I see is to manually remove «msvsmon.exe» from my system or rename it. Unfortunately there seems also not to be any option to uninstall this component from the VisualStudio installation in order to get rid of the error. Although renaming/removing shall be quite safe as the binary anyway is not supposed to serve any purpose on 32-bit systems. It even cannot be run on 32-bit system as it is a pure 64-bit application.
CAUTION: Do not rename/remove the file on 64-bit Windows installations as it might be required there. Althoug on such systems you will likely not see the SideBySide error — or at least you would be able to install the common controls package for AMD64 architecture to solve the problem.
Hi Dale, I am receiving the exact same error as «Martins911» posted below (7/13/11 @ 8:47 PM) . Basically just a slightly different «flavor» of the VC++ 32 & 64 bit library version conflicts as the original post that you responded to. However, I feel your «solution» for anyone wanting to eliminate the flood of Event ID 33-related error messages being generated by the underlying issue(s), while well intentioned, is less than acceptable . particularly in my case!
You see, I have a brand new system with only Windows 7 Pro 64-bit and all its relevant patches/updates installed (with the exception of SP1 because I experienced other issues with that on a previous install, but that’s another story!). NOTHING else . No 3rd party applications, No Anti-Virus/Anti-Malware, etc. Call me crazy, but I consider the two options you appear to be providing as «solutions» to this error — That is, to either ignore the numerous, frequently generated Error Messages flooding the Event Log, or to spend God-knows-how-long «isolating applications and Side-by-Side Assemblies to correct the DLL versioning conflicts» — Unacceptable. It’s not MY job to debug and fix Win 7 issues for Microsoft which exist on a simple, «vanilla» install of the OS, and I don’t think it’s asking too much to expect a clean (or at least relatively clean) Event Log for a typical Win 7 install!!
So, I am formally requesting that Microsoft PLEASE create a Win 7 patch/update immediately that automatically identifies and corrects all of the Event ID 33-related errors (i.e. — x86 & x64 VC++ versioning conflicts). BTW, I’ve read many of the other posts and I do not think that the other «solution» commonly cited by Microsoft in these forums . i.e. — asking people to manually install the Run-Time libraries of one or more versions of VC++, is acceptable either given the substantial # of people that have reported not having any success with that approach. Anyway, if that was an appropriate solution, it should be automated and bundled into a self-fixing patch since the burden of fixing internal OS glitches falls solely upon Microsoft, and not its customers!
Thank you for your time, and I look forward to your reply . — Ron
