• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 594
  • Last Modified:

Exchange 2003 Information Store Corrupt

Hi Experts
Have a broken Exchange Store.
Using SBS 2003 (Exchange SP2).
Server stopped responding last night. Tied to reboot this morning. Hangs when trying to load theinformation store service. When service is disabled the server boots. If try to start the service manually once server has booted the server hangs. Have modified the mailbox & public store to not load on on startup of the server.
Have tried all sorts of repair functions using eseutil. My experience with Exchange repair or restore is non existant. When running the eseutil /p option on the priv1.edb the server crashes on the last a step. Need some help troubleshooting this or restoring from backup Exec Information Store Backup. Any help would be appreciated.
Thanks
Kane
0
Wycom
Asked:
Wycom
  • 6
  • 4
1 Solution
 
PlusITCommented:
how does the server crash?  Complete lock up?

If so start by running chkdsk on the filesystem, also check disk health.
0
 
WycomAuthor Commented:
Complete Lockup, but the mouse does move (but cannot click on anything)
Ran a chkdsk on the c drive and it reported as having errors.
So then ran chkdsk /f on c drive and it performed during reboot.
Ran chkdsk on other drive (main data drive - E) and it did not report as having any errors.
Do you think I should run a chkdsk /f on the main data drive (holds the exchange database files)?
Thanks
Kane
0
 
PlusITCommented:
yes there is deffo corruption on your filesystem, hence why it locks up while trying to repair the database.
0
Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

 
WycomAuthor Commented:
Will run chkdsk /f on all drives.
Will report back
Thanks
Kane
0
 
lucid8Commented:
I would also see if you can successfully first copy the EDB off to another location for safe keeping in case things get worse, i.e. eventually cant get to the disk etc and then at least you MAY be able  to see if you can save the data within.  (If your interested in 3rd party utilities for data recover of EDB's check my profile)
0
 
WycomAuthor Commented:
Ran chkdsk /f on both drives. No Fix.
Tried the next morning to fix.
Ran eseutil /mh on the stores and both showed clean shutdown for some reason
Ended up deleting the transaction logs and then the Stores Remounted successfully.
Something must have happened overnight with the defragmentation or somthing
Kane
0
 
PlusITCommented:
then it was a faulty transaction log, prolly due to the fs corruption you had in earlier.
0
 
WycomAuthor Commented:
Is is normal practice to try to delete the transactions to try to mount the stores?
0
 
PlusITCommented:
no not at all.  The transaction logs are there to recover the store from the logs.  But sometimes a faulty log can achieve what you had.
0
 
WycomAuthor Commented:
OK. Thanks for all the help
0
 
WycomAuthor Commented:
Fixed problem myself.
But awarding points fr helping
0

Featured Post

2018 Annual Membership Survey

Here at Experts Exchange, we strive to give members the best experience. Help us improve the site by taking this survey today! (Bonus: Be entered to win a great tech prize for participating!)

  • 6
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now