Report Generation working on Dev machine but not on Deployment + Lessons learned

[SimpleJack]

I don't do deployments very often with Teststand. But I have to say, I learned a lot from this one from trial and error and help from the message board. I have got my deployment to final work (almost) with these lessons learned:

1. Create a base installer for the engines and drivers, that way if you need to update it is much smaller.

2. Dont install Teststand before Labview on a new development machine (not related to this deployment but I did learn that)

3. Don't have your Testexec window open, alter the Station Globals, then close the window. It just puts them back to the old version (probably my biggest problem).

4. Paths are extemely important.

I think I have figured it out with much time involved and kept notes of what I have done for future. The ONLY issue I have left is this below. My dev machine works as it should but when I deploy, it does not. FYI- I manually copied over Station Globals, Process model, and Testexec. DO I need something else?

I create serial numbers for my UUT's in the proceses model. It all works fine in development. The serial numbers are generated and the UUT filename is titled [023232232].txt and changes per unit. The path for example lets say is C:\Users\Ryan\Desktop\temp.  A logfile is generated for each and put in that folder.

When I deploy, it does something different. Instead of putting the files into the temp folder, it errors out saying it is in use. If I delete the temp folder, it creates a file called "temp" which contains my text logfile. This file just keeps getting overwritten.

Any ideas on this?

[~jiggawax~]

In the <TestStand>/Cfg folder you will find a file called TestStandModelReportOptions.ini.  This is what gets configured every time you go to Configure>>Report Options from either the Sequence Editor or the User Interface. Sometimes it's a good idea to deploy this file and sometimes it's not.  Depends on your situation.

To do a quick check you can go to Configure>>Report Options on your dev machine fromt the Sequence Editor and see if they match Configure>>Report Options from the User Interface on your deployed machine.  If they do then I'm guessing you have permission issues with the temp folder or something like that.  I bet you'll find they don't match.

Cheers,

[TaylorG]

Hi SimpleJack,

One way you can ensure that the Report Options you want to have stay with your sequence file is to actually override them using a Sequence File Callback.  I have attached a link to a KnowledgeBase article that walks you through how to add the ReportOptions callback to your sequence and programmatically set the options that you would normally set by going to Configure»Report Options from the Sequence Editor.  

Also, to ensure that the correct Process Model is being used with your sequence file after distributing, you can set the Process Model within the Sequence File Properties.  This can be found by going to Edit»Sequence File Properties, and then going to the Advanced tab.  I have attached a screenshot of this window below, as well.  From here, you can set the Model Option to Require Specific Model, which especially comes in handy if you are using your own custom Process Models.

I hope this helps, SimpleJack!  Have a great day!

How Can I Programmatically Enable or Disable Database Logging or Report Generation?