asked on

BSOD on Exchange VM after XenTools upgrade

Hello:

I was in the process of upgrading the XenTools on a XenServer based guest, which is running Exchange 2007 on Windows 2008 (no r2).

It hung, so I rebooted it. Now when I bring it up I get a couple seconds of the Windows progress bar, and then it BSODs with 0x00000007b. This indicates to me that it's choking on whatever storage drivers were bring installed.

Any ideas on how to resolve this? This is a production machine. I've tried doing the StartRep.exe command from the Windows CD, but it couldn't fix the problem. Ran a CHKDSK with no switches.

Thanks,

Dan

Radweld

Can you get it up in safe mode at all or is it fried? As you allready guessed a 7b is innacessable boot device and suggest corruption of the storage controller. Problem you probably have is a disparity with the registry and the actual files present on the system. I would be tempted to mount he v hard disks onto another server and backup the exchange databases and their log files and blow away the dead server.

Reset the computer account in ad
Rebuild the server using the same name and ip
Install exchange using the /recoverserver switch to retrieve the exchange config from ad, you can then manually restore the databases back to their original location.

ddotson

ASKER

I'm worried that this is the only solution. I'm on with MS support right now and we aren't getting very far. They are combing the registry trying to disable the XenTools drivers.

So how painful/risky is blowing the server away? I installed Exchange to the data drive (E:), so I'm not worried about losing that during reinstall.

I'm thinking, disconnect the E drive, then reinstall the OS. Patch it up and then bring the E drive back. Do the Exchange install using the /recoverserver switch. What do you think?

Also, it was originally installed with 2008 (no r2). I'd prefer to install 2008 r2. Thoughts on that idea?

Radweld

It's pretty painless really, you can use r2 but you need to make sure you use exchange 2007 sp1 media to support r2. In this scenario I would rebuild using 2008 though.

ASKER CERTIFIED SOLUTION

ddotson

membership

Create a free account to see this answer

Signing up is free and takes 30 seconds. No credit card required.

See answer

ddotson

ASKER

Resolved outside of EE.

joebilek

Hello, I just got this error too.

All the registry settings were actually gone, but still the BSOD appears, any more tips?

regards,
josef

ddotson