LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How to correct the Local Cache paths for Additional Installers

NI Software : LabVIEW version 8.5.1
OS : Windows XP

After upgraded to LabVIEW 8.5.1, I received the following error message during the build.

*** Error: Windows SDK function returned an error. (Error code -12) The system cannot find the path specified.

Researching the problem revealed cause is due to the Local Cache paths for several Additional Installers being incorrect.  If I try to correct these path or change them back to the network installer I receive an error message stating I cannot change the path.

For example, here's the detail for one of the additional installers required for my application.

NI Measurement & Automation Explorer 4.4.1
Distribution title: Local Cache
Installer source location: C:\Program Files\National Instruments\Shared\ProductCache

Actual local cache folder location: C:\Program Files\National Instruments\Shared\ProductCache\NI Measurement & Automation Explorer 4.4.1 [4.4.13009]

If I try to change the path the following error message is displayed and the path reverts to the original folder.
{C5C70081-39C0-4EBF-BC13-EFF5DC231945] has been cached to your local hard drive. You cannot change its location.

Does anyone know how to modify the Local Cache paths for Additional Installers?
Is there an INI or similar file where these are defined?

Thanks for any suggestions.

 

 

LabVIEW 5.0 seems so long ago...
0 Kudos
Message 1 of 11
(6,447 Views)

Hi jrjones,

The local cache paths are stored in registry keys.  You can modify the registry through the following steps:

1. Select Start > Run and enter regedit
2. To create a backup copy of the registry, select File > Export from the Registry Editor window
3. Make sure the Export Range is set to All, and save the registry
4. Browse to HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\Common\Installer\ProductCache, find the correct key, and modify the path as necessary

 

Jennifer R.
National Instruments
Applications Engineer
Message 2 of 11
(6,419 Views)
Jennifer,
 
Thanks for the additional information and suggestions.  However, before I continue to make modifications I want to provide additional details and get your feedback.  When checking the registry entry for the previous example, NI-MAX, The entries appear correct.
 
Name                           Type                    Data
(Default)                       REG_SZ             (value not set)
DeleteOnUninstall        REG_DWORD   0x00000001
FullProductPath           REG_SZ             C:\Program Files\National Instruments\Shared\ProductCache\NI Measurement & Automation Explorer 4.4.1 [4.4.13009]\
UserPoductRoot          REG_SZ             C:\Program Files\National Instruments\Shared\ProductCache\
 
Is the UserProductRoot supposed to match the FullProductPath which appears correct?
Most of the registry entries match this path structure, however, some have the UserProductRoot matching the FullProductPath.
The paths for the Runtime Engine match and that installer works correctly, can I assume this is the same for all Additional Installer entries?
 
Thanks for the assistance.
 
James 
LabVIEW 5.0 seems so long ago...
0 Kudos
Message 3 of 11
(6,405 Views)

Here are updates and additional details regarding this problem.
The Additional Installers selected for this application are:

NI LabVIEW Run-Time Engine 8.5.1
NI Measurement & Automation Explorer 4.4.1
NI-488.2.2.5
NI-DAQmx 8.7
NI-VISA Configuration Support 4.3
NI-VISA Runtime 4.3

These same build options worked without errors for LV 8.2.1.  Following a computer failure I updated my PC and LV installation.

I updated registry paths for all of these Additional Installers, but still receive the same error.  If any Additional Installers (other than LV Run-Time Engine) are selected the same error message appears.  The complete text of the error mesage is:

CDK_Item_OnDblClick.vi.ProxyCaller >> CDK_Item_OnDblClick.vi >> CDK_InstallerConfiguration_Editor.vi >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_Build.vi >> NI_MDF.lvlib:MDFDistCopyList_CopyItem.vi

Loading product deployment information
Loading product deployment information
Adding files to installer
Done adding files
Preparing to build deployment
Copying products from distributions
Copying distribution 'NI LabVIEW 8.5.1' from: M:\Engineering Documentation\Software\National Instruments\NI Installers\LabVIEW\LabVIEW 8.5.1\ to: C:\LV Projects 8.5\Builds\VSM Tester\VSM Installer\
 
**************
*** Error: Windows SDK function returned an error. (Error code -12)
The system cannot find the path specified.

*** End Error Report
**************
 
Done building deployment

Based on the error message, I searched the ..\Shared\ProductCache folder and located the "NI MDF Support [2.51.88]" folder, then searched and updated the registry entry for this item.  However, this change did not correct the problem.  Thanks for any additional suggestions.

LabVIEW 5.0 seems so long ago...
0 Kudos
Message 4 of 11
(6,395 Views)

Hi James,

Did you install the drivers on your machine after you upgraded to LabVIEW 8.5.1?  Were they installed from a CD, a network, or a location on your hard drive?  I noticed the message refers to drive M:\ - is that a network with installers for NI software?  I would suggest copying any installation files to your hard drive and pointing to that location as the installer source location. 



Message Edited by Jennifer_R on 08-08-2008 08:19 AM
Jennifer R.
National Instruments
Applications Engineer
0 Kudos
Message 5 of 11
(6,372 Views)

Jennifer,

The installation of LV 8.5.1 and all drivers was done at the same time from a network based installation created with the VLM 2.1 software.  I am still working on the issue and there appears to be some errors in paths in registry entries created during the installation.  If able to correct, I'll post solution to this thread.  Otherwise, I may try updating to the latest release to solve this issue (just received new DVDs yesterday).  However, that may cause problems with my application that are more difficult to correct than not being able to create an installer.

Thanks for all the suggestions.

LabVIEW 5.0 seems so long ago...
0 Kudos
Message 6 of 11
(6,366 Views)

Hi James,

When creating an installer, LabVIEW looks to the original source of the installer files - in your case the network drive.  Often times build errors are eliminated by copying the installers to the local hard drive.  Please do post any solutions.  I'm sure the community would benefit. 

I would not expect any problems to occur by upgrading to LabVIEW 8.6.  If you have specific concerns, please feel free to create a new thread to discuss the upgrade process. 

Jennifer R.
National Instruments
Applications Engineer
0 Kudos
Message 7 of 11
(6,354 Views)

Solution!!

I was finally able to get the installer build to work, even though it takes about ten minutes!!  The network and CPU activity is minimal, so I don't know what LV is waiting on during all this time?

For this installation it appears to be related to the directory structure created by the Volume License Manager 2.1 software.  There are two sets of users at my company, LabVIEW Professional and Developer Suite, which have different license numbers and installers.  The errors were related to source files located in the Products folder of the network distribution.  My installation expected the Products folder to be in a different location that it was actually placed by the VLM software.  I copied the entire Products folder from _SourceFiles up to the LabVIEW 8.5.1 folder and now it works, although very slowly.

Original Structure:

LabVIEW 8.5.1
--> _SourceFiles
 -->

 

LabVIEW 5.0 seems so long ago...
0 Kudos
Message 8 of 11
(6,309 Views)

 



Message Edited by jrjones on 08-12-2008 03:22 PM
LabVIEW 5.0 seems so long ago...
0 Kudos
Message 9 of 11
(6,309 Views)

Solution!!

I was finally able to get the installer build to work, even though it takes about ten minutes!!  The network and CPU activity is minimal, so I don't know what LV is waiting on during all this time?

For this installation it appears to be related to the directory structure created by the Volume License Manager 2.1 software.  There are two sets of users at my company, LabVIEW Professional and Developer Suite, which have different license numbers and installers.  The errors were related to source files located in the Products folder of the network distribution.  My installation expected the Products folder to be in a different location that it was actually placed by the VLM software.  I copied the entire Products folder from _SourceFiles up to the LabVIEW 8.5.1 folder and now it works, although very slowly.

LabVIEW 8.5.1
-->_SourceFiles
    -->Bin
    -->Device Drivers
    -->Licenses
    -->Products   (original location)
    -->Signal Express
-->Dev Suite
-->LV Pro
-->Products    (manual copy)

I hope this information may be of use to NI or other users.
Message Edited by jrjones on 08-12-2008 03:21 PM



Message Edited by jrjones on 08-12-2008 03:23 PM
LabVIEW 5.0 seems so long ago...
0 Kudos
Message 10 of 11
(6,309 Views)