Modifications to SequentialModel.seq

[Cimteker]

Hi,

I've implemented SequenceFilePostStepRuntimeError in my sequence and now SequentialModel.seq is automatically modified every time I load my sequence. Why is that? And why do I get error -17205 (Access Denied) when I try to save it?

Thanks

CT

[RaviShrigiri]

The first error is probably because your test sequence has types changed (different) form the base type which is used in sequntial model.

The second error is due to the read only ( for win 7 system files are not allowed to be saved under program files directory).

Did you change/update any types?

Did the original sequence ( before changes) did not give this issue?

[Cimteker]

Thanks SunRS,

I am not aware of any type changes. Previously I did not have that problem. Is there a way to find out what changed?

CT

[dug9000]

Assuming you are using a recent version of TestStand (2010 or newer). Diff the two files in the File differ, with the file differ option "Automatically Merge Types" option unchecked in the file differ application. Then look at the types section of the diff. See which types in common are different, those are likely the ones causing the process model file to get updated.

-Doug

[Cimteker]

Thanks Doug,

This is what I see(attached). I do not remember making these changes. I may be changing that flag programatically in one of my sequences but that should not change my model file should it?

Thanks

CT

[dug9000]

It's not just a different setting, it's a different version of the type. Perhaps you added a process model callback to your client sequence file while a newer version of the process model was active? What verison of TestStand are you using? Are the process models you are using perhaps from an earlier version of TestStand? If so perhaps you should update and resave them to include the later version of the type. Or perhaps you accidentally got a newer version of the type in your client sequence file. If you are in a more recent version of TestStand, you can downgrade the version of your type in your client file to match the version in your process model as follows:

1) temporarily change the station option under the File tab called "Allow Automatic Type Conflict Resolution" to "Only if a Type Palette File has the Higher Version"

2) Restart the sequence editor to get back into the default state.

3) Load your client sequence file. You should get a type conflict dialog for the ModelOptions type. Choose the version of the type that exists in the SequenceModel.seq file. This will cause your client sequence file to be modified to use that vesion of the type. Save your client sequence file and now the problem should be gone.

Hope this helps,

-Doug