am facing a serious problem after restoring database files from other sever to a new server. I tried guidelines related to eseutil /p, but things doesnt seems to work with me. before restoring database i enabled "can be over written by restore" after finishing it I checked if files are properly replaced or not. and it was ok till here.. when i tried to mount it back.. for the error of c1041724 :-( ran eseutil /p , and tried mounting again, but no luck.
The MAPI call 'OpenMsgStore' failed with the following error: The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance. The MAPI provider failed. Microsoft Exchange Server Information Store ID no: 8004011d-0526-00000000
Posts: 3004
Joined: 9.May2007
From: India
Status: offline
hi, before you mount the database, check "do not mount the database" and then try to start the information store service?
Rename old mdbdata folder to mdbdata old and check with blank database.
Now i would suggest to save and clear application even log then after that stop the IS service.... run eseutil /mh "path of the database" check the status what is it showing whether it clean shutdown or dirty shutdown. If it is clean shutdown then move all the log files, checkpoint file i.e keep only priv1.edb, pirv1.stm, pub1.edb and pub1.stm in mdbdata folder
then run eseutil /d on the database after that check the state again.
Then run isinteg fix command... then start to mount the database if then also fail please paste the event log...i.e the complete error message
After going through your guide, still getting error in event viewer
Event Type: Information Event Source: ESE Event Category: General Event ID: 100 Date: 7/14/2007 Time: 10:50:23 PM User: N/A Computer: EXCHANGE Description: Information Store (3552) The database engine 6.05.7638.0002 started.
Event Type: Information Event Source: ESE Event Category: General Event ID: 102 Date: 7/14/2007 Time: 10:50:23 PM User: N/A Computer: EXCHANGE Description: Information Store (3552) First Storage Group: The database engine started a new instance (0).
Event Type: Error Event Source: ESE Event Category: Logging/Recovery Event ID: 619 Date: 7/14/2007 Time: 10:50:23 PM User: N/A Computer: EXCHANGE Description: Information Store (3552) First Storage Group: Attempted to attach database 'C:\Program Files\Exchsrvr\mdbdata\pub1.edb' but it is a database restored from a backup set on which hard recovery was not started or did not complete successfully.
Event Type: Error Event Source: MSExchangeIS Event Category: General Event ID: 9519 Date: 7/14/2007 Time: 10:50:23 PM User: N/A Computer: EXCHANGE Description: Error 0xfffffde0 starting database "First Storage Group\Public Folder Store (EXCHANGE)" on the Microsoft Exchange Information Store. Data: 0000: 46 61 69 6c 65 64 20 74 Failed t 0008: 6f 20 61 74 74 61 63 68 o attach 0010: 20 74 6f 20 4a 65 74 20 to Jet 0018: 44 42 00 DB.
Event Type: Error Event Source: MSExchangeSA Event Category: MAPI Session Event ID: 9175 Date: 7/14/2007 Time: 10:50:04 PM User: N/A Computer: EXCHANGE Description: The MAPI call 'OpenMsgStore' failed with the following error: The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance. The MAPI provider failed. Microsoft Exchange Server Information Store ID no: 8004011d-0526-00000000
Posts: 3004
Joined: 9.May2007
From: India
Status: offline
thanks grogran, the below article was my target to give him.
Wasim r u restoring the database and then trying to mount, if so then pls follow the grogran article... because right now the database will be inconsistent state and log required is stored in the temp which u have choosed during restoring point so inorder to mount it back you need run this command "eseutil /cc path of the directory that contains restore.env" it is clearly explained in the article which is being refferred by grogran.
Operation terminated with error -939586631 (Unknown Error, Unknown Error) after 0.0 seconds.
ok other thing.. the server from which i have taken backup was having 270 users mailbox and the new server on which i am trying to restore is having arround 254, some of them got missed.. can this be reason for not properly mounting?
Posts: 3004
Joined: 9.May2007
From: India
Status: offline
the error which you have pasted indicates that the command is not running on proper file location.
Let say: I have my database and log file restored in D:\exchsrvr\mdbdata While doing restore, it will ask for temp for restoring the log files which are not committed during the time of backup and restore.env. I will save in C:\Temp folder.
Now before i could run eseutil /cc, first i will confirm that my log files which are restored in C:\temp file are in sequecne or will check wether it is damaged
so i will go to my directory through command prompt and will type following command for the log files which are stored in a temp folder C:\exchsrvr\bin>eseutil /ml "c:\temp\e00" once i confirm each and every log files are in sequence then i will go eseutil /cc option
Posts: 3004
Joined: 9.May2007
From: India
Status: offline
hi,
You need to run like this C:\Program Files\Exchsrvr\bin> C:\exchsrvr\bin>eseutil /ml "c:\logfiles ex\First Storage Group" if the log files is ok then run eseutil /mh on priv1.edb and check the line logs required if you have all the logs then run
I also having the same problem I tried thiseseutil /cc "c:\logfiles ex\First Storage Group" it's getting error Operation terminated with error -939523486 Existing log file has bad signature. please help me to resolve this problem
Posts: 3004
Joined: 9.May2007
From: India
Status: offline
hi mate,
I believe the log file what you have for the database and the log file in the first storage group is mismatching.
I believe when you restore the database it will ask you temp location to store the uncommitted log file.
And at the same time : you will have log files in the mdbdata folder folder along with the database.
My suggestion would be: > Move all the log files for first storage group to some other location accept .edb and .stm > Run eseutil /mh on the priv1.edb and check the logs required option.. it will give the logs required
> then go to the temp folder and under that you will first storage group folder and in that confirm that you have those log files.
> If so then run eseutil /cc path of "C:/temp/First Storage Group"
Note : The error what you are getting is just because your database require the log file which is on temp folder and in the mdbdata folder you have logs which is older or new then restore and mismatch is happening
Event Type: Error Event Source: ESE Event Category: Logging/Recovery Event ID: 619 Date: 7/14/2007 Time: 10:50:23 PM User: N/A Computer: EXCHANGE Description: Information Store (3552) First Storage Group: Attempted to attach database 'C:\Program Files\Exchsrvr\mdbdata\pub1.edb' but it is a database restored from a backup set on which hard recovery was not started or did not complete successfully.
You mentioned you ran ESEUTIL /P on the database?? did you complete the process by running defragmentation and ISINTEG (integrity check)?
I would recommend trying to restore the database again but make sure you clear out ALL contents of the folders where exchange database and transaction logs are located before hand. Make sure you select to commit the logs are restoring and mount the database from the backup application. After restoring and it still fails, then run eseutil /mh on the database and post the output please.
_____________________________
Ibrahim Benna - Microsoft Exchange MVP Forum Moderator Navantis
Hi I have a similar problem. My exchange server 2003 cannot mount and fails with ID number c1041724 and event ID 9175. I did eseutil /mh and the state was clean shutdown. There is no useful backup.
This error message appears 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.
To resolve the above 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 recovery software.
A third party Exchange database recovery application uses advance repair techniques to repair logically damaged Exchange Server database. The tool can be used by any technical/non-technical user who has no prior database repair experience.
Few best reasons to choose Kernel for Exchange Server Recovery are: repairs public and private database folders, recovers deleted user mailbox data, three recovery modes to trace out every damaged data and evaluate exchange recovery capabilities with free version.
That is good one software for Exchange Server Recovery, But there is one more advance and unique software for Recover Exchange Server data. It gives complete data recovery guarantee. Read here: http://www.exchangeedbtopst.edbpst.biz
Thanks and Regards
_____________________________
Yasar Arafat Business Development Manager at Exchange Recovery
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [Microsoft Exchange 2003] >> Outlook Web Access >> Unable to Mount Store error id:c1041724 
Unable to Mount Store error id:c1041724 - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread
