• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2614
  • Last Modified:

MTA stacks generating RPC errors after IIS metabase reinstall

http://www.experts-exchange.com/Networking/Email_Groupware/Exchange_Server/Q_21129348.html

That is the link to the question that generaed the metabase reinstall....

Here is situation...Primary FE/BE Exchange 2003 server had full IIS reinstall along with exchange in reinstall mode.

Now getting the following errors in the event logs, but all mail is being delivered.

Product: Exchange
ID: 9318
Source: MSExchangeMTA
Version: 6.5.0000.0
An RPC communications error occurred. Unable to bind over RPC. Locality Table (LTAB) index: 43, Windows 2000/MTA error code: 9297. Comms error 9297, Bind error 9297, Remote Server Name MAIL1 [MAIN BASE 1 500 %10] (14)

Product: Exchange
ID: 9297
Source: MSExchangeMTA
Version: 6.5.0000.0
Calling client thread does not have permission to use MTA RPCs. Windows 2000 error code: 0X80070005. Client user account: NT AUTHORITY\ANONYMOUS LOGON. [BASE IL INCOMING RPC 25 237] (14)

Product: Exchange
ID: 9318
Source: MSExchangeMTA
Version: 6.5.0000.0
An RPC communications error occurred. Unable to bind over RPC. Locality Table (LTAB) index: 44, Windows 2000/MTA error code: 9297. Comms error 9297, Bind error 9297, Remote Server Name CHAN-MX-01 [MAIN BASE 1 500 %10] (14)

This is the structre of the exchange system

Webserver:   FE/BE, no local mailbox store, master in the routing group, win2k3 and exchsvr2k3
mail1: BE, local mail store, member in routing group, win2k3 and exchsvr 2k3
chan-mx-01:  BE, old local mail store, member in routing group, win2k and exchsvr 2k

The RPC service is running, as are all exchange related services.  I know this is a permission issue I just can't find where to change them and most KB articles deal with exchange 5.0 and 5.5.......





0
ChrisWillis
Asked:
ChrisWillis
  • 4
  • 4
1 Solution
 
munichpostmanCommented:
The above errors are actually quite normal and have nothing to do with your IIS metabase install. They indicate that there is some network latency which is causing the RPC errors. What can also happen is that the sending or receiving MTA may be close to the limit on the number of available threads, which is what is causing the errors. As long as mail is flowing, do nothing. If queues start to backup, you should consider tuining the MTA for better performance as outlined in Chapter 9 of the following link.

http://www.microsoft.com/technet/prodtechnol/exchange/2000/deploy/upgrademigrate/series/deploymentguide/d_09_tt1.mspx#EGAA
0
 
ChrisWillisAuthor Commented:
what got me thinking was the following event log indicating a permission error

Product: Exchange
ID: 9297
Source: MSExchangeMTA
Version: 6.5.0000.0
Calling client thread does not have permission to use MTA RPCs. Windows 2000 error code: 0X80070005. Client user account: NT AUTHORITY\ANONYMOUS LOGON. [BASE IL INCOMING RPC 25 237] (14)

All three of the events repeat every 10 minutes.  The 3 servers in question are all in the same rack on a gigabit backbone, so latency should not be a problem.  

I have checked the queue's and nothing is being help up.....
0
 
munichpostmanCommented:
Do  your x.400 MTA's require password authentication? It sounds as if you have password authentication enabled and the calling MTA is not using the correct credentials.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
ChrisWillisAuthor Commented:
The x.400's are default, I have not messed with them....where can I go to check.
0
 
munichpostmanCommented:
In Exchange 2003, drill down to the routing group, connectors. Right click a x.400 connector and choose properties. In the remote x.400 name field, click on modify, this is where the options are to set a password. If mail is flowing outbound from your routing group, it sounds as if a connected x.400 system has the  general options on their system misconfigured and is trying to resend you mail every ten minutes, with an incorrect password specified on their connector.
0
 
ChrisWillisAuthor Commented:
Thats the thing...there are no x.400 connectors under routing groups....there are x.400 entires under the protocal listings for each server, but all server communication should be over SMTP.  All systems are controlled by me and no one else has the authority to change any of the exchange stuff.
0
 
munichpostmanCommented:
Hi Chris,

let's recap.

Under Routing Groups do you have any connectors?

You say mail is flowing, where to? Do you have a SMTP Virtual Server setup to forward all mail to a smart host? The MTA errors you are seeing are usually caused by issues with the MTA threads. Which other connectors do you have in the routing group? Are you using any third party apps such as Fax connectors or connectors to Groupwise or Notes?
0
 
ChrisWillisAuthor Commented:
Internet Mail SMTP connector is the only connector I have.

My FE handles all mail/protocals for the 3 BE servers, all on SMTP.  I have dedicated T1 links and need messages to get where they are gong so all servers are in the same rounting group.  

The only 3rd party apps are Symantec MailSecurity latest version (4.1 I think).

Mail is traveling through the front end to all 3 backend servers, the backend servers are all sending mail out.....all internal mail between backends is flowing nicely (about 10-15 seconds depending on location)

just getting weird MTA stack errors.....
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now