Software

Ask something
Discussion Locked

Services unexpectedly terminate

0 helpful
7 replies

by jmcmul

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have Exchange 2000 running on a W2K server. At random times throughout the day and night, several of the Exchange services, the IIS Admin service, and the WWW service terminate unexpectedly. I set the services to restart automatically, but afterawhile teh POP3, IMAP4, and SMTP services refuse to start up and I am forced to reboot. Everything seems to work fine when the services are up, but I am looking for ideas to try and cure this problem. Only Exchange and IIS services are affected. A quick response would be appreciated.

7 replies

by curacao_dejavu

what are the service pack levels of exchange 2000 (sp1) and w2k (sp2). Is IIS patched against the existing vulnerabillities ?
Do you have a antivirus running on the server to protect againt virusses , both for the email and locally?

regards,

Leopold,

by jmcmul

I am running SP2 on W2K and SP1 on Exch2K. I do have anti-virus running for both internal and external email. However, even turning it off has no effect. Thanks for the quick response. BTW, IIS has been patched to the latest hot fix.

by rlevesque

Do you have any other services or applications running thats normally not installed with NT itself? What I mean, is have you installed any other application such as VNC, or pcAnywhere, or anything else like Diskeeper, etc... If you have, I would turn them off, and one by one turn them on and see if thats the culprit.

I had the same problem with IIS4 and NT4, and finally I narrowed it down to a conflict with Crystal Reports 7 and VNC. Once I disabled VNC, and went to pcAnywhere on that server, my Web service hasn't shut down since.

Granted this was with NT4, but the idea is the same. Maybe there is a conflict with a certain installed app or service.

Good luck!!

Richard

by maxwell edison

Run Eseutil (eseutil.exe), one of Exchange Server’s troubleshooting and disaster-recovery tools to determine whether Exchange Server believes that the Directory Store database (i.e., dir.edb) is corrupted. Eseutil is a command-line utility that resides in the \%systemroot%\system32 folder, so you can run it regardless of your current directory.

To determine dir.edb’s integrity, type:

eseutil /g /ds

The /g switch tells the tool to run in integrity check mode (this is a read-only mode and won’t make any changes to your database), and the /ds switch tells Eseutil to evaluate the Directory Store database. If you want verbose output, you can also use the /v switch; if you want detailed error messages, use the /x switch. (To view the available switches, run Eseutil with the /? switch only.)

Running Eseutil might provide additional information about the problem, including whether compromised database integrity-a likely though not guaranteed suspect-is to blame as well as the severity of any corruption. Assuming that database corruption is the problem, the next step is to use Eseutil’s /r (for recovery) option attempt a soft recovery. Type:

eseutil /r /ds

Eseutil provides output during the recovery operation and informs you whether the recovery was successful.

At least this may provide a clue.

Maxwell

This discussion is closed to new replies.