Server crashing after 6-8 days, diagnostics?

[torres]

Hello,

I have written my LabVIEW application (or rather, modified an old program), on my WinXP Pro SP3 laptop with Labview 2009. I built an executable and an automated installer program. It has been installed on other machines (with no Labview application installed) and runs fine.

- Runs on WinXP laptop, have had no crashes and has run 1wk+

- Runs on Win2003 server R2, no crashes and has run 1 month ++

- Runs on Win2008 server, but O/S tends to crash consistently after 6-7 days. Has to be rebooted remotely using DRAC (remote access control card on the server) - the normal access method of VNC (remote desktop) fails to work.

While it seems that the problem is probably server related rather than Labview application related, I have the following questions:

- Are there diagnostics available to see if there is a memory leak or similar on the Labview application? We have observed indications of this with Windows diagnostic tools but it doesn't say what application is using the memory.

- Is it possible that a memory leak or other problem would manifest itself on one operating system (win2008 server) and not another (win2003 server)??  

- Is there any difference in where the LabVIEW program is built / run? Ie, should we try installing LabVIEW 2009 on a win2008 server and build the application from there? Will that be any different?

Thanks for any ideas.

Nick

[Vivek_N]

Hello Nick,

It does not look like this problem is being caused by LabVIEW. You should be able to use Windows Task Manager to take a look at the RAM usage of LabVIEW when you run your application. If you observe that the RAM usage on your Win2008 server machine is different from that on your Win2003 server and WinXP machines, definitely let us know. 

The operating system on which the LabVIEW application is built is not a concern. As long as the deployment machine has the right version of the LabVIEW Run-time engine installed (2009 in this case), it should work.