Exchange 2007 server with OWA failure. I have an Exchange 2007 that seems to have worked fine until the latest Rollup came out and was applied. Since then, I am unable to access OWA, get a blank web-page with an error at the bottom of the status bar. From there, I get errors on the Exchange Management Console when I look at the Outlook Web Access Settings. Something about HResult. -***, if the number really matters, I can post it. I have done LOTS to try getting this going including:Removing the Virual Site, Virtual Directory Using the Remove-OWAVirtualdirectory to uninstall the OWA path (Succeeds) Using the IIS plugin to create a BRAND NEW site that is blank Using the New-OWAVirtualdirectory to Reinstall the OWA path (succeeds) Found some article about unstalling .NET 1.1 and the setting .NET 2.0 to disable 32-bit running (seemed to work) Did all this in every order known to man, still no OWA. No help from Microsoft, and other peoples having this issue if you search for OWA Blank Page on the Internet.SO>>>> There is one thing that I have not done that was suggested in a forum. It was suggested to reinstall the "Client Access Role". The only comment I've found about doing that is: User1: "Do you loose data by doing this?" User2: "I didn't" So... Since it looks as if I need to reinstall that roll (WHICH IS BS, MICROSOFT!), will I loose my data? This is a single Exchange 2007 server that has all the access roles, with a retired Exchange 2003 server that has all services turned off and the procedure to remove it finished. Is there something I should prepare for when I try this? Will I loose the data, sure hope not, this thing is working. And finally, will this fix the OAB Sync error the Outlook Clients get, or is that a different issue? I have the OAB moved to the Exchange 2007 server, so I figure it's due to the IIS site not working.Please advise as not having remote access to e-mail SUCKS! MICROSOFT, support your product! Thank you for your time!Blaze

Is your problem simmilar to this one? 440 Login Timeout for OWA http://www.pro-exchange.be/modules.php?name=News&file=article&sid=519 How to fix is included. Deli

Thank you for your reply, but it has nothing to do with the stated issue. I have recreated OWA sites, I do NOT get any errors, I pasted the HTML source I get. There are no other errors that I can find except this one in the UpdateOWa.log file [08:48:06] ***********************************************[08:48:07] * UpdateOwa.ps1: 5/22/2007 8:48:07 AM[08:48:10] Updating OWA on server ECB-EXCHANGE[08:48:10] Finding OWA install path on the filesystem[08:48:10] Updating OWA to version 8.0.709.0[08:48:10] Copying files from 'C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa\Current' to 'C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa\8.0.709.0'[08:48:11] Getting all Exchange 2007 OWA virtual directories[08:48:11] Error patching OWA: Command execution stopped because the shell variable "ErrorActionPreference" is set to Stop: Unable to create IIS (Internet Information Service) directory entry. Error Message is: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.. HResult = -2147023838 The first thing that the Rollup does is stops and disables about every service imaginable. It never completes and I have to manually go and re-enable the services and start them to get Exchange, IIS and other services back up and running. Please help, OWA has been broke for weeks. My main question is whether or not I can reinstall the Client Access Role w/o affecting the data on the Exchange server. I only have 1!

You can uninstall and reinstall only the CAS server role without any loss of data for the Mailbox Server role Deli

I was able to reinstall CAS w/o data loss, but it wasn't very smooth. Here's what happened and what I did about it. 1: Go Command Prompt style and uninstall the CAS via command line. Seems that option wasn't available via the add/remove programs, even though every piece of documentation said it would be (which there aren't many). 2: Ran *\Exchange\bin\exsetup.exe /mode:uninstall /roles:ca 3: This failed several times, so with the result pointing to the IIS server. 4: So I uninstalled IIS from the Add/Remove Windows Components. Directions said to clear every check box, except the Common Files: 5: No errors, but it went WAY too fast to really remove anything and kept complaining about cluster* files that were older on the source than the destination. 6: Finally after 6 tries, I told it to replace the source files(Really bothered me to do this). During this period, I was unable to reinstall IIS, it ran through the motions, but never acted like it was copying files. It just seemed to fail and the MMC Snap-in, was there, but it "failed to initialize". 7: I ignored the document that said to leave the common files checked and I went ahead and unchecked the Root of the IIS install. So that it cleared out all files related to IIS. (this worked only after I said "Yes" to replace older files) 8: Reinstalled IIS by checking the same check box (This was the 9th time I tried to install IIS), but this time it took and the files copied. (Lots of reboots between this point too, but I don't figure they affected the overall outcome) 9: From the command line, I tried to run *\exchange\bin\exsetup.exe /mode:install /roles:ca 10: FAILED! 11: Rebooted 12: Used the Add/Remove Programs to Install it. It finally took 13. This whole process took over 2 hours to simply get IIS uninstalled and to click a check box. There is something logically wrong with 64-bit Windows and I feel that the support Microsoft has give for this is Null. 14. Seemed to work, I didn't even try to move the OWA directory out of the Default Site as I just wanted it to work for a bit. I really hope this helps someone out there as there is no help for this issues. I feel that this issue was caused by Security Rollup #4 and possible that the OWA site was not on the default web-site. I'm not sure, because Microsoft only has 13 documents on their support site, if you search for "Client Access Role". And almost none of them even apply to Exchange 2007. Enjoy, it works again. Atleast until the next update.Blaze Lewis

Thanks Blaze! You pointed me in the right direction to fix the failures that the Dec 11, 2007 updates caused in my OWA. The error I was getting (among others) was: System.IO.FileLoadException: The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) (included so people can search on the error code) I tried uninstalling the CA role by just stopping Internet Services on the server (not just the website, ALL IIS), and it worked. Reinstalled, reconfigured, and everything is back to good. Thanks, Derek Harris

Blaze may not read this but he may just be the hero of the hour. I have been at my wits end for the last week rebuilding an Exchange Server 2007 following a domain rename (don't go there!) I have been having great difficulty in getting OWA working and you have given me the information I needed in order to put everything back to rights.I was able to uninstall the EX2007 CA Server followed by an uninstall of IIS ( from add remove programs).Reboot the server.Install IIS and RPC over HTTP.Install EX2007 CA ServerOWA working. Blaze Sir, I am in your debt, many thanks, Iain Mckeand

Very useful post. Worked like a charm here. BUT, if you have Service Pack 1, be sure to re-download the package and extract it. You need to specify the new target OF THE SERVICE PACK 1 to reinstall the CA Role without error. Have a nice day!