Microsoft KB Archive/821889

= Message Transfer Agent Event IDs 9322 and 8197 Are Logged =

Article ID: 821889

Article Last Modified on 11/10/2005

-

APPLIES TO


 * Microsoft Exchange Server 2003 Enterprise Edition
 * Microsoft Exchange Server 2003 Standard Edition

-





SYMPTOMS
The following events may be logged in the Windows Event Viewer application event log: Event Type: Warning

Event Source: MSExchangeMTA

Event Category: Interface

Event ID: 9322

Computer:

Description: An interface error has occurred. An MtaBindBack over RPC has failed. Locality Table (LTAB) index: 15, Windows 2000/MTA error code: 1722. Comms error 1722, Bind error 0, Remote Server Name, Protocol String ncacn_ip_tcp: [1151] [BASE IL INCOMING RPC 25 507] (14)

Event Type: Error

Event Source: MSExchangeFBPublish

Event Category: General

Event ID: 8197

Computer:

Description: Error initializing session for virtual machine. The error number is 0x8004011d. Make sure Microsoft Exchange Store is running.

The Windows 2000/MTA error code of 1722 that is in the message transfer agent (MTA) event indicates that the server that is named  cannot be contacted.



CAUSE
This issue may occur when your Exchange 2003 computer cannot contact other Exchange Server computers that are in the domain. The symptoms that are listed in the &quot;Symptoms&quot; section may indicate that there is a problem with name resolution of the computer that is listed in the 9322 event error ( in the example that is given in the &quot;Symptoms&quot; section).

The Domain Name System (DNS) server that is listed in the TCP/IP properties of your Exchange 2003 computer network settings is the primary server that is used for name resolution. If information is missing or incorrect on this DNS server, these events may be logged.



RESOLUTION
To resolve this issue, run the ipconfig /all command on your Exchange 2003 computer. Perform the following tasks as part of the ipconfig procedure:
 * Verify that all DNS server settings that are listed in the Exchange 2003 computer’s configuration are correct.
 * Make sure that the DNS servers that are listed have forward lookup zones that are configured with the information that resolves the fully qualified domain name of each Exchange Server computer that is in your domain. If not, manually add a host record for each Exchange Server computer with its associated IP address.
 * Remove any entries that are not valid.
 * If there is more than one DNS server listed in the TCP/IP properties of your Exchange 2003 server network settings, make sure that each listed server is correct.



MORE INFORMATION
For additional information about the Windows 2000/MTA error code 1722, type Net HelpMsg 1722 at the command prompt.

For additional information about how to troubleshoot the issue that is described in this article, click the following article numbers to view the articles in the Microsoft Knowledge Base:

200525 Using NSlookup.exe

217014 Description of the Ping and Tracert Tools

Additional query words: XADM

Keywords: kbprb KB821889

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.