Runtime error in TestStand 4.1

[Sgy1]

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

[Scott_Richardson]

Sgy -

We are not aware of any issue like this. Are you running the simple or the full-featured?

I am curious as to whether you tried to run the UI with the executable that came with TestStand 4.1, or whether you compiled the project first with VS 2008? If you did compile it, does the original executable that we ship work?

If full-featured, does the simple have the same problem out of the box and after you compile the project?

Are you running on a 32 or 64-bit version of XP?

[Pranchal Srivastava]

I agree with Scott , meanwhile looking at your error screen shot , it points to the compiler of VC++ . Could you please elaborate of how you encountered this ?

Thanks

[Scott_Richardson]

I am also curious, does the Sequence Editor work just fine because it is also a C# based application?

The C++ runtime error could be coming from the TestStand UI Controls or the Engine, since these are written in C++ and not C#. The code in the UI Controls do have a lot of exception handling which should prevent this type of error from being exposed to the application, but there could be something that we have missed. Once we have the additional information that we need, we will try to duplicate the problem.

[Scott_Richardson]

Looking at the image, we noticed that the variables view is empty. This might suggest that when you are changing the step, the variables view is refreshing and something is happening there. Some additional questions?

1) Does this problem occur with any other sequence file, or just the one that you showed in the image?

2) Have you customized the UI in any way? If yes, can you post the project and source files, so that we can try it? The goal is to solve your problem and to possibly determine if we can guard against this and handle the error better if it is related to some edit that you might have done.

[Sgy1]

Hi!

Thanks for ur efforts.

The screenshot shown is while running C# UI provided by TestStand (in National Instruments\TestStand 4.1\UserInterfaces\Full-Featured). The NI TestStand SequenceEditor is working fine.

No change have been made in theC# UI provided by TestStand. Still problem exists. Problem menitoned is not dependent on any sequence file.

My doubt is if there is any problem iwth OS, will this occur.

Thanks & Regards

Sgy

[Josh_W]

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: 

1. Install Win Debug from here: http://www.microsoft.com/whdc/devtools/debugging/installx86.Mspx
2. Launch WinDbg and go to File»Symbol File Path and enter this:http://msdl.microsoft.com/download/symbols
3. Start your program that crashes
4. Now in WinDbg, go to File»Attach to a Process and select your running program (probably TestExec.exe)
5. Hit F5 so the process will resume
6. 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.
7. 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]

Sgy1,

After taking a closer look at the screenshot you attached, I noticed that you were running the C# UI from the /debug folder.  Since we don't ship a compiled executable in that folder, that means that you must have just built it before running.  This leads me to think that the problem might be related to some configuration of your computer.

What I'd like you to try is running the C# UI from the start menu (Start»Programs»National Instruments»TestStand x.x»User Interfaces»C#).  Does this UI work?  If it doesn't, it is possible that you have compiled the C# ui in release mode and so overwritten the default shipping file, so I am attaching a copy of the default file to this post.

Could you try the VB.NET UI?  Does that one work?  What I'm trying to figure out is if there is a problem with the way that your UI has been compiled, or with the .NET framework itself.

Also, what version of Visual Studio are you using?