Runtime error in TestStand 4.1

Hi!
I installed TestStand 4.1 and tried to run the C# user interface provided by TestStand. When I click on Sequence view control in sequence editor tab, I get a run time error and the application closes by iteslf. Im attaching a screen shot of this.
My OS is windows xp with visual studio 2008.
Please provide some solution to this.
Thanks & Regards
Sgy
Attachments:
RunTIme Error.PNG ‏63 KB

Sgy1,
The best way to debug a crash like this where we can't reproduce it here on one of our machines is going to be to get a crash dump from the application. To do this, please follow these steps:
Install Win Debug from here: http://www.microsoft.com/whdc/devtools/debugging/installx86.Mspx
Launch WinDbg and go to File»Symbol File Path and enter this:http://msdl.microsoft.com/download/symbols
Start your program that crashes
Now in WinDbg, go to File»Attach to a Process and select your running program (probably TestExec.exe)
Hit F5 so the process will resume
Now perform whatever action makes the program crash. During the crash, focus should automatically transfer back to WinDbg, and its window should come to the front.
Back in WinDbg create a crash dump file. Do this by entering in the command at the bottom of the command window. The syntax for the command is:
.dump /ma "c:\AFileName"
Then send us that dump file. We will be able to debug it and hopefully get some more information from it. Since the dump file is generally very large (100-400 MB) you can post it on the ni FTP site at ftp://ftp.ni.com/incoming. When you do this, post back to this forum with the name of the file so that I can download it.
Alternatively, if you would like to handle this directly by e-mail or phone, please post back to this forum that you wish to do so, and I can ask the forum administrator for your e-mail address. The admin will not give out this information without your express permission.
Josh W.
Certified TestStand Architect
Formerly blue

Similar Messages

How To Handle Labview Runtime Error in Teststand

Hi,
I am working NI-CAN device to transfer CAN frames through the VI's using TestStand. Before transmission took place, we need to choose for the port, in case if the port is selected wrong, Labview take it as a runtime error and handles accordingly while teststand keeps on running i.e. if I have 7 steps that are calling that VI, the runtime error from the labview will appear that many times also. Is there any way to handle labview runtime errors directly through TestStand. I have a sequence that will take care of the Runtime Errors in my sequence file.
Please help me soon.
Thanks in Advance,
Vivek

Hi Vivek,
If the LabVIEW VI is handling the error, then what you probably want to do is make the VI have an Error Out output terminal. You'd have to wire the appropriate error out wires to the terminal of course.
This way, when you call the VI from TestStand, you can check the value of the Error Out and decide in TestStand how to handle it (skip the remaining steps, popup a message, etc).
Jervin Justin
NI TestStand Product Manager

Runtime error not notified, it's a Bug of TestStand 4.2.1?

Hi All,
I found an issue during setting the precondition of a steps in Teststand 4.2.1
I have a Statement Step named "Cleanup if WRONG barcode"
AnyOf(
RunState.Sequence.Main["ID#:NPMo1DuN+0KuxglET/DQiD"].Result.Status == "Error",
RunState.Sequence.Main["ID#:gv4JwcInbU2jx2Ek6SsJ2A"].Result.Status == "Error",
RunState.Sequence.Main["ID#:nUMiG7Q3Q0mOkCtVRok26C"].Result.Status == "Error",
RunState.Sequence.Main["ID#:5KBfxx3r+ki+2TaRkv0Z3D"].Result.Status == "Error",
Parameters.Socket_Data.Product.OrderNumber < 8)
the last argument is Parameters.Socket_Data.Product.OrderNumber that contain the string of the Order number.
The error is the following:
But When I execute the code the Runtime error is not notified, as expected.
Note: in the station Option I have On Runtime error notification "Show Dialog".
Could you please tell me why ?
Thank you very much
Attachments:
AnalyseBarcode.seq ‏7 KB

It's because Parameters.Socket_Data.Product.OrderNumber is a string value that is empty so it cannot be coerced to a number so the expression:
Parameters.Socket_Data.Product.OrderNumber < 8
gives the error you are seeing, but at runtime, the string is set to a number which can then be coerced to an actual number so the expression succeeds at runtime.
You can see this same issue if you create a local variable in a sequence that's a string that's empty and create statement step as follows:
Locals.string < 8
If you do, you will get the same error you are seeing. Then edit the local variable and set it to 10 and look at your expression again. The error is now gone.
You can avoid the error in the statement by either setting the string to an initial value that contains a number (e.g. 0) or change the data type of that variable to a number rather than a string.
Hope this helps,
-Doug

Intermittent Runtime error - pure virtual function call

I have an intermittent runtime error - pure virtual function call & don't know what cause it? Since It only occurs & crashes once awhile therefore it's difficult to trap it for debugging.I suspect it come from TestStand ActiveX API which I use in my User Interface Application project but I'm not really sure.
Does anyone experience this kind of problem when working with TestStand API ? If so any
suggestion? I have noticed in the TestStand API header file teapi.tlh contain many raw_.... function defined as pure virtual function. What are these raw_... function ? I don't think I use any of these function in my project.
Many thanks!

Danh,
I don't believe that your problem can be solved with the information you have provided unless someone else has experienced the same symtpoms which coincidentally have the same cause as in your case.
Is there any other information you can provide that can help localize the problem?
1) What is happening when the error occurs?
2) Does the error always occur in the same place?
3) Does it always occur with use of certain resources (e.g. DAQ, GPIB, VISA, printer)?
4) Does it occur when using the sequence editor?
5) Does it occur when using one of the shipping operator interfaces?
6) Does it occur only when using your operator interfaces?
7)Is it related to a specific sequence or any sequence?
8) Does it happen when you executed your sequence with/without a process model entr
y point (i.e. Execute>>Test UUTs, Execute>>Singal Pass or Execute>>Run MainSequence)?
9) How often does it happen?
10) What version of TestStand are you using?
11) With what language (include versions) are you programming your code modules?
12) With what language (include versions) are you programming your operator interface?
13) Is there any error code reported with this error message?
14) Is this error reported in a TS run-time error dialog or is it reported directly 1by the operating system?
15) Have you searched the web for related errors? For example, the following link describes a particular programming mistake that can lead to this error
http://support.microsoft.com/support/kb/articles/Q125/7/49.asp
By investigating answers to the above questions you may be able to narrow the cause of this error, which might allow you or others to help solve the problem.

How to handle runtime error in PreUUT step when running in Parallel mode

I would like to run Test UUTS in parallel mode, and some actions are done in PreUUT such like read serial number and fixture control.
The process model won't goto PostUUT Step when runtime error occurs in PreUUT step, so i would like to add some actions to check if sequence error in cleanup and go back to setup in PreUUT step, but i find it skip all the actions in setup and main step?
What should i do if i want to go back to run PreUUT again as the first time to run when runtime error occurs?
Or, is there any good way to handle this kind of error withour restart program?
Solved!
Go to Solution.

This question does not depend on PreUUT or ParallelModel at all.
First of all:
A Runtime Error is a situation where TestStand encounters a problem which makes further testing either impossible or senseless. So a Runtime Error always indicates a situation where proceeding the test sequence is not recommended.
Nevertheless, there are situation where you want to handle those errors without stopping the execution. A "traditional example" for this is initialising serial/GPIB devices. If the device does not reply, there might be different issues the operator can easily resolve and (if corrected) the sequence can proceed properly. The operators action could be:
- Check if device is switched on
- Check connection between PC and device
So the error state is used to inform the operator about the malfunctioning device and regarding of the actions the operator takes, the execution will either proceed or terminate.
When TestStand encounters a Runtime Error, it initially reacts with displaying a dialog. This behavior can be modified in the Station Options >> Preferences >> On Runtime Error.
Furthermore, you can install callback sequences which are called if an error occurs. Those would be either SequenceFilePostStepRuntimeError or ProcessModelPostStepRuntimeError (depending on the fact if you are changing the process model or simply working with client sequence file callback overrides). These are "normal" sequences you can use in order to get system information, loop on the step or....essentially do whatever you want. If you want to proceed though, you must not forget to reset the error flag.
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Runtime Error when trying validate password in Teststand2.0/LabVIEW6.1

Hi there,
I am trying to build a custom user login (LabVIEW 6.1) for TestStand2.0. I am trying to validate the user password. I am using a reference from the TS.IEngine and about every other time I run it I get the following error:
Microsoft Visual C++ Runtime Library
Runtime Error!
Program:...ogram Files\National Instruments\LabVIEW 6.1\LabVIEW.exe
R6025
-pure virtual function call
I have attached the vi to see if you get the same error. Also, I have not been able to get the function to successfully return a true for validated password.
Thanks,
Kevin
Attachments:
TestStand_-_Check_User_Name_and_Password_Error.vi ‏22 KB

Nemo,
Thanks for the reply. This is not exactly what I needed but your comments really helped a lot!! (especially regarding obtain the Engine Reference from the sequence context---missed that one I thought I could just open a new reference to the TestStand Engine but as it turns out (not quite sure yet why...ActiveX rules I sure but I do not know them all yet one can simply open the reference and use it. I actually thought I was doing something similar to what the LV TestStand Operator Interface does, which is open a reference and then start using it...bad assumption! So, long story short, When I place this vi in a TS sequence (remove the garbage) and run it, it works how I want it to. So thanks again for the advice.
Kevin

Runtime Error R6025 and DAQ-Driver

Operating System Windows2000
Teststand  Version 3.0
DAQ-Driver  6.9.3f5
Serial Driver  1.7
LabvIEW RTE build with LabVIEW 6.1
hello,
we have build a testsytem based on LabVIEW and Teststand.
We use the NI-PCI boards 6713, RS232/16 and MIO-164E. We dont use any operator interface, only the
original Teststand sequence-Editor and the Single-Pass Prozess-model.
It works very fine for e.g. a whole week running and then
,suddenly, the ERROR Window pops up :
"Window-Head: Microsoft Visual c++ Runtime Library
RUNTIME ERROR
Programm ...\National Instruments\Teststand3.0\Bin\SeqEdit.exe
R6025
- pure virtual function call"
After pressing the OK-Button, the Computer will boot and generate a memory-dump.
We have analyzed the dump-file with the Microsoft WINdbg Tool.
The Bugcheck Analysis reported an error with the Nidaq32k-Driver !!
What should/can we do ?
See below the analysis report:
Debugging Details:
*** ERROR: Symbol file could not be found. Defaulted to export symbols for Nidaq32k.SYS -
OVERLAPPED_MODULE: kmixer
FAULTING_IP:
Nidaq32k!mdsSimpleDIGPortPrimitive::_accessCheck+600
bc4370a0 c745fcffffffff   mov     dword ptr [ebp-0x4],0xffffffff
DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO
BUGCHECK_STR: 0xCB
LAST_CONTROL_TRANSFER: from 804bce30 to 80440665
STACK_TEXT:
bc175c54 804bce30 80064bd4 00000000 804bd199 nt!MmCleanProcessAddressSpace+0x421
bc175d04 804bd1b3 00000000 84973a28 80431261 nt!PspExitThread+0x4e1
bc175d10 80431261 84973a28 bc175d48 bc175d3c nt!PsExitSpecialApc+0x1a
bc175d4c 80465bfa 00000001 00000000 bc175d64 nt!KiDeliverApc+0x158
bc175d4c 77e017da 00000001 00000000 bc175d64 nt!KiServiceExit+0x58
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012f7a4 00000000 00000000 00000000 00000000 0x77e017da
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
Nidaq32k!mdsSimpleDIGPortPrimitive::_accessCheck+600
bc4370a0 c745fcffffffff   mov     dword ptr [ebp-0x4],0xffffffff
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: Nidaq32k!mdsSimpleDIGPortPrimitive::_accessCheck+600
MODULE_NAME: Nidaq32k
IMAGE_NAME: Nidaq32k.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 3f39592e
FAILURE_BUCKET_ID: 0xCB_Nidaq32k!mdsSimpleDIGPortPrimitive::_accessCheck+600
BUCKET_ID: 0xCB_Nidaq32k!mdsSimpleDIGPortPrimitive::_accessCheck+600
Followup: MachineOwner

hello,
unfortunately the msiBlast tool dont indicate the LV RTE 6.0 !, too.
See attachment .pdf file for all installed applications
So it seems to be a other problem of the MAX Version 3.0, showing a LV RTE, which does not exists.
(The expected folder ...\shared\LabVIEW Run-time\6.0 is not present, too.)
Nevertheless i dont have any idea to solve the problem with the R6025 Error ?
Note: In case of manually killing the LV TS RTE within the windows system control (testsequence is running) , a blue screen with error indication for nidaq32k.sys arises !?
regards
Attachments:
msiblast-all.pdf ‏18 KB

Custom Runtime Error Dialog Always showing

Hi,
(TestStand 2.0.1f1)
Using the Callback based on the example C:\TestStand\Examples\Callbacks\PostStepRuntimeErrorCallback\ErrorHandlerExample.seq.
The error dialog always appears. I was expecting from the comment in the Set ErrorReport Flag that the Dialog would not appear again. (Comment: If this flag is set, TestStand does not send a UIMsg_BreakOnRunTimeError event to the GUI. This step sets the flag to prevent the GUI from displaying a runtime error dialog because this callback has already displayed a runtime error dialog to the user.)
When you use the default Error Reporting, you can check a checkbox so that Dialogbox is not seen again for the same execution. I was expecting the same thing from the SequenceFil
ePostStepRuntimeError callback.
Any clues as to whats going on.
See attached example.
Regards
Ray Farmer
Regards
Ray Farmer
Attachments:
RuntimeError1.seq ‏52 KB

Hi,
In the Programmer Help for DisplayRunTimeErrorDialogEx method it says
"dontShowAgainForExecution Boolean Returns whether the user wants this dialog box to appear again if another run-time error occurs in the current execution. If this value is true, set Execution.RTEOptionForThisExecution to specify what to do on a run-time error for this execution."
Now I have tried setting each of the RTE Options (except the Display Dialog) to try get the same effect as not using the Callback for runtime errors when it comes to ignoring all further errors. Nothing seems to work as expected. So whats the engine doing extra thats not detailed in the Programmer Help or the examples provided.
Regards
Ray Farmer
Regards
Ray Farmer

When running labview's test executive I recieve runtime error: Call to step "PRE-RUN" failed. Could someone explain this error?

I have a set of vi's that work when run under labview. However, when calling these vi's from labview's test executive I recieve runtime error: Call to step "PRE-RUN" failed. in Assign Connector Pane.vi->Call Test.vi->Execute Pre-Run.vi->Test Executive. Could someone explain this error to me? (or ideally tell me how to fix it?) Thanks.

Hello,
There are any number of possible causes to this problem. Which version of Test Executive are you using? Have you upgraded your Test Executive recently? The latest version is 5.1.1. If you have changed anything about Test Executive on your computer recently, I recommend you perform a mass compile of all your VI libraries, as having different versions of the VIs on your system could often result in the "Call to Step XYZ Failed" errors. Also, are you using any DAQ or Analysis VIs in your steps? We have seen problems where the use of DAQ or Analysis VIs in the sequence can cause intermittent "Call to Step...Failed" errors. There are some KnowledgeBase entries on our website that discuss this problem. Are you using the Test Executive in the VI environment, or
as an executable? Again, there are some problems with using Test Executive as an executable that result in these errors, and there are also KnowledgeBase entries that discuss these problems.
If you have a pared-down application that demonstrates the problem, feel free to send me your VIs and your .seq file and I will try to reproduce the problem.
Alternatively, I would suggest you visit www.ni.com/teststand to learn about TestStand, our state-of-the-art Test Sequencing software that completely outperforms Test Executive. It is very easy to use and much more powerful, and we have a top-notch support team available dedicated exclusively to supporting TestStand. As you are probably aware, we are no longer developing Test Executive, and instead are concentrating our efforts on making TestStand the penultimate solution for all our customers' test sequencing needs.
I appreciate your patience on this issue. Please let me know if I can offer further assistance.
Have a pleasant weeken
d.
Sincerely,
Darren Nattinger
Applications Engineer
National Instruments
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

When running labview's test executive I recieve runtime error

When running labview's test ( Measurement & Automation Explorer) executive I recieve runtime error ms vc++
win95 labview6.0
<<<<>>>>
Mensaje publicado mediante http://noticias.ipbusiness.com,
las news a través de web.

Hello,
There are any number of possible causes to this problem. Which version of Test Executive are you using? Have you upgraded your Test Executive recently? The latest version is 5.1.1. If you have changed anything about Test Executive on your computer recently, I recommend you perform a mass compile of all your VI libraries, as having different versions of the VIs on your system could often result in the "Call to Step XYZ Failed" errors. Also, are you using any DAQ or Analysis VIs in your steps? We have seen problems where the use of DAQ or Analysis VIs in the sequence can cause intermittent "Call to Step...Failed" errors. There are some KnowledgeBase entries on our website that discuss this problem. Are you using the Test Executive in the VI environment, or
as an executable? Again, there are some problems with using Test Executive as an executable that result in these errors, and there are also KnowledgeBase entries that discuss these problems.
If you have a pared-down application that demonstrates the problem, feel free to send me your VIs and your .seq file and I will try to reproduce the problem.
Alternatively, I would suggest you visit www.ni.com/teststand to learn about TestStand, our state-of-the-art Test Sequencing software that completely outperforms Test Executive. It is very easy to use and much more powerful, and we have a top-notch support team available dedicated exclusively to supporting TestStand. As you are probably aware, we are no longer developing Test Executive, and instead are concentrating our efforts on making TestStand the penultimate solution for all our customers' test sequencing needs.
I appreciate your patience on this issue. Please let me know if I can offer further assistance.
Have a pleasant weeken
d.
Sincerely,
Darren Nattinger
Applications Engineer
National Instruments
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Download PDF, Runtime Error & LabVIEW Crash

Hello
I create a VI to download a PDF file with an HTTP request (using WebBrowser). This VI is used in a TestStand application. When it's working, the following Internet Explorer window opens suggesting to Open/Download/Cancel a pdf file. I used this solution because the TestStand execution doesn't stay blocked on this VI until the user make a choice (Open/Download/Cancel) (the execution must continue to next steps without waiting for a user action).
When it's working fine :
The problem is that sometimes (executing with labview or teststand) a runtime error or a labview crash (or both) occurs :
Examples of errors :
Here I put the block diagram of the VI (the left part enable to build the url) :
Have you any idea of what cause this error ?
Or have an other solution to process this operation (a solution where the PDF file is automatically openned would be better !).
Thanks for your help !

You can open a PDF within LabVIEW using this VI:
http://digital.ni.com/public.nsf/allkb/9A6A259EB5A2BEDA86256DD00048C604
Thoric (CLA, CLED, CTD and LabVIEW Champion)

Runtime error postexpression

Hello,
from the TestStand 4.1 Reference Manual, table 3.4 "Order of Actions a Step Performs", I gather that steps 16 (Evaluate Post-Expression) and 17 (Evaluate Status expression) are executed before step 27 (Call Post-Step Failure Engine callback). Therefore, I would assume that these expression are evaluated in case of a runtime error, but my observations indicate otherwise.
Does TestStand evaluate these expressions also in case of a runtime error?
Perhaps an important detail: I am testing this by setting Step.Result.Error.Occurred=True in the Pre-Expression; the table 3-4 does not indicate that this should make a difference, but ...
Regards
Peter

Hi Peter,
I think your right. TestStand does not evaluate Post Expression and Status Expression in case of a runtime error of the step.
So you better should retry the step with the runtime error until he has no error and then the 2 expressions will be evaluatet.
Regards
DianaS

Why does Step Fail cause a Lost ActiveX Connection Runtime Error?

A Step failure is a legitimate event. It should be recorded and execution should pass to the next step or cleanup as set up in the sequence or Station config. But I get this 17702 runtime error popup everytime. The steps are setup as single threads, dynamically loaded and unloaded.

Hello Bob,
Error -17702 is a CVI OLE (ActiveX) adapter error. This scenario that I'm familiar with is the following steps:
1) TestStand's CVI adapter is configured to "Execute Steps in an External Instance of CVI".
2) From TestStand, step into a CVI code module.
3) While inside the code module in CVI, click the "Stop" button. This stops the CVI debugger, and TestStand interprets this as error -17702. Here's the error message you see:
Error Message: Lost ActiveX connection to CVI. The CVI adapter will attempt to reconnect on next execution. [Error Code: -17702]
Note that if this scenario occurs, ALL CVI steps after this in the sequence will be marked with this same error number.
In the scenario I just described, the step is listed by TestStand wi
th a status of "Error", not "Failed".
Are your steps being marked with a status of "Error" or "Failed"? If they are listed as "Error", then an unrecoverable error (which kills the CVI debugger) is what has happened, and that needs to be corrected.
For instance, in the scenario I described above, the correction is to NOT click the "Stop" button; always let the CVI debugger execute through the code.
However, if your steps being marked with a status of "Failed", then perhaps something else is going wrong. I would first repair the installation of TestStand and CVI on your computer to see if that fixes the problem.
David Mc.
NI Applications Engineer

Runtime error in starting Lightroom

I receive the following message when I try to start Lightroom:
Microsoft Visual C++ Runtime Library
Runtime Error!
Program:...Files\Adobe\Adobe Photoshop Lightroom 1.2\lightroom.exe
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Lightroom ran well for several days and then failed to open with the above message.
I have tried everything I know to do (uninstalled and reinstalled the application, restored the computer to a restore point before Lightroom was originally installed, etc.) and do not know were to go from here. Suggestions would be appreciated.
I am using Windows XP sp2 and have 4 GB of ram and 250 GB of hard disk space.
Thanks,
Cliff Culp

Aha! A fix! Please look at this...
http://www.adobeforums.com/cgi-bin
bob frost, "Help! Runtime error after Lightroom 1.1 install!" #10, 27 Jun 2007 6:54 am

Runtime error while executing rule

Hello All,
While executing the DTP for a cube, im facing the error as Runtime error while executing rule -> see long text .
For this source is another Cube, where im loading the data from Cube to Cube.
Error Description are as follows:-
Error Location: Object Type    TRFN
Error Location: Object Name    0T9SCR6Q4VWS1SOPNRRBOY1YD51XJ7PX
Error Location: Operation Type ROUTINE
Error Location: Operation Name
Error Location: Operation ID   00034 0000
Error Severity                 100
Original Record: Segment       0001
Original Record: Number        557
and Also descripton is :-
Diagnosis
    An error occurred while executing a transformation rule:
    The exact error message is:
    Division by zero
    The error was triggered at the following point in the program
    GP4H0CW3MLPOTR3E8Y93QZT2YHA 4476
System Response
    Processing the data record has been terminated.
Procedure
The following additional information is included in the higher-level
node of the monitor:
   Transformation ID
   Data record number of the source record
   Number and name of the rule which produced the error
Let me know ur valuable suggestions on these error...
thanks.

Hello,
I have checked all the transformation and End Routines.All are working fine.Yesterday i have loaded some data into it, but today its gettting errored out.
Checked completely in the forum for threads related to this, but couldnt find proper thread which had solutions....
thanks,
srinivas.

Runtime error in TestStand 4.1

Similar Messages

Maybe you are looking for