I've been running Exchange 2007 for a little over a year now. When SP1 came out, I installed it the same day. Things have been working great. That is until a few days ago. My Public Folder database will no longer mount. When I try to mount it, I get this error: --------------------------------------------------------Microsoft Exchange Error--------------------------------------------------------Failed to mount database 'Public Folders'. Public FoldersFailedError:Exchange is unable to mount the database that you specified. Specified database: PLUTO\Second Storage Group\Public Folders; Error code: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-501). --------------------------------------------------------OK-------------------------------------------------------- At the same time, I see 2 errors in the event logs ID: 454 Source ESE MSExchangeIS (204) Second Storage Group: Database recovery/restore failed with unexpected error -501. ID: 9518 Source: MSExchangeIS Error Log file is corrupt starting Storage Group /DC=local/DC=StuartBusiness/CN=Configuration/CN=Services/CN=Microsoft Exchange/CN=First Organization/CN=Administrative Groups/CN=Exchange Administrative Group (FYDIBOHF23SPDLT)/CN=Servers/CN=PLUTO/CN=InformationStore/CN=Second Storage Group on the Microsoft Exchange Information Store. Storage Group - Initialization of Jet failed. When I run an eseutil /p, it completes very quickly and with no errors. When I run an isinteg on the database, it fails with the same 501 error. Can anyone help me?

Stuart, Please try the following: First make a offline backup before messing up everything. Then eseutil /mh "database path + name" and check if the shutdown is clean If the database is consistentthen the status is "clean shutdown" in this case please move all the files to a save location. And try to start the information store and mount the database. WARNING: you will lose data because the data in the corrupted log is not in the database If the database is inconsisntent then the status is "dirty shutdown" in this case you need to perform a soft recovery. You will have to stop the information store service for this to prevent mail being processed. Go to the directory where the database is located and execute the following command: Eseutil /r E00, where E00 is the 3 character code from the log file. If this doesn't fix the issue you will have to restore it from an old database or run eseutil /p (but you have already tried that I believe) What you can do extra with eseutil /p is the following 1. Run a hard repair on the database by using Eseutil /p 2. Defragment the database by using Eseutil /d. Offline defragmentation creates a new physical database structure and moves the existing data to that structure. 3. Check the consistency of the database by using Isinteg -fix. You may need to run Isinteg several times until the summary report returns no errors. Please let me know if this solves your issue. Regards, Johan

I did an eseutil /mh and saw that it was cleanly shutdown. The rest of the directions don't make sense. The information store is already started with the First Storage group (mailboxes) up and running fine. Please be more specific. I did consolidate the Storage group log files, the storage group system files, and the database file into a single location. Before they were on 2 drives, now they are on the same drive. Was hoping to that if all the files were in the same location the the repairs would work. They did not.

Hi, I understand that you are unable to mount the public folder store in the second storage group, Its no matter with mailbox database in the first storage group, right? I support Johan's suggestions, and the first direction should help to resolve this issue. please allow me to explain it more clearly. While database is in clean shutdown state, all complete transaction logs should have been written to database store. However, if some corrupted transaction logs still left in second storage group folder which can block store mounting process. To eliminate this effect, please move all transaction log files out of the second storage group folder (or toanother place) and then mount the database. If it not works well, we surely can run Eseutil /D (offline Defragment).I would like simply introduce why we need perform offline defrag in this situation. Offline defragment actually was creating a new store, and then move the data from the old store to the new store, and then replace the new one. During this process, it will actually rebuild, and fix many problems in the store. Note: 1. While preparing to do offline Defragment, you need ensure you have enough free disk space( almost about 120% as the database file size). 2. recommend you run isinteg after thedefragment. More links: ======== http://www.msexchange.org/tutorials/Exchange-ISINTEG-ESEUTIL.html http://technet.microsoft.com/en-us/library/aa995748(EXCHG.65).aspx if the issue persists, please help post the /mh result with below information running in EMS. Get-storagegroup id your second storage group name |FL >C:\1.txt (Note: the result will output to C:\1.txt file, I need get this info because i want to verify the detailed transaction logs path. Meanwhile, ESEUTIL /R also will be useful while database is clean but you may want to replay more logs in order to reduce the data loss. Per myself, I dont like to perform ESEUTIL /P in the first time as it may cause data loss. -Jason

Hi Stuart, It Jason again. If the situation is really urgent in your production environment, I suggest you contact PSS and submit an support incident. -Jason

That's it. I saw that I did have a file marked E01.chk in the log directories. I moved it along with all the other logs out of the log folder and mounted the database cleanly. Thank you for your help!

Welcome, Glad to see it helps resolving the issue. -Jason

Hi does anyone know how much difference the offline defrag will make to the speed and performance of the exchange server? I am thinking about performing an offline defrag but not sure on the results to expect yet.shivun pilwalwww.lime-group.co.uk