Troubleshooting C/C++ Isolated Applications and Side-by-side Assemblies - Scenario based with solutions

re: Troubleshooting C/C++ Isolated Applications and Side-by-side Assemblies - Scenario based with solutions

Ramanathan — Fri, 22 Sep 2006 22:38:32 GMT

This blog is really helpful

re: Troubleshooting C/C++ Isolated Applications and Side-by-side Assemblies - Scenario based with solutions

Swapnil — Thu, 19 Oct 2006 16:08:25 GMT

I am facing a peciliar error in production. We have migrated our MFC apps to VS 2005 and now use MFC 8.0 libraries. We get the folowing error in event log:

Generate Activation Context failed for \\network\share\MFC80.dll. Reference error message: The operation completed successfully.

Please let me know if you have faced such an error.

Thanks in advance.

Swapnil

re: Troubleshooting C/C++ Isolated Applications and Side-by-side Assemblies - Scenario based with solutions

jreddy — Thu, 19 Oct 2006 16:34:00 GMT

Are you able to run the application successfully?

If you are seeing errors only in event viewer, then the scenario 4 above may be applicable to you

re: Troubleshooting C/C++ Isolated Applications and Side-by-side Assemblies - Scenario based with solutions

Swapnil — Wed, 01 Nov 2006 18:47:17 GMT

The application freezes and is required to restart the app.

On some of the user's machines, we have to reboot. When this scenario occurs, we get that "Generate Activation Context failed" event log.

Thanks,

Swapnil

re: Troubleshooting C/C++ Isolated Applications and Side-by-side Assemblies - Scenario based with solutions

jreddy — Wed, 01 Nov 2006 19:09:08 GMT

I see that you are copying MFC80.dll into

\\network\share\.

Are you copying the manifest file also.

I mean Microsoft.VC80.MFC.manifest into the same folder.

re: Troubleshooting C/C++ Isolated Applications and Side-by-side Assemblies - Scenario based with solutions

Swapnil — Wed, 01 Nov 2006 20:54:54 GMT

yes it is in the same folder.

re: Troubleshooting C/C++ Isolated Applications and Side-by-side Assemblies - Scenario based with solutions

jreddy — Fri, 17 Nov 2006 16:09:51 GMT

would it be possible to have a repro using which i can simulate the problem?

re: Troubleshooting C/C++ Isolated Applications and Side-by-side Assemblies - Scenario based with solutions

Aris — Sat, 03 Feb 2007 05:31:50 GMT

Is it possible to statically link MFC and C libraries to application so i dont have to worry about manifest stuff ?

I have set of apps that worked fine and different machines after building with VS 2005 after i updated VS to SP1 it started throwing all kinda of different error (from side-by-side to just unable to execute and no error at all)

Apps were developed on XP but i usually want to run those on 2003

re: Troubleshooting C/C++ Isolated Applications and Side-by-side Assemblies - Scenario based with solutions

Mike Blake-Knox — Fri, 14 Sep 2007 00:19:14 GMT

I've been troubleshooting a problem that happens when our ActiveX control is started if Acrobat Reader 8.1 is installed. Our dll is built with version 50727.42 of msvcr80.dll. It seems that Acrobat provides/uses version 50727.163 and causes Windows explorer to immediately load it once Acrobat is installed. If we try to load our module, an event (Generate Activation Context failed ... component version required by the application conflicts with another component version already active.) is generated.

This seems to result from the absence of a redirect for version .42 in the .163 policy file. It works fine if I add a redirect to the .163 policy file.

re: Troubleshooting C/C++ Isolated Applications and Side-by-side Assemblies - Scenario based with solutions

Eric Gentry — Wed, 03 Oct 2007 20:31:56 GMT

When will the merge modules for debugCRT be available to support the SP1 versions of msvc*80d.dll?

re: Troubleshooting C/C++ Isolated Applications and Side-by-side Assemblies - Scenario based with solutions

jreddy — Sat, 06 Oct 2007 03:28:53 GMT

you can do that but we recommend not to do that. By doing so you might miss security updates to the runtime dll's.

If you have compiled your app using vs2005 sp1 and run it on a different system where you dont have the latest version of dll's then you will get errors.

Please install vcredist_x86.exe (with sp1 changes) on your target system.

Let me know if you need further help