Batch model hangs when Windows is locked

[tdibble]

I'm running the batch model with 5 sockets.  When the Windows screen is locked, the model hangs after all of the test sockets have completed at the batch model step titled "Sync With Controller -- AfterPostUUT."  This call is part of the ManagedModelSupport.dll.  I have TestStand 2012 SP1 running on Windows Server 2008 R2 SP1.

I have attached some screenshots.

[STASHkal]

hello tdibble,

Is the hang specificaly associated with this step?  

if you do not lock the windows screen does the program hang?  

can you tell me a little about other steps you have taken so far?

[tdibble]

Yes, problem hangs at this step and the test completes successfully if windows is not locked.

I haven't done anything to get around this except disabling windows from locking the screen.

Thanks,

Ted

[dug9000]

Do you have or use any custom process model plugins?

-Doug

[tdibble]

dug9000,

I don't think so.  I'm pretty sure I have the out-of-box TestStand.  However, how can I verify this?

[STASHkal]

You can check the process model you are using at the bottom left of the TestStand window.  That being said you could have renamed or modified the model.....

does the behaviour only happen with the batch model? does a sequential or parallel model exhibit hangs?  

[tdibble]

StaysKool,

Nope, we didn't make changes to the batch model.  The sequential model works as expected.  I haven't used the parrellel model.

Thanks,
Ted

[STASHkal]

I tried running a Batch model with the windows screen locked today and the sequence completed successfuly (granted I am using a different version of TestStand and not on windows server 2008).  

I assume you initialy discovered this behaviour because your test takes longer than the windows timeout for your computer.  Can you force the hang by pressing Windows-L after you begin running a batch? 

[tdibble]

StaysKool,

Thanks for the response.  We did force the hang for locking the windows screen by pressing Windows-L.  For the time being, we have windows timeout disabled.  However, the IT policies will catch eventually catch up with us and we'll have to re-enable the setting.

[STASHkal]

Im shore IT is thrilled to have computers that never lock:)

Are you running the program with Admin privileges?  It is possible that going to sleep without admin privileges may terminate some threads.  

Additionally, have you attempted to run a batch model shipping example and locking the computer?  What are the results of such a test?