Article ID: 169690 - Last Review: October 28, 2006 - Revision: 4.1

XCON: MTA Terminates Suddenly with 2191, 2198, 2197, and 9405 Events

Retired KB ArticleRetired KB Content Disclaimer
View products that this article applies to.
This article was previously published under Q169690
Expand all | Collapse all

SYMPTOMS

The Microsoft Exchange message transfer agent (MTA) may terminate unexpectedly with event messages similar to the following: 
   Event ID:2191
   Source:MSExchangeMTA
   Type:Warning
   Category:Internal Processing
   Description:
   An MTA database server error was encountered while adding an entry to a
   queue. Called from MTA. Procedure 234. Database error code: ODXOINIU -
   Object does not exist. Queue name: 00000000. Object at fault: 06000040.
   [DB
   Server DISP:FANOUT 11 62] (14)

   Event ID:2198
   Source:MSExchangeMTA
   Type:Warning
   Category:Internal Processing
   Description:
   An MTA database server error was encountered while unlocking a queue.
   Called from MTA. Procedure 234. Database error code: ODXOINIU - Object
   does
   not exist. Queue: 00000000. [DB Server DISP:FANOUT 11 127] (14)

   Event ID:2197
   Source:MSExchangeMTA
   Type:Warning
   Category:Internal Processing
   Description:
   An MTA database server error was encountered while locking a queue.
   Called
   from MTA. Procedure 205. Database error code: ODXOINIU - Object does not
   exist. Queue: 00000000. [DB Server DELIVER 9 84] (14)

   Event ID:9405
   Source:MSExchangeMTA
   Type:Error
   Category:Field Engineering
   Description:
   An unexpected error has occurred which may cause the MTA to terminate.
   Error: Double acquire of semaphore 2151. [BASE DELIVER 9] (16)
Back to the top

CAUSE

This problem occurs when an internal list within the MTA, called the Intentions List, becomes corrupt.
Back to the top

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange versions 4.0, SP1, SP2, SP3, and SP4. This problem has been corrected in the latest U.S. Service Pack for Microsoft Exchange Server version 4.0. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K

Microsoft has confirmed this to be a problem in Microsoft Exchange versions 5.0 and SP1. This problem has been corrected in the latest U.S. Service Pack for Microsoft Exchange Server version 5.0. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K
Back to the top
APPLIES TO
  • Microsoft Exchange Server 4.0 Standard Edition
  • Microsoft Exchange Server 4.0 Service Pack 1
  • Microsoft Exchange Server 4.0 Service Pack 2
  • Microsoft Exchange Server 4.0 Service Pack 3
  • Microsoft Exchange Server 4.0 Service Pack 4
  • Microsoft Exchange Server 5.0 Standard Edition
  • Microsoft Exchange Server 5.0 Service Pack 1
  • Microsoft Exchange Server 5.5 Standard Edition
Back to the top
Keywords: 
kbqfe kbhotfixserver kbbug kbfix kbusage KB169690
Back to the top
Retired KB ArticleRetired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
Back to the top
 

Get Help Now

Contact a support professional by E-mail, Online, or Phone

Article Translations