Microsoft KB Archive/322126

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

Article ID: 322126

Article Last Modified on 2/21/2007

-

APPLIES TO


 * Microsoft Exchange 2000 Server Standard Edition

-



This article was previously published under Q322126



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 &quot;G:\EXCHSRVR\MDBDATA\S3-SG1-MS2-Std.edb&quot; at offset 10889854976 (0x0000000289160000) for 4096 (0x00001000) bytes failed with system error 21 (0x00000015): &quot;The device is not ready. &quot;. 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 &quot;S4-SG2\S4-SG2-MS5-Std&quot;.



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

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



WORKAROUND
Shut down and then restart the passive node.



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.

Keywords: kbhotfixserver kbqfe kbbug kbexchange2000presp3fix kbexchange2000sp3fix kbfix KB322126

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.