Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

OWA Error after SP3 upgrade - The custom error module does not recognize this error.

Posted on 2014-10-08
9
Medium Priority
?
3,293 Views
Last Modified: 2014-10-08
I upgrade Exchane 2007 to SP3 and it went without errors.
However on using OWA I get an error.

https://mailserver.domain.co.uk/owa/auth/owaauth.dll

The custom error module does not recognize this error.

This error appears regardless of a correct username/password combination.

OWAApppool show net 2.0.50727.
owaauth.dll version is 8.3.83.0

Any help appreciated

Thank you
0
Comment
Question by:Majicthise
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 3
9 Comments
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 40367822
Did you install the latest rollup after installing the service pack?
If not, go and do that to begin with.

Simon.
0
 

Author Comment

by:Majicthise
ID: 40367835
No, wanted to make sure everything worked before I went ahead and did anything else.
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 40367849
I would patch it to begin with. SP3 on its own is very old. Bring the server fully up to date.

Simon.
0
Survive A High-Traffic Event with Percona

Your application or website rely on your database to deliver information about products and services to your customers. You can’t afford to have your database lose performance, lose availability or become unresponsive – even for just a few minutes.

 

Author Comment

by:Majicthise
ID: 40367862
OK. Well we'll see how it goes...
0
 

Author Comment

by:Majicthise
ID: 40367877
Problem has not gone away after Rollup 14.
0
 

Author Comment

by:Majicthise
ID: 40367878
owaauth.dll version now 8.3.377.0
0
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 2000 total points
ID: 40367883
Have you seen this TechNet forum thread?
http://social.technet.microsoft.com/Forums/office/en-US/94c812b5-4bd5-41eb-8396-462e03295201/exchange-2007and-iis7?forum=exchangesvrclientslegacy

Don't want to go over old ground if you have.

Is there anything else on the server that could have changed the netframework configuration?

Simon.
0
 

Author Comment

by:Majicthise
ID: 40367908
There's nothing thats changed other than the SP£ upgrade and rollup.

I saw that link but the instructions aren't clear.
I found the same problems as the OP.
Menu options suggested weren't listed etc.

However if I select basic settings for the web site the pysical path is correct
There is a button to test settings

Which throws an error

The server is configured to use pass-through authentication with a built-in account to access the specified physical path. However, IIS Manager cannot verify whether the built-in account has access. Make sure that the application pool identity has Read access to the physical path. If this server is joined to a domain, and the application pool identity is NetworkService or LocalSystem, verify that <domain>\<computer_name>$ has Read access to the physical path. Then test these settings again.

C:\Program Files\Microsoft\Exchange Server\ClientAccess\OWA has read access for authenticated users, and full permissions for system and administrators

Checking the logs I get an error

The Module DLL C:\Program Files\Microsoft\Exchange Server\ClientAccess\Owa\auth\exppw.dll failed to load.  The data is the error.

About to follow steps i nthis article

http://social.technet.microsoft.com/Forums/exchange/en-US/686d1a90-a016-4a4c-ae2e-6725914a5d5a/the-module-dll-cprogram-filesmicrosoftexchange-serverv14clientaccessowaauthexppwdll-failed?forum=exchangesvrsecuremessaginglegacy
0
 

Author Closing Comment

by:Majicthise
ID: 40368007
Quote

In the particular case of owaauth.dll failing to load, you need to do the same thing with the permissions of the folder '%Program Files%\Microsoft\Exchange Server\ClientAccess\Owa\auth'.

Quote

That was the issue.
Once I'd correctly added the traverse folders/execute files permission it worked like normal.

Odd bcasue the permissions are inherited and so I had to explcitly set them.
0

Featured Post

Office 365 Training for IT Pros

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

After hours on line I found a solution which pointed to the inherited Active Directory permissions . You have to give/allow permissions to the "Exchange trusted subsystem" for the user in the Active Directory...
Unified and professional email signatures help maintain a consistent company brand image to the outside world. This article shows how to create an email signature in Exchange Server 2010 using a transport rule and how to overcome native limitations …
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…

722 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question