Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
?
Solved

MSExchangeMTA Error

Posted on 2006-06-27
6
Medium Priority
?
733 Views
Last Modified: 2010-08-05
Good Afternoon -

I am running Exchange Server 2003 and I keep getting the following warning in my Event Viewer:

An RPC communications error occurred. Unable to bind over RPC. Locality Table (LTAB) index: 198, Windows 2000/MTA error code: 1722. Comms error 1722, Bind error 0, Remote Server Name YORKTOWN [MAIN BASE 1 500 %10] (14)

The ID is 9318
The Category is Interface
The Source is MSExchangeMTA
The Type is Warning

The server "YORKTOWN" was setup as a backup, but has since crashed and been decommissioned.  However, whatever this message is stemming from is continuing to fire.  Can I do anything to let Exchange know that this box is no longer in use and to stop looking for it?
0
Comment
Question by:kokeefe
  • 3
  • 2
5 Comments
 
LVL 4

Expert Comment

by:mkumar23
ID: 16995731
Product: Exchange
Event ID: 9318
Source: MSExchangeMTA
Version: 6.5.0000.0
Message: An RPC communications error occurred. Unable to bind over RPC. Locality Table (LTAB) index: value, Windows 2000/MTA error code: error code. Comms error value, Bind error %4, Remote Server Name %5 [%7%8%9%10] (14)
   
Explanation
A system call from the message transfer agent to the operating system failed.
   
User Action
At the Windows 2000 command prompt, use the Net Helpmsg command for an explanation of the Windows 2000 error. For example, if you want to get an explanation of Windows 2000 error code 3817, type "Net Helpmsg 3817" at the command prompt, and then press Enter.
Verify that the remote procedure call (RPC) service is running.

Check network connectivity. If the error persists, stop and restart the message transfer agent service. If the error still persists, restart Microsoft Exchange Server.

The most common error codes are listed with possible resolutions:

5 - access denied - check the permissions and account being used by the service.
1722 - this problem is usually DNS. Use nslookup to verify that you can resolve the host by fully qualified domain name (FQDN).
1753 - this problem is also usually DNS, but on the bind back. Verify that the host reporting this problem is able to resolve the remote host by FQDN.
If necessary, use Network Monitor to capture network traces, then view these traces from Network Monitor for any network issue.
 
0
 

Author Comment

by:kokeefe
ID: 16995968
I found an article very similar to this feedback.  However, none appear applicable as the issue is the box/server in question is no longer in use.  
0
 
LVL 4

Expert Comment

by:mkumar23
ID: 16996197
Have you deleted this server form Active Directory Configuration partion
0
 

Author Comment

by:kokeefe
ID: 16996225
This server is not in the list of "Computers" in the AD Users and Computers.  Is this what you mean?  
0
 
LVL 4

Accepted Solution

by:
mkumar23 earned 1050 total points
ID: 16996839
No, to do this follow the steps below, but before that let me know what all you were running on the decommishoned server and is that server still appear in ESM under any administrative group you may have in your current exchange org.

Install Windows Support Tools

Then run ADSI Edit

Go to Configuration Partation

CN=Configuration, DC=your domain name
CN=Service
CN=Microsoft Exchage
CN= your organization name
CN=Administrative Group
CN=your administrative group
CN=Servers

Now check what all servers you have listed under (CN=Servers), if you see that decomissioned server, than delete it from there and close the ADSI Edit window.

0

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this post, I will showcase the steps for how to create groups in Office 365. Office 365 groups allow for ease of flexibility and collaboration between staff members.
This article will help to fix the below errors for MS Exchange Server 2016 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…
Suggested Courses
Course of the Month15 days, 3 hours left to enroll

578 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question