• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1305
  • Last Modified:

HTTP 500 error when opening OWA

Ok, have 2008 server 64bit with exchange 2007 running on it. its been running fine.  I needed to install sql 2005 on it with reporting services.  so i enabled all the iis 6.0 stuff in the role manager, also need to  force IIS to use asp.net 2.0 32 bit. so i followed

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

but now OWA isn't working. pretty sure its related to asp.net.  just not sure how to start looking..

thanks

0
jasonmichel
Asked:
jasonmichel
  • 10
  • 9
1 Solution
 
sublimnl_Commented:
You could try changing back to the old version of ASP.net to verify.  I dont have a 2008 box in front of me, but on 2003 it was...

1) Go to IIS, select the domain.
2) Right click on domain and select properties.
3) Click on the tab ASP.NET.
4) In the field ASP.NET version, select the desired version.
5) Click on Apply to change the settings.
0
 
tboy6423Commented:
What is the full HTTP error?
0
 
jasonmichelAuthor Commented:
500 - Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed.


0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
jasonmichelAuthor Commented:
if i try to run from IIS 7.0  i get this

Server Error in Application "DEFAULT WEB SITE"Internet Information Services 7.0

Error Summary
HTTP Error 500.0 - Internal Server Error
Calling LoadLibraryEx on ISAPI filter "C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa\auth\owaauth.dll" failed Detailed Error InformationModule IIS Web Core
Notification Unknown
Handler StaticFile
Error Code 0x800700c1
Requested URL http://localhost:80/ 
Physical Path C:\inetpub\wwwroot
Logon Method Not yet determined
Logon User Not yet determined
 Most likely causes:
IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred.
IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly.
IIS was not able to process configuration for the Web site or application.
The authenticated user does not have permission to use this DLL.
The request is mapped to a managed handler but the .NET Extensibility Feature is not installed.
 Things you can try:
Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account.
Check the event logs to see if any additional information was logged.
Verify the permissions for the DLL.
Install the .NET Extensibility feature if the request is mapped to a managed handler.
Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
 Links and More InformationThis error means that there was a problem while processing the request. The request was received by the Web server, but during processing a fatal error occurred, causing the 500 error.
View more information »

Microsoft Knowledge Base Articles:

294807


0
 
tboy6423Commented:
That's a little better!  ... Can you check to make sure you are using .net framework version v2.0.50727(64-bit)
0
 
tboy6423Commented:
You should also check your ISAPI Filters specifically the bitness to find out what it is set to run:
CSCRIPT %SYSTEMDRIVE%\Inetpub\AdminScripts\adsutil.vbs GET W3SVC/AppPools/Enable32bitAppOnWin64
0
 
jasonmichelAuthor Commented:
i see the folder and i'm pretty sure i installed it..but like i said..i had to force it to use 32 bit so i could do 2005 reporting services.  

i followed http://support.microsoft.com/kb/894435 

0
 
tboy6423Commented:
hmmm ok check the bitness
0
 
jasonmichelAuthor Commented:
Microsoft (R) Windows Script Host Version 5.7
Copyright (C) Microsoft Corporation. All rights reserved.

Enable32bitAppOnWin64           : (BOOLEAN) True
0
 
tboy6423Commented:
ok run this:
cscript %SystemDrive%\inetpub\AdminScripts\adsutil.vbs set w3svc/AppPools/Enable32bitAppOnWin64 1
0
 
jasonmichelAuthor Commented:
same out put
0
 
tboy6423Commented:
Did you restart IIS?
0
 
jasonmichelAuthor Commented:
yes
0
 
jasonmichelAuthor Commented:
is there a way to undo what i had to do to get 32bit to work?  do you think that is the issue
0
 
tboy6423Commented:
ok try:
cscript %SystemDrive%\inetpub\AdminScripts\adsutil.vbs set w3svc/AppPools/Enable32bitAppOnWin64 0
0
 
tboy6423Commented:
It is an issue because of a misconfigured  64bit ISAPI DLL, now I am pretty sure that you it is the bitness, it's just a matter of which one to set it to. I know there is a MS KB doc on which one to set it to, but I am not able to remember which one..sorry
0
 
jasonmichelAuthor Commented:
yeah that got owa working again..so i guess i won't be able to run 32bit with exchange running
0
 
tboy6423Commented:
yeah you have to use either 32-bit or 64-bit you just can't run both modes at the same time...hence the reason OWA stopped working on you.
0
 
jasonmichelAuthor Commented:
that sucks...thanks for the help tho
0
 
tboy6423Commented:
Your welcome, I wish there was a better way...you could call Microsoft...
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 10
  • 9
Tackle projects and never again get stuck behind a technical roadblock.
Join Now