Exchange 2007 SP2 SBS 2008

Please Help!!
I am trying to install Exchange SP2 os an SBS 08 server. I have solved all the errors up to the upgrade point where it fails with the Windows installer. I have now found an article and installed the 'SBS2008 SP2 install tool' but it fails as it says Exchange SP1 must be installed!! At this point i have an exchange that is not working and i can't get SP2 on. Is there anyway i can reverse the install back??
Gazmo30Asked:
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.

Alan HardistyCo-OwnerCommented:
Have you followed the MS KB Article in the link below which advises you to make a registry change before attempting the installation? :
http://support.microsoft.com/default.aspx?scid=kb;EN-US;973862 
0
Rick FeeMessaging Engineer - Disaster Recovery EngineerCommented:
0
Rick FeeMessaging Engineer - Disaster Recovery EngineerCommented:
Windows Installer 4.5 is required  to install Exchange 2007 SP2, so you might need to install this on SBS2008
0
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

Gazmo30Author Commented:
alanhardisty, EndureKona

I have added the key as it suggests. The server passes all the checks but fails at the upgrade part. On further investigation i have found that the microsoft exchange transport service is not running. It will start and then stops.
0
Gazmo30Author Commented:
EndureKona,

I have also installed installer 4.5!!
0
Alan HardistyCo-OwnerCommented:
What is your application event log saying when you try to start the Transport Service?
0
Gazmo30Author Commented:
I am afraid all of this:

The service will be stopped. Reason: Microsoft.Exchange.Transport.TransportComponentLoadFailedException: Loading of component 'AD Configuration Readers' failed. ---> Microsoft.Exchange.Transport.TransportComponentLoadFailedException: The transport component 'SequentialTransportComponent' couldn't be loaded successfully. ---> Microsoft.Exchange.Transport.TransportComponentLoadFailedException: Loading of component 'PoisonMessage' failed. ---> Microsoft.Exchange.Transport.TransportComponentLoadFailedException: The poison message component couldn't access the registry information. Locate the registry location and verify that the Network Service account or the account with which the Microsoft Exchange Transport service is running has read/write permission for the registry. ---> System.UnauthorizedAccessException: Access to the registry key 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Transport\PoisonMessage\BootProcess' is denied.
   at Microsoft.Win32.RegistryKey.Win32Error(Int32 errorCode, String str)
   at Microsoft.Win32.RegistryKey.CreateSubKey(String subkey, RegistryKeyPermissionCheck permissionCheck, RegistrySecurity registrySecurity)
   at Microsoft.Exchange.Transport.PoisonMessage.Load()
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Transport.PoisonMessage.Load()
   at Microsoft.Exchange.Transport.SequentialTransportComponent.<>c__DisplayClass2.<Load>b__0()
   at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.RunADOperation(ADOperation adOperation, Int32 retryCount)
   at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.TryRunADOperation(ADOperation adOperation, Int32 retryCount)
   at Microsoft.Exchange.Transport.SequentialTransportComponent.Load()
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Transport.SequentialTransportComponent.Load()
   at Microsoft.Exchange.Transport.ParallelTransportComponent.<>c__DisplayClass2.<OnLoadChild>b__0()
   at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.RunADOperation(ADOperation adOperation, Int32 retryCount)
   at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.TryRunADOperation(ADOperation adOperation, Int32 retryCount)
   at Microsoft.Exchange.Transport.ParallelTransportComponent.OnLoadChild(Object state)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Transport.ParallelTransportComponent.Load()
   at Microsoft.Exchange.Transport.SequentialTransportComponent.<>c__DisplayClass2.<Load>b__0()
   at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.RunADOperation(ADOperation adOperation, Int32 retryCount)
   at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.TryRunADOperation(ADOperation adOperation, Int32 retryCount)
   at Microsoft.Exchange.Transport.SequentialTransportComponent.Load()
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Transport.SequentialTransportComponent.Load()
   at Microsoft.Exchange.Transport.Components.Activate()
0
Gazmo30Author Commented:
Ok, i have the transport service running again. I found an article about permissions and the network service did not have full control. OWA is still not working!!
0
bcbigbCommented:
Wait... did you try to install Exchange over the default 2007 install? SBS2008 comes with Exchange 2007 out of the box. You should simply download SP2 either via Windows Update/Catalog or the web site and apply it.

If you are simply patching it, then I'm assuming this is where it's failling... is this correct?

~BC
0
Gazmo30Author Commented:
i download the E2K7SP2EN64.exe file and ran that, after the registry entry and windows installer update. The problem i have is that it seems stuck in limbo between SP1 and SP2!! It is now working but OWA has stopped - not so worried about this at the moment. What i really want to do is restore SBS back to before i applied the update!!
I also think windows installer is causing a problem. All the checks show it works, but even 07 SP12 is failing with this:

Hub Transport Role
Failed

Error:
Installing product C:\Program Files\Microsoft\Exchange Server\bin\dw20sharedamd64.msi failed. Fatal error during installation. Error code is 1603. Last error reported by the MSI package is 'The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.'.
0
bcbigbCommented:
I would highly suggest taking a full backup of your exchange store and your server and then proceed to uninstall Exchange, install it once more, uninstall it a final time (to clear any remnants out), and finally install it one last time. Then, on this fresh copy, upgrade to SP2.

~BC
0
Gazmo30Author Commented:
I was dreading somebody suggsting an uninstall!! Is it easy to do and what are the implications to the users?? There must be a better way??!!
Any ideas on the 'windows installer' issue??
0
Alan HardistyCo-OwnerCommented:
If you want a 2nd opinion, I would call Microsoft Support and let them troubleshoot the issue with you and with any luck, they will be able to resolve the issue without resorting to uninstalling anything.
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
Gazmo30Author Commented:
Anybody else got any ideas??

What i really want to be able to do is roll Exchange back to SP1 and start over. Is there a registry key, for example, that would enable this??
0
bcbigbCommented:
There are no registry keys I have ever seen to do so. After 10+ years of experience, I can safely say that doing a hack-job fix may save you some downtime now, but you will almost certainly have wierd little unexplainable issues with the box from now on as a result. Microsoft support may know something I don't as they have access to documentation about Exchange that I can't touch but if they can't fix it I'm telling you: do a clean reinstall or you may well regret it! ;-)

Good luck,
~BC
0
Gazmo30Author Commented:
Ok, this has been sorted by getting Microsoft support involved - they were very good.

The reason SP2 had failed was due to a rouge registry entry in the MSIServer key. It was the installer that was failing. The entry was 'WOW64' and they think it was left over from the install of SBS SP2.

I hope this helps somebody else out. The engineer said there was only one other reported case of this happening. Just my luck!!
0
Alan HardistyCo-OwnerCommented:
Nice - well done on spotting the deliberate mistake and making it past the post in 2nd place - do you win a medal? : )
Alan
0
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.