Error -17329: Types Conflict in TestStand 2016

Updated Jan 6, 2018

Reported In

Software

  • TestStand 2016

Issue Details

I opened an example for the new TestStand Property Loader step and saved the updated types in my Process Models. Now, every time I run an execution, I get a Run-Time Error with
Error Code: -17329; Invalid type - conflicts with an existing type.
How can I fix this?

Solution

This error will only present in the following cases:

1. If the Allow Automatic Type Conflict Resolution setting in Configure»Station Options..»File is set to "Only if a Type Palette Files will not be Modified (default)" before one of these examples is opened, upon closing the example, a dialogue box similar to Figure 2  will appear and prompt to you to save SequentialModel.seq, or the process model in use.

After the sequence file is saved, if conflict resolution settings are changed to "Only if a Type Palette File has the Higher Version" or "Never," then this type conflict can occur.

2. If the Allow Automatic Type Conflict Resolution setting is set to "Only if a Type Palette File has the Higher Version" or "Never" initially, upon opening a property loader step type example, you would see a prompt similar to this one:

 
If you choose "Use Type from Property Loader - x.seq" from the type conflict dialog box, this conflict could also occur if you choose to Increment Type Versions.

Additional Information

This issue was introduced by a type mismatch in two Property Loader examples. 

WAS THIS ARTICLE HELPFUL?

Not Helpful