Exchange Server Forums

i am getting error when mounting the store. Error :ID no:c1041724

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2000] >> Migration >> i am getting error when mounting the store. Error :ID no:c1041724

Page: [1]

Message

<< Older Topic Newer Topic >>

i am getting error when mounting the store. Error :ID n... - 3.Dec.2004 8:23:00 AM

Guest

After restoring backup.
when I try to mount store i am getting Error :ID no:c1041724

Post #: 1

Featured Links*

RE: i am getting error when mounting the store. Error :... - 3.Dec.2004 4:58:00 PM

MegaDuck

Posts: 35
Joined: 21.Sep.2004
From: California
Status: offline

That error usually occurs when you have a disk space problem on the drives that host the information stores.

Here is a KB article regarding the error:

http://support.microsoft.com/?id=294318

(in reply to Guest)

Post #: 2

RE: i am getting error when mounting the store. Error :... - 2.Feb.2012 9:31:30 AM

Ellinor

Posts: 105
Joined: 24.Oct.2011
Status: offline

Generally, this error occurs when their is not sufficient space on the disk (as mention in Microsoft KB article). However, sometimes this error message can also be appeared because of the following reasons:

1. Exchange Server Log file contains an invalid signature.
2. Your anti-virus software erases or quarantines MS Exchange Server Log file.
3. Executing eseutil/p on damaged Exchange databases without deleting the log files.
4. Running �eseutil /r three-character logfile base name� command with wrong log file base name.
5. Corruption of Exchange Server database.

How to solve

To rectify the this error message and successfully mount the database, you will need to follow the below steps:

1. Recover Exchange Server Log file from quarantine folder in the anti-virus program.
2. Run eseutil/p to repair corrupted database.

Eseutil/p command is used to bring the corrupted database in a mountable state but sometimes it removes the databases pages permanently during the repair process and users have to face the data loss problem. To avoid such data loss situations, using an advance third party Exchange database recovery application will be a good choice.

(in reply to MegaDuck)