Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

IIS, SMTP & Exchange Services Stop Responding - HELP

Status
Not open for further replies.

WinNT511

IS-IT--Management
Apr 24, 2003
53
US
Over the past serveral weeks we have noticed that Event ID 7031 is repeatly logged to the system event viewerm with the following details:

Event Type: Error
Event Source: Service Control Manager
Event ID: 7031
Description: The IIS Admin Service service terminated unexpectedly. It has done this X time(s).
The following corrective action will be taken in 1 milliseconds: Run the configured recovery program.


Event Type: Error
Event Source: Service Control Manager
Event ID: 7031
Description: The Microsoft Exchange IMAP4 service terminated unexpectedly. It has done this X time(s).
The following corrective action will be taken in 0 milliseconds: No action.
Event Type: Error
Event Source: Service Control Manager
Event ID: 7031
Description: The Microsoft Exchange POP3 service terminated unexpectedly. It has done this X time(s).
The following corrective action will be taken in 0 milliseconds: No action.


Event Type: Error
Event Source: Service Control Manager
Event ID: 7031
Description: The Microsoft Exchange Routing Engine service terminated unexpectedly. It has done this X time(s).
The following corrective action will be taken in 60000 milliseconds: Restart the service.


Event Type: Error
Event Source: Service Control Manager
Event ID: 7031
Description: The Simple Mail Transport Protocol (SMTP) service terminated unexpectedly. It has done this X time(s). The following corrective action will be taken in 0 milliseconds: No action.

Event Type: Error
Event Source: Service Control Manager
Event ID: 7031
Description: The World Wide Web Publishing Service service terminated unexpectedly. It has done this X time(s).
The following corrective action will be taken in 0 milliseconds: No action.

Event Type: Error
Event Source: Service Control Manager
Event ID: 7031
Description: The Network News Transport Protocol (NNTP) service terminated unexpectedly. It has done this X time(s). The following corrective action will be taken in 0 milliseconds: No action.

THis happens serveral times a day with no particular event triggering these error messages. These services will stop and then restart or at times we have to re-start the services manually. The exchange server is Exchange 2000 with SP3 and all hotfxes applied. The exchange server is installed on Windows 2000 Server SP4 with all patches up to date. The exchange server hosts about 55 e-mail accounts.

I have performed the following to the system:
**Have Ran 2 AV scans (Yielding 0 Infections)
**Have logging enabled on the on both IIS and exchange but the logs have yielded nothing suspioious.
**Installed Service Pack 4 (6-1-05) with no improvment.

The Server also Hosts (DNS, DHCP, and is a Domain Controller). I know that the (MS KB Q316612) Code Red Worm can have a effect on these services, but we have run multiple AV scans with no trace of virus infection.

We need to fix this problem as we plan on adding additional activity to our e-mail system in the next few months.

Please Provide HELP on how to proceed.

Winnt511


 
Just recently I had this problem as well. It kept me frustrated for about a week.

Now I think this problem originated from service pack updates... because I had this problem and also I had corrupt XML parser DLL files. I was able to resolve the XML parser problem without much issue... but this issue was much bigger.

My problem that was causing this had to do with a program called ArchiveStoreEM. Our company uses this program with a company called Amerivault who provides a remote archive mirror of our Exchange mailboxes.

Based on the findings of Microsoft (who did a close exam of crash debug logs) ... they traced the problem to a DLL having to do with the ArchiveStoreEM program.

To resolve this, Amerivault had me remove the EventSync plugin which this program uses and also did the following....

-Enable Exchange Native Journaling
-Setup BCC Journaling.

If anyone uses ArchiveStoreEM ... then this is your answer!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top