Test Stand Execution Abort

I have a button that executes TS_ExecutionAbort. When I press that button in debug, it seems to work find but when I exit the program, I get the following error:
Global type list not empty!
Error Code: -17001
Where raised:
function: TypeUsageList:eleteGlobalTypeList
file: c:\TestStand_Autobuild\Build30\Dev\Src\tstobj2\TypeList.cpp
line: 195
compilation time: 12:31:43 Jul 31 2003
Where caught: Debugging When Exception Constructed
WARNING!!! 'destructor exception' Line 9962 in function in file c:\TestStand_Autobuild\Build30\Dev\Src\tstobj2\TestObj.cpp
Compilation Date: Jul 31 2003 Compilation Time: 12:31:41
Not all type usage lists have been destroyed!
Error Code: -17001
Where raised:
function: TypeUsageList:eleteAllTypeUsageLists
file: c:\TestStand_Autobuild\Build30\Dev\Src\tstobj2\TypeList.cpp
line: 853
compilation time: 12:31:43 Jul 31 2003
Where caught: Debugging When Exception Constructed
WARNING!!! 'destructor exception' Line 9963 in function in file c:\TestStand_Autobuild\Build30\Dev\Src\tstobj2\TestObj.cpp
Compilation Date: Jul 31 2003 Compilation Time: 12:31:41
When I press the button in release, I get popups errors while waiting for the step to finish. The errors are as follow:
ActiveX Error
sCode = 0xffffbc6c
Description: Value invalid or out of range
And
ActiveX Error
Unknown Error
My gui is compiled in CVI 7.0 and I am using teststand 3.0.
Here is my button code otherwise the cvi gui is just updating status.
int CVICALLBACK cmdAbortCallback (int panel, int control, int event, void *callbackData, int eventData1, int eventData2)
int error = 0;
ERRORINFO errorInfo;
ErrMsg errMsg;
switch (event)
case EVENT_COMMIT:
tsErrChkMsgPopup(TS_ExecutionBreak (m_oExecution, &errorInfo));
// Prompt the user to make sure he wants to abort
if (ConfirmPopup ("Abort Confirmation", "Are you sure you want to abort?"))
m_bUserAbort = TRUE;
m_eState = ABORT_PENDING;
tsErrChkMsgPopup(TS_ExecutionAbort (m_oExecution, &errorInfo));
UpdateGUI();
else
tsErrChkMsgPopup(TS_ExecutionResume (m_oExecution, &errorInfo));
break;
return(0);
Error:
return(-1);
Do any of you know why I am getting these error or how to find the problem?

To gsflat -
You appear to have created a global variable called "m_oExecution" which I assume that you have created using
CA_DuplicateObjHandle() within some callback. If you are just copying a callback parameter to your global variable, the handle may have already been released.
If you fail to call CA_DiscardObjHandle() on object handles that you duplicate before shutdown or before you reassign a new value to an already assigned variable, TestStand will not be able to release the object on shutdown and you will get these debug warnings. Failing to properly release any type of object handle can result in these warnings.
As to why you release build is erroring, you will have to determine which functions in the project that uses the tsErrChkMsgPopup
macro are failing and then figure out why.
Scott Richardson (NI)
Scott Richardson
National Instruments

Similar Messages

  • How To Trigger Test Stand To Assign Step = Error

    Hi everyone, I have a LabVIEW VI step in my sequence and I have an abort button the user can select to abort the user interface VI.  I want the "abort button" boolean to pass back to test stand that abort button = TRUE and I want the sequence step to be set to an "ERROR."  Is there a command to send to the Test Stand Engine to flag this step as an error?
    Thanks so much!
    Solved!
    Go to Solution.

    Hi
    Glad It was helpful.
    There are two ways in which you could achive this..
    1. Use this expression: RunState.Engine.TerminateAll()
    But be wary, this will terminate all the current excutions and the report indicates the status as "terminated"
    or
    2. Use this expression: RunState.Execution.Terminate()
    or
    3. You can add a Goto step (comes with teststand. You can find it under Flow Control section of the insertion palette) and select Cleanup as the destination step.
    This way you can run some clean up steps before closing the execution. (eg, Shutting down any hardware, etc.,)
    Deepak

  • Test Stand seq w/ dll batch file execution not working

    I am using Test Stand 4.1, running a seq that calls a dll.  The dll contains a batch file execution function that has not been working properly.  I am not 100% sure what the function is as I do not have access to the direct code from which the dll was created.  I believe I have a file, however please remember this is a guess that I am looking at the correct function/file. 
    This is a Pass/Fail test step that calls a batch file.  The batch file runs properly without the use of Test Stand and called by the dll.  In the code that I believe is running, I see there is a step that I am guessing does not run (see below for test steps).  It seems as though these steps are being "stepped over" and not running, however the test does seem to be entering this function.  The test reports a pass/fail status as the data is reported into a txt file.  If the txt file contains the correct data, the test step reports PASS, even though the batchfile does not run.
    :Note:  [batchfile.bat] is the name of the batch file being called; the [ ] are not present 
    // Run Batch File
     ChkErr(LaunchExecutableEx([batchfile.bat] ,windowState,&handle));   
     // Wait for batch file to complete task
     do{
      ProcessSystemEvents();
     }while(!ExecutableHasTerminated (handle));
     RetireExecutableHandle (handle);
    Any one have any suggestions as to why the batch file is not being called and running properly?
    Thank you
    Jason_C

    Thanks for the feed back.  I have realized and it seems as though sometimes the CWD varies.  The current working directory when the batch file does not run seems to be set to the desktop, not to the specified directory.  The batch file is used to program a chip, calling the exe to run using commands.  The file are speciifed by an absolute path, however the exe is not.  The batch file is as below and seems to match up with a problem with the CWD.  How can change though?  I will have to check in the Start in field, but where can I find that property? 
     Thank You
    --Jason
    del ..\misc\mplab.txt
    echo C:\Program Files\JTRS\01_P55461U\bin\uutsw\CR1_T2V3L_PMM_STUB_LOAD.hex
    ..\misc\pm3cmd /5 /BLCC:\Program Files\JTRS\01_P55461U\misc\t2v3l_pmm_stub_load\t2v3l_pmm_stub_load.pm3 /k /m /y /e >> ..\misc\mplab.txt >> ..\misc\mplab.txt
    ..\misc\pm3cmd /5 /BVCC:\Program Files\JTRS\01_P55461U\misc\t2v3l_pmm_stub_load\t2v3l_pmm_stub_load.pm3 >> ..\misc\mplab.txt

  • Test Stand 3.5 install problem

    I'm having problems installing Test Stand 3.5 Development Edition on a WinXP SP1 machine - would anyone have any suggestions.
    I'm performing a custom install and selecting all components other than "Device Drivers".
    The install fails on "NI TestStand 3.5 Support Files. Part 1 of 1" with "Error 1335. The cabinet file 'Cabs.m6' required for this installation is corrupt and cannot be used. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package".
    If I select abort at this point the install of the support files is rolled back and the remaining components apper to install correctly. I can now run Test Stand but am missing the help files. If I rerun setup it attempts to install the support files but fails with the same error.
    I have tried uninstalling and reinstalling & have copied the CD contents to the local hard disk (without any problems) and installing from there. All this is to no avail.
    I've also uninstalled and reinstalled an installation on a second machine using the same install media. This install succedded with no issues.

    What is the difference between the two machines - where you've had successful and unsuccessful installs?
    Like you've said sometimes this is caused by a faulty read from the CD drive, or faulty media, but as you've managed the install with the same media on the machine - then its not the media, and you've already tried the copy to hard disk from the CD without any luck. 
    What OS is on this other (working) machine?
    Do you have administrator privileges on the machine where you can't install the software? Is the .NET framework 1.1 installed (I think this is part of Windows XP SP 2) so this could be the issue - as TestStand requires the .NET framework 1.1
    Also - I've attached the readme which includes information to consider before installation - and known issues with the installation - check this and see if any of these could be the issue with this machine.
    I hope this helps
    Regards
    Hannah
    NIUK & Ireland
    Attachments:
    ReadMe.txt ‏51 KB

  • How to get the value of the global variable of test stand in labview User interface?

    Hi.
     Can anyone Please share examples and tell me to how access the test stand global variable using labview user interface.
    Solved!
    Go to Solution.

    I'm not surprised that what you are doing doesn't work.  The Start Execution UI Message is triggered when the user clicks a button to start an execution.  Realize that most executions go through a process model.  So you could be looking at the sequence context of the process model and not your client sequence file.
    I recommend reading that link I posted above.  UI Messages are your best bet but you cannot just piggy back on an existing UI Message like this.  They may not be getting sent at the time you need them to be.  The only way to ensure you get what you want is to trigger one yourself at the right time.
    Regards,
    jigg
    CTA, CLA
    teststandhelp.com
    ~Will work for kudos and/or BBQ~

  • How to test cloned VI file from Test-Stand

    Hi All,
    I am having one doubt in Test - Stand.
    I am having VI file which is having four controls and four indicators. I am just connecting one control with one indicator like one - one mapping. I have created connector pane for this. Say save this file as dummy1.vi.
    In another VI file I have taken four controls. These controls are connected with dummy1.vi file.  Save this file with test1.vi file. Now run the test1.vi file with highlight execution on. While it is continuosly running, double click on the sub vi files. You can see different files with clone, clone1, clone2 ...etc...
    Now I will pass values to test1.vi file from Test - Stand sequence step. In second step I want check the result from dummy1.vi file. But I am unable to do it.
    Can anybody tell me how to achieve it?
    Regards,
    Nagaraju

    Hey NagRaj,
    The reason you see the clones is because your VI is reentrant.  You can change that in the VI Properties in the Execution section.  Also, you may want to read more about that in the LabVIEW help to understand it better.
    You should have no problem testing these VIs from TestStand if you set your Step result to the value you are testing against.  I've attached an image that shows how to set the outputs of your VI to the step results.  What kind of test are you doing? (i.e. NumericLimit, StringLimit, Pass/Fail etc..)
    Is dummy1.VI a subvi of test1.VI?  If so do you have the output terminals of dummy1.vi connected to the output terminals of test1.vi to propogate the values back to TestStand.  This is assuming you only have one step in TestStand calling test1.vi which has dummy1.vi as a subvi.
    If you want two steps where one step calls test1.vi and the other calls dummy1.vi then you have to call them seperately.  They can't be tested in the same step this way.
    If this is confusing you can always post your simple example (seq and vis) and I could look and see how to better assist you.
    Regards,
    Message Edited by Sam R on 02-28-2007 09:06 AM
    jigg
    CTA, CLA
    teststandhelp.com
    ~Will work for kudos and/or BBQ~
    Attachments:
    stepresult.JPG ‏56 KB

  • Test stand crashes: "test stand has detected that your script debugging"

    05-01-201203:18 PM
    Hi everyone. I am setting up a new installation of Test stand and writing my first sequence with an existing sequence of legacy code.
    When I run the sequence and stop on the call to the DLL, and then step into the dll and I get this error:
    test stand has detected that your script debugging settings might cause visual studio to hang when attaching to the teststand process to perform this step into operation.
    To fix this problem, open internet explorer, select tools>>Internet options>> Advanced, check Browsing>>Disabl script debugging, click okay, and restart your sequence execution.
    The message is vague and it is indermanent as to whether I should "enable" or "disable" Script debugging so I tried both. Test stand then crashes again and I get the same error.
    Do I need to reboot after each crash? I'll try that next. Any ideas on how to make this error go away?
    Thank you for your help.
    Richard

    This is a duplicate. Please go here instead:
    http://forums.ni.com/t5/NI-TestStand/quot-test-stand-has-detected-that-your-script-debugging-quot/td...

  • I am trying to debug HTBasic code modules while using Test Stand, how do I refresh the subs that have been loaded in memory?

    I am writing an application for Test Stand, we are using modules previously written in HTBasic. Whenever I make a change to the code and try to re-run the program, it just runs the old version of the code. The only way to refresh the code is to close Test Stand down and restart it. Is there a way to flush the memory of modules?

    Hi,
    I haven't used HTBasic with TestStand 2.0.x, but I'm assuming that you have the steps in the sequence set to unload when sequence file is closed (look under the step properties -> run options tab).
    If you're still prototypeing, use the File->Unload all modules option. Have a look at page 4-3 in the user manual - it refers to .DLLs, but I'm assuming the HTBasic falls into the same methodology.
    Altering the run options from it's default will affect the memory useage and speed of execution of the test sequence. Have a look at page 5-22 (page 158 in the .pdf) in the TestStand user manual - basically, if a code module is loaded into memory already, when the step gets to execute, the loading overhead is already done. If it stays in memory after this, then it's avail
    able for next time (quicker second run 'cos it doesn't need to load again. However, the balanceing factor is the sequence is useing more memory at a time, by haveing the module ready.
    My usual setting is to use Load dynamically, and Unload after sequence executes. I use this is only during development however, as this is not the most speed friendly, but a compromise so that if I don't call a step I don't load it, but if I do use a step, I'm sure it's free again when I need to modify the .dll modules I create. If you have a look on page 5-7 (143) of the user manual you can set the sequence file to effectively over-ride each step's load and unload settings - useful if you want to revert back again later. If you use this, you'll see that the top two run options for the step are greyed out, but if you set it back with the sequence file options, they do revert back to their original settings.
    Hope that helps (and works!!)
    S.
    // it takes almost no time to rate an answer

  • Test Stand Report Security

    I am looking for ways to incorporate some level of security for Test Reports produced by Test Stand, such as making the text files read-only for example.  From what I can determine there is no in-built security options for Test Reports.  How would Test Stand then be used in a Part 11 compliant enviroment?

    In order to change the ReadOnly attribute from TestStand, the file must be completed (closed). 
    We do some similar post processing of the Report File (HTML) by renaming it to prepend the number of errors in the file, but this does require that the Report File be completed and closed.  In order to accomplish this we use a "Main Test" sequence that lists all of the test subsequences to be run.  The Main Subsequence call step uses the "Run Sequence in a new execution" (created as a custom step).  Each test therefore generates it's own HTML report file.  Post Processing for that sequence from the "Main Test" then calls a step that renames the file.  You could do the same thing only to change the Attributes to Read Only. 

  • Windows Network Drive Mapping properties not being associated with Test Stand deployment

    I recently upgraded a TestStand/LabVIEW (Developer Suite 2012 DS1) deployment project from a Windows XP Pro OS to Windows 7 Enterprise. Now, when I run the Test Stand deployment, Network paths that used to be hard coded into my File Globals are no longer recognized. I re-wrote the vi's, and put "File Dialog" pop-ups so that I could see what path the control is being opened up at, and what appears to be happening is the Network Drive that I am defaulted to is appearing as if it is "disconnected" in the navigation window, and the path is defaulted to my root directory. I can navigate out to my network path no problem from the navigation window, and after the first time I perform this user action, subsequent executions open up to the path I have hard coded in my Sequence File Globals. However, if I reboot my host computer, I again have to go through the exercise of manually pointing to the proper network location? If I use the Windows Explorer to check Mapped Networked Drives, everything is properly mapped and connected.
    Has anyone ever seen this behavior? 

    Hi ATE Dude 22,
    I have not come across this problem before but here is a document from MSDN and one from NI which discuss file path conventions. From what I've seen, UNC is also accepted under Windows XP so I would advise using it for your file globals.
    Cheers,
    KyleP
    Applications Engineer
    National Instruments

  • Problam of Closing exexute threads in test stand from c# code

    Hi
    I want to close my .net application therefor i need to close all test stand resource. to do so im using the follow lines:
    axApplicationMgr1.CloseAllExecutions();
    axSequenceFileViewMgr1.GetCommand(CommandKinds.CommandKind_Exit).Execute(false);
    axApplicationMgr1.GetEngine().UnloadAllModules();
    It dosent seem to be helpfull, because sometime after the application closed the proccess is still exist (i can see it in the windows task manager)
    any idea how can i close my application and test stand togther?
    yaniv

    Hi yaniv,
    Typically, you can simply call ApplicationMgr.Shutdown().
    This will close all opened sequences and executions. If it returns true, you can exit out of the application and if it returns false, you can wait for an ExitApplication event to get generated at which point you can close the application.
    For an example on how to do this, please refer to the C# Simple Operator Interface that ships with TestStand.
    Jervin Justin
    NI TestStand Product Manager

  • Modules execcution times in test stand

    Hello Everyone:
    Maybe some can help me.
    I wrote a test sequence using Test Stand program with LabView and using Field Point for hardware. There is one issue that has been notice on the test results and that is the execution time of each of the modules.
    This question has been ask is Why does the execution time of the modules varies from one test to the next.
    We also notice that if we run a same unit several times we do not get the same results, they are very close but never the same and that includes the module execution times.

    Hello Toro,
    That is a great question. Depending on what controller and modules you have, the execution times of the modules vary from one to another. There is an excellent tutorial that explains this really well, below you will find a link to it:
    http://zone.ni.com/devzone/conceptd.nsf/webmain/a14d3c3314a0e24a86256dbe00664943?OpenDocument
    If you don't have a real time module, then by switching to one, you are going to see a significant change in the accuracy of the times displayed. Please let me know if you have any further questions.
    LA

  • Test Stand Deployment; Internal Error Code 1

    Hi,
    I get the following message from the deploymeny tool when trying to deploy my system...
    Internal error code 1 Processing VIs...
    An installer was not created due to an error
    I have mass compiled everything and all the VIs are working, my workspace processes okay and the sequences run okay in the Run time Engine adaptor of Test Stand.
    Any ideas what could be causing this? I have Test Stand 4.0.0 and labview 8.5.
    Many thanks
    Matt

    Hi Rick, see below cut and paste from this file, does this help?
    08:55:43tarting Log.
    08:55:45tarting Analysis
    08:55:45tarting to process workspace file
    08:55:56one processing workspace file
    08:55:56:Finished Analysis
    08:55:57:Building...
    08:55
    08:57:01:Internal error code 1 Processing VIs...
    08:57:01:Could not process LabVIEW VIs. Fix any broken VIs before rebuilding. LabVIEW error:
    Error copying files.
    Source:
    Destination: <Not A Path>
    Librarian Path Location.vi
    <Call Chain>Error 1 occurred at ABAPI Dist Copy Non-VI Files.vi -> ABAPI Dist Build LLB Image.vi -> ABAPI Copy Files and Apply Settings.vi -> TestStand - Build VI Distribution 8 AX Wrapper.vi -> TestStand - Build VI Distribution 8 AX Wrapper.vi.ProxyCaller
    Possible reason(s):
    LabVIEW:  An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.
    =========================
    NI-488:  Command requires GPIB Controller to be Controller-In-Charge.
    08:57:01:An installer was not created due to an error
    08:57:01:The build is finished
    08:57
    08:57:01:Aborted
    08:57:01:---------------------------------------
    Many Thanks
    Matt

  • Test Stand intermitte​nt error/cras​h problems

    I've been experiencing an intermittent crash problem on TestStand 4.0 for a long time.
    Previously, I got customer support on this issue (Reference#7226468)
    and they suggested repairing Test Stand to solve the problem. It seemed the repair solved the problem for a while. But after one month w/o crash, I got the same Run-time Error/crash,
    with following messages:
    “Microsoft Visual C++ Runtime Library Error”,
    “Sequence Editor: Operation failed, error code: -17500”,
    “Sequence Editor: Can’t get type palette file list; they must be loaded
    first, error code: -17500 Oparetion failed, Source: TSAPI”, etc.
    How can I solve this issue?Regards,
    Pelin Y.
    Test Systems Design Engineer

    Pelin,
    I would recommend trying to repair TestStand
    again if it worked the first time, but having to repeatedly do so could
    become bothersome.  Did you change anything in the code between when it
    worked and when you get this error? Do the errors come from the same
    step in your execution as the did a month ago? If so what is happening
    in your code when you get these errors? Have you seen this same error
    on any other machines? Are you calling a C++ DLL and if so what version
    of Visual Studio do you have on the machine?
    Richard S -- National Instruments --Applications Engineer -- Data Acquisition with TestStand

  • Test stand not showing cutsom columns

    I'm working on a custom UI for Test Stand in C# 2010 and I've selected the columns I want shown in the properties window of the Sequence Viewer. When I run the UI, the execution view is defaulting to the standard columns. I tried adding the line ApplicationMgr.UseStepListConfigurations = false to my code, but all that does is turn the execution view background to black. Is there something else I should be doing?
    Thanks
    Solved!
    Go to Solution.

    I've tried that, but all it does is turn the background color of the view black, which I did not set (see the attached screen shot). Is there some way of preventing the background from turning black?
    Thanks
    Attachments:
    Screenshot.jpg ‏18 KB

Maybe you are looking for