In this Article, I am going to explain how to resolve the blue dump error in Exchange 2010.
Problem Reported: When rebooting the Server, Getting Blue Dump Error
As per the error meesage, The error code is 0X00000074. Please follow the below steps to resolve the issue without restoring the OS.
Collected the Crash DUMP and analyzed to find root cause. Found Registry got corrupted which caused for this issue.
By Default, Your Registry backup folder will be there in the path,
Now, map the VM in the base server and go to OS Drive of the VM and find the path,
C:\Windows\System32\config and delete the Following Files,
And Copy the Files all files from C:\Windows\System32\config\RegBack and paste those files in the
Now you have replaced corrupted registry files and you can reboot the Server. You can see the server is getting boot screen and going through properly.
As Expected, You Could see all your Exchange Databases are Corrupted. Below is the Screen shot of the event.
if you try to mount the Database, You will end up with the same error message.
The same you can see it in exchange Console by using ESEUTIL /mh “d:\chnpfdbdb01\chnpfdb01.edb”
Database is in Dirty Shutdown, Hence run the below command to make this Database for Clean Shutdown.
Map the Log File Path,
But, Log Files are got damages and there is not other last log file is available in healthy condition. Thus We are going to force repair without the log files,
Now, you can see the Database is showing dismounted status and if you run the Command ESEUTIL /mh “d:\chnpfdbdb01\chnpfdb01.edb”. You will see the database in clean shutdown.
But You will end of with another issue that IIS Service is not getting start even you force it do start.
The Event Log Says,
No Problem, You can solve this too by using the below option,
Check in C:\Windows\System32\Inetsrv\History, you should have a backup of Metabase.XML & MBSchema.XML. Backup the existing Metabase.xml and MBSchema.xml from C:\Windows\System32\Inetsrv.
Rename the backup from the ‘History’ folder. Copy & Paste each of these to the C:\Windows\System32\Inetsrv. Then run iisreset.
WOOT, You have resolved the issue. Will see you in another article. Stay tuned..