OWA fails (500 internal server error)

Check the solution and see if it applies to you.

https://www.experts-exchange.com/questions/27473256/IIS-Exchange-2010-Problems.html

Regards,
Exchange_Geek

We did review this earlier, and verified that things are set to 64bit. Is there a way I can verify this?

<applicationPoolDefaults> this is what you see in the log file applicationHost.config?

Regards,
Exchange_Geek

Is IIS and WWW services running on the machine ??

- Rancy

Also seeing these errors in the event log every few seconds.
1st:
The HTTP Filter DLL C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa\auth\owaauth.dll failed to load.  The data is the error.

Followed by:
Could not load all ISAPI filters for site 'SBS WEB APPLICATIONS'.  Therefore site startup aborted.

Yes Rancy they are.

Are those errors 2214 and 2268?

Regards,
Exchange_Geek

yes they are.

https://www.experts-exchange.com/questions/26168262/SBS2008-HTTP-Error-500-0-Internal-Server-Error-Calling-LoadLibraryEx-on-ISAPI-filter-owaauth-dll-failed.html

http://www.msexchange.org/tutorials/OWA2003Forms-based-Authentication-default-domain.html

- Rancy

I'm seeing this in the config

<applicationPoolDefaults enable32BitAppOnWin64="false">

http://social.technet.microsoft.com/forums/en-US/exchangesvrclients/thread/94c812b5-4bd5-41eb-8396-462e03295201/

http://social.technet.microsoft.com/Forums/en-US/exchangesvrclients/thread/0b9d2ed2-b27b-41bc-8428-36f9957d89fe/

I am possibly boring you, but I am trying my best to research through what seems to be a tough issue.

hope the above articles, ones posted by Rancy and mine help you.

Regards,
Exchange_Geek

Replace the entry <applicationPoolDefaults enable32BitAppOnWin64="false"> with the following <applicationPoolDefaults>

Once done perform iisreset OR reboot your box once.

Regards,
Exchange_Geek

unfortunately the same thing. Here is an clip of what I see.

     </recycling>
            </add>
            <add name="ASP.NET v4.0" managedRuntimeVersion="v4.0" />
            <add name="ASP.NET v4.0 Classic" managedRuntimeVersion="v4.0" managedPipelineMode="Classic" />
                  <applicationPoolDefaults>
                <processModel identityType="NetworkService" />
            </applicationPoolDefaults>
        </applicationPools>

        <!--

Can the box be rebooted OR was IISReset attempted?

Regards,
Exchange_Geek

I can reboot the box, and I have reset IIS a good bit. I did add the IIS Users to the 2 files mentioned in the web address concerning the 2 config files.

What is the Exchange version and RU ?? DId you try to upgrade the server for some application ....
https://www.experts-exchange.com/questions/26168262/SBS2008-HTTP-Error-500-0-Internal-Server-Error-Calling-LoadLibraryEx-on-ISAPI-filter-owaauth-dll-failed.html

- Rancy

Work on this solution

ASP.NET 2.0, 64-bit version

To run the 64-bit version of ASP.NET 2.0, follow these steps:
Click Start, click Run, type cmd, and then click OK.
Type the following command to disable the 32-bit mode:
cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 0

Type the following command to install the version of ASP.NET 2.0 and to install the script maps at the IIS root and under:

%SYSTEMROOT%\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe -i
Make sure that the status of ASP.NET version 2.0.50727 is set to Allowed in the Web service extension list in Internet Information Services Manager.

Regards,
Exchange_Geek

I also noticed that the OWA virtual directory I created earlier went under Default WebSite instead of SBS Web Applications.

This is the command I ran.
new-OwaVirtualDirectory -OwaVersion "Exchange2007" -name "owa (SBS WEB APPLIC
ATIONS)"

Are Exchange virtual directories under Default Web Site or SBS Web Applications?

Also, did you run the commands i posted earlier?

Regards,
Exchange_Geek

This will surely put the Website under the Root .....

- Rancy

The exadmin, exchange and exchweb and remote are all under SBS Web Applications. OWA is under Default Web Site

OWA should have been under SBS Web Applications too. Wouldn't make sense to have it under different website.

Remove owa virtual directory and confirm if it is removed under IIS and then recreate it under sbs web applications.

Regards,
Exchange_Geek

I tried again to recreate the virtual directory. And if you look at the last line after it create it. It is showing it moves it to the Default Web Site. Even though in the command I specified "SBS Web Applications)


PS>new-OwaVirtualDirectory -OwaVersion "Exchange2007" -name "owa (sbs web applic
ations)"

Name                       Server                     OwaVersion
----                       ------                     ----------
owa (Default Web Site)     JCCSBS                     Exchange2007


PS>

Thats just the Name you are giving to the OWA Virtual directory not its location so by default its created under Default Web Site.

- Rancy

Remove the above mentioned Virtual directory and try this

New-OWAVirtualDirectory -WebsiteName "SBS Web Applications" -OwaVersion "Exchange2007" -ExternalAuthenticationMethods Fba

Regards,
Exchange_Geek

Ok, running that command did put the OWA directory under the SBS Web Applications. Thank you.

Still get the 500 error. I attempted to run the ASP commands, but it says it can't find cscript.

Again, thank you guys for your help. I appreciate you sticking with this and your thoughts.

Search for cscript.exe on your machine and run it from the command prompt from that particular location.

Regards,
Exchange_Geek

Ok, I did find it, and ran those commands. I also verified Allowed was set. Then performed an IISReset with no different outcome.

I get a error 500 when hitting the https://remote.jcc-ri.com/owa

Restart the server.

- Rancy

Is the following steps taken care of???

.    Please try to make sure that the status of ASP.NET version 2.0.50727 is set to Allowed in the
“Web service extension” list in IIS manager.
3.    Please verify the path to asp.net is correct. Right click on Default Web Site and then properties. The location should look like:
"C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\aspnet_filter.dll"
4.    Please check the permissions on the owaauth.dll and AirFilter.dll, it should be like below:
 
Administrators - Full Control
Authenticated User - Read & Execute/Read
System - Full Control
 
5.    Please try to add these dlls into ISAPI filter, if you have another CAS, then I recommend you to copy these files there and then past to the problematic CAS.

Regards,
Exchange_Geek

Also check if you are facing an issue opening EMC
http://support.microsoft.com/kb/2619202

Hope the above article may solve the issue.

Regards,
Exchange_Geek

would you believe when I do a search I do not find either DLL?

I did check the ASP, and the directory looks correct. See the attached.
ASP.jpg

The variable "path" was empty. I added what the site recommended and I'm restarting.

Added this:  C:\Program Files\Microsoft\Exchange Server\Bin\

Hope you havnt tried or upgraded your .NET ?

- Rancy

No updates were installed when we experienced this issue. Last update installed were over a week ago, and the server was restarted after the installs. I would have to check to see if any .net updates installed. When this started yesterday it was strictly a reboot.

bes to check so that if that has happened we can check that ...... Do you have Automatic updates enabled on the Exchange server :(

- Rancy

No automatic updates is not setup. We install them manually.

OK, server is backup. Some good news first. The Intranet site is up and working! :o) They rely heavily on that, so that is great.

OWA is still not working after all the changes.

Whats the error for owa? Can you open it using https://localhost/owa OR https://servername/owa?

Regards.
Exchange_Geek

This is the error I get when I try both addresses. Since I couldn't find that owaauth.dll is there a way to recreate it? Or is it hidden and that is why a search doesn't see it?

HTTP Error 500.0 - Internal Server Error

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

which SP version OR Roll up update you have installed of Exchange?

Regards,
Exchange_Geek

owaauth.dll does have the IIS_Users permissions

Exchange is showing..
Exchange Server 2007

Microsoft Corporation

Version: 08.01.0340.000

Verify the Roll up for Exchange using Add/Remove Programs OR Programs and Features - and see if you can re-apply the same Rollup again.

Regards,
Exchange_Geek

From what I am seeing with this Version number, it could still be sitting at the initial install of exchange with no SP's. Do you agree? There is 8.1, 8.2 and 8.3 for each service pack. I would hate to try and upgrade to a bunch of SP's and break the operation of exchange.

As mentioned earlier, your roll ups would be mentioned in the add/remove programs.

Regards,
Exchange_Geek

This is the only update I am seeing installed in 2010

Update Rollup 6 for EXchange Server 2007 Service Pack 1 (KB959241)
Installed On: 3/8/2010

Can you re-apply it and keep fingers crossed?

Regards,
Exchange_Geek

it's a possibility, I'm just waiting to hear back from some members of my team on their thoughts.

Ok do post back for us to understand and help you further.

Regards,
Exchange_Geek

Hello,

Could you check this rticle http://learn.iis.net/page.aspx/267/how-to-use-http-detailed-errors-in-iis-70/

Please check the Figure 3 and the notes # 1 and # 2 for the over-ride settings and the Table description.

I think if you use the over-ride settings you will get the information you need?

Last night around 12:45am we opened a case with Microsoft. We need to have this issue fixed before Business starts for the client tomorrow. So far, no fix.

I'm afraid they might ask you to re-install IIS and Exchange from scratch.

Regards,
Exchange_Geek

Yeah i too .... not sure if the IIS is corrupted .... hope they tried to check the metabase of IIS.

- Rancy

Hey guys, yes we finally were able to resolve the issue by installing Roll Up 10 to exchange. there was an issue with the files physically being there, but unable to be read. So we were able to get fixed up yesterday morning. Thank you again for your guys suggestions and assistance.

Exchange_Geek was very helpful and responsive. We are very appreciative of the assistance.