RE: OWA HTTP 500 Error for some users
- From: v-innjin@xxxxxxxxxxxxxxxxxxxx ("Inn Jin [MSFT]")
- Date: Thu, 11 Jan 2007 08:40:21 GMT
Hi EdMena,
Thank you for posting.
From the description, I understand this issue is that when some user browseOWA, they get HTTP 500 Error. If I am off base, please don't hesitate to
let me know.
Base on my experience, it's a common issue, and can be caused by many
factors. Let's follow the steps below to troubleshoot this issue:
Step One:
================
Please refer to the following KB and check whether the issue persists?
Known issues that cause the "HTTP 500 internal server error" error message
in Exchange Server 2003 Outlook Web Access
http://support.microsoft.com/kb/894965/en-us
Step Two
================
Verify whether the user is only allowed to logon from certain workstations.
To do so:
a. Click start -> administrative tools -> Active Directory Users and
Computers
b. Locate to the yourdomain.local -> MyBusiness -> Users -> SBSUsers, and
double-click the problematic users.
c. Click the Account Tab, click Log On To¡. , make sure All Computers are
selected.
d. Test the issue.
Step Three:
================
On the SBS 2003 server, open ''Internet Information Services (IIS)
Manager'' in ''Administrative Tools''. Expand <Server Name>\''Application
Pools''. Can you see ''ExchangeApplicationPool'' in the tree view? If the
application pool is missing, please try the following steps to rebuild the
ExchagneApplicationPool:
a. In Internet Services Manager, expand your server and then expand
Application Pools.
b. Right-click Application Pools, point to New and select Application Pool.
c. Name the application pool "ExchangeApplicationPool" and click OK.
d. Right-click ExchangeApplicationPool and select Properties.
e. Uncheck "Recycle worker processes" on the Recycling tab.
f. On the Performance tab, uncheck "Shutdown worker processes after being
idle for".
g. On the Identity tab, set the Application Pool Identity to Local System
and click OK.
h. Right-click Application Pools, point to New and select Application Pool.
i. Name the application pool "ExchangeMobileBrowseApplicationPool" and
click OK.
j. Right-click ExchangeMobileBrowseApplicationPool and select Properties.
k. Uncheck "Recycle worker processes" on the Recycling tab.
l. On the Performance tab, uncheck "Shutdown worker processes after being
idle for".
m. On the Identity tab, verify that the Application Pool Identity is set to
Network Service and click OK.
If you can see the ExchangeApplicationPool or you rebuild it with the above
steps, please go to check the Application Pool settings in the default web
site, then check the issue. I would like to suggest you refer to the
following KB article for the detailed steps:
829167 "HTTP 500 - Internal Server Error" Error Message When You Use
Outlook Web Access to Connect to Your Microsoft Exchange Server 2003 Mailbox
http://support.microsoft.com/?id=829167
Step Four
======================
On the server box, delete all files in ''%systemroot%\TEMP'' folder and
''%systemroot%\IIS Temporary Compresses Files'' folder. Test the OWA site
again.
Step Five
======================
Create a new HTTP virtual server on the SBS 2003 server box.
a. Open "Exchange System Manager", navigate to "Servers"\<Server
Name>\"Protocols"\
b. Right-click "HTTP"-->"New"-->"HTTP Virtual Server".
c. In the new http virtual server properties, input the new VS name such as
"TESTOWA", click "Advanced" button, and modify the host name of the
identity (This is very important since we need to use different host header
to identify the different web requests to the OWA sites. You can add the
host header with ''TESTOWA'' here). Click "OK" to close the dialog box.
d. In the new virtual server properties, select "Mailboxes for SMTP
domain", click "Modify" button to select the served SMTP domain name. Click
"OK" to finish the creating.
e. Right-click the newly created virtual server, click "New"-->"Virtual
Directory". In the VD properties, input the name "Exchange", select
"Mailboxes for SMTP domain". Click "Modify" to select the served domain.
Click "OK" to close the dialog box. Right-click the virtual server again
and also create a new virtual directory named "Public" for the "Public
folder".
f. Open "Internet Information Service (IIS) Manager" console, you will find
the new web sites in "web sites" folder. Click ''Start''-->''Run''-->Type
''iisreset'' (without the quotation marks) and press Enter.
g. Go to a workstation, open ''hosts'' file located in
%systemroot%\system32\drivers\etc\ folder by using Notepad program. Add the
following entry:
<IP address of the SBS box> TESTOWA
h. Save the hosts file and close the notepad program. On this workstation,
try to access the OWA site http://TESTOWA/exchange/ Does the same error
occur?
Step Six
=============
If the issue persists, please kindly gather the following information:
1. How many users in your domain?
2. Did the issue happened suddenly or after some change?
3. Open Internet Explorer, click ''Tools''-->''Internet Options''. In the
option window, click ''Advanced'' tab. Under ''Browsing'', click to clear
''Show friendly HTTP error messages''. Click ''OK'' and restart the
Internet Explorer. Try to access the OWA site again. What's the error
message now? Please capture a screen-shoot, if you get a different error
message, then get a screenshot and send to my working mailbox
v-innjin@xxxxxxxxxxxxx
4. Please gather the IIS metabase and IIS log
IIS Metabase.
a. Download the IIS Resource Kit tools from the following page:
http://www.microsoft.com/downloads/details.aspx?FamilyId=56FC92EE-A71A-4C73-
B628-ADE629C89499&displaylang=en
b. Install it, run MBExplorer (Metabase Explorer)
c. Right click the "LM" node and choose "Export to file".
d. Specify a file name, specify the password and finish the export.
e. Send the file and the password to me
IIS log:
a. On Exchange Serves, open IIS MMC, right click Default Web Site and then
click Properties.
b. Click Website tab and then check Enable logging.
c. Stop the Default Website and RENAME the existing IIS log files under
C:\WINDOWS\system32\LogFiles\W3SVC1.
d. Restart the Default Website and reproduce the problem, which will
generate new IIS log file with the exact error.
e. Go to the following folder on Exchange Server:
C:\WINDOWS\system32\LogFiles\W3SVC1.
f. Send me the log files to my working email address v-innjin@xxxxxxxxxxxxxx
5. Download and run the setup MPS report tool On the SBS 2003 server
a. Visit
http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd9
15706/MPSRPT_Exchange.EXE to download the file.
b. Run the MPSRPT_Exchange.EXE on the server box.
c. Wait for 10~15 minutes.
d. Open Windows explorer, navigate to %SYSTEMROOT%\MPSReports\Exchange\cab
e. Send the .cab file directly to me at v-innjin@xxxxxxxxxxxxx
I appreciate your time. I am happy to be of assistance to you and look
forward to your reply.
Have a nice day!
Best regards,
Inn Jin (MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
.
- Follow-Ups:
- RE: OWA HTTP 500 Error for some users
- From: "Inn Jin [MSFT]"
- RE: OWA HTTP 500 Error for some users
- Prev by Date: Re: Event 529 Logins from external source
- Next by Date: RE: Web Proxy for quantitive surfing time analysis
- Previous by thread: RE: Roaming Profiles
- Next by thread: RE: OWA HTTP 500 Error for some users
- Index(es):