?
Solved

HTTP Error 500.19 - Internal Server Error Calling LoadLibraryEx on ISAPI filter "C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa\auth\owaauth.dll" failed

Posted on 2013-01-23
10
Medium Priority
?
2,557 Views
Last Modified: 2013-08-25
We have Exchange Server 2007 that is running on Windows Small Business Server 2008; our owa stopped working and when you try to access it you get this error "HTTP Error 500.19 - Internal Server Error
Calling LoadLibraryEx on ISAPI filter "C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa\auth\owaauth.dll" failed"
I have run this command
cscript.exe adsutil.vbs set W3SVC/AppPools/Enable32BitAppOnWin64 true"
but the issue still occurs.
0
Comment
Question by:xpandit
[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
  • 4
10 Comments
 
LVL 29

Expert Comment

by:becraig
ID: 38810915
Take a look at this link:

http://support.microsoft.com/kb/2619202

Solution listed as:
Use the following steps to resolve the issue:

1.  Open Control Panel

2.  Open the System Icon

3.  Click Advanced System Settings

4.  Click the Environment Variables button

5.  In the Sysem Variables section, edit the variable for Path

On Small Business Server 2011 append the path variable with C:\Program Files\Microsoft\Exchange Server\V14\Bin\

On Small Business Server 2008 append the path variable with C:\Program Files\Microsoft\Exchange Server\Bin\

6.  Restart the Windows Small Business Server
0
 

Author Comment

by:xpandit
ID: 38813222
Hi becraig thanks for the response;I've done those steps but even after reboot its still the same; the eventvwr is showing the following errors. Thanks,
2268.PNG
2274.PNG
0
 
LVL 29

Expert Comment

by:becraig
ID: 38813908
Please check the following:

    Go to %windir%\system32\inetsrv\config\applicationhost.config
    Under <Filters> find the OWA ISAPI filter

Can you copy the information there for owa and let me know:
<filter name="Exchange OWA Cookie Authentication ISAPI Filter" path="C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa\auth\owaauth.dll" enabled="true" preCondition="bitnessxx" />
0
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.

 

Author Comment

by:xpandit
ID: 38818150
<filter name="Exchange OWA Cookie Authentication ISAPI Filter" path="C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa\auth\owaauth.dll" enabled="true" preCondition="bitness64" />
0
 
LVL 29

Expert Comment

by:becraig
ID: 38818283
You need to change the bitness to 32 since you are launching on an x86 machine.

That should resolve your problem.
0
 

Author Comment

by:xpandit
ID: 38818287
Hi becraig; thanks for your response.  The server is a x64 bit machine.
0
 
LVL 29

Expert Comment

by:becraig
ID: 38818595
Sorry I don't know where I ended up with that I was between two conversations and posted too soon.

Here are the values that should exist for OWA to work:
In the file %windir%\system32\inetsrv\config\applicationhost.config:

     change the line
    <filter name="Exchange OWA Cookie Authentication ISAPI Filter"
    path="C:\Exchange\ClientAccess\owa\auth\owaauth.dll" enabled="true"  />

    to the following
    <filter name="Exchange OWA Cookie Authentication ISAPI Filter"
    path="C:\Exchange\ClientAccess\owa\auth\owaauth.dll" enabled="true" preCondition="bitness64" />
    change the line
    <filter name="Exchange ActiveSync ISAPI Filter"
    path="C:\Exchange\ClientAccess\sync\bin\AirFilter.dll" enabled="true"   />

    to the following
    <filter name="Exchange ActiveSync ISAPI Filter"
    path="C:\Exchange\ClientAccess\sync\bin\AirFilter.dll" enabled="true"
    preCondition="bitness64" />
    change the line
    <add name="exppw"
    image="C:\Program Files\Microsoft\Exchange Server\ClientAccess\Owa\auth\exppw.dll"  />

    to the following
    <add name="exppw"
    image="C:\Program Files\Microsoft\Exchange Server\ClientAccess\Owa\auth\exppw.dll"
    preCondition="bitness64" />
    change the line
    <add name="kerbauth"
    image="C:\Program Files\Microsoft\Exchange Server\V14\Bin\kerbauth.dll"  />

    to the following
    <add name="kerbauth"
    image="C:\Program Files\Microsoft\Exchange Server\V14\Bin\kerbauth.dll"
    preCondition="bitness64" />
    change the line
    <add name="exppw" />

    to the following
    <add name="exppw" preCondition="bitness64" />
0
 

Author Comment

by:xpandit
ID: 38834939
Hi becraig, I didn't need to change anything as the current settings are identical to the ones you are suggesting.
0
 

Accepted Solution

by:
xpandit earned 0 total points
ID: 39132345
this issue was resolved by reinstalling IIS
0
 

Author Closing Comment

by:xpandit
ID: 39436815
this issue was resolved by reinstalling IIS
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

If you troubleshoot Outlook for clients, you may want to know a bit more about the OST file before doing your next job. IMAP can cause a lot of drama if removed in the accounts without backing up.
There are times when we need to generate a report on the inbox rules, where users have set up forwarding externally in their mailbox. In this article, I will be sharing a script I wrote to generate the report in CSV format.
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…

719 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