Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

How to troubleshoot an event ID 9322 message in Exchange Server 5.5, in Exchange 2000 Server, and in Exchange Server 2003


View products that this article applies to.

This article was previously published under Q266312
This article is a consolidation of the following previously available articles: 266330, 821889, 275468, 279537 and 303156
INTRODUCTION
This article describes how to troubleshoot an event ID 9322 message. This event may be logged when you experience mail flow issues.

↑ Back to the top


Summary

This article describes how to troubleshoot scenarios in which an event ID 9322 message may be logged in the event log. This event ID message may be logged in the following scenarios in Exchange Server 5.5:
  • Servers in a site communicate through a firewall that uses NAT
  • A firewall filters incoming and outgoing ports
This article also describes the following methods that you can use to troubleshoot the event ID 9322 message:
  • Verify that fully qualified domain name resolution is working
  • Verify that there is enough RAM
  • Verify the network connection
  • Verify that the user accounts are turned on and replicated after you move mailboxes

↑ Back to the top


More information

You may experience mail flow issues in Microsoft Exchange Server 5.5, in Microsoft Exchange 2000 Server, and in Microsoft Exchange Server 2003. When you experience this issue, the following event may be logged in the Application log.

Note The description in the event may vary.

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

Event ID: 9322
Description:
An interface error has occurred. An MtaBindBack over RPC has failed. Locality Table (LTAB) index: xx, NT/MTA error code: 9260. Comms error BASE IL, Bind error INCOMING RPC, Remote Server Name xxx, Protocol String xxx [%7 %8 %9 %10] (14)

Additionally, the following events may be logged in the Application log:

Event Type: Error
Event Source: MSExchangeDSAccess
Event ID: 2064
Description: Process WINMGMT.EXE (PID=936). All the remote DS Servers in use are not responding.

Event Type: Error
Event Source: MSExchangeSA
Event ID: 9098
Description: The MAD Monitoring thread was unable to read its configuration from the DS, error '0x80041001'.

Event Type: Error
Event Source: MSExchangeFBPublish
Event ID: 8197
Description: Error initializing session for virtual machine xxx. The error number is 0x8004011d. Make sure Microsoft Exchange Store is running.

Event ID: 9318
Source: MSExchangeMTA - Interface
Description: An RPC communications error occurred. Unable to bind over RPC. Locality Table (LTAB) index: xxx, NT/MTA error code: 1722. Comms error 1722, Bind error 1722, Remote Server Name SERVERNAME [MAIN BASE 1 500 %10] (14)

For more information about the Microsoft Windows message transfer agent (MTA) error code, type Net HelpMsg ErrorCode at a command prompt.

Scenarios in which an event ID 9322 message may be logged in Exchange Server 5.5

The servers in a site communicate through a firewall that uses NAT

Consider the following scenario:
  • Two servers that are running Exchange Server 5.5 SP4 are located in the same site.
  • Server1 is in an internal network, 172.x.x.x. Server2 is in external network, 10.x.x.x. The external network is behind a firewall that uses Network Address Translation (NAT).
  • NAT is used to translate 10.x.x.x into an internal IP address, 172.x.x.x.
In this scenario, mail may queue on the computer that is behind the firewall until the external server connects to deliver the messages. Additionally, an event ID 9322 message and an event ID 9318 message that includes error code 1722 are logged in the Application log.

↑ Back to the top


Keywords: KB266312, kbprb

↑ Back to the top

Article Info
Article ID : 266312
Revision : 6
Created on : 3/26/2008
Published on : 3/26/2008
Exists online : False
Views : 365