Why is my deployment throwing a warning on BatchModel.seq?

[JoeDG]

In the process of deploying several sequences, I'm getting a warning:

Warning: You may need to add any sequence file(s) referenced by the following expression(s). Because TestStand cannot determine which sequence file(s) will be called,this message reminds you to make sure you include the called sequence file(s) in your distribution. If you are distributing the called files you can ignore this message.

And then a bunch of messages, mostly regarding BatchModel.seq.  (Full warning text is below)

Any ideas why I'm getting this warning?

I'm new on this project (and to TestStand), so I don't know everything about this setup, but here's a little background:

I'm in the process of upgrading our test software from TestStand 2 to 2010.

The sequences I'm deploying are from Teststand 2, and have been upgraded using the "Update Sequence Files" tool (In TestStand 2010), but are otherwise unchanged.

I'm told that several of the tests use custom process models, and in the original setup, these process models were overwritten over the stock process model files.  I have these modified process model files, but am not exactly sure where to put them so this will deploy correctly.

---------------------------------------

Warning: You may need to add any sequence file(s) referenced by the following expression(s). Because TestStand cannot determine which sequence file(s) will be called,this message reminds you to make sure you include the called sequence file(s) in your distribution. If you are distributing the called files you can ignore this message.

"reportgen_" + Parameters.ReportOptions.Format + ".seq" in step 'Initialize the On-The-Fly Report Generator Object', sequence 'Configure Post Result Callbacks', sequence file 'C:\Program Files\National Instruments\TestStand 2010\Components\Models\TestStandModels\ModelSupport.seq'

"reportgen_" + RunState.Root.Parameters.ModelData.ReportOptions.Format + ".seq" in step 'Process Step Result', sequence 'SequenceFilePostResultListEntry', sequence file 'C:\Program Files\National Instruments\TestStand 2010\Components\Models\TestStandModels\BatchModel.seq'

"reportgen_" + RunState.Root.Parameters.ModelData.ReportOptions.Format + ".seq" in step 'Process Step Result', sequence 'ProcessModelPostResultListEntry', sequence file 'C:\Program Files\National Instruments\TestStand 2010\Components\Models\TestStandModels\BatchModel.seq'

"ReportGen_" + Parameters.ModelData.ReportOptions.Format + ".seq" in step 'Get Batch Report Footer', sequence 'BatchReport', sequence file 'C:\Program Files\National Instruments\TestStand 2010\Components\Models\TestStandModels\BatchModel.seq'

"ReportGen_" + Parameters.ModelData.ReportOptions.Format + ".seq" in step 'Get Batch Report Header', sequence 'BatchReport', sequence file 'C:\Program Files\National Instruments\TestStand 2010\Components\Models\TestStandModels\BatchModel.seq'

"ReportGen_" + Parameters.ModelData.ReportOptions.Format + ".seq" in step 'Get Batch Report UUT Item', sequence 'BatchReport', sequence file 'C:\Program Files\National Instruments\TestStand 2010\Components\Models\TestStandModels\BatchModel.seq'

"ReportGen_" + Parameters.ModelData.ReportOptions.Format + ".seq" in step 'Set Report Disabled Message', sequence 'BatchReport', sequence file 'C:\Program Files\National Instruments\TestStand 2010\Components\Models\TestStandModels\BatchModel.seq'

"ReportGen_" + Parameters.ReportOptions.ReportStyle + ".seq" in step 'Set ReportOptions based on ReportStyle', sequence 'Get Report Options', sequence file 'C:\Program Files\National Instruments\TestStand 2010\Components\Models\TestStandModels\BatchModel.seq'

"ReportGen_" + Parameters.ReportOptions.ReportStyle + ".seq" in step 'Set ReportOptions based on ReportStyle', sequence 'Get Report Options', sequence file 'C:\Program Files\National Instruments\TestStand 2010\Components\Models\TestStandModels\BatchModel.seq'

"ReportGen_" + Parameters.ReportOptions.Format + ".seq" in step 'Get Report Footer', sequence 'TestReport', sequence file 'C:\Program Files\National Instruments\TestStand 2010\Components\Models\TestStandModels\BatchModel.seq'

"ReportGen_" + Parameters.ReportOptions.Format + ".seq" in step 'Get Report Header', sequence 'TestReport', sequence file 'C:\Program Files\National Instruments\TestStand 2010\Components\Models\TestStandModels\BatchModel.seq'

"ReportGen_" + Parameters.ReportOptions.Format + ".seq" in step 'Get Report Body (Sequence)', sequence 'TestReport', sequence file 'C:\Program Files\National Instruments\TestStand 2010\Components\Models\TestStandModels\BatchModel.seq'

"ReportGen_" + Parameters.ReportOptions.ReportStyle + ".seq" in step 'Get Report based on ReportStyle', sequence 'TestReport', sequence file 'C:\Program Files\National Instruments\TestStand 2010\Components\Models\TestStandModels\BatchModel.seq'

"ReportGen_" + Parameters.ReportOptions.Format + ".seq" in step 'Set Report Disabled Message', sequence 'TestReport', sequence file 'C:\Program Files\National Instruments\TestStand 2010\Components\Models\TestStandModels\BatchModel.seq'

RunState.ProcessModelClient in step 'MainSequence Callback', sequence 'Single Pass -- Test Socket Entry Point', sequence file 'C:\Program Files\National Instruments\TestStand 2010\Components\Models\TestStandModels\BatchModel.seq'

RunState.ProcessModelClient in step 'MainSequence Callback', sequence 'Test UUTs -- Test Socket Entry Point', sequence file 'C:\Program Files\National Instruments\TestStand 2010\Components\Models\TestStandModels\BatchModel.seq'

Step 'Call Requested Sequence', sequence 'ProcessDialogRequests', sequence file 'C:\Program Files\National Instruments\TestStand 2010\Components\Models\TestStandModels\BatchModel.seq'

RunState.ProcessModelClient in step 'Create Test Socket Execution', sequence 'Initialize TestSocket', sequence file 'C:\Program Files\National Instruments\TestStand 2010\Components\Models\TestStandModels\BatchModel.seq'

---------------------------------------

[~jiggawax~]

Basically because the report generation sequences are called using expressions then it's hard for the deployment utililty to know which exact one you will be calling.  So all it means is make sure those are on the deployed machine.  Which they should be.  If they aren't then you just need to deploy them as well.  I find that most people just deploy the entire Models folder to save time.  In general you can ignore those warnings.

Hope this helps,