TestStand 4.0 reportgen_html.seq Type Conflict

Question

We have converted from TestStand 3.5 to TestStand 4.0.  We had created a custom reportgen_html.seq in TestStand 3.5 which we copied over to the TestStand 4.0\Components\User\Models\TestStandModels directory and updated using the Update Sequence Files utility (which is nice by the way).  Everything works fine until we try enabling on the fly report generation.  Then we get the following error when we run any sequence using single pass:
Details:
Type 'NI_BatchTestSocket' is invalid because it conflicts with the existing type of that name. To avoid this error message, you should open the file with the type conflict in the Sequence Editor and resave it.
The sequence file 'C:\Program Files\National Instruments\TestStand 4.0\Components\User\Models\TestStandModels\reportgen_html.seq' could not be loaded.
Error Code:
-17329; Invalid type - conflicts with an existing type.
Location:
Step 'Process Step Result' of sequence 'SequenceFilePostResultListEntry' in 'SequentialModel.Seq
If we open the \User copy of reportgen_html.seq prior to running a sequence, the error does not occur.  If we view the sequence file types for the \User copy of reportgen_html.seq, the Usage column shows reportgen_html.seq twice, which is a surprise and an indication that the \NI copy of reportgen_html.seq is involved.  If we rename the \NI copy of reportgen_html.seq and restart TestStand, we can run without errors without having to open the \User copy first.
We had thought that if a copy of reportgen_html.seq was in \User, then the \NI copy would not be loaded or used at all, but it looks like TestStand is trying to load both the \NI and the \User sequences.  Is that how it is supposed to work?  If so, it seems like we have to modify files under \NI to avoid the error.  It is our understanding that we really don't want to change anything under \NI so that future versions of TestStand won't stomp the changes.
Hans

Answer 1

Hi Hans,
It looks like you are having two problems. The first appears to be a type conflict. You can resolve this by opening the file in TestStand and saving it. The update utility will update the files to the 4.0 format, but it won't necessarily fix any custom types.
The second problem you are experiencing is because TestStand is still loading the reportgen_html.seq file from the NI directory. I would assume that you are still loading one of our process models from the NI directory. The process models have a relative path so they will find the reportgen_html.seq file in the NI side first. Renaming that file fixes your problem because the file is not found in the local directory (which I would assume is your first search directory) but is instead found in the User directory. If you copy everything from the NI directory to the User directory and use the user files, then everything should be taken care of for you.
Matt M.
NI