Microsoft KB Archive/266330

= XCON: Message Transfer Agent Event ID 9322 =

PSS ID Number: 266330

Article Last Modified on 6/17/2003

-

The information in this article applies to:


 * Microsoft Exchange 2000 Server

-



This article was previously published under Q266330



SYMPTOMS
The following events may be logged in the Application event log:

Event Type: Warning

Event Source: MSExchangeMTA

Event Category: Interface

Event ID: 9322

Computer: SERVERX2K

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 SERVERX2K-OTHER, Protocol String ncacn_ip_tcp:SERVERX2K-OTHER.LCXADMPT.COM[1151] [BASE IL INCOMING RPC 25 507] (14)

Event Type: Error

Event Source: MSExchangeFBPublish

Event Category: General

Event ID: 8197

Computer: SERVERX2K

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

The event ID 1722 error message in the message transfer agent (MTA) event indicates that the server named SERVERX2K-OTHER cannot be contacted.



CAUSE
This issue can occur if the Exchange 2000 server cannot contact other Exchange 2000 servers in the domain. In the error messages in the &quot;Symptoms&quot; section of this article, the primary Domain Name System (DNS) server is a server that is aware of the domain's domain controllers and SERVERX2K-OTHER, which is another Exchange 2000 server in the domain. However, the secondary DNS server is offline or unaware of these other servers.

For example, this problem can occur in a test environment, if the primary DNS server is manually entered on an Exchange 2000 server as the IP address of a test DNS server that is aware of SERVERX2K-OTHER. If Dynamic Host Configuration Protocol (DHCP) assigns the secondary DNS server to a production DNS server that is unaware of the Exchange 2000 server called SERVERX2K-OTHER and any domain controllers, whenever network problems prevent the test DNS server from responding in a timely manner and the Exchange 2000 server queries the secondary server, that query does not work and results in the error and warning messages in the &quot;Symptoms&quot; section of this article.



RESOLUTION
To resolve this issue, set the secondary DNS server to a valid DNS server that has knowledge of the other Exchange 2000 servers in the domain.



WORKAROUND
To work around this issue, set the secondary DNS server IP address to the same address as the primary DNS server.

Additional query words: DC exch2kp2w

Keywords: kberrmsg kbprb KB266330

Technology: kbExchange2000Search kbExchange2000Serv kbExchange2000ServSearch kbExchangeSearch

-

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

© 2004 Microsoft Corporation. All rights reserved.