TestStand Deployment Utility Error

[ShawTestEng]

I am getting the error below when attempting to build a TestStand deployment.  I am running TestStand 4.2.1.83 and LabVIEW 2009 Service Pack 1 Version 9.0.1f3.  Any help would be appreciated as I cannot find any of the VIs mentioned in the error.  Thanks!

Starting Log.
Starting Analysis
Processing Workspace...
Workspace Processed
Finished Analysis
Building...
10:15 AM
Internal error code 6503 Processing VIs...
Could not process LabVIEW VIs. Fix any broken VIs before rebuilding. LabVIEW error:
Exception occured in LabVIEW: LabVIEW:  The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located. Select <b>File>>Open</b> to open the VI and then verify that you are able to run it. in Dynamically Call Build VI Distribution LV 8.6 or Above - TestStand.vi->TestStand - Call Build VI Distribution for Unique VI Hierarchies LV 8.6 or Above.vi->TestStand - Package VIs.vi->TestStand - Build.vi->TestStand - Distribution Wizard GUI.vi->TestStand - Deployment Utility Splash Screen.vi
An installer was not created due to an error
The build process is done.
10:15 AM
Aborted

[ShawTestEng]

The above error does not appear to be due to my sequence files or VIs, but rather the TestStand Deployment Utility itself!  I tried the "Deploying the TestStand Engine" example in the TestStand Reference Manual (May 2009) and received the same error code 6503 as above.  I went through and ensured all the required patches were installed, not sure what to try next??? Any assistance is greatly appreciated, thanks!

[Shawn_S.]

Hello George Mah,

I found CARs # 258761 and # 3OP9RE6I for TestStand which may be related to this issue and to error 6503.  The error was created because VIs with duplicate names were included in a deployment.  Would you verify that you do not have any duplicate VIs in your project?  Are you noticing anything else strange with your deployments?  Have you tried creating a blank deployment that only includes the TestStand engine or a run-time engine?  

[ShawTestEng · Accepted solution]

Hi Shawn,

I did get the same error when trying to create a blank deployment containing only the TestStand engine.  I believe the issue may have been related to VIs with duplicate names (not my VIs, but NI provided VIs) as I managed to resolve my issue by uninstalling all my NI software and then reinstalling only my latest software versions of TestStand 4.2.1 and LabVIEW 2009 SP1.  My previous installation was from earlier versions that were updated over time and that may have resulted in duplicated VIs?

Thanks for your assistance.

George