Exchange Server TechCenter >
Exchange Server Forums
>
Exchange Software Updates
>
Update Rollup 9 for Exchange Server 2007 Service Pack 1 (KB970162) has been released
Update Rollup 9 for Exchange Server 2007 Service Pack 1 (KB970162) has been released
All Replies
- I made the jump again and successfully installed RU9 for Exchange Server 2007 SP1. However before I started doing so, I carefully read Amit Tank's blog
Exchange Update Rollup Installation. It is not Nightmare!!!
See: http://exchangeshare.wordpress.com/2009/05/30/exchange-update-rollup-installation-it-is-not-nightmare/
What I did:
1. disabled WSSG GPOs (a pop up message appears that I don't have permission, although I logged in as Administrator)
2. stopped Forefront for Exchange Server
3. installed RU9 by Enabling Verbose MSI Logging to generate a setup log, using the Command Prompt (Exchange2007-KB970162 -x64-EN.msp /lxv* c:\SP1RU9.log)
Next time I also will apply Amit Tank's recommendation #6 "Lack of Internet Connectivity". That may speed up the installation.
ahh nevermind, i'm a complete idiot. got it.
Don't you wish you could delete posts ;-)
Hey Moderator - why can't we delete our own posts ?? (Please)- I am having an issue RU9 that I need some guidance with. I am attempting to install the update on SBS2008.I did not read Amit's blog ahead of time and perhaps missed a step. I start installation of the update and it stalls out at about 30% installed. There are no errors or anything interesting in the logs. I am installing via SUS and not via the command line. Any suggestions on what to do next? Since the update stops all my web services too, it's killing my website. I'll start off by running the standalone update with the logging option mentioned below. What else?
UPDATE: I pored over the log generated from install and discovered that setup was going component by component and checking all possible paths for the original Exchange components. However, for some reason they were not found. I extracted the path that setup was looking for Exchange binaries at and copied the original sources from the insall disk there. That seemed to work and setup completed
Cheers
John- Edited byJohn McCrae Thursday, July 30, 2009 9:28 PM
- As usual Windows Update grabbed RU9 and auto-installed it on my lab machine. The only reason I noticed is once again the Hub Transport services was not auto-restarted. I have noticed this in the past with RUs, in that the service is set to Auto but not restarted. All the other services are running fine.
Windows 2008 Standard w/SP2 running in a Hyper VM.
Forefront for Exchange is installed as well and up to date.
Any ideas why the Hub Transport service seems to be overlooked? - I have a bigger problem. the update was installed for me. Around Midnight server rebooted. when it came back up. Exchange isn't working at all. I can't get it to pull up VIA OWA and outlook will not connect to it. I found out while back hub transport services i needed to start after a reboot to get my mail. But i still can't connect to my exchange server.
and this is SBS2008 also. - Hotfix - IMHO downloading and auto applying a RU via Windows Update doesn't sound like a good idea.
re the Hub Transport - once I got the RU eventually installed - the HT seemed fine. I have had that problem with older RU's.
Again IMHO a reboot worthwhile after a RU.
John - good job with the log...
JMatson - have you tried un-installing the RU9 ?
Hotfix - IMHO downloading and auto applying a RU via Windows Update doesn't sound like a good idea.
Well when you have auto-updates turned on for all of your test machines, an Exchange RU more or less gets applied whether you want it to or not. As for not using auto-updates in the lab, I really see no reason not to as it helps make sure they are up to date and honestly the Exchange RU's are the only updates that don't leave the machine as they found it (in regards to started services).
So I guess I was more or less reporting to MSFT that their update installer that they released through Windows Update didn't properly start all the services again.- For the 5th straight rollup, the OWA is broken for us post install. The HTML is gone and you get some semi functional text that allows you to login, but the page is completely garbled.
Any chance MS can fix this problem in rollup 10? I can find thousands of posts on this exact problem for every rollup for 2007 SP1. None of the suggestions work outside of uninstalling the update. I am stuck on rollup 4 as this is the only update that does not break OWA. Very frustrating. For the 5th straight rollup, the OWA is broken for us post install. The HTML is gone and you get some semi functional text that allows you to login, but the page is completely garbled.
Any chance MS can fix this problem in rollup 10? I can find thousands of posts on this exact problem for every rollup for 2007 SP1. None of the suggestions work outside of uninstalling the update. I am stuck on rollup 4 as this is the only update that does not break OWA. Very frustrating.
I have not seen the OWA problem you mentioned on any of the various systems I was responsible for managing, so I would strongly suggest you call PSS and open up a case. Something else may be wrong with your system that is preventing the OWA portion to apply appropriately.- Papaman - I agree PSS sounds like a good idea. Look in these forums though as there have been OWA faults already reported with RU9 and fixes posted I believe
Hotfix 10 ? I expect not as SP2 is inearly here.
Hotfix - Auto install in LAB - I hear what you say, sure safe enough I guess, as long as you track what is happening.. - Yeah, I'm unable to apply this update. It's actually listed as an "installed update", but I got an error about the installation "ending prematurely". Tried installing it via MU first, it failed (albeit being listed as an installed update), removed and tried manually.
Generic error 1603 and the verbose log is cramped with errors suggesting theres something wrong with the patch. Beyond me, as the signature and hash checks out (The SHA1 of my MSP is 93c0cef45ba5246ae3d67f35dd8c7779ee1f3a1e)
The test machine is running Win2K8SP2 with vanilla Exchange 2007 SP1 installed. I made sure to run the patch with Admin-rights, I even enabled THE Administrator and tried.
I've upped the verbose log to http://rapidshare.com/files/264910351/RU9.zip
Update: I managed to resolve the issue. I don't know exactly what made the difference, but i ghosted the server back to a core install, joined it to the domain and installed Exchange again. This time I did EVERYTHING as THE Administrator, instead of using my own account . I also rebooted at every step along the way.
During my first try I got some errors, first the IPv6-thingie, second I got an error whilst "copying Exchange files (exchangeserver.msi)" during install (it did install once I restarted the process though). This time I encountered no errors whatsoever and UR9 installed like a charm. - What a disaster! This rollup made a complete mess of my Exchange 2007 on SBS 2008 that I just installed this weekend!As others have stated here, the installation of the rollup got part way into its installation, then I noticed that nothing was happening.No prompts or errors, but no disk activity or much else going on for about 30 minutes. I pressed "Cancel Installation", and waited about 15 minutesmore, and finally it said installation was cancelled and the update failed.I checked my installed updates, and sure enough it was listed as an installed update. Everything, though seemed to be working fine.Doing some research, I stumbled on this site, and read that there were some prerequisites that I need to do before installing it. Nice. So much for trusting MS to releasean update that will install correctly without tinkering with a magnitude of settings first!Here was my big mistake, though--even though everything appeared to be working, I wanted it out of my list of installed updates, so I chose "uninstall" on it.It chugged along then requested a file "EXCHANGESERVER.MSI". More research was needed, since that file was nowhere to be found. Turns out, it's on the Components and repair DVD, and required I copy the whole Exchange12 folder to my hard drive and point the requester box there. So, it finished uninstalling RU9 (which, since I cancelled it, it should not have been installed in the first place).The by-product of that? Every Exchange or Exchange-related service was stopped and set to DISABLED!!!! DISABLED??? Why the heck would it DISABLE all my Exchange services (and IIS services)??Fortunately, I had a client's server with SBS 2008 to look at and compare service-by-service and set accordingly to Automatic/Manual/Disabled. Once set, everything seems to be working.Needless to say, I will be waiting until Exchange 2007 SP2 before running any Rollups.Thanks, MS.
- Hi,
Do I still need to install this RU 9 before i apply Exchange Serve 2007 SP2 ?
/* Windows Infrastructure Support Engineer */ Hi,
No, SP2 contains all fixes up to SP1 UR9 so it doesn't require to install before you apply SP2.
Do I still need to install this RU 9 before i apply Exchange Serve 2007 SP2 ?
/* Windows Infrastructure Support Engineer */Issues That Are Fixed in Exchange Server 2007 Service Pack 2
Amit Tank | MVP – Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com
- Iancorp,
I have exactly the same problem, what services need to be set to auto, started etc ? Iancorp,
I have exactly the same problem, what services need to be set to auto, started etc ?
I'd be happy to send you screen shot of my MS Exchange services screen so you can see.There are too many for me to list/retype.How can I get an image to you?- Hi Lancorp,
Thanks for your willingness to share here, please upload it here using imageshack.us :-)
/* Windows Infrastructure Support Engineer */
