[ExchangeList] Re: Failure to Mount exchange database -Exchange 2000 server
- From: "Dolly Bareqet" <Dolly.Bareqet@xxxxxxxxxxxx>
- To: <exchangelist@xxxxxxxxxxxxx>
- Date: Sun, 14 May 2006 16:49:38 +0200
Check if your AV software quarantined any log file.
Dolly
_____
From: exchangelist-bounce@xxxxxxxxxxxxx
[mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Elmehdi Bendriss
Sent: Sunday, May 14, 2006 2:21 PM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: Failure to Mount exchange database -Exchange
2000 server
there is also this article that may help:
Article ID: 300608
Article Last Modified on 4/25/2005
_____
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:
The name of one of the database files in this store is invalid.
ID no.: c1041737
Exchange System Manager
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://www.microsoft.com/contentredirect.asp.
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://www.microsoft.com/contentredirect.asp.
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://www.microsoft.com/contentredirect.asp.
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://www.microsoft.com/contentredirect.asp.
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.
On 5/14/06, Elmehdi Bendriss <bendriss@xxxxxxxxx> wrote:
here is the description of your error :
Article ID: 307790
Article Last Modified on 11/1/2005
_____
APPLIES TO
* Microsoft Exchange Server 2003 Standard Edition
* Microsoft Exchange Server 2003 Enterprise Edition
* Microsoft Exchange 2000 Server Standard Edition
_____
This article was previously published under Q307790
This article is a consolidation of the following previously available
articles: 822934, 327065, 823169
SYMPTOMS
The Microsoft Exchange Information Store service may start. However, one
or more of the store databases may not mount successfully. The following
error messages may be logged in the Application log:
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9519
Description:
Error 0xfffff764 starting database " Storage_group \Database" on the
Microsoft Exchange Information Store.
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9518
Description:
Error 0xfffff764 starting Storage Group
Distinguished_name_of_storage_group on the Microsoft Exchange
Information Store.
Event Type: Error
Event Source: ESE98
Event Category: Logging/Recovery
Event ID: 454
Description:
Information Store (976) Database recovery/restore failed with unexpected
error -2204
Additionally, you may receive the following error message:
Exchange System Manager:
An internal processing error has occurred. Try restarting the Exchange
System Manager or the Microsoft Exchange Information Store service, or
both.
ID no: c1041724 Exchange System Manager
CAUSE
This issue may occur if either of the following conditions is true:
* The streaming file (.stm) that is associated with the database
has been deleted.
* Permissions for the streaming file (.stm) that is associated
with the database have been modified. Therefore, Exchange cannot access
the streaming file.
These conditions may occur when your antivirus program scans the
Exchange 2000 Server or the Exchange Server 2003 folders.
RESOLUTION
To resolve this issue, restore the missing streaming file from a good
backup to the Exchsrvr\Mdbdata folder. You can also see whether the
antivirus software moved the streaming file to the Quarantine folder. If
the streaming file is in the Quarantine folder, move the streaming file
to the original location. Then, configure the antivirus program so that
it does not scan the Exchange 2000 Server or Exchange Server 2003
folders.
Note Some antivirus programs change the file properties to Read-only
when the files are moved to the Quarantine folder. If you find the
streaming file in the Quarantine folder, right-click the file, and then
click Properties. Click to clear the Read-only check box before you try
to mount the database.
For more information, click the following article number to view the
article in the Microsoft Knowledge Base:
823166 : Overview of Exchange Server 2003 and antivirus software
MORE INFORMATION
The name of the streaming file corresponds to the name of the associated
database file. However, the streaming file has a different file name
extension. For example, the default mailbox store file name in Exchange
2000 Server is Priv1.edb. The matching streaming file for Priv1.edb is
Priv1.stm. For more information about streaming files, click the
following article number to view the article in the Microsoft Knowledge
Base:
232323 : Native content storage in Microsoft Exchange
On 5/14/06, Willy Matuku <WillyM@xxxxxxxxxxx > wrote:
Dear All,
I have spent 2 days trying to resolve a problem whose solution I have
been unable to get inclduing researching on the internet. I have tried
most of the solutions without success.
I have re-installed exchange 2000 and whenever I mount the database I
receive an error with event ID.9519 and the actual error is ID:c1041724
Exchange systems manager and the application logs gives the event id
9519 Source: MSExchangeIS
I have tried checking on the data integrity and is fine. I have also
checked the various security allocation to the folders and they are
fine. I have checked to ensure the necessary 2 files (priv1.edb and
priv1.stm ) and available.
Does anyone have a solution to this problem?
Thanks
Willy
The information contained in this e-mail is intended only for the personal and
confidential use of the recipient(s) named above. If you are not the intended
recipient(s) or the person responsible for delivering this communication to the
intended recipient(s), you are hereby notified that you have received this
communication in error and that any review, dissemination, distribution, or
copying of this message is strictly prohibited. Please notify the sender
immediately via e-mail and delete this e-mail from your system. iMDsoft shall
not be liable for any damage of whatsoever nature in connection with any
information received in error.
Other related posts:
