Teststand Sequence Context reference becomes invalid

[GoKu25]

I have an Action step VI that calls another VI asynchronously and passes the TS sequence context along. Inside the Async VI, the reference becomes invalid when i check with not a refnum function. 

 The error is: 

Error 1 occurred at Unzulässige Funktion.
in Initialize Termination Monitor.vi->TPL.PXI RF.Interface.lvlib:AsyncObjects_Viewer.vi->TPL.PXI RF.Interface.lvlib:AsyncObjects_Viewer.vi.ACBRProxyCaller.D4A00078

Possible reason(s):

LabVIEW: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.

How is the  reference going out of memory?

[GoKu25]

Update:

When I turn off my highlight execution in the Async VI, the reference seems valid. But the problem is that I want to pass this reference to a sub VI inside a While loop within the Async VI and the reference becomes invalid in the while loop and a valid one is not passed into a sub VI. I also tried using the reference as a global variable but it does not help.

I have attached a simple TS program and VIs to present my case. Have a look

[TBasel]

Hello,

Please send back full LabVIEW project with a VI that can generate the same error, enclosed in a ZIP file, because I didn't encounter any errors on my side while running your attached VI.

Thanks.

[GoKu25]

It still doesn't run the way I want it to. I didn't say how to run the VI previously. 

Please follow the steps 

1. Have the front panels of Called VI open

2. Run TS program and minimize the message pop up

3. In Called Vi, click check button and observe the dialog boxes

4. Click stop to end all VIs

5. Close the message popup in TS to end the program

[PatrikKaranNI]

Hi GoKu25,

It has been a while this post was active.

Are you still experiencing an issue with reference becoming invalid in your application?

Thanks,

Patrik

[GoKu25]

Yeah, I haven't been able to find a solution and ended up using a global variable to make it work

[PatrikKaranNI]

Hi,

could you share a solution with us to have this topic solved and closed with your workaround?

Patrik