After System State Restore - get stop error 0x0000007B

Hi All,

I have an unhappy server on my hands.  The server crashed a day ago and we are in the process of returning it to service.

What happened?
•      Hard and the mirror crashed on the server.
•      We were able to save the data that was stored on the server as well as the Priv1.edb and pub1.edb of the exchange server.

What have we done so far?
•      One of our technicians set up the server, but did not have the hard disk controller (SATA) set up in RAID mode, thus no RAID drivers were required during the setup.
•      She returned all the data files from backup to their original locations.
•      She performed a System State Restore from a two day before the failure.
•      Result – blue screen of death.  Stop error 0x0000007B

Now, thinking that this is a raid driver issue, I switched the SATA controller over to RAID mode to get around any driver conflict.  No joy.

I don’t have time to hunt for a solution.  Can one of you help?

Regards,
M
LVL 13
itcozaAsked:
Who is Participating?
 
Jay_Jay70Connect With a Mentor Commented:
shiezen...... this can get tricky...

There is a link that will show you how to change the system partition letter, once we get this cranking we can play with your other drives

http://support.microsoft.com/?kbid=223188
0
 
Jay_Jay70Connect With a Mentor Commented:
have you still got the backup and the RAID drivers yet? if so, build your RAID and reinstall
0
 
itcozaAuthor Commented:
Nope... this is not an option as the RAID failed - corruptions... The OS was functioning fine until a system state restore was done to return the server to its functional state. Lets look for a way to fix the problem, not just revert to re-install.

:-)
0
Cloud Class® Course: Amazon Web Services - Basic

Are you thinking about creating an Amazon Web Services account for your business? Not sure where to start? In this course you’ll get an overview of the history of AWS and take a tour of their user interface.

 
Jay_Jay70Connect With a Mentor Commented:
i agree, i just wanted to see how far long you were before trying to troubleshoot it,

you can try jumping through a windows repair with the latest SATA RAID drivers, this at least wont destroy your system state
0
 
itcozaAuthor Commented:
Nice... that worked well... Now just one small problem... The drive letters have changed on the hard disk and for some odd reason C drive is and extended partition now.   I need to change the D drive to E drive to allow Exchange to function.   Only problem is that the now D drive is the System Partition.  Not nice as it does not want to let me change the drive letter for this drive... any ideas?

:{
0
 
itcozaAuthor Commented:
OK,

- Server is back up and running,  
- I have changed the partition letter to E so Exchange can re-Install (or so I thought)

Huston, we have a problem.

I get an error when performing the reinstall of Exchange.  The error pops up during the Messaging and Collaboration Services section of the installation:
“Setup failed while installing sub-component Base DAV protocol with error code 0x8007042C (please consult installation logs for a detailed description). You may cancel the installation or try the failed step again.”

I have checked the Exchange installation log file and based on that it is WMI that does not want to start.  An yes… it fails to start – Error 1068: The dependency service or group failed to start.  

Now WMI requires the Event Log service and the RPC service.  Although this looks like an Exchange problem, we are still dealing with failures on the server side. Both are running nicely.  So then we are left again in the middle of a rock and a hard place.  

Please help.
Regards,
0
 
itcozaAuthor Commented:
By the way.. the reason the server was rebooting all the time in the beginning was because the server had been installed with SP1 and the repair was done with Pre SP1 CD... The system state was post SP1 and thus there was a bit of a mix up in the system.  One of the technicians did the repair and then dutifully installed SP1 and then loaded the system state from backup again... this time there were no reboots... or failures.

Regards,
M

PS - thanx for the help... I will open a new question for the Exchange and WMI problem.
0
 
Jay_Jay70Commented:
ah ok mate no problem, good luck with the exchange setup!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.