Having trouble getting TestStand 3.0 Deployment to work!

[jsharlan]

I get the following error with TestStand 3.0 and Lavbiew 7.0. The target lib (baseanly.llb) references vis that are not part of the base system, ei. Hanning Window.vi and others.
Error Code:7 Could not process LabVIEW VIs. Fix any broken VIs before rebuilding. LabVIEW error: C:\Program Files\National Instruments\LabVIEW 7.0\vi.lib\Analysis\baseanly.llb\ - source does not exist

[Rick_Francis]

Sharlan,

Error code 7 indicates a file not found error. I have seen a similar problem that was the result of a bad entry in a VI's help path. Here is what I suspect is happening:

The 3.0 Deployment Utility checks the entire VI hierarchy to insure the VI will not be broken. In 3.0 we check for help files as well as the subVIs and controls that are in the hierarchy. If the top level (or a subVI) has a bad path to a help file you would get an error similar to the one above.

To check the help file path load the VI in LabVIEW, right click on the VI's icon and select VI Properties. Change the category to documentation and check the help path field. If you see a or the path points to a file that does not exist the deployment utility wi
ll generate an error. You can get around the error by deleting the Help path entry or by adding an empty help file with the correct path.

Let me know if that solves the problem.

-Rick Francis

[jsharlan]

Rick,
Thanks for the response. I fixed some entries in some of the vi's and that got me a little farther. I also had to rename a vi "Open/Create/Replace File.vi", the forward slashes seemed to be the problem. Another problem I uncovered was a long filename in the OpenG lib (ogtk.llb, write & read_tab_page_controls_to_from_INI_file.vi).

I am now getting the following errors!
+++++++++++
Processing Workspace...
Done processing workspace file
Building...
12:20 PM
An installer is being created.
The installer is finished
The build process is done.
12:23 PM
---------------------------------------
The following merge modules are missing:
C:\Program Files\National Instruments\TestStand 3.0\Production Test Stand\fulllvoi.msm
C:\Program File
s\National Instruments\TestStand 3.0\Production Test Stand\dbsteptypes.msm
C:\Program Files\National Instruments\TestStand 3.0\Production Test Stand\dbsource.msm
. . . removed (approx 64) additional names!
C:\Program Files\National Instruments\TestStand 3.0\Production Test Stand\msvcrt.msm
C:\Program Files\National Instruments\TestStand 3.0\Production Test Stand\comcat.msm
C:\Program Files\National Instruments\TestStand 3.0\Production Test Stand\msflxgrd.msm
Error Code:26282
TestStand - Deployment Utility Splash Screen.vi >> TestStand - Distribution Wizard GUI.vi >> TestStand - Build.vi >> TestStand - Create Installer.vi >> TestStand - Set NI Paths Entries.vi >> MSI DK Add Entry to NIPaths Requested.vi

[Rick_Francis]

Sharlan,

The merge modules are missing error refers to files that by default are installed in the TestStand\redist directory. Check to see if you have a redist directory. If not you can go to the control panel Add/Remove programs and select National Instruments Software. You should get another dialog showing all of the NI software, select TestStand and 3.0 press modify. The redistributable Engine Components are the piece you are missing- insure it gets installed.

Alternately, you can use the redist files off of the 3.0 CD. There is an ini file named Deployment Utility MMPath.ini that you can edit to point to an alternate directory (such as D:\redist).

Let me know this solves the problem.

-Rick Francis

[jsharlan]

Rick,
You were correct, the redistributable Engine Components were not installed. The bad news is when I tried to install them from the CD, it said that the Cabs.w1.cab was damaged, (Internal Error 2350). So I am going to have to pursue that problem!

Thanks,
Steve

[Rick_Francis]

Steve,

The evaluation CD for TestStand 3.0 will contain that cab file. Check with the NI sales rep in your area, I think it likely they can get you an evaluation CD quickly. I could put the redist directory up for download but it is rather large (142MB).

-Rick

[jsharlan]

Rick,
I have a demo CD and am getting the same error with it! I uninstalled TestStand and re-installed, SAME error. The next step is to uninstall everything and try that.

Steve

[Rick_Francis]

Steve,

After you uninstall be sure that the TestStand\redist directory is empty. If the installer was corrupted it is difficult to say if all the files will be correctly uninstalled.

-Rick