Microsoft KB Archive/281800

Knowledge Base

XCON: Troubleshooting Message Failures in Exchange 2000

Article ID: 281800

Article Last Modified on 9/11/2007

---

APPLIES TO

• Microsoft Exchange 2000 Server Standard Edition

---

This article was previously published under Q281800

SUMMARY

This article provides troubleshooting steps for message flow issues in Exchange 2000.

MORE INFORMATION

1. Determine where the message is stuck or from where it is generating a non-delivery report (NDR).
   1. Track the message if it just seems to disappear. See where it is stuck--the categorizer, message transfer agent (MTA), Internet Mail Service, Bad Mail folder, and so on.
   2. Check the NDR for error codes, and what server and component is generating the NDR.
2. Check the server where the message is stuck or from where it is generating NDRs, and make sure that all the services are running. In Exchange System Manager, check Tools and Monitor for the status of connectors.
3. See what Event IDs are in the Application event log. Increase logging on the components that the message is stuck in or that are generating NDRs.
4. Check the errors codes in the NDR. NOTE: These errors may give you the solutions, such as check Domain Name Service (DNS) or network connectivity.
   
   For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

   256321 XCON: Enhanced Status Codes for Delivery - RFC 1893

5. Get a raw property dump of the object that you are trying to send mail to, even if there are not any Event IDs or NDRs. For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:

   255253 XADM: How to Perform a Dump of a Container or Object in Exchange 2000

   271201 XADM: Alternative Methods to Obtain a Dump of an Object

   199412 XGEN: Administrator Program Dump Files (Admindmp.txt)

6. Verify that all the required object attributes that are being sent to User, Contact, and so on, are correct on the global catalog server.
   
   NOTE: This needs to be the same global catalog server that is being referenced by the Exchange 2000 server where the message is stuck or getting an NDR from.
7. Compare these attributes to the object's attributes on the object's home Exchange 2000 server. For Microsoft Exchange Server 4.0, 5.0, and 5.x, compare these attributes to the object's raw properties.
   
   Legacyexchangedn
   Homemdb
   Homemta
   mailNickname
   proxyAddresses
   msExchHomeServerName:
   msExchMailboxSecurityDescriptor
   msExchMailboxGuid
   
   For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

   281761 XCON: Attributes Required to Route Messages Through the Categorizer

8. If all attributes are incorrect:
   1. Verify that replication is working between global catalog servers. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

      200525 Using NSlookup.exe

   2. Verify that the Recipient Update Service is working. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

      246127 XADM: Troubleshooting the Exchange 2000 Server Address List Service

   3. Verify that the Active Directory Connector (ADC) and all Connection Agreements are working correctly if you have any Exchange Server 5.5 computers. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

      261227 XADM: Exchange 2000 Servers Do Not Replicate to the Exchange Server 5.5 Directory

   4. Verify that Site Replication Service (SRS) is running if you have Exchange Server 5.5 computers, including remote sites. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

      261227 XADM: Exchange 2000 Servers Do Not Replicate to the Exchange Server 5.5 Directory

   5. If everything in the preceding steps appears to be working well, manually correct the incorrect attributes with ADSI Edit in Active Directory.
      
      WARNING: If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows 2000 Server, Microsoft Exchange 2000 Server, or both. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes at your own risk.
9. Run regtrace, and collect a trace file on the Exchange 2000 server with the issue.

Additional query words: IMS GC RUS AD

Keywords: kbhowto KB281800

---

Send feedback to Microsoft

© Microsoft Corporation. All rights reserved.