NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Variables View crashes

I have two machines here which should be identically installed with WIndows XP SP2, TestStand 4.0.1 (exact version ist 4.0.0.1030). On one machine, everything runs normal, on the other one, the Sequence Editor as well das the Operator Interfaces (I tried the MFC version) crash, reporting that the VariablesView does not work.

 

The only difference I can currently make out between the machines is that the one with the problem does not run the "HID service" (for generic access to human interface devices). Is there a possible connection?

 

Regards

 

Peter

 

0 Kudos
Message 1 of 5
(3,240 Views)

Peter,

 

When does the crash occur?  Does it happen when you try to interact with the TestStand Variables View or does it happen when the program is initialized?  Can you attach a screenshot?

 

What versions of the .NET framework do you have installed on those two machines?  Do you have TestStand 4.0.1 or 4.0.1f1 installed?  (they both list the build version as 1030, but f1 contains a fix documented here).

Message Edited by Josh W. on 10-08-2008 09:59 AM
Josh W.
Certified TestStand Architect
Formerly blue
Message 2 of 5
(3,231 Views)

Josh,

 

thank you. Took me a while to check it all and it wasn't TestStand's fault at all, but your link pointed me in the right direction. The description of the fix mentioned using the TestStand Version Selector, and that complained about being unable to register the "NationalInstruments.TestStand.Interop.UI.AxControls.dll". Using regasm directly in /verbose mode revealed that System.Windows.Forms could not be loaded. A simple repair of the .NET Framework 2.0 installation fixed the problem.

 

Thanks

 

Peter

 

0 Kudos
Message 3 of 5
(3,214 Views)

Peter -

I am glad that you figured out the problem. Just curious, do you know why the .NET framework might have gotten messed up?

Scott Richardson
https://testeract.com
0 Kudos
Message 4 of 5
(3,199 Views)

Scott,

 

sorry that took so long. No, actually I have no idea what messed up the .NET framework, except that there were a lot of back and forth installations on that machine of various things.

 

Regards

 

Peter

 

0 Kudos
Message 5 of 5
(3,149 Views)