Software

Ask something
Discussion Locked

Service(s) Freeze

0 helpful
5 replies

by asifmah

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Though rare, I have encountered this problem; where Services on my NT 4.0 (especially Exchange v5.5) and sometimes other Services don't properly Stop.

Apparently they appear as being Stopped, when you click on Start - the system says "They are already Running" when you try to Stop them again from Command prompt or by using any 3rd party software like Hyena etc... - the systems says "The Service cannot be conrolled in its current state". This finally leads to the complete Server shut-down and restart.

Recently, I have learntly about RoboER s/w from Heroix which can terminate freezing processes; but, this requires you to physically connect to the server through its Serial Port, isolate the process and kill it. Also, it is pretty expensive.

Does anyone have an idea with a Tool or Technique which can addres this freezing issue without requiring the Server reboot everytime it happens ?

5 replies

by xpertdragon

Make sure you have at least service pack 4 for your exchange server 5.5, and other exchange 5.5 patches. there are several that address services that lock and or hang up.

Paul

by asifmah

Yes! I have the latest SP-4 for all of my Exchange v5.5 servers. Like I mentioned, though it is especially with Exchange Service - I have found this to be happening with other Services too (like DHCP, IIS Admin etc...)

by dynamo2003

It seem as if you are rather impatient, sometimes when you are stopping services in Exchange no doubt it seems as if the services have frozen but the trouble is that because Exchange uses various services in one go, the services has to be stopped inthe right order. For example, stopping System Attendants stops all running services in the right order but because logs have committed with other processes running you will have to be patient.

Alternatively you can schedule an ‘AT command’ to stop services in the following order:
MTA
Information store
Directory services
Systems Attendant.

by asifmah

The Services are being Stopped in the correct order.
When I conclude the Service as "Freeze"; it means I have waited for quite sometime before my Exchange Monitor sends me an 'Alert' of Service as being stopped.

I repeat, it is not alone with Exchange - it is a generic problem with Windows NT 4.0 and Windows 2000. All, I am looking for is if there is something like 'Pviewer' or 'Kill' which can detect the frozen component / process and help in killing it.

This discussion is closed to new replies.