Downgrade version of NI steptypes in a sequence

[markus kossmann]

We have a sequence , which includes the NI Action step in version 3.1.0.2 ,NI PassFailtest in Version 3.1.0.2 and  EditSubstep in version 3.1.0.9098

This sequence should be modified on  a on a clean Teststand 3.1 installation with NI Action step in version 3.1.0.1 ,NI PassFailtest in Version 3.1.0.1 and EditSubstep in version 3.1.0.9095.  Just opening that sequence on 3.1 and saving it causes the Teststand 3.1 installation ( ni_types.ini )to be upgraded to the newer versions.  Any way to avoid that ?

[j_dodek]

Hi markus

It seems you have been affected by a type virus.

To get more information about this please visit this thread:

http://forums.ni.com/ni/board/message?board.id=330&message.id=17427#M17427

In this thread there is a link to tookit. (I dont know if this is working under TS3.1)

If this is not working. Try this.

1.) Use a clean TS3.1 (best reinstall)

2.) Start your editor (now clean Steps are loaded)

3.) Load your SeqFile

4.) Now - Type conflict

5.) Be sure that "use currently loaded.." is selected.

6.) Do not click Apply all just do it step by step to see which type is affected

7.) Save your SeqFile

8.) Close the editor no savings to NI-Steptypes should appear.

9.) Reopen with no conflicts.

If your production machines now having conflicts they are infected, too.

If a copy from clean NI Types would not help, re-install and pray for more project money

Good luck

greetings from the lake of Constance, Germany

and get never affected by a type virus

juergen

greetings from the lake of Constance, Germany

and get never affected by a type virus

juergen

[markus kossmann]

That method didn't work for me because when loading on the clean system, the "infected" sequence was modified silently without any type conflict popup. After saving the sequence and saying "no" to the changes in the NI types when closing Teststand, you could repeat that game again and again.

But now I managed to solve the problem by replacing the "infected" type definitions with the definitions from a not infected backup of that sequence with a text editor.

Message Edited by markus kossmann on 01-17-2008 07:01 AM

[j_dodek]

Hi markus

Just one thing to check. Is your model and frontendcallback clean?. I had this a few weeks ago were my frontend was infected.
But your procedure is well, i kown this (search and replace all 🙂 ).

Greetings

Juergen 

[markus kossmann]

On the machine ,where the the sequence was infected, I've replaced the the complete Teststand installation tree with a copy  from a clean machine. So I'am quite sure that the installation on the infected machine is now clean. 

[James M]

The TestStand Type Differ tool ships with a Master file containing all the 3.1 types from a clean installation of TestStand. If your solution doesn't fix the issue, download the Type Differ and merge your sequence with the Master file (merge in the direction of your sequence so it gets "downgraded").

-James

[markus kossmann]

I've seen the Type Differ tool. But I haven't used it, because it requires a Teststand-4.0 Installation to work.

[James M]

The latest release now supports TS 3.1.

Regards,
James