LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Installer build errors 3 & -12

Hi,

I am building a LabVIEW 2012 installer with the following drivers:

NI-DAQ 9.7.5

NI-Serial 4.0

Ni-VISA 5.4.0

When I run the installer I get a pop-up window that indicates some of the installers are not available on the computer.  It directs me to insert the NI Developer Suite 2012 DS2 DVD 1 to install “NI System Components.”  So, I put the indicated DVD into the computer and press OK.  The Installer “thinks” for a while and then I get the build error that follows:

“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_Build.vi >> NI_MDF.lvlib:MDFDistCopyList_CopyItem.vi

 

 

Loading product deployment information

Adding files to installer

Validating...

Copying files...

Scanning files...

Updating files...

Build complete successfully.

Done adding files

Preparing to build deployment

Copying products from distributions

Copying distribution 'NI Developer Suite 2012 DS2 DVD 1' from: E:\ to: C:\ProgramData\National Instruments\MDF\ProductCache\

 

**************

*** Error: Windows SDK function returned an error. (Error code -12)

The system cannot find the path specified.

 

**************

*** Error Details:

Error in MDF API function: _MDFDistCopyList_CopyItem

Windows function FindFirstFile returned an error. Error code: 3

*** End Error Report

**************

 

Done building deployment”

 

Any ideas?

 

Thanks,

B

0 Kudos
Message 1 of 14
(3,073 Views)

I've also attached the build log.

 

Thanks,

B

0 Kudos
Message 2 of 14
(3,058 Views)

NI-DAQ version 9.7.5 makes me think you have a co-Install of LabVIEW 2013 or something else off the Aug 2013 DVD set or later.

 

If so, you need to configure LabVIEW 20xx for use with .NET 4.0 (see here)

 

Once you install some system components from the Aug 2013, a little birdie told me that you must target Windows XP SP3 or higher.  .NET4.0 and sp3 for Win XP may have some co-dependancies that I cannot claim to fully understand.Smiley Wink

 

 


"Should be" isn't "Is" -Jay
0 Kudos
Message 3 of 14
(3,045 Views)

Thanks for the quick reply!  I have LV 2011, 2012, & 2013 installed on my Win 8 box.

 

I followed your advice and put the config file in the same directory as the LV 2012 exe.  Here's the contents of the file:

 

<configuration>
<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5"/>
</startup>
</configuration>

 

However, I still get the same errors.

 

Any other ideas?

 

Thanks,

B

0 Kudos
Message 4 of 14
(3,028 Views)
Its 4.03.... I forget exactly. and am mobile. dig through profile page tags for .net

"Should be" isn't "Is" -Jay
0 Kudos
Message 5 of 14
(3,001 Views)

Hi Jeff,

The registry has the following keys for .net framework v4 Full:

Release = 378389

TargetVersion = 4.0.0

Version = 4.5.50709

 

Which of these values would you use and how would you build the text for the config file?  I've tried a number of combinations to no avail.  The only combination that doesn't error when I launch LabVIEW is the text I posted in the previous post.

 

Thanks,

B

0 Kudos
Message 6 of 14
(2,980 Views)

Ah, following my previous link:

 


<configuration>
<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="v4.0.30319"/>
</startup>
</configuration>


"Should be" isn't "Is" -Jay
0 Kudos
Message 7 of 14
(2,968 Views)

Thanks Jeff, that did allow LabVIEW to launch without errors.  Unfortunately I am still not successful with the build.  The errors were slightly different this time.  Here's part of the final portion of the build log.  I also attached the complete build log.

 

> Copying distribution 'NI Developer Suite 2012 DS2 DVD 1' from: E:\ to: C:\ProgramData\National Instruments\MDF\ProductCache\
Getting file list for product: NI OPC Support
Cache location: C:\ProgramData\National Instruments\MDF\ProductCache\NI OPC Support [13.0.296]\
Source location: E:\Common\Products\p104\
     Part name: opcsupp.msi
     Relative path: opcsupp\
     Full path: E:\Common\Products\p104\opcsupp\
          File(s): opcsupp.msi
               From: E:\Common\Products\p104\opcsupp\opcsupp.msi
               To: C:\ProgramData\National Instruments\MDF\ProductCache\NI OPC Support [13.0.296]\opcsupp\
          File(s): opcsupp.cab
               From: E:\Common\Products\p104\opcsupp\opcsupp.cab
               To: C:\ProgramData\National Instruments\MDF\ProductCache\NI OPC Support [13.0.296]\opcsupp\
          File(s): opcsupp_mft.cab
               From: E:\Common\Products\p104\opcsupp\opcsupp_mft.cab
               To: C:\ProgramData\National Instruments\MDF\ProductCache\NI OPC Support [13.0.296]\opcsupp\

Performing file copy

>  
> **************
> *** Error: Windows SDK function returned an error. (Error code -12)
> The system cannot find the path specified.
> **************
> *** Error Details:
> Error in MDF API function: _MDFProdPreview_GetUnavailableProducts
> Windows function FindFirstFile returned an error. Error code: 3
> *** End Error Report
> **************
>  
WARNING: Function should not be called after MDFDistCopyList_Open
Done copying products from disks

 

Any other ideas?

 

Thanks,

B

0 Kudos
Message 8 of 14
(2,954 Views)

For clarity

 

Building with 2013 App Builder supporting a LabVIEW 2012 app on Windows 8

 

(You did install versions in order right?  - repair the app builder from media containing LabVIEW 2013 and let the update advisor apply the patches)

 

This is one of those times I'd get on the horn and use my SSP to chat with a NI AE.  What are they suggesting?


"Should be" isn't "Is" -Jay
0 Kudos
Message 9 of 14
(2,947 Views)

I am building using LabVIEW 2012.  Not sure if this is utilizing the 2013 app builder behind the scenes or not?  I installed 2012 first and then subsequently installed 2013.  I don't recall seeing anything about repairing the app builder or applying patches during the 2013 install...

 

I will wait to hear from an NI AE on this post and call in if necessary.  Thanks so much for all your help!

 

B

0 Kudos
Message 10 of 14
(2,940 Views)