TestExec Access violation After Exit !!

[Sven.S]

Appreciate Any help I can get with this error !! Its driving me nuts !!

Firstly, on my development PC all the compiled applications function as expected, the problem lies with the target PC. I have set all applicable executable files (labview compiled projects) to run with admin rights, even though I am using a admin windows user account just to be sure. Both PC's are running windows 7 professional with the latest service packs and updates installed. No virus software is running on the target machine either.

Overview Description of my implementation:

Parent Application (labview compiled)  - launches using the command prompt (system exec) a shortcut link to my TEST STAND operator interface which through the parent application allows the operator to select specific sequence test files. I setup system exec to run minimized and wait until completion.

Operator Interface - Runs the sequence file, all error handing comes back clean and once I quite the operator interface. Returns me back to the parent application from which it was called.

As the operator interface is closed down, (modified SIMPLE USER INTERFACE, which comes standard with TESTSTAND) I get a access violation error as the parent application regains focus. This error only occurs on my test PC, not on my development PC which would indicate there is probably nothing wrong with my logic but a mystery setting on the target PC.

Has anyone encountered a similar problem before, if so how did you fix it. ANy help is appreciated.

Best regards,

Sven

[Sven.S]

Also on a second note, the traget application is a deployment made from test stand. Hence there is only a test stand deployment liscence on the target machine.

[Sven.S]

I have done further investiation.

1 - if I call the operator interface shortcut file directly through windows, the same access violation occurs !!

2 - I have attempted dissabling NIER (responsible for reporting the error), still no luck. Windows comes back during the operator interface closure, "the program has stopped responding" and searches for a solution online, doing a force closure after a few seconds

3 -  I have installed the trial version of the full development system incase my deloyed installer missed key instillation files. This also had no effect.

Anyone have any further suggestions?

[Norbert_B]

---

@Sven.S wrote:

I have done further investiation.

1 - if I call the operator interface shortcut file directly through windows, the same access violation occurs !!

[..]

---

So you already tested the UI without the "parent application"?

Does it crash when it shuts down or if it loses the focus?

Does the unmodified Simple OI run without crash on this machine?

Does the crash occur if you call an example sequence (the crash might be connected to your custom sequence....)?

Do you use a default process model?

You should have posted this question in the TestStand forums.....

Norbert 

[Sven.S]

Thanks the the help,

1 - same error occurs without the parent application, running the shortcut directly gives the same access violation on close

2 - crash occurs during shutdown (using the "Shutdown" labview command)

3 - Unmodified IU - still working on this

4 - Untested, will check that today

5 - yes, the default process "Batch Model" with two sockets is used

I will report back my findings on the above two possibilities. Just remember. My development PC has no issues and runs the application flawlessly. So my guess is there is something different between the development and the target PC.

Thanks,

Sven