Re: Orphaned Process and Pview

Hi Thomas,

Thank you for getting back to me. I've tried that among many other
utilities I have found on the net. Since my post I have discovered it's not
just a single orphaned executable, but an entire session that is orphaned
(not disconnected). It just so happens this one EXE consumes 25% of the CPU
and that is what we were focusing on.

When this problem happens, most of the time we're not able to see any of the
sessions in the Terminal Services Manager, the question mark just hangs over
the server name. Although when it does open, we find the session that
started the EXE in question isn't there.

Today I found that it's not just that one EXE. For the same session ID
(found in task manger) I see other in-house written EXE's running as well as
WINLOGON.EXE, CSRSS.ESE, rdpclip.exe and explorer.exe. I am unable to kill
any of them and I am unable to log that session id out using a TSLogOff
utility I got off the net. The utility claims that session id wasn't found.

This happens a few times a week on various production Windows 2000 servers.
The only solution so far is to reboot the server.

I'm not sure if the EXE that is using 25% of the CPU is the cause of this
hung session or the effect of the hung session.



I've tried that amoung ever
"ThomasT." <ThomasT@xxxxxxxxxxxxx> wrote in message
news:ujfzM$uRHHA.1860@xxxxxxxxxxxxxxxxxxxxxxx
Since this is a Terminal Services related group, I assume that you are
talking about under an TS session.
On terminal server, I figureout that the kill does not work well, use
TSKill instead

Regards

Thomas T.

"jokes54321" <jokes54321@xxxxxxxxxx> a écrit dans le message de news:
%23iCGGstRHHA.4896@xxxxxxxxxxxxxxxxxxxxxxx
Microsoft has the KB article http://support.microsoft.com/kb/197155 that
lists three things to try to kill an orphaned process. The first two
methods failed and I'm a little lost on Pview.

I have two different versions of pview and neither of them have the
security pane this KB article talks about.

Any ideas?

TIA,

Denny





.

Relevant Pages

  • Re: RWW Timing
    ... I understand that you want to monitor when and how ... > to an internal Windows XP or Terminal Server computer. ... SBS creates a connection to the internal client on port 3389 which is ... But it can not tell which one session from the RWW, ...
    (microsoft.public.windows.server.sbs)
  • Re: Restricting TS USers
    ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Terminal Services and Microsoft Windows Server 2003 Service Pack ... the remote session does not end immediately. ...
    (microsoft.public.windows.terminal_services)
  • Re: ASP sessionstate
    ... :>: so it is a clientside issue. ... ASP doesn't know or care what browser it ... but then it is not a new session. ... :> How can a Response.Write write to the server screen? ...
    (microsoft.public.inetserver.asp.general)
  • Re: ASP sessionstate
    ... ASP doesn't know or care what browser it ... ticket number given when the first item is added to the cart. ... How can a Response.Write write to the server screen? ... :> delete the cart file and set the session ...
    (microsoft.public.inetserver.asp.general)
  • Re: Explanation of macros; Haskell macros
    ... > server and I got to dictate the form of the commands and arguments. ... it boiled down to (funcall command client-session args). ... Let's assume there is a type "Session" for sessions. ... You don't need the first constraint, ...
    (comp.lang.python)