Hi JB,

This is why MS doesn't advocate running Excel on a server. It's too easy to
leave orphaned instances hanging around, which, as you know, will cause
problems as they chew up more and more memory.

One thing you can try is to execute this vbscript code:

ShowExcelApp

Sub ShowExcelApp()
Dim obj

Set obj = GetObject(, "Excel.Application")
obj.Visible = True

Set obj = Nothing
End Sub

Just put this code in a text file and name it getexcel.vbs. You should then
be able to execute it on the server with wscript or maybe by double-clicking
the icon. It should grab one orphaned instance and make it visible, thus
enabling you to see what state the application is in. Likely, you'll see
that an unanswered error message or prompt is keeping Excel from closing.

--
Regards,

Jake Marx
www.longhead.com


[please keep replies in the newsgroup - email address unmonitored]


JB2005 wrote:
Situation: Inactive or incorrectly terminated Excel process images
accumulate on server

Anyone out there with knowledge/advice on how to access a hung(?)
instance of Excel and pull information about the calling event or
anything else that may help identify the root cause?

Any auditing techniques out there that can record such events?

Your help much appreciated.