MSVCR90.DLL Error when start LabVIEW 2009

[tom_z]

Hi,

   My LabVIEW 2009 failed to start. It pops up a window says fault module MSVCR90.DLL. I have reinstalled LabVIEW but the problem is still there. Anybody has similar problem before?

   Thanks for help!

   Tom

[James_W]

MSVCR70.dll is a DLL associated with the Microsoft Visual C compiler - if I remember correctly.

LabVIEW definititly installs somthing lliek this with the Mobile module, so maybe it's the addional modules you need to install, or maybe you have 2 copies of the dll on your system now - 1 from Visual C, and 1 from LabVIEW.

Hope this helps point you on your way to debugging your problem.

Try removing bothe the Microsoft Compiler and LabVIEW, then start again.

James

[pericles]

Hi!

I have similar problem as you discussed above : LabView (2010 32b) loads and executes a VI properly, but if this VI is loaded as a step in a TestStand sequence (TS Version 2010 , development environment) the LabView crashes wirh an error message:

Error in a module MVSCR90.dll version 9.0.30729.6161.

I have found a lot of MVSCR90.dll on this computer, there is one from LabView (version 9.0.30729.1 in an NI RT Image module) and some in Microsoft Common files.

There are 2 MVSCR90.dll with the version named above (in the error message) , I found them in c:\windows\winsxs\amd64_microsoft.vc90.crt... and in c:\windows\winsxs\x86_microsoft... The have the same version.

Is it possible that Labview can't distinguish between them and uses the false ( the amd64?)? 

Regards

[tom_z]

Hi,

    Sorry to let you know but I tried all differnt methods and end up reinstall windows and labview. Hope you have better luck.

    Tom

[pericles]

And what were "different methods"? I 'm not an admministrator on this mashine and must try everything before I ask the administrator to reinstall LabView or something else.

[Wee-Bey]

Hi there.

So I have a couple questions. Have you ever been able to run this .vi previously within TestStand, or has the error always occurred? Is this a new setup, or have you been using LabVIEW successfully for a while?

There are a couple of possibilities here. It could be pointing to the wrong .dll file like you said, or it could be the case that the DLL file has been corrupted.

[pericles]

Hi,

I was able to run this TestStand sequence successfully before on another computer (Windows XP). The set up is: .NET assembly DLL is put in the directory with LabView.exe.

I have searched MSVCR90.dll on this computer and found some versions in C:\windows\WinSXS\x86_Microsoft.VC90.CRt*..Misrosoft Visual C studio is not installed on this computer.

My problems occur on another computer running under Win7. As I wrote the LabView executes the VI correctly and finds obviously proper DLLs. The problems occur only under Test Stand. 

[Wee-Bey]

One of the first things you might try is backing up the DLL file in the amd64 folder (change the extension to .dllback) and copying the other version in there, then seeing if it works or throws a different error. Then you could even do it vice versa. This might tell us a little more about what's going on.

Do you know what version of Visual Studio you're running? Does it happen to be 64-bit?

[tom_z]

Hi,

     I have try to install the dll file and also logged all  the errors.

     Tom

[pericles]

Hi,

unfortunately I can't do anything in c:\windows\... because I'm not an adnministrator. I have to wait at least a week before he comes back and maybe do it for me. There are 2 Versions of Microsoft Visual C+ installed on this comuter: 2008 and 2010. When LabView crashes and I select "Debug" there are 2 possibilities: 2008 and 2010. The msvcr90.dll which is marked as "failure" in an error message referres to Microsoft RunTime Engine 2008 (according to its properties). 

I had made another experiment: set "runTime Engine" as VI server by Test Stand. In this case VIs are marked as "erroneus" (with a red button on the module panel). I have to reload every VI (the red button stays, but the picture is loaded), then start execution and ingnore the message, that there are errors. The sequence works OK. When I close TestStand I get an error message "TestStand doesn't work any more-> SeqEdit APPCRASH". 

I think it shows, that RunTime Engine (I select the option "Recognize the version automatically") loads VIs in another way than LabView Development Environment does.