Article ID: 300608
Article Last Modified on 2/28/2007
APPLIES TO
- Microsoft Exchange 2000 Server Standard Edition
This article was previously published under Q300608
SYMPTOMS
When you attempt to mount an Exchange 2000 Server database, you may receive the following error and event messages:
Event Type: Error
Event Source: ESE98
Event Category: Database Corruption
Event ID: 470
Date: May 29, 2001
Time: 4:55:47 P.M.
User: N/A
Computer: Servername
Description:
Information Store (3112) Database E:\Program Files\Exchsrvr\Mdbdata\Priv1.edb is partially attached. Attachment stage: 4. Error: -1022.
For more information, click http://search.support.microsoft.com/search/?adv=1.
NOTE: If you receive the error message, you also receive the event message (Event ID 470 that refers to error 1022).
In addition to the preceding messages, one or more of the following events may be recorded in the Application log:
Event Type: Error
Event Source: ESE98
Event Category: Performance
Event ID: 0
Date: May 29, 2001
Time: 4:55:47 P.M.
User: N/A
Computer: Servername
Description:
Information Store (3112) Unexpected Win32 error: -273865466L
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9519
Date: May 29, 2001
Time: 4:55:47 P.M.
User: N/A
Computer: Servername
Description:
Error Disk IO error starting database "First Storage Group\Public Folder Store (Servername)" on the Microsoft Exchange Information Store.
For more information, click http://search.support.microsoft.com/search/?adv=1.
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9518
Date: May 30, 2001
Time: 3:49:49 P.M.
User: N/A
Computer: Servername
Description:
Error Disk IO error starting Storage Group /dc=com/dc=Candk/cn=Configuration/cn=Services/cn=Microsoft Exchange/cn=Candk/cn=Administrative Groups/cn=First Administrative Group/cn=Servers/cn=Servername/cn=Informationstore/cn=First Storage Group on the Microsoft Exchange Information Store.
For more information, click http://search.support.microsoft.com/search/?adv=1.
Event Type: Information
Event Source: ESE98
Event Category: General
Event ID: 104
Date: May 30, 2001
Time: 3:49:49 P.M.
User: N/A
Computer: Servername
Description:
Information Store (1732) The database engine stopped an instance (0) with error (-1090).
For more information, click http://search.support.microsoft.com/search/?adv=1.
CAUSE
This behavior can occur when Exchange 2000 cannot write to the hard disk, and generates an error message: Either software that has been installed has prevented the write operation or the hard disk itself is corrupted. The event message, which accompanies the error message, refers to an error 1022. This type of error occurs when there is a disk input/output (I/O) error: It may mean that the hard disk has been corrupted.
An error 1022 is generated by Exchange 2000 whenever Exchange 2000 cannot write to the hard disk. Even though you may have a problem with the hard disk (for example, it has been corrupted), this type of error may also be a result of other software that is not compatible with Exchange 2000, which prevents Exchange 2000 from writing to the hard disk.
This issue can also occur because of incorrect permissions on the Exchsrvr folder structure.
RESOLUTION
To resolve this behavior, begin by running the following command on all hard drives which host Exchange data:
chkdsk /f /r
If chkdsk does not resolve the issue, examine the permissions on the Exchsrvr folder structure. Make sure that SYSTEM has full control of Exchsrvr and all subfolders on each partition that contains Exchange data.
If you still cannot mount the databases, troubleshoot any Windows NT file-level antivirus software running on the Exchange 2000 computer.
NOTE: You cannot fix this behavior if you only stop the antivirus services.
You must attempt to reconfigure your antivirus software so that it does not scan your Exchange database and log file directories. In a default installation of Exchange, the database and log files are placed in the C:\Program Files\Exchsrvr\Mdbdata folder. If you have manually moved your logs and/or databases to another drive you must also exclude those directories from being scanned by the antivirus software. After you have made these changes, you can attempt to mount your databases.
If you still have a problem when you attempt to mount your databases, you must remove your antivirus software, and then restart the server. This step can remove the hooks that the antivirus software has into the file system that is not performed if you only stop the antivirus services. When the server has restarted, you can attempt to mount your databases.
If the behavior still persists, you have to troubleshoot your hard disk again. This time, examine the System log for any disk-related errors. You may also want to run the Chkdsk utility on the hard disk to scan for errors.
Additional query words: exch2kp2w
Keywords: kberrmsg kbprb KB300608
