LabVIEW 2011SP1 Error building installer: LabVIEW Run-Time Engine 2013 is missing 3 dependencies???

[TroyK]

I'm having a problem building an installer in LabVIEW 2011SP1.

It's been a while since I've tried to build an installer but it used to work fine and building executables is still working fine.

Now when I try to build the installer I get "The build was unsuccessful."

Possible reasons: Error generating preview for My Application 3.1.7.

Details:

Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:

CDK_Build_Invoke.vi.ProxyCaller >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> IB_MSI.lvclass:Build.vi >> IB_MSI.lvclass:Engine_InitializeDistribution.vi >> IB_MSI.lvclass:Report_Preview_Error.vi >> IB_Source_Container.lvclass:Report_Preview_Error.vi

Loading product deployment information
*** WARNING ***
NI LabVIEW Run-Time Engine 2013 is missing 3 dependencies. This product, or other products that depend upon NI LabVIEW Run-Time Engine 2013, may not function properly while the dependencies are missing.  Visit ni.com/info and enter the Info Code "" for more information.
 
**************
*** Error: An internal error occurred for which the cause is unknown. (Error code -41)
**************
*** Error Details:
Error in MDF API function: _MDFCommon_GetNextLogMessage
Error in MDF::GetInstance - MDF static instance is not initialized!
*** End Error Report
**************
 
Loading product deployment information
*** WARNING ***
NI LabVIEW Run-Time Engine 2013 is missing 3 dependencies. This product, or other products that depend upon NI LabVIEW Run-Time Engine 2013, may not function properly while the dependencies are missing.  Visit ni.com/info and enter the Info Code "" for more information.

The really strange thing about this is that I'm using LabVIEW 2011SP1, I don't even have LabVIEW 2013 installed, not even the runtime.

Where is the problem? Why is it even complaining about LabVIEW 2013? Has anyone seen this before?

[Norbert_B · Accepted solution]

Troy,

seeing this behavior makes me assume that you updated some components compared to the past. There are drivers from NI which do use LV components (e.g. afaik the Test Panels of DAQmx).

Did you update things? If so, why don't you have the LV 2013 RTE installed as it would be required for a full functionality of the driver?

Norbert

[TroyK]

I do have the LabVIEW 2013 discs but didn't install it.

I checked in Control Panel > Programs and Features > National Instruments Software and the LabVIEW 2013 Run-Time is not listed there.

I also checked in MAX > Software and I must have missed it the first time I looked. LabVIEW Run-Time 2013 is listed there after all.

Now I remember installing VISA 5.4 to get rid of a nasty bug. It must have installed the 2013 Run-Time when I did that.

So now I need to distribute 2 runtimes with my application?!?!

[Norbert_B]

Troy,

if you add/require the VISA RTE, you will have to distribute both LV RTE's. It will increase the size of the installer and the installation on the target machine.

But i would think that for a working application, most customers won't care for an additional RTE and the size should be reasonable. The other option would be to roll back to the (for your application) buggy version of VISA which doesn't seem to be an option.

The last option would be to update the applications code base to LV 2013 as well to have (again) only one LV RTE version: 2013.

Norbert

[TroyK]

Hmmm, looks like I'll be moving to LabVIEW 2013 after all.

I try to avoid changing runtimes too often. Upgrading an app is so much easier for my users if the runtime remains the same.

I may as well move completely to 2013 if I have to install it's runtime anyway.

Thanks for your help Norbert.

[Purushothaman]

Dear Team,

I am using LabVIEW 2013,   LabVIEW 2013 Error code (-20) building installer: 

We try build Installer we can able create  .exe  file. but not able to do Installer.

Here with attached Error building installer error code file.

How can i resolve the issue.