XCON: One Message Is Stuck in Work Queue After You Rename a Scheduled X.400 Connector

This article was previously published under Q309193
This article has been archived. It is offered "as is" and will no longer be updated.
When you configure a scheduled X.400 connector between two Exchange 2000 servers in different organizations, and then change the name of the connector in Exchange System Manager while the connector is inactive, one message will remain stuck in the Work queue on message transfer agent (MTA) of the sending Exchange 2000 server. This message will not be delivered and no non-delivery report (NDR) is generated until you stop and then restart the Microsoft Exchange MTA Stacks service.

For example, after you change the connector name, the X.400 queue that represents the connector in question in Exchange System Manager shows that there are 49 messages. However, Performance Monitor shows that the actual number of messages in the Work queue is 50.

When you restart the MTA on the sending server, the stuck message returns an NDR with the following error message:
A network connection problem or an offline server prevented delivery of the message
To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 2.

Article ID: 309193 - Last Review: 10/24/2013 07:51:45 - Revision: 1.4

  • Microsoft Exchange 2000 Server Standard Edition
  • kbnosurvey kbarchive kbbug kbexchange2000sp2fix kbnofix KB309193