NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

TestStand 2016 : Step Setting : An error has occurred. Save your work and restart the sequence editor.

Hello everyone,

 

Anyone already experienced this attached bug ?

It is on one step type which calls (SubStep Menu) in post-step a LabVIEW VI.

The same VI and same step (just its name has changed) have been used in LabVIEW/TestStand 2014 without any issue. We got other similar steps which are runing fine in both 2014 and 2016 environement.

I cannot find a way de reproduce this bug and still not solved.

Any help will be apreciated.


BR,

Vincent

0 Kudos
Message 1 of 22
(3,636 Views)

If you copy and past the step to a new sequence file does it still cause the issue?

jigg
CTA, CLA
testeract.com
~Will work for kudos and/or BBQ~
0 Kudos
Message 2 of 22
(3,614 Views)

Yes it still does. I'am stucked with this and really can't find a way to solve it 😞

0 Kudos
Message 3 of 22
(3,610 Views)

Does it happen when you create a new step in a new sequence file and set it up exactly like that one?

jigg
CTA, CLA
testeract.com
~Will work for kudos and/or BBQ~
0 Kudos
Message 4 of 22
(3,605 Views)

I think i don't understand your question. My stepType is configured into "Type" Windows.

So everytime i use this step i get this error on the limits tab only.

The properties tab shows the right Type.

 

Vincent

0 Kudos
Message 5 of 22
(3,601 Views)

can you send a sequence file with that type in it?

jigg
CTA, CLA
testeract.com
~Will work for kudos and/or BBQ~
0 Kudos
Message 6 of 22
(3,583 Views)

Generaly this error occurs because of a corrupt installation of TestStand development system. The error can be resolved by Repairing the software from Add/Remove programs in Control Panel.

If that does not work, uninstall TestStand and reinstall it.

 

Hope it will help you

Regards,

Maxime G. | Application Engineer
National Instruments France

0 Kudos
Message 7 of 22
(3,573 Views)

Using TesStand 2013, 2014 and 2016 32 bits could corrupt all installation ?

I switch between TestStand versions with TestStand version Selector.

0 Kudos
Message 8 of 22
(3,568 Views)

I have installed TestStand2016 on new PXI we received and we got the same "error".

Does it mean TestStand2016 installation is corrupted ?

 

StepStype CheckNumericValue attached

0 Kudos
Message 9 of 22
(3,558 Views)

Why do i have a custum datatype from previous project on TestNI.seq ?!!!

How can i replace it by the one which already exists on other typepalette ?

0 Kudos
Message 10 of 22
(3,555 Views)