after installing the LV evaluation a mclmcrrt79.dll missing and prevent LV run

[amit.ezer]

after installing the LV2011 evaluation a mclmcrrt79.dll missing error appears and prevent proper LV run, i can not run demos or open any VI.

the operation system is windows 7, previously i had an XP OS and everything worked fine...

please advice, thanks 

Amit

[KatieC]

Amit, 

Does this occur when you run examples from the included LabVIEW example finder? If so, try repairing LabVIEW through the control panel through programs and features. If that doesn't work, then try uninstalling and reinstalling. If you had installed using a disc, try downloading it from the website instead. You shouldn't need that dll to run the examples included in LV. 

I googled the dll, and found this link that may be helpful to you as well. 

Let me know if that eliminates the error!

Katie

[agrunnet2]

You probably got the message “mclmcrrt79.dll is missing” as soon as you launched your VI (which includes a DLL which calls the MatLab Runtime engine)

This error means that the MatLab runtime engine cannot be found, even though you had installed it.  

The fix:

The MatLab run-time engine installer is not properly updating the System Path during the installation on Windows 7.

1. Exit LabVIEW

2. Locate the MatLab Runtime engine folder.  It is most likely in the following location:

        C:\Program Files\MATLAB\MATLAB Compiler Runtime\v79\runtime\win32 

(it may be a different version like v76. Make sure that you are using the correct MatLab runtime engine or you will get this error again even afgter you apply this fix.  The correct version is the one required by your own program)

3. In the Windows Start search field type in “path” and you will see “Edit the system environmental variables”.  Select this.

4. In the Window that opens, in the bottom half under “system variables”, scroll down and select “Path” and press the “Edit” button

5. At the end of the string ending with “;” add the Matlab runtime engine path shown above in (2).

Now go to your VI and try to run your VI again. (You may have to reboot your PC but I dont think it is neccessary)

I hope this helps.