General discussion

Locked

Exchange 5.5 Bridgehead Errors

By The underdog ·
There are 2 exchange 5.5 servers in our site. We are removing one and making the other the bridgehead, pointing to a new location in a different site. Once we set up the connectors and directory replication, mail will NOT flow. Here is the error we are receiving on our end: Event ID 9318 MSEXCHANGEMTA. An RPC communications error occurred. Unable to bind over RPC. Locatlity table [LTAB] index: 4, NT/MTA error code:5. Comms error 5, Bind error 5, Remote Server Name BSPEXCH3 [MAIN BASE 1 500 % 10] [14]

We have a trust established and it listed "successful" months ago. We test with an RPCping utility, which tested successfully, ironically, considering this error.

Any helpful comments will be greatly appreciated. Thanks!

This conversation is currently closed to new comments.

6 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

MSDN Article's Preface

by LordInfidel In reply to Exchange 5.5 Bridgehead E ...

I am posting some msdn aritcles for you.. None were exact, but I think combinded you might find an answer.

The NT/MTA error code: 5 is a security context code.

I was only able to find one LTAB: 4, the rest were 76's.

Collapse -

Article 1

by LordInfidel In reply to MSDN Article's Preface

XCON: DRAS Fails with Event 9322

Q217142


--------------------------------------------------------------------------------
The information in this article applies to:

Microsoft Exchange Server, versions 5.0, 5.5

--------------------------------------------------------------------------------


SYMPTOMS
When you attempt to connect two Microsoft Exchange Server 5.5 computers using the Dynamic RAS (DRAS) connector over TCP/IP, and the servers are in two different, untrusted domains, the Exchange Server computer that dials may log a 9318 and a 289 message transfer agent (MTA) event in the application log. The Exchange Server computer that is being dialed into will log a 9322 event with a Windows NT/MTA error of 5:

9322: MSExchangeMTA
An interface error has occurred. An MtaBindBack over RPC has failed.
Locality Table (LTAB) index: %1, NT/MTA error code:5.
Comms error %3, Bind error %4,Remote Server Name %5, Protocol String %6 [%7 %8 %9 %10]


CAUSE
A Windows NT error code of 5 signifies that there is a security problem between the two servers.


WORKAROUND

Create a new Windows NT user account called RASCON. Repeat this process on each of the untrusted domains.


Give the new RASCON accounts the exact same password.


Add the RASCON account to the Domain Admins group.


Verify that the RASCON account has permission to log onto the Exchange Server computer. This is done using the Windows NT User Manager.


Within the Microsoft Exchange Administrator program, give the new RASCON account Service Account Admin permission at the Organization, Site, and Configuration levels of the Exchange Server computer.


Adjust the RAS Override tab of the DRAS connector to use these new accounts on both Exchange Server computers.


Retest mail flow over the DRAS Connector.

Collapse -

Article 2

by LordInfidel In reply to MSDN Article's Preface

XCON: Event ID 9318 Occurs Within Site When Servers Operate over a WAN

Q248488


--------------------------------------------------------------------------------
The information in this article applies to:

Microsoft Exchange Server, version 5.0

--------------------------------------------------------------------------------


SYMPTOMS
When you review the Event Viewer application log for Microsoft Exchange Server 5.0 Service Pack 1, you notice that the message transfer agent (MTA) is logging Event ID 9318 at random intervals. The entry is similar to the following example, though the index and Microsoft Windows NT error code numbers vary:

Event I 9318
Source: MSExchangeMTA
Type: Warning
Category: Interface
Description: An RPC communications error occurred. Unable to bind over RPC. The locality table (LTAB) index is 76. Windows NT error code: XXXX. [BASE IL MAIN BASE 1 500] (12)


CAUSE
This behavior can occur when you have more than one server in a site, but the servers are connected across a wide area network (WAN) rather than a local area network (LAN). Event Viewer logs this event when WAN traffic is heavy or when network connectivity is unstable.


RESOLUTION
To work around this problem, follow these steps:


Open the MTA Site Configuration Properties dialog box, and then click the Messaging Defaults tab.


Type 15 in the Checkpoint Size (K) box.


Type 90 in the Recovery Timeout (sec) box.


Type 3 in the Window Size box.


NOTE: If most of the WAN is regularly experiencing heavy traffic, this workaround may not completely alleviate the problem. It may be necessary to redesign the Exchange Server organization.

Collapse -

Article 3

by LordInfidel In reply to MSDN Article's Preface

XCON: Message Transfer Agent Logs RPC Bind Errors (931 with Error Code 0

Q288195


--------------------------------------------------------------------------------
The information in this article applies to:

Microsoft Exchange 2000 Server

--------------------------------------------------------------------------------


SYMPTOMS
The Exchange 2000 Server message transfer agent (MTA) may log RPC bind errors (931 with error code 0:

Event Type: Warning
Event Source: MSExchangeMTA
Event Category: Interface
Event I 9318
Date: 11/16/2000
Time: 10:03:52 AM
User: N/A Computer: ComputerName
Description: An RPC communications error occurred. Unable to bind over RPC. Locality Table (LTAB) index: 4, NT/MTA error code:0. Comms error 5, Bind error 0, Remote Server Name RemoteServer [MAIN BASE 1 500 %10] (14)


CAUSE
This problem may occur if a Source Bridgehead server is not a target Bridgehead for the other end of the Routing Group Connector. There is no mail loss or delay, but you do receive confusing warnings in the Application log.


RESOLUTION
To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, please see the following article in the Microsoft Knowledge Base:

Microsoft has confirmed this to be a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 1.

Collapse -

Article 4

by LordInfidel In reply to MSDN Article's Preface

XCON: Event Messages 9318 and 9322 Are Logged During RPC Communication

Q275468


--------------------------------------------------------------------------------
The information in this article applies to:

Microsoft Exchange Server, versions 5.5, 5.5 SP1, 5.5 SP2, 5.5 SP3

--------------------------------------------------------------------------------


SYMPTOMS
The Microsoft Exchange Server Message Transfer Agent (MTA) does not deliver messages over a dynamic Remote Access Service (RAS) connector, an X.400 connector, or a site connector or during intra-site communication. When you set the MTA diagnostic logging level to Maximum for Field Engineering and X.400 Service categories, the following events are reported in the application event log (numbers in the descriptions may vary):

Event I 9322
Source: MSExchangeMTA
Description: An interface error has occurred. An MtaBindBack over RPC has failed. Locality Table (LTAB) index: %1, NT/MTA error code:14. Comms error %3, Bind error %4,Remote Server Name %5, Protocol String %6 [%7 %8 %9 %10].

Event I 9318
Source: MSExchangeMTA
Description: An RPC communications error occurred. Unable to bind over RPC. Locality Table (LTAB) index: %1, NT/MTA error code: 14. Comms error %3, Bind error %4...,

When you attempt to troubleshoot using the RPC ping command, the following message is logged:
-RpcServerUseProtSeqEp returned a status 0xE

Collapse -

Article 4 pt b

by LordInfidel In reply to Article 4

CAUSE
This issue can occur if your computer does not have enough available Random Access Memory (RAM).


RESOLUTION
To resolve this issue, check the computer's available RAM with either Performance Monitor or Task Manager, and then close programs to make more RAM available. After you restart the computer, if the computer still does not have enough RAM, you have to add more RAM to your computer.


MORE INFORMATION
To determine the meaning of the error message, type Net Helpmsg 14 at a command prompt. (The hex value 0xE is equal to a decimal value of 14.) The Windows NT error is translated as: "Not enough storage is available to complete this operation." The word "storage" in this message refers to RAM.

Back to IT Employment Forum
6 total posts (Page 1 of 1)  

Related Discussions

Related Forums