Systems Administrator
Are there any solutions for this issues? Log Name: Application Source: SideBySide Date: 7/29/2011 10:18:00 AM Event ID: 33 Task Category: None Level: Error Keywords: Classic User: N/A Computer: C3PATCHTEST2.C3PO 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.16816" could not be found. Please use sxstrace.exe for detailed diagnosis.Leonard Edwards
July 30th, 2011 11:48am

Found this somewhere else... 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.
Free Windows Admin Tool Kit Click here and download it now
July 30th, 2011 11:59am

Thanks. I also found that .NET Framework also causes this issue. Which is what we are running. Thanks again.Leonard Edwards
July 30th, 2011 12:49pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics