Exchange Server Forums

Unable to mount replicated mailstore - errors c1041724 & 9175

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2003] >> Information Stores >> Unable to mount replicated mailstore - errors c1041724 & 9175

Page: [1]

Message

<< Older Topic Newer Topic >>

Unable to mount replicated mailstore - errors c1041724 ... - 23.Oct.2005 4:15:10 AM

bobbiness78

Posts: 1
Joined: 22.Oct.2005
Status: offline

Hi there,

I've built a new Exchange (2003 Enterprise) server and although the Exchange services start fine but I can't mount the database - errors c1041724 and 9175.

I built the server:

1. Using the /disasterrecovery switch
2. Copying the entire 'exchsrvr' directories from the old server using Veritas Storage Replicator
3. Resetting the computer account

I've done the following:

- Removed the duplicate 'systemmailbox' object according to http://support.microsoft.com/?kbid=274534.
- Checked the server is in the 'Exchange Domain Server' group

I think the problem is the way I copied the DB, normally it is done from backup/tape but the Veritas White Paper says you can copy the entire Exchsrvr directory to the same effect. The aim is to have a backup Exchange Server on standby by replicating the database.

Any advice would be gratefully received:

Post #: 1

Featured Links*

RE: Unable to mount replicated mailstore - errors c1041... - 17.Dec.2005 5:22:17 AM

jchong

Posts: 2516
Joined: 1.Dec.2005
From: Centreville, Virginia
Status: offline

Before you mount make sure you go into the properties of the store in ESM, click the database tab, where it says this database can be overwritten by a restore make sure it is unchecked. After you do a restore, if it is still checked it won't mount. Not sure if this is the case with you though.

(in reply to bobbiness78)

Post #: 2

RE: Unable to mount replicated mailstore - errors c1041... - 2.Feb.2012 10:19:07 AM

Ellinor

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

Generally, this error occurs when their is not sufficient space on the disk. Furthermore, This problem can also be occured due to 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.
3. In case, the repair utility fails, then restore the database from a valid backup.
4. However, with backup file inaccessible or corrupt, use a third-party Exchange server recovery tool.

There is no doubt that Eseutil/p command is capable to bring the corrupted database in a mountable/consistent state but sometimes it creates data loss situations as it removes the corrupt databases pages permanently during the repair process and users have to face the data loss problem. Therefore, to avoid such data loss situations, user can opt for a powerful third party Exchange recovery software.

(in reply to bobbiness78)

Post #: 3