LV 2009 Dispose report leaves Excel in memory

[NPI_Chris]

Hello all,

I am hoping somebody can help, we think that the below problem is part of a larger problem where LV2009 is crashing on our server with memory is full errors.

In the attached vi which contains the excel portion of our larger vi with dummy data, it duplicates the issue where everything seems to run OK, but when you check windows task manager it appears the Excel is staying in memory after this executes. Despite the dispose report being at the end of the chain.

any help at all would be greatly appreciated.

thanks

[RavensFan]

I ran your VI and it works okay for me.

[NPI_Chris]

Strange, both on my machine and the server its leaving excel open but you can only see it in the processes tab in task manager.  we are running excel 2003 with sp3, are you running a different office version maybe? is it a backwards compatability type issue?

thanks for the fast response

[RavensFan]

Same version of office.  LV 2009f2.  OS is Vista 64 bit home premium.

I can try on my work computer tomorrow.

[RavensFan]

I can't run it here at work.  My version of Office is 2000 and this causes errors in a lot of the Report Generation VI's.

[PJS]

I remember having this problem a couple years ago, My fix was to kill the task programmitcally from my LabVIEW app.  Probably not the best solution in terms of fixing issues in toolkits, but I was in a hurry 😉 Sounds like this was not only my issue.

[NPI_Chris]

For OS its xp on my box, and server 2003 on the server.

PJS, interesting solution, not one I think I'd want to use long term, but it might help in figuring out if this is a contributer to our memory full issue.  I am not quite sure how to do that though, would it be possible for you to post an example?

thanks to everyone for the continued help, I know i can always count on the forum when I'm stuck :manvery-happy:

[PJS]

See this thread.

Message Edited by PJS on 11-05-2009 12:51 PM

[NPI_Chris]

PJS Thanks Very nice VI, it looks like it can come in real handy, I am thinking I might be able to modify it to log memory usage to help us troubleshoot the larger issue.

I am still hoping for a more permanent solution though....id really hate to have to continually add a kill process sub vi to all our excel use instances, as we use so many in our application....

thanks again

Chris

[RavensFan]

---

NPI_Chris wrote:

For OS its xp on my box, and server 2003 on the server.

---

What do you mean by "server 2003 ont he server"?  How does the server fit into the equation of what is running on your PC?  Is this file actually located on a server instead of at c:\ like in your posting?

If it's on a network drive, could it be that there are some longer delays in having the file open and close?  These long delays are causing code to run before earlier parts have finished loading.  So you wind up sort of actually closing the reference to Excel before it actually opens, then it gets stuck open?  What if you run it with execution highlighting on or step by step?