TS deployment shutdown no log

[mfitzsimons]

TS version 3.1 running on Win 2000 shut down without a reason. Checked in the morning and TS was completely exited. I searched for a log file to see why application crashed but can't find any log files. This is the second time it has happened on different deployment machines. Main loop consist of an infinite loop so there is no other way except pressing terminate.

A message board with a spell checker 🙂

[RajivG]

Hi mFitzSimons,

When you said Main loop containing infinite loop, does that mean you are having that loop on some steps in the main sequence? Also, what are you calling in those steps? I am thinking if it is because of some memory overrun or incorrect DLL call, etc?

If you are looking for some sort of log for errors, I would suggest using Windows Event Viewer located in Control Panel >> Admin Tools >> Event Viewer. TestStand does not create its own log file for errors.

I hope this helps,
Rajiv

[mfitzsimons]

---

@mfitzsimons wrote:
TS version 3.1 running on Win 2000 shut down without a reason. Checked in the morning and TS was completely exited. I searched for a log file to see why application crashed but can't find any log files. This is the second time it has happened on different deployment machines. Main loop consist of an infinite loop so there is no other way except pressing terminate.

A message board with a spell checker 🙂

---

Thanks! I did not find anything in the event log why TestStand crashed. The main loop as has only one way out, while (testCount < testRequested). When TestStand exited the count was way below the desired test count value.

Thanks again,

Matt

[RajivG]

Hi Matt,

TestStand usually never closes itself without any error messages unless there is some code module causing some trouble 🙂

To better understand the problem, see if you can provide the following information:
1) Are you using TestStand Sequence Editor (3.1) or Operator Interface (LV, CVI, etc)?
2) does the error occur all the time or just appears once in a while?
3) What kind of code modules are you calling (ActiveX, DLLs, etc)
4) Do you similar error if you run any/all of the shipped features? (like shipped OI, shipped examples, etc)
5) Does the TestStand application's UI disappears but a process remains in the memory? (when looking at Task Manager)

Do post whatever information you might have regarding this error.
Rajiv G

[mfitzsimons]

To better understand the problem, see if you can provide the following information:
1) Are you using TestStand Sequence Editor (3.1) or Operator Interface (LV, CVI, etc)?
- Using TS recompiled Operator Interface for version 3.1 (Nov 2004 release)

2) does the error occur all the time or just appears once in a while?
- Once in a while usually after a week or so. Other systems run fine for weeks. I am doing Windows Memory Monitoring on the system and there was 360 Meg Ram in use on a system that has 512 Meg of RAM when the system crashed.

3) What kind of code modules are you calling (ActiveX, DLLs, etc)
- Some activeX but 99% is LabVIEW

4) Do you similar error if you run any/all of the shipped features? (like shipped OI, shipped examples, etc)
- Can't run shipped OI, caused many problems because it is written in LV 6.1 so needs to be mass complied and rebuilt. I have not tried to run shipped examples but assume they would run fine.

5) Does the TestStand application's UI disappears but a process remains in the memory? (when looking at Task Manager)
- Task is gone with no sign of why it exited

[RajivG]

Hi Matt,

It's little odd for TS OI to crash. I believe you are using the same version of the OI on both computers and calling the same sequences. Do you know of differences in the computers where it works fine and where it crashes?

Rajiv