TestStand Warning message

[TommyB]

Hello all...
I am using a modified version of the simple LV user interface in the
examples directory that is making calls to TestStand. When I restart the
application I get the following warning...
"Warning: Some executions were not released the last time the TestStand
engine was destroyed."

Does anyone know how to determine what executions TestStand is referring to?
This isn't a terribly big problem as when I hit "OK" the application
continues. It only occurs when I restart the application after having run
it at least one.

I have tried looking all throughout the application and can't seem to
determine what hasn't been closed.
Thanks,
-Tom

[Richard McDonell]

Tom-

I have seen this warning before at the start of an operator interface that I modified. This type of warning can result from the TestStand Engine not being shut down properly by the operator interface. It is important to remember that shutting down the TS Engine within the operator interface is actually a two step process. For more information regarding this process, see the Writing an Application section of the Help>>ActiveX API Reference guide accessed through the Sequence Editor help menu.

Another thing that could cause this type of warning is if you did not properly release all of your sequence files before shutting down. You need to make sure that all of your test sequence files are being released before you close the operator interface. Any refer
ence you obtain to a sequence file should be released by calling the Engine.ReleaseSequenceFile method of the TS API before shutting down the TS Engine. For more information regarding this API method see the above ActiveX API Reference guide as well.

If you make sure you are doing both of these items properly the warning you are seeing when the operator interface starts up (i.e. a TS Engine object is created) should go away and execute properly.

Richard McDonell
Product Marketing Engineer
National Instruments Corp.
www.ni.com/ask

[TommyB]

Richard:
I am doing both of these steps. It must be something else. The only thing
that I've added that is different from the simple LV example is that I allow
for two simultaneous sequence executions. At shutdown I close everything
associated with both executions as previously done when there is only one
execution. I also made two execution globals instead of the one global in
the that is in the example.
*Also worth noting is that if I just start the VI and then close it without
loading any sequences or running anything I get the same warning when I go
to restart the VI Therefore I think it is definitely asociated with the
shutting down of the engine and not with releasing any of the sequence
files.
Any other ideas are appreciated. Again, it's not that big of a deal just
somewhat of an annoyance at restart.
Thanks again,
-Tom


"Richard McDonell" wrote in message
news:506500000005000000D11F0000-984882144000@quiq.com...
> Tom-
>
> I have seen this warning before at the start of an operator interface
> that I modified. This type of warning can result from the TestStand
> Engine not being shut down properly by the operator interface. It is
> important to remember that shutting down the TS Engine within the
> operator interface is actually a two step process. For more
> information regarding this process, see the Writing an Application
> section of the Help>>ActiveX API Reference guide accessed through the
> Sequence Editor help menu.
>
> Another thing that could cause this type of warning is if you did not
> properly release all of your sequence files before shutting down. You
> need to make sure that all of your test sequence files are being
> released before you close the operator interface. Any reference you
> obtain to a sequence file should be released by calling the
> Engine.ReleaseSequenceFile method of the TS API before shutting down
> the TS Engine. For more information regarding this API method see the
> above ActiveX API Reference guide as well.
>
> If you make sure you are doing both of these items properly the
> warning you are seeing when the operator interface starts up (i.e. a
> TS Engine object is created) should go away and execute properly.
>
> Richard McDonell
> Product Marketing Engineer
> National Instruments Corp.
> www.ni.com/ask

[Richard McDonell]

Tom-

Hmmm...I agree with you in that it definitely sounds like an engine shutdown issue. The only thing that I can think of at this point is to make sure that you are only creating 1 (one) TS Engine reference when you start your operator interface. Does the problem occur when you run the original simple operator interface that installs with TestStand? I would definitely try to find the reason for this warning. While it may appear as just an inconvenience it is not good for such a warning to persist otherwise the developers would not have created the warning. If you run out of ideas, I would suggest that you email an example of your code to our support engineers www.ni.com/ask so they can take a look at it and figure out the problem. Hope thi
s helps...

Richard McDonell
Product Marketing Engineer
National Instruments Corp.
www.ni.com/ask

[TommyB]

Richard:
I finally found the problem. I was not closing an execution reference.
Little did I realize that I wasn't even using the reference. I have
attached a picture showing the problem that I was encountering. Hopefully
other can avoid this problem in the future. Would it be possible for NI to
make those execution terminals require a valid sink rather than being open
ended? Thasnk for your assistance.
-Tom

"Richard McDonell" wrote in message
news:50650000000500000097200000-986092468000@quiq.com...
> Tom-
>
> Hmmm...I agree with you in that it definitely sounds like an engine
> shutdown issue. The only thing that I can think of at this point is
> to make sure that you are only creating 1 (one) TS Engine reference
> when yo
u start your operator interface. Does the problem occur when
> you run the original simple operator interface that installs with
> TestStand? I would definitely try to find the reason for this
> warning. While it may appear as just an inconvenience it is not good
> for such a warning to persist otherwise the developers would not have
> created the warning. If you run out of ideas, I would suggest that
> you email an example of your code to our support engineers
> www.ni.com/ask so they can take a look at it and figure out the
> problem. Hope this helps...
>
> Richard McDonell
> Product Marketing Engineer
> National Instruments Corp.
> www.ni.com/ask



[Attachment labview picture.bmp, see below]

[dordon73]

Hi all,

I have the same warning popup problem on a LabVIEW executable interface that manages teststand engine and run sequences and can't find the source of it.  If I press the OK button all works fine....but this popup is unwanted by the customer !

Is there a trick to disable this popup (from Testastand APIs in LabVIEW or from TestStand editor itself) ?

The popup doesn't appear if I lanuch sequences from TestStand editor !

Thanks.

[RaymondFarmer]

This should have been a new message rather than hanging it on old message dated 2001 which was completed.

Also, it a bit lacking in information, maybe some screen shots if you can not provide some sample code. When does this popup occur? Is it actually a warning message?

regards

Ray

[dordon73]

Sorry I realized the original thread was very old only after sending my message.

I finally solved the problem: I found wich sequence file was not unloaded at the end of the execution, then added a ReleaseSequenceFileEx command.

As often appens, a long time to discover the problem, a very quick solution 🙂

Anyway, thanks for you interest in my problem !

Best Regards