I just installed LV2011 and one dll from my vi won't load with the error "application configuration is incorrect"

[u87]

I just installed LV2011 and one dll from my vi won't load with the error "application configuration is incorrect", which is Windows lingo for "missing package dependencies".  All the computers at my company with 2010 loaded seem to do OK.  When I do a Dependencies Walk I get missing Visual C debug dll's missing plus IEshims and wer which both have a whole tree of dependencies missing on my machine.  The Windows install is the same "Windows XP version 2002 Service Pack 3" on my PC and the working PC's. So I'm thinking I have to uninstall 2011 and go back to 2010.  Is this correct?  Those VC debug dll's were installed on the machines with 2010 in them but were not installed in mine.

I've heard the advice to recompile the dll with debug turned off but I don't have access to the source code.

Thanks in advance.

..

[rolfk]

What DLL is it? If it is a NI supplied DLL then you should file a bug report with them as NI should not distribute debug DLLs at all. If it is from somewhere else you have to contact the supplier. LabVIEW does NOT install debug runtime DLLs. It couldn't do that legally since MS does not allow to distribute those DLLs. The only way to get legally Debug runtime DLLs on your computer is by installing the Visual C development environment.

[u87]

Thanks for the reply.  This at least tells me that going back to LV2010 is not likely to solve the problem.  The missing dll's are:

MFC90D.dll

MSVCR90D.dll

IESHMS.dll

WER.dll

And, once again, IESHMS and WER have other dependencies.  So perhaps i need to install the Visual C++ development environment.

[rolfk]

---

@u87 wrote:

Thanks for the reply.  This at least tells me that going back to LV2010 is not likely to solve the problem.  The missing dll's are:

MFC90D.dll

MSVCR90D.dll

IESHMS.dll

WER.dll

And, once again, IESHMS and WER have other dependencies.  So perhaps i need to install the Visual C++ development environment.

---

IESHIMS.dll is an Internet Explorer DLL that gets usually delay loaded by shdocvw.dll. As delay load it can not cause DLL load errors but only runtime errors. Maybe your DLL has it as direct dependency but that is unlikely since it does not have a documented interface.

WER.dll is Windows error reporting for Vista/Win7.

MFC90D.dll is the Microsoft Foundation classes and MSVCR90D.dll is the MS C runtime library, both as debug variant.

So all the DLLs you mention are actually MS DLLs! You haven't identified the DLL that you try to access in LabVIEW that causes these error messages. IESHIMS and WER are usually delay loaded by any component that needs it and should not likely be used by non MS code.

What is the DLL you try to load into LabVIEW and by whom? Get the provider of that DLL to provide you a non Debug build of the DLL. Installing Visual C on all the machines just to make the DLL load is not a solution, besides that it is likely not legal since I doubt you have that many licenses.