Why NI_CriticalFailureStackEntry errors ?

[MatsA]

I am using a sequence file made in 2.0 and trying to migrate it to 3.0. When I'm trying to load the sequence I get the message:
Type "NI_CriticalFailureStackEntry" is invalid because it conflicts with the existing type of that name. To avoid this error message you should open the file with the conflict in the Sequence Editor and resave it.

.. and I open it and resave it - but the error message won't disappear!!

[Scott_Richardson]

MatsA -
The NI_CriticalFailureStackEntry is an NI custom data type that is located in process model files. When the sequence editor launches it will load the default process model file, typically the NI copy of SequentialModel.seq. When you open your file, it may contain an edited copy of this type and your copy of the type may be marked as modified. Normally if a type is not marked as modified TestStand will attempt to resolve the conflict using the type versions. I suspect that your TestStand 2.0 sequence file has the type and it is marked as modified.

Questions:
1) Are you using the default NI model when the sequence editor is launched?

2) Is the type marked as modified or did you every edit the type?

3) Can you attach the sequence file that con
flicts when loaded? If not, you can send it directly to me at "ni.com" using the email address "scott.richardson"

Scott Richardson