Problems with logoff or restart of windows 2000 server

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

hi out there
During the last 2 months I have seen a problem show up which escalates -
when a windows 2000SP4 server has been running for "some" weeks (2-3) we
cannot logoff the console - nor reboot the server - only a forced power off
(unplugging the power cable or resetting the box) will restart the server. I
cannot find any erros in the eventlog nor anything suspect on the server
itselfs. They run fine but we cannot restart them. We are using them for RDP
and has a Sybase DB ruuning on it. It looks to me as a leak somewhere - but
it doesn't help to run a full windows update and ensure that everything is
updated (have tried). If we kill the explorer running on the console we just
ge a "blank blue screen".
Has somebody ideas for tracking this problem?
 
TIwang said:
hi out there
During the last 2 months I have seen a problem show up which escalates -
when a windows 2000SP4 server has been running for "some" weeks (2-3) we
cannot logoff the console - nor reboot the server - only a forced power off
(unplugging the power cable or resetting the box) will restart the server. I
cannot find any erros in the eventlog nor anything suspect on the server
itselfs. They run fine but we cannot restart them. We are using them for RDP
and has a Sybase DB ruuning on it. It looks to me as a leak somewhere - but
it doesn't help to run a full windows update and ensure that everything is
updated (have tried). If we kill the explorer running on the console we just
ge a "blank blue screen".
Has somebody ideas for tracking this problem?
Click to expand...

- Make a note of the amount of memory consumed by the various
application, using the Task Manager.
- As a work-around, reboot the server automatically once every week.
 
Hi again
The problem isn't that simple - when we issue an cntrl-alt-del from the
console nothings happens - any idea of what can force the kernel (csrss.exe
probably or lsass.exe ? which of the processes are responsibel for handling
this?) Even a remote issued shutdown doesn't work - accepted but ignored. I
have seen this behavior now at approximately 10 servers on different -
independent - sites.
regards /ti
 
inhi again
During a brainstorm this afternoon we concluded that the server is probably
in some fase of a shutdown - we expect that we have a process which will not
terminate and responds with a negativ reply to a terminate request (the
deployment staff are not sure that they request a forced shutdown) - is there
a wayu to check-up how far in a shutdown the system is? Or more precisely -
is there a way to determine in what state the system in fact currently is ?
regards /ti
 
high again
During a discussion this afternoon we concluded that the server is probably
in some fase of a shutdown - we expect that we have a process which will not
terminate and responds with a negativ reply to a terminate request (the
deployment staff are not sure that they request a forced shutdown) - is there
a way to check-up how far in a shutdown process the system is? Or more
precisely - is there a way to determine in what state the system in fact
currently is ?
regards /ti
 
Back
Top