Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. XADM: Cluster Service Terminate Function Does Not Kill the Information Store Unless It Times Out

XADM: Cluster Service Terminate Function Does Not Kill the Information Store Unless It Times Out

View products that this article applies to.

This article was previously published under Q322126

↑ Back to the top

Symptoms

On a cluster server, neither MAPI nor non-MAPI clients can connect to the mailbox store. The Application event log is full of event ID 482 and event ID 1159 errors. Both of these events indicate that the information store cannot access the database. These events are logged for all storage groups.

NOTE: There is no indication of hardware failure in the System logs.

The following are the descriptions of an event ID 482 and of an event ID 1159:
Source ESE
EventID 482
Description
Information Store (3080) An attempt to write to the file "G:\EXCHSRVR\MDBDATA\S3-SG1-MS2-Std.edb" at offset 10889854976 (0x0000000289160000) for 4096 (0x00001000) bytes failed with system error 21 (0x00000015): "The device is not ready. ". The write operation will fail with error -1022 (0xfffffc02). If this error persists then the file may be damaged and may need to be restored from a previous backup.

Source MSExchangeIS
EventID 1159
Description:
Database error 0xfffffbbe occurred in function JTAB_BASE::EcSetCurrentIndex while accessing the database "S4-SG2\S4-SG2-MS5-Std".

↑ Back to the top

Resolution

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 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: Cluster

File nameVersion
Store.exe6.0.5770.97
Davex.dll6.0.5770.97
Dsaccess.dll6.0.5770.97
Dscmsg.dll6.0.5770.97
Excdo.dll6.0.5770.97
Exmgmt.exe6.0.5770.97
Exoledb.dll6.0.5770.97
Exprox.dll6.0.5770.97
Exres.dll6.0.5770.97
Exsp.dll6.0.5770.97
Exwmi.dll6.0.5770.97
Jcb.dll6.0.5770.97
Mad.exe6.0.5770.97
Mdbmsg.dll6.0.5770.97
Mdbsz.dll6.0.5770.97
Phatcat.dll6.0.5770.97

NOTE: Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 2.

↑ Back to the top

Workaround

Shut down and then restart the passive node.

↑ Back to the top

Status

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 3.

↑ Back to the top

Keywords: KB322126, kbfix, kbexchange2000sp3fix, kbexchange2000presp3fix, kbbug, kbqfe, kbhotfixserver

↑ Back to the top

Article Info
Article ID : 322126
Revision : 5
Created on : 2/21/2007
Published on : 2/21/2007
Exists online : False
Views : 447