Article ID: 822939 - Last Review: April 9, 2008 - Revision: 7.0 Messages that are sent in an Exchange Server 2003 and Exchange 2000 Server organization are not deliveredThis article is a consolidation of the following previously available articles: 319885 and 290290 On This PageSYMPTOMSYou may experience one or more of the following symptoms in Microsoft Exchange Server 2003 or Microsoft Exchange 2000 Server. SYMPTOM 1When users try to send messages to addresses in your Microsoft Exchange organization by using Simple Mail Transfer Protocol (SMTP), they may experience one of the following behaviors:
SYMPTOM 2If you view the tracking history of the sent message, you may notice information resembles the following information:SYMPTOM 3If there are other servers in the routing group, those servers can send mail to each other. However, those servers cannot send mail to or from the server that is experiencing the problem. If a user tries send mail to a mailbox on the server that is experiencing the problem, the user receives a non-delivery report (NDR) that resembles the following NDR:-----Original Message----- From: System Administrator Sent: Tuesday, February 20, 2001 6:04 PM To: Ops, Global Subject: Undeliverable: Test Message Your message did not reach some or all of the intended recipients. Subject: Test Message Sent: 2/20/2001 6:04 PM The following recipient(s) could not be reached: Ops, Global on 2/20/2001 6:04 PM The e-mail system was unable to deliver the message, but did not report a specific reason. Check the address and try again. If it still fails, contact your system administrator. server.domain.com #5.0.0 SYMPTOM 4The following Exchange services may not start:
Could not start the Microsoft Exchange Routing Engine service on Local Computer. Error 1083: The executable program that this service is configured to run in does not implement this service. SYMPTOM 5In Exchange Server 2003, e-mail messages may be stuck in the Message Transfer Agent (MTA) queue.CAUSEThis problem may occur if the association of Microsoft Exchange to the SMTP service is damaged or if the IIS (or only SMTP component of IIS) for Microsoft Windows 2000 and Windows Server 2003 has been reinstalled, but the Exchange Server SMTP service extensions have not been restored. RESOLUTIONTo resolve this issue, follow these steps: Step 1: TroubleshootDetermine whether all the Exchange command verbs for the SMTP service are present:
Step 2: Reinstall Exchange ServerIf some of the Exchange association SMTP command verbs are missing, you must reinstall Exchange 2003 or Exchange 2000.Note When you reinstall Exchange, it does not overwrite the databases. It only backfills any missing files and metabase entries. This does not affect the settings or mailboxes on the server that is running Exchange. To reinstall Exchange 2003 or Exchange 2000, follow these steps:
To run Smtpreinstall.exe, follow these steps:
MORE INFORMATIONWe strongly recommend that you perform regular metabase backups. You can do this by choosing the System State backup option with your backup program. You can also do this by right-clicking the server in Internet Service Manager. If you have a good metabase backup, you can restore that backup instead of using the steps in the "Resolution" section. The Windows 2000 or Windows 2003 SMTP service is a key underlying component of Exchange 2000 or Exchange 2003. If you uninstall IIS or SMTP, the bindings and registrations that Exchange requires are removed. Therefore, you should not remove and reinstall IIS on an Exchange server, except in extreme cases. IIS stores its configuration in an enhanced registry-like binary hive that is called the metabase. If you are running IIS, we strongly recommended that you back up the metabase. If your SMTP service is removed unexpectedly, check to make sure that the Exchange Server 5.5 MSExchangeIMC key does not exist on the server that is running Exchange 2000 or a later version of Exchange. Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: 322756
(http://support.microsoft.com/kb/322756/
)
How to back up and restore the registry in Windows To check for the MSExchangeIMC key, follow these steps:
294804
(http://support.microsoft.com/kb/294804/
)
SMTP is removed when you upgrade to Windows 2000 Service Pack 1 or Service Pack 2
REFERENCES
For more information about how to remove and to reinstall IIS, click the following article number to view the article in the Microsoft Knowledge Base:
320202
(http://support.microsoft.com/kb/320202/
)
How to remove and to reinstall IIS on a computer that is running Exchange Server
For more information about troubleshooting transport issues in Exchange Server 2003, click the following article numbers to view the articles in the Microsoft Knowledge Base:
821910
(http://support.microsoft.com/kb/821910/
)
How to troubleshoot for Exchange Server 2003 transport issues
821905
(http://support.microsoft.com/kb/821905/
)
Message tracking event IDs in Exchange Server 2003
| Article Translations
|
| United States | Change | | | All Microsoft Sites |
Back to the top
|
