Re: Error loadin VS 2005 DLLs in Windows Vista

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

On Mar 17, 4:15 pm, "Patricio" <Patri...@xxxxxxxxxxxxxxxxx> wrote:
Hello everyone,

We have spend several days trying to make this work to no avail.

The scenario is a Legacy VC 6.0 application which we are adding new mixed
mode DLLs compiled with VS 2005.  The Legacy application works fine in
Vista, but we can not make it run when we replace a couple of DLLs with
their VS 2005 version.

1. In Windows XP (with VS2005 installed) the Legacy application ran with the
VS 2005 DLLs only after we added an application.exe.manifest with the
reference to Microsoft.VC80.CRT.  This was the expected behavior.

2. In Vista (Virtual Machine, no VS2005 install to mimic client
configuration) we added the VS2005 DLLs and the manifest and we got error
0xC0150002, which means that Windows was not able to process the application
binding information.

3. Using the Dependency Walker we see that the VS2005 DLLs have dependencies
on MSVCR80.dll, MSVCP80.dll, and MSVCM80.dll, which are the correct VS2005
C++ run-time dependencies.

4. Installing the Visual C++ 2005 Redistributable changes the error to: This
application has failed to start because MSVCR80.dll was not found.

5. Manually copying the MSVC*80 DLLs to System32 generates runtime error
R6034: An application has made an attempt to load the C runtime library
incorrectly, and then we get error 0xc0000142.

I found many post in the internet with the same errors.  Some of them have
been fixed by adding the manifest, but we had the manifest all along (even
though here,http://durgaprasad.wordpress.com/2007/06/04/r6034-c-runtime-error-in-...,
he says that he needed to "touch"the file using the Cygwin tools to force
the metadata to update).

Is there a way to debug/solve this issue?  Do we have to go to the Fusion
log?  Are we running into UAC issues?  We got the same results installing
the new DLLs as administrators.  We are using InstallShield 2008 Premier,
but I don't think that is the issue because we get the same results if we
copy the DLLs manually.

Thank you in advance for your time and help.  Regards,
Patricio.

Have you tried a "Thinstall Solution"?

If your not familar with the technology, it is a form of
virtualization, that allows you to create a single executable
that has a program and all it's dependencies built into it. It is
wonderful for Distributing Aplications,
and increasing the portability of Apps. A variety of Vendors offer
Thinstall solutions.

LanDesk's solution involves taking pre and post system snapshots,
which are compared, and
an app is compiled from the differences. But you'll need a license
for eachPC that uses a thinstaled app from their.

I've also seen a Package Development Solution (I cannot remember the
vendor), That allowsyou to create Thinstall Executables, and silent
installation apps. By using a thinstalled Ver, you canforce it to use
the working DLL's.
.

Relevant Pages

  • Re: Error loadin VS 2005 DLLs in Windows Vista
    ... how it will work deploying our new DLLs using Thinstall. ... fees per installation is a deal breaker for us, unless it is very afordable, ... The scenario is a Legacy VC 6.0 application which we are adding new mixed ... Have you tried a "Thinstall Solution"? ...
    (microsoft.public.vc.language)
  • Error loadin VS 2005 DLLs in Windows Vista
    ... The scenario is a Legacy VC 6.0 application which we are adding new mixed ... mode DLLs compiled with VS 2005. ... Using the Dependency Walker we see that the VS2005 DLLs have dependencies ... Installing the Visual C++ 2005 Redistributable changes the error to: ...
    (microsoft.public.vc.language)
  • Application failed to initialize 0xc0000022 - Access rights to System32 DLLs
    ... I had EXACTLY the same issue on our Win2k Citrix farm after installing ... We found that the ICA clients got this error ... are running fine if the user has Admin rights but if not, ... Those DLLs do not allow ANY access to ordinary ...
    (microsoft.public.vb.general.discussion)
  • Re: directx redistribution
    ... and tried installing it on another machine. ... If you were referanceing the dlls in the project directory you ... > I would remove the referances to the MDX files and re add them making sure ... >> including a copy of the direct3d dlls in the target folder. ...
    (microsoft.public.win32.programmer.directx.managed)
  • Re: location of MFC71*.dlls when installing a program ?
    ... A local copy of the MFC DLLs doesn't take up too much room and you are always assured that your program will have the DLLs you intended to run it with. ... MSFT does not recommend touching sys32 with your libraries. ... Also, when you are installing it local, chances of it being deleted by ...
    (microsoft.public.vc.mfc)