Exchange 2007 SP3 upgrade FAILED - WHY?

Hello,

I was wondering if someone could look at our exchange logs and tell me why the SP3 upgrade failed.  I performed the PrepareAD switch to Active Directory then ran Setup. Setup just was moving along fine and then poof setup window was gone. Rebooted and tried again and it said setup was in an incosistant state and disaster recovery mode was only available.  I then restored a backup I took with BackupExec 12 and then none of the services were starting. I had to call MS support to fix the issue.

Jason

The date in the log that i started the upgrade was September 29th around 5:45PM ExchangeSetup.log
TPRaysAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

RadweldCommented:
Im a little unlclear about what state your exchange is in? also whats the layout of servers? is this a single multi role server or a cluster? there are specific instructions to deploy service packs to clusters.

Anyway when Exchange setup fails, it leaves a water mark in the registry in order to continue where it left off if you exit and restart setup, this is great until something goes wrong then your teft with exchange being inconsistent. Usually deleting the watermark enables you to rerun setup and hopefully complete the installation.

http://blogs.technet.com/b/exchange/archive/2007/05/21/3402900.aspx

What you would do is delete registry keys (with care) relating to the unpacked version, in some cases I have had to modify the installed version keys to fool Exchange into thinking it's got a lower version of the binaries and thus forces a full reinstall of the service pack.
0
TPRaysAuthor Commented:
My exchange is working fine now. We called MS Support and got it back up and running. What I need to know (rather others need to know) is Why the servicepack 3 update failed and caused our exchange server to be down for this amount of time.  Is this common? Did I do somthing wrong? Ect..

We have Two Exchange servers one is the main server and the other is the DR server at the DR site, that is doing SCR.
0
South ModModeratorCommented:
TPRays,

I changed the zones for this question from

--Citrix
--Exchange Email Server

to
--Exchange Email Server


SouthMod
Community Support Moderator
0
RadweldCommented:
Its not possible to download the log file from EE for some reason but you can review the logfile and extract the errors using a nice powershell command

 
Get-SetupLog c:\exchangesetuplogs\exchangesetup.log - error -tree

Open in new window


Assuming the log location is c:\exchangesetuplogs\exchangesetup.log, this command will parse the log file and display errors or warnings. Once you know where setup failed it will be possible to investigate that issue further.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

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.