batch model crashes with unknown property DATA source TSAPI

[Michael_Munroe]

I have a working sequential model test sequence and I am converting it to a batch model.  The UUT dialogs have been disabled and replaced with my own sequence to get the number of units and serial numbers.  There are up to 10 units set as a constant near the begining.  At the end there is a new sequence called to show the results.  The step where the unused units where disabled is skipped because the disabled state caused the unused threads to hang on some type of syncronization notification.

My main problem is that after I run the user sequence, both dialogs show correctly, and the tests run fine.  Sometime after the post-processing state is entered TS crashes with "Unknown property DATA, source TSAPI".  This dialog repeats many times and then the TS editor window is missing all data displays and step details.  HELP...

[herosphro]

Hello Micheal,

Just to check, are the UUT dialogs the only changes you have made to the process model in this case?  When you reference 'post-processing' do you mean Cleanup section of Main Sequence or the ProcessCleanup sequence? Also just for reference what version of TestStand are you using? 

The fact that 'DATA' is mentioned as the unknown property might point to some issues with database logging.  Are you doing logging with this sequence?  If so, the reason that this dialog may be appearing multiple times is that its trying to log data it can't map to the database.  I look forward to hearing back from you and getting this problem solved.

[Scott_Richardson]

Michael -

The database logging could be getting messed up, but the question is what is the underlying cause? It appears that the either memory is getting corrupt and the sequence file is getting hit, or maybe an extra release is getting called on the Data property of the file and it gets released. The key to debugging this is to slowly remove various operations that are being done to attempt to isolate what operation might be causing the problem. So you might want to disable/noop different aspects of your test senario to see if the problem no longer occurs or the problem changes. Areas include, database logging, report generation, simplify the client seuqences called, noop portions of the model file operations, etc.

Another option is to place inspection steps into the various stages of your execution (model and client) to see if the Data property still exists. Moving the inspection steps will tell you when the Data existed and when it does not.