Teststand deployment error -17500

Just wondering if anyone had seen this error before (also attached jpg):-
Starting Log.
Processing Workspace...
Done processing workspace file
Error Code:-17500
Unknown System Error in TestStand - Read Seq Files in Workspace.vi->TestStand - Find Dependent Files.vi->TestStand - Add File and Dependent Files.vi->TestStand - Process Workspace File.vi->TestStand - Update File Info.vi->TestStand - Distribution Wizard GUI.vi->TestStand - Deployment Utility Splash Screen.vi
+++++++++++++++++++++++++++++++++++++++
My build hasn't been changed - I simply got the latest versions of files from sourcsafe and went for a build. I've tried rolling back to previous versions of sequences and vi's but still get the same error. The error isn't particularly specific so I'm not really too sure where to start debugging it - especially when it appears nothing has changed!
Any replies appreciated.
Message Edited by davidpcl on 04-25-2006 05:28 AM
David Clark
CLA | CTA
CLA Design Ltd
Hampshire, England
Attachments:
Teststand Build Error.jpg ‏44 KB

Hi,
here is a link with the same symptoms as yourself. Doesn't look like it was resolved but may highlight something for you to check.
http://forums.ni.com/ni/board/message?board.id=330&message.id=9578&query.id=86918#M9578
Regards
Ray Farmer
Regards
Ray Farmer

Similar Messages

Teststand deployment error without error number and listing out error module

Hi,
I have been getting an error message mentioned below,
While Processing VIs...
Error: Unable to find all subVIs from saved VIs. Either a subVI is missing or the VI is not saved in the current LabVIEW version.
Please consult TestStand online help to get more information on how to resolve deployment errors.
Can anyone help me out to fix this this ?
Things tried so far;
Opening all the top level VIs, subVIs and save all
Mass compiling of instrument driver folder and other almost all the fielders
More info:
LabVIEW version: LabVIEW 10.0.1
TestStand Version: TestStand 2010 SP1
Thank you
Adarsh

try running up the seqeditor with the labview adapter set to the RTE and then load your sequence files to see if this helps with identifying which VIs are having problems.
Also dont forget to mass compile the TestStand area as these have VI's that might be called up in your Code modules.
Regards
Ray Farmer

Teststand deployment error

I am getting the following error when I try to create my Teststand deployment files from my workspace:
Error Code:1035
Could not process LabVIEW VIs. Fix any broken VIs before rebuilding. LabVIEW error:
Invoke Node in TestStand - Dist Chg and Save VIs.vi->TestStand - Dist Build LLB Image.vi->TestStand - Build VI Distribution.vi->TestStand - Build VI Distribution AX Wrapper.vi->TestStand - Build VI Distribution AX Wrapper.vi.ProxyCaller
Anyone know what's happening here or how to fix the broken vi's this references?

Hi,
Check that all your VI's are Ok and that there are no broken arrows. One way would be to mas compile your LLB's/VI's that you are trying to deploy.
Regards
Ray Farmer
Regards
Ray Farmer

TestStand Deployment Error Code 1055 when using LabVIEW Storage VIs

After a couple of days of playing with the TestStand Deployment. I final tracked down the VI that was causing this Error.
It was using thethe LabVIEW Storage VIs to save data to a TDM file.
My work around at the moment is to use a Wrapper VI and call this VI by reference.
That way the TestStand Deployment can't detect the Storage VIs.
I'm using LabVIEW 8.6.1 and TestStand 4.1.1 does anyone know if this issue has been address in TestStand 4.2?
Looks like the upgrade might be worth it.
Simon Holman
Software Engineer
Certified LabVIEW Developer
Certified TestStand Developer
measX GmbH & Co. KG.
http://www.measx.com
Solved!
Go to Solution.

Hi Simon,
I tested your sequence file in TestStand 4.2 and I didn't get any error! Which version of TestStand do you have? Can you post a screenshot of the complete internal error pop up?
Usually internal errors can be eliminated with the Clean Reinstall Procedure.doc, where you will remove all NI software and all references to NI software from your computer to start over with a fresh installation!
I hope these informations help you!
Best regards
Suse
Certified LabVIEW Developer (CLD)
Attachments:
Clean Reinstall Procedure.doc ‏32 KB

Deployment error:Error Code:-17500, Unknown System Error in TestStand - Read Seq Files in Workspace.vi-

Help!
When trying to deploy a test system i got the following error:
Error Code:-17500
Unknown System Error in TestStand - Read Seq Files in Workspace.vi->TestStand - Find Dependent Files.vi->TestStand - Add File and Dependent Files.vi->TestStand - Add All TestStand User Files to File Info Array.vi->TestStand - Update File Info.vi->TestStand - Distribution Wizard GUI.vi->TestStand - Deployment Utility Splash Screen.vi
I then tried to re-deploy previously successfully deployed systems - same error. (I have done nothing to my teststand setup/installation/engine or deployment files since the last successful deployment)
I removed teststand & then re-installed it - i still got the same error. These files it is searching for do not exist on my pc.
Any ideas what has gone wrong/how to fix it?
cheers
Fi

I've just had exactly the same problem and after posting a message, have been forwarded to this thread. Luckily it looks as though we've found a solution, or a cause of the problem. One of my work colleagues (SercoSteve on discussion forums) suggested removing the Teststand 3.1\cfg directory, and replacing it with a default one from another machine, and this seems to have done the trick and made the deployment wizard be able to analyse the files and build. We are editing files in cfg so I've now got the task of replacing each file in this directory one by one to find which is causing the problem.
I'll add another post when I find out which one it is.
David Clark
CLA | CTA
CLA Design Ltd
Hampshire, England

TestStand GUI (TestExec.exe) randomly reports error -17500 (TestStand SeqEdit R6025-pure virtual call)

Using Labview 2009 and TestStand 4.1, I have developed a test solution.
Found that I get the intermittent Error -17500 appear while running my sequence file using the TestExec.exe (TestStand simple user interface), which then abort testing.
I then used the TestStand Sequence editor to run my seq file, and again, I get an intermittent failure, but this time it reports:
Microsoft C++ Runtime Library Error, R6025 - pure virtual call - seqedit.exe
Seems this must be a Labview/TestStand bug.
Anyone ever come across this ? Very annoying bug this as it stops our production line.
Thanks
Solved!
Go to Solution.

Do you have any dll calls or only LabVIEW VI calls? Do your LabVIEW VIs call into dlls?
This error can happen if a dll is unloaded and then called into or if memory is getting corrupted, there are probably other things that can cause this error as well.
It's much easier to have such bugs in C/C++ dlls then it is with LabVIEW VIs, that is why I'm asking what type of code modules you are using.
If the problem is easily reproducible, can you try narrowing down which part of your sequence is required for the problem to occur? Also, if you are using the LabVIEW runtime can you try switching to running your code modules in the labview development environment and see what happens. For example, does the LabVIEW process now crash instead of the TestStand one?
Hope this helps,
-Doug

TestStand Deployment Utility Error

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
Solved!
Go to Solution.

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?
Regards,
Shawn S. | NIC
Instrument Driver/IVI PSE
National Instruments

TestStand Deployment build Internal error code 6625

I use TestStand 4.2 create a sequence which call LabVIEW code mouldes. All LabView code moudles are developed by LabVIEW 8.5.
I want to deploy it so use TestStand Deployment Utility. An error is occur when build. The log is as below:
+++++++++++++++++++++++++++++++++++++++
Starting Analysis
Processing Workspace...
Done processing workspace file
Finished Analysis
Building...
12:33
Internal error code 6625 Processing VIs...
Could not process LabVIEW VIs. Fix any broken VIs before rebuilding. LabVIEW error:
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中的Exception occured in LabVIEW: LabVIEW: File version is later than the current LabVIEW version.
An installer was not created due to an error
The build process is done.
12:33
Aborted
I already configured the TestStand adapt with LabView Run-Time engine 8.5.1. Why the TestStand Deployment Utility still Dynamically Call Build VI Distribution LV 8.6?
Could anyone have answer for this?
Thanks very much.

Gregg,
Here is a bit more information to help debugging:
This code is looking at the sequence files in the image directory TestStand - Check Linkages in SubSteps.vi get all the substeps of a user defined step type and TestStand - Check Linkages in Step.vi checks for absolute paths in the code modules of those substeps. Error code 97 means a property or invoke node got a null reference. I reviewed the code and I only see one place the error could be occurring, ultimately StepType.Getsubstep is returning a null reference for some substep.
If I can get files to reproduce the error here I can find out exactly what is causing it. Since I'm sure you don't want to post your entire system, but we can narrow it down.
First this error will only happen with a user defined step type, so I would make a test sequence that contains an instance of each user defined step type you have in your system and see if deploying the test sequence also produces the error.
If you have a large number of step types I would try to narrow it down by deleting half of the steps and saving the sequence to a new path. If the new sequence still has the error you reduced the size by half. If it doesn't the other half should have the error and you still reduced the size by half. You can keep iterating until you have a reasonable number of step that reproduces the error. At that point you could post that sequence and it's dependencies, and I will find the exact problem.
-Rick Francis

TestStand Deployment build error

Hi,
I am using TestStand deployment tool for the first time. I am getting an error and I am not able to fix it. It is a reference to Query Available Printer.vi (which I don't use in my projet, unless one of the instrument driver is using it). I checked the file and it is not broken. If I just perform the analysis, everything is fine though. It is only when I build that I run into it.
I am not including any of the TestStand or System32 files in the build. I am not including User Interfaces file either. Finally, I don't install TestStand Engine or any other Drivers or Components.
Thanks
Alexandre Boyer
Here is the deployment log file :
Starting Log.
Starting Analysis
Starting to process workspace file
Done processing workspace file
Finished Analysis
Building...
1:46 PM
An installer was not created due to an error
The build is finished
1:50 PM
Aborted
Warning: You may need to add any sequence file(s) referenced by the following expression(s):
RunState.ProcessModelClient in step 'MainSequence Callback', sequence 'TestComponent', sequence file 'C:\Projets\Opnext\OTM-440 Manufacturing Test Stations\Trunk\Technical\D - Execution\TestStand 4.0\Components\User\Models\TestStandModels\ProligentSequentialModel.seq'
RunState.ProcessModelClient in step 'MainSequence Callback', sequence 'Routing Entry Point', sequence file 'C:\Projets\Opnext\OTM-440 Manufacturing Test Stations\Trunk\Technical\D - Execution\TestStand 4.0\Components\User\Models\TestStandModels\ProligentSequentialModel.seq'
RunState.ProcessModelClient in step 'MainSequence Callback', sequence 'Test UUTs', sequence file 'C:\Projets\Opnext\OTM-440 Manufacturing Test Stations\Trunk\Technical\D - Execution\TestStand 4.0\Components\User\Models\TestStandModels\ProligentSequentialModel.seq'
Locals.ModelPath in step 'Call PostUUT of the Process Model', sequence 'PostUUT', sequence file 'C:\Projets\Opnext\OTM-440 Manufacturing Test Stations\Trunk\Technical\D - Execution\TestStand 4.0\Components\User\Callbacks\Station\StationCallbacks.seq'
Locals.ModelPath in step 'Call PreUUT of the Process Model', sequence 'PreUUT', sequence file 'C:\Projets\Opnext\OTM-440 Manufacturing Test Stations\Trunk\Technical\D - Execution\TestStand 4.0\Components\User\Callbacks\Station\StationCallbacks.seq'
Locals.ModelPath in step 'Call PostUUT of the Process Model', sequence 'PostUUT', sequence file 'C:\Documents and Settings\All Users\Documents\National Instruments\TestStand 4.1.1\Components\Callbacks\Station\StationCallbacks.seq'
Locals.ModelPath in step 'Call PreUUT of the Process Model', sequence 'PreUUT', sequence file 'C:\Documents and Settings\All Users\Documents\National Instruments\TestStand 4.1.1\Components\Callbacks\Station\StationCallbacks.seq'
Warning: The following dependencies were detected but not selected; you must decide if they should be included:
C:\WINDOWS\system32\kernel32.dll
C:\WINDOWS\system32\user32.dll
C:\WINDOWS\system32\advapi32.dll
C:\WINDOWS\system32\ole32.dll
C:\WINDOWS\system32\version.dll
C:\WINDOWS\system32\SHLWAPI.dll
C:\WINDOWS\system32\msvcrt.dll
C:\WINDOWS\system32\mscoree.dll
C:\WINDOWS\system32\KERNEL32.dll
C:\WINDOWS\system32\ntdll.dll
C:\WINDOWS\system32\USER32.dll
C:\WINDOWS\system32\GDI32.dll
C:\WINDOWS\system32\ADVAPI32.dll
C:\WINDOWS\system32\RPCRT4.dll
C:\WINDOWS\system32\Secur32.dll
Error: Unable to find all subVIs from saved VIs, either a subVI is missing or the VI is not saved under the current LabVIEW version.
The missing file path is:C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\printing\Query Available Printers.vi
while Processing VIs...
+++++++++++++++++++++++++++++++++++++++

Do you have the sequence files in your project that it lists?
C:\Projets\Opnext\OTM-440 Manufacturing Test
Stations\Trunk\Technical\D - Execution\TestStand
4.0\Components\User\Models\TestStandModels\ProligentSequentialModel.seq
I recommend going over chapter 14 of the TestStand reference manual with a clean sequence and attempting to deploy to a clean computer. Once you can get that to work, deploying with your actual code is much easier.
http://digital.ni.com/manuals.nsf/websearch/D4A50986EECCF7218625757C00697617
Richard S -- National Instruments --Applications Engineer -- Data Acquisition with TestStand

Getting error 1035 using teststand deployment.

Whenever I do a Teststand deployment and I select to password protect my VI's, I get a very freindly and descriptive: Error 1035. I assume (because I am a LV user and have been trained to decode cryptic error messages) that this means that one of my VI's cannot be password protected. Any help is appreaciated.
Michael Aivaliotis
VI Shots LLC

Hi Michael,
I have been able to reproduce the error on my end and I have something I would like you to try.
The proper way to deploy a Project Library (*.lvlib) from TestStand is
to insert a Deploy Library step before you call the VI with the shared
variables. To get the Deploy Library step you right click in your
sequence and go to Insert Step » LabVIEW Utility » Deploy Library.
Right click on this step and go to Configure Deploy Library... Change
the Library Path to the Project Library (*.lvlib) that contains your
shared variables. Set the Operation to Deploy. When you are done
calling the VIs, you need to Undeploy using the
same step. Set the Operation to Undeploy.
Also, make sure you add the .lvlib file to the workspace as well. In the example you posted, when I completed these steps, I could build the deployment successfully. I hope this helps!
Matt S
National Instruments
Applications Engineer

Using LabVIEW RTE vs. LabVIEW ActiveX Automation Server (TestStand LVRTS) for a TestStand Deployment and experienceing Unabel to Launch LabVIEW.Application ActiveX Automation Server Error 18001

I am developing in TestStand 4.2.1 and LabVIEW 2009, I have accomplished the following:
1. Deployment package is built and deployed on PC
2. PC has activated TestStand Deployment License
3. LabVIEW 2009 RTE was selected as the adapter for the sequence and thus I believe the deployed testexec.ini contains this.
I am experiencing the following error: "see attachment".
Is the LabVIEW RTE the right selection?
Is there something I may have missed in building the deployment?
Do I need to register the ActiveX server.
THere seems to be conflicing solutions based on Version of TestStand and LabVIEW!!
Thanks!!
Attachments:
TS_LV ActiveX Error.doc ‏77 KB

Howdy mobiux,
Please consider KnowledgeBase 4V58058Z: -18001 Errors in TestStand. If you're using Vista or Windows 7, then this may apply as well. You might also consider ensuring you have the proper LV version active in the TS Adapter Options.
Warm regards,
pBerg

Unable to include Operator Interface in TestStand deployment

Hello. I have created a test system using TestStand 3.5.
There is only one sequence file, and this sequence calls several VIs
that I have created in LabVIEW 8.0. I would like to distribute
this test system to a target computer, which will then run the default
Operator Interface. No bells and whistles, just plain and
simple. However, I'm running into problems.
First, I created a Workspace file in TestStand. I then added a
Project to it. In the Project, I added all necessary files for my
project (the sequence file as well as all of the custom VIs).
Then I proceeded to follow the TestStand reference manual in order to
deploy my system.
For reference, text in italics is the reference guide and text in bold is my comments.
Deploying the TestStand Engine
1. Launch the TestStand Deployment Utility by selecting Tools»Deploy
TestStand System from within the sequence editor.
I did this, and set up my build how I wanted it.
2. On the System Source tab, enable the Deploy Files in TestStand User
Directories option.
This option collects files from the <TestStand>\...\User
directories, so that any customizations that you have made to process
models, step types, language strings, and so on, will be distributed to
the target computer.
I did this, and copied my Operator Interfaces\NI folder to Operator
Interfaces\User. This would assure (I hope) that I would have the
default operator interfaces included in my project.
3. On the Installer Options tab, enable the Install TestStand Engine
option.
Done.
4. On the Installer Options tab, click Engine Options to launch the
TestStand Engine Options dialog box, which you use to select the
TestStand components that should be present in the installer.
Done. Everything is checked.
In the TestStand Engine Options dialog box, expand Operator
Interfaces»Full-Featured in the tree view.
a. Click the X next to LabWindows/CVI to include the
Full-Featured LabWindows/CVI Operator Interface in the engine
installation. The X should become a green checkmark.
b. Click OK to accept the new settings and close the dialog box.
This is where things go wrong. There is NO Operator Interfaces box in my tree view. It simply doesn't exist.
I've tried several different builds using different strategies.
I've done builds with the CVI operator interface in the User directory,
and I've also tried copying over the files manually. On the
target computer, I've always gotten either an error message (Could not
open the TestStand Engine), or else TestStand opens in evaluation
mode. In both cases, my custom VIs and sequence files are nowhere
to be seen. Can anyone shed some light on this? It's
driving me a bit crazy!
Thanks very much,
Brett Gildersleeve

Hi Brett,
Whenever you deploy your TestStand application to target machines, you will always needs a license. The licenses for distributing TestStand are different than for distributing LabVIEW and LabWindows/CVI code modules.
LabVIEW does not require you to purchase any run-time licenses for a deployment system. You can even run LabVIEW VIs in VI format (not executables) from TestStand without using the development environment and without an additional license.
In order to run LabWindows/CVI code modules, you will need the LabWindows/CVI Run-Time engine which is also available free of charge.
Regarding TestStand, you will need a license for each machine that runs a TestStand sequence. TestStand has three types of licenses which are the TestStand Development System License, the TestStand Debug Deployment Environment License, and the TestStand Base Deployment Engine License.
TestStand Development System License
The TestStand Development System License is required for any test sequence development and/or editing of existing TestStand sequence files that you perform within the TestStand Sequence Editor or programmatically using the TestStand API.
TestStand Debug Deployment Environment License
The TestStand Debug Deployment Environment License gives you maximum flexibility for deploying TestStand and LabVIEW, LabWindows/CVI, and Measurement Studio-based systems. This license allows you to install the development versions of TestStand, LabVIEW, LabWindows/CVI, and Measurement Studio, along with any corresponding add-on toolkits, so that you can debug your test application on your deployed test station. This license does not include the ability to perform any development tasks within the TestStand Sequence Editor or programmatically using the TestStand API.
The TestStand Debug Deployment Environment License has debugging capabilities including settings breakpoints, monitoring variable values, and stepping into test code directly from the TestStand sequence.
(Note: This license does not provide the software but rather gives you the right to install a previously purchased piece of software on the target machine.)
TestStand Base Deployment Engine License
The TestStand Base Deployment Engine License is the minimum license required for all deployed TestStand-based applications. This license allows you to deploy the TestStand Engine, a TestStand Operator Interface, and TestStand sequence files to the single test station for which the license is applicable.
The TestStand Base Deployment Engine License provides simple sequence debugging capabilities, including setting breakpoints and single stepping through test sequences in your Operator Interface. You cannot save sequences and open the sequence editor.
I hope this clears things up.
Best Regards,
Jonathan N.
National Instruments

TestStand Deplyment Error- Error: Unable to locate all subVIs from saved VIs because a subVI is missing

Hi,
I am a Systems and Software Engineer based in Vancouver. I developed an automated test system using LabVIEW 2013 and TestStand 2013 with custom operator interface.
I encountered 'missing VIs' problem which is kind of weird because I passed analyzing the sequence for both TestStand Sequence Editor and TestStand Deployment Utility >> Distrubuted Files Tab.
But when I tried building the installer and reaching the point 'Calling distribution VIs, it always throw an error saying 'An error occurred while trying to read the depencies of the VIs, possible because the VIs are not saved in the current version of LabVIEW. Do you want to save any modified now?'. I tried both cases (i.e. Yes and No) for this option but it did not solve the issue.
This is part of the original error message displayed in TestStand Deployment Utility:
While Processing VIs...
Error: Unable to locate all subVIs from saved VIs because a subVI is missing or the VI is not saved in the current version of LabVIEW.
The call chain to missing VIs:
1 - ATE_AccelerometerTest.vi
2 - CreateAndMergeErrors.vi (missing)
3 - LogControl_CheckForErrorSendUpdates.vi (missing) "
All missing VIs are coming from userlib.
Actions Done:
- Analyzed sequence file using TestStand Sequence Editor and TestStand Deployment Utility
- Verified 'Search Directories' include all necessary files/dependencies.
- Mass compile the directory of the missing VIs
- Added all needed files and folders in the workspace file.
The result is still the same based from the actions done.
The last debugging I did earlier is that I tried locating the sequence and steps of missing VIs as mentioned above (e.g. ATE_AccelerometerTest.vi)
and I found out that the step seems to be an empty action step. Would this be possible even if it already passed the analysis?
Other considerations include:
I am using LabVIEW 2013 sp1 and TestStand 2013. We tried building from three (3) computers and we only succeeded once to a freshly-installed comptuer.
Hope to hear from you soon.
With Best Regards,
Michael Panganiban
Systems and Software Engineer
www.synovus.ca
[email protected]

Hi All,
We were able to resolve the issue. First to note is that the release notes in TestStand 2013 is outdated and we confirmed from NI Engineer in Austin that TestStand 2013 works fine with LabVIEW 2013 SP1.
Secondly, we played around TestStand Deployment option that resolved the issue. Attached are the images.
We just enabled the 'Remove Unused VI Components'. It could be one of the libraries (lvlib) we included in the build but we haven't figured it out yet because we verified that all VIs are working. It could be also something else that I think very difficult to find based from the information. However, if anybody experienced the same issue, this could be helpful.
Again, we revert back in using TestStand 2013 and LabVIEW 2013 SP1.
I appreciate any comments and feedbacks. Otherwise, you can close this support request.
Thank you.
With Best Regards,
Michael Panganiban
Systems and Software Engineer

Why do I get error -17500 when calling a batch file using the call executable step type?

I am calling a batch file using the call executable step type. If the path to the batch file contains a space I get error -17500 and a message stating there was an error in "Post". For example the path to the batch file is "c:\TestWin\Test Files\...\Program.bat" When I run this I get the above mentioned error, however if I change my directory structure so the path is now "c:\TestWin\TestFiles\...\Program.bat" it runs fine. I use the browse feature to find my batch file so it is not me typing in a path incorrectly. I have removed the batch file and I get a different error stating that it couldn't find the file so it appears that for my error it can find the file but can't run it. I am
sure that this has something to do with the fact that batch files are written in DOS but really don't want to resort to changing my directory structure on all my test stations. Is there any way to fix this problem so I can leave a space in my path?

It appears I have figured it out. This was on another computer so I was unaware of how they used their computer. I like you got it to work in the temp directory and in fact got the program.bat file to work as long as I put it under the temp directory, but when I switched out to my TestWin directory it wouldn't work, so I removed everything from the directory except the batch file it self and it work. What I found out after adding files in one at a time is that the person had a file called "Test" with no file extension in there "c:\TestWin\" directory. Removing this file made it work. Putting the file back broke it. So it appeares that when teststand was running it followed the path saw a space and attempted to grab the "Test" file instead of bro
wsing into the "Test Files" directory. If you create a file in your temp directory called "temp" with no file extension you will see the same problem. Thank you for your help.

Problem with deploying FPGA host VIs using TestStand deployment utility

I am using a PCI-7831R FPGA to control an automated test fixture. I have several host VI's that I am calling from TestStand (4.2.1) in order to control the 7831R. The host VI's that TestStand calls are setup as sub-VI's and are used for various things such as opening an FPGA reference (which is bound to a strict type def), downloading and executing the files on the 7831R, reading writing to controls, and finally closing the reference. In the sequence file, I am passing the reference values as a file global so that the host sub-VI's can communicate correctly. I have all functionality working correctly in TestStand on my development PC. When I go to deploy this to a production PC, I get errors when the sequence file trys to load the first host VI. The error basically states that the VI is broken - try to open and run it (which I can't because I have no development license on the production PC). I am currently trying to deploy this to another development PC to see if I can track down where the VI might be breaking.
I have included the lvbitx and strict type def control that the host subVI's reference in my deployment files. I can't think of anything that I might be missing. Is there any good documentation on exactly which files I need to include in the deployment when using FPGA Host VIs (the TestStand reference manual is pretty vague at best)? It seems that any documentation that I read says the TestStand deployment utility will analyze all VI dependencies (other than shared variables). On a side question, is the strict type def considered a shared variable?
Has anyone successfully deployed a sequence that calls host VI's? Any help would be greatly appreciated. If any of the above needs further clarification please ask away and I will be happy to give more details.
Thanks,
Mike

Hi hawkstringer
Do you encounter this problem using a deployed version of your code? Note that the subject of this topic is about deploying an FPGA application.
I forgot I posted here, in the mean time I've managed to deploy my application. I think my problem was solved when I included all necessary drivers and components (but I'm not absolutely sure). I included the following:
NI IVI Compliance Package
NI FlexRIO
NI PXI Platform Services Configuration Support
NI R Series Multifunction RIO
NI DAQmx Core Runtime
NI DAQmx MAX Configuration Support
NI RIO
Good luck!

Teststand deployment error -17500

Similar Messages

Maybe you are looking for