EX2010 SP1 has broken OWA!!!

[jakanc]

Would you please explain what was wrong with your headers and what you have their now? I have the same problem and no matter what I do, I cannot get it working. Thanks.

[adamf]

Yep. On your CAS Server, open IIS Manager and select the Default Web Site. On the right hand side, under actions, click bindings. On one of the http bindings I had our internal FQDN for OWA and removing this fixed the problem.

[jakanc]

Damn, I must have something else wrong as well. Thanks.

[sacrej]

still having the problems.

in bindings on default website I have 'http' 'host name is blank' 'port =80', have also tried the hostnames exchange2010 and exchange2010.rhsnet.local, none seem to make much difference, although when people access OWA they access https://exchange2010/OWA is this correct or should it be https://exchange2010.rhsnet.local/owa? i'm pretty new to setting up mail servers so go easy

[JHK]

I encountered the same issue and we found that a circular redirect had been populated into the web.config file on the Exchange Install Directory, ClientAccess, OWA

 

I removed the follwoing lines from the web.config

 

After resetting the IIS services on the server we are no longer seeing the OWA errors. We did not have this issue prior to the application of SP1.

[RabbieBurns]

im having an issue since sp1 upgrade that the search function doesnt work in OWA.. did anyone else have this issue and how did it get resolved?

[DrCheese]

yes, give me a minute to find what I did

[DrCheese]

Right ok, you will probably be seeing errors like this in the application log on the server

"received an unusual and unexpected error code from MSSearch. "

If that's the case, I had to re-run the Schema upgrade files from the extracted SP1 files and reboot the server before it worked.

 

OWA 2010 SP1 Search problems

 

setup /PrepareAD

 

setup /PrepareSchema

 

reboot

[RabbieBurns]

Do i need to reboot between the prepareAD and the Schema prepare?

 

Im getting the following error:

 

Configuring Microsoft Exchange Server

   Extending Active Directory schema                         FAILED
    The following error was generated when "$error.Clear();
       install-ExchangeSchema -LdapFileName ($roleInstallPath + "Setup\Data\"+$
RoleSchemaPrefix + "schema0.ldf")

" was run: "There was an error while running 'ldifde.exe' to import the schema f
ile 'C:\Windows\Temp\ExchangeSetup\Setup\Data\PostExchange2003_schema0.ldf'. The
error code is: 8224. More details can be found in the error file: 'C:\Users\rob
ert.PMG\AppData\Local\Temp\2\ldif.err'".


The Exchange Server setup operation didn't complete. More details can be found
in ExchangeSetup.log located in the :\ExchangeSetupLogs folder.

Exchange Server setup encountered an error.

 

The error in the log file says "unable to connect"

[RabbieBurns]

hmm.. just tested Search in OWA and its working now, without a reboot.

 

I guess the prepareAD was enough to fix it??

 

Thanks

[Arthur]

Update Rollup 3 is out now.

 

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=413b8979-76b8-4be4-a18b-015d025eb368&displaylang=en

[chrisbrown]

Update Rollup 3 is out now.

 

Download details: Update Rollup 3 for Exchange Server 2010 Service Pack 1 (KB2492690)

 

Might roll this one out in my test environment first..Has anyone else run it yet?

[RabbieBurns]

I installed it yesterday, and insterstingy Exchange seems to be using about 10% less RAM since installing it..

[chrisbrown]

My two Ex2010 servers are both chewing over 20GB of their 24GB available. Hooray for cheap DIMMs!

[RabbieBurns]

yeh I was under the impression exchange was designed to use up as much of the available memory as possible. Mine only has 3GB and utilisation used to sit at about 50% to 60%.. Since yesterday its dropped to 40% now.

 

But with dynamic RAM in hyperV its not much of an issue.

[oxide54]

yeh I was under the impression exchange was designed to use up as much of the available memory as possible.

 

yes its caching that much because its allowed to, it doesn't mean it needs that much to perform well, but i don't know how many users he has,

[D34d10ck]

I applied the new rollup and it hosed my BESExpress server. I had to remove it for my blackberry users to recieve mail.

[Arthur]

Microsoft withdrew RU3 over two weeks ago due to an issue with BlackBerry's, so this shouldn't come as a surprise.

 

http://blogs.technet.com/b/exchange/archive/2011/03/14/exchange-2010-sp1-rollup-3-and-blackberrys-sending-duplicate-messages.aspx

[SYNACK]

I applied the new rollup and it hosed my BESExpress server. I had to remove it for my blackberry users to recieve mail.

 

BES is a horror show anyway, I would rather cut my own arm off with a plastic spoon than install or support another one, I am pretty sure that BES users still can't use Exchange 2010 SP1 reliably with calanders yet.

[chrisbrown]

BES is a horror show anyway, I would rather cut my own arm off with a plastic spoon than install or support another one, I am pretty sure that BES users still can't use Exchange 2010 SP1 reliably with calanders yet.

I can endorse this. I've spent over 18 hours on the phone with RIM regarding this...

[RabbieBurns]

Im having to run BES for 2 bloody users!!

[Arthur]

Update Rollup 3 has now been re-released.

 

http://blogs.technet.com/b/exchange/archive/2011/04/06/announcing-the-re-release-of-exchange-2010-service-pack-1-update-rollup-3-v2.aspx

 

Announcing the Re-release of Exchange 2010 Service Pack 1 Update Rollup 3 (V3)

On March 14th we posted an announcement to the EHLO blog about removing Update Rollup 3 for Exchange Server 2010 SP1 due to an issue related to Blackberry devices.

 

The Exchange Servicing team has fixed the reported issue with E2010 SP1 RU3 and is making available a new version of RU3 for our customers, version 14.01.289.007, (KB2529939). We strongly advise all customers install this newly released version of Microsoft Exchange Server 2010 SP1 Update Rollup 3 and to discard any prior version of RU3 (KB2492690) which you may have.

 

RU3 Installation Guidance:

 

• Customers with RU3 already installed within your Exchange environment
  It is not necessary for you to uninstall the existing RU3 within your environment. The new RU3 package can be installed over the top of the existing package installed on your servers.
   
   
  
• Customers with previous SP1 RUs installed within your Exchange environment
  You can simply install the new version of the RU3 package.
  

General RU Installation Guidance

 

Note for deployments that leverage Forefront Security for Exchange: For those of you running Forefront Security for Exchange perform these important steps from the command line in the Forefront directory before and after this rollup's installation. Without these steps, Exchange services for Information Store and Transport will not start back up. You will need to disable Forefront via "fscutility /disable" before installing the patch and then re-enable after the patch by running "fscutility /enable" to start it up again post installation.

We deeply regret the impact that these issues have had on you, our customers, and as always, we continue to identify ways to better serve your needs through our regular servicing releases.

[oxide54]

only installed rollup 2 today.

 

any reports on rollup 3 yet? my exchange servers work 'd like to keep it that way

[cromero]

Thank you .. after 8hrs of looking for a solution, I did what you suggested and it fixed the issue I had in OWA, EMC and EMS. Funny that disabling the redirect in IIS was not good enough.

 

I encountered the same issue and we found that a circular redirect had been populated into the web.config file on the Exchange Install Directory, ClientAccess, OWA

 

I removed the follwoing lines from the web.config

 

After resetting the IIS services on the server we are no longer seeing the OWA errors. We did not have this issue prior to the application of SP1.