General discussion

Locked

Latent AD/DS Entry From Old Mailserver

By skylinepc ·
I had an E2K mailserver crash while online several weeks ago and was unable to recover it. I have a new mailserver and am fully back in production, but I'm getting Event ID 929 errors from MSExchangeTransport, Routing Engine/Service.

Apparently, Inetinfo.exe is still looking for a connection to the old mailserver. I've searched through AD looking for it, but there's no reference to the old mailserver anywhere that I can find.

However, I did find an MS Mail Connector in my Routing Groups that points to the old mailserver, but I can't remove it (error code c1039e74) from ESM, stating "You must remove all members from the routing group before it can be deleted."

As far as I know, I don't have any members in this routing group. I run an intranet with a single E2k server. No POP, IMAP, Lotus, MS Mail, etc. Plain vanilla Exchange.

Help.

Thanks.

This conversation is currently closed to new comments.

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

All Comments

Collapse -

by compgirlfhredi In reply to Latent AD/DS Entry From O ...

If an error occurs when the Exchange 2000 routing engine is communicating with Active Directory, Exchange 2000 may ignore available routes. When the routing table is rebuilt in Exchange 2000, the current table is removed and then the new table is reloaded. If a communication error occurs between Exchange 2000 and Active Directory while the current table is being removed and the new table is being reloaded, Exchange 2000 is without a routing table, which causes e-mail messages to generate NDRs. This behavior continues until the routing is successfully reloaded from Active Directory. To resolve this problem, the following changes were made in the fix that is described in the "Resolution" section of this article:
An error message in the following format is logged when this problem occurs:

EVENT I 929
TYPE: ERROR
DESCRIPTION: Failed in reading Connector's DS Info
Messages queue up in the Currently Unreachable queue instead of generating NDRs immediately.
The routing code logic is changed so that when Exchange 2000 attempts to reload the routing table, Exchange 2000 verifies that it can obtain the new routing table before Exchange 2000 destroys the old routing table. If an error occurs during this process, Exchange 2000 logs the 929 error message and keeps the current routing table.
For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
281382 XCON: How to Use the WinRoute Tool

Collapse -

by compgirlfhredi In reply to

To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, check the following article number to view the article in the Microsoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack

The English version of this fix should have the following file attributes or later:

Component: Transport Core

File name Version
Mtaroute.dll 6.0.4418.57
Phatq.dll 6.0.4418.57
Reapi.dll 6.0.4418.57
Resvc.dll 6.0.4418.57
Tranmsg.dll 6.0.4418.57

Collapse -

by skylinepc In reply to

I examined the routing groups using WinRoute as the Q article described, but found no entries referencing the old mail server. The current production mail server is listed as the Routing Group (RG) Master. The RG Members entry only lists the current mail server as a member.

Yesterday, 22 Oct 03, I reinstalled Exchange SP3 at least 3 times while setting up IM services on this server so I'm certain that any patches/updates have been applied to the server.

Back to Software Forum
3 total posts (Page 1 of 1)  

Related Discussions

Related Forums