Exchange Server Forums
Forums |
Register |
Login |
My Profile |
Inbox |
RSS 
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
[URGENT] 500 - Internal server error
|
Users viewing this topic:
none
|
Logged in as: Guest
|
Login  | |
|
 Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM
|
|
TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!
|
[URGENT] 500 - Internal server error - 21.Jan.2008 7:34:23 PM
|
|
|
user001
Posts: 170
Joined: 2.Jun.2007
Status: offline
|
Hello everybody and thanks for advance for your help,
We have got a architecture frontal (owa) and dorsal (mailboxes) cluster.
The frontal is a Win 2k3 Enterprise SP2 and when we connect internal or external with OWA we've got the error 500 - Internal server error.
Thanks for advance
|
|
|
|
|
RE: [URGENT] 500 - Internal server error - 22.Jan.2008 9:44:07 AM
|
|
|
tcaud
Posts: 119
Joined: 17.Sep.2004
From: Alabama
Status: offline
|
There are a LARGE number of things that can cause this problem. Be patient, methodical and thorough and you will eventually locate the problem.
Essentially, in the front-end(frontal)/back-end (dorsal) setup, OWA runs on two separate IIS webservers. The frontal proxies the information from the dorsal. Keep in mind that you might have to look at both of them.
The 500 error, just it occur when you first browse to the webpage on the front-end? If so, then check the user account that is running the web processes (locked out?) Check the Application Pools to see if they are started and that the Exchange parts of the website are in the correct App pool. All of the OWA related sites should be running in the ExchangeApplicationPool. Are you missing some of the parts of the OWA web? See this article for how to "reset" it http://www.msexchange.org/tutorials/Fixing-Damaged-Incorrectly-Configured-OWA-2003-Installation.html Check the IISsettings: http://www.msexchange.org/tutorials/Resetting-OWA-Folder-IIS-security-permissions-Exchange-2003.html
Do you get presented the login page and then receive the 500 error after you attempt to login? If so, then your problem most likely exists on the back-end of the servers. Try going to the website on the back-end. Internally, you can visit http://servername/exchange and (if Integrated Windows Authentication is enable) you should be presented with your OWA mailbox. If you get errors here, then it is most liekly the culprit. Check the same items as above.
Good luck.
_____________________________
Tony Caudill
MCSE, MCSA
|
|
|
|
|
RE: [URGENT] 500 - Internal server error - 22.Jan.2008 9:09:40 PM
|
|
|
user001
Posts: 170
Joined: 2.Jun.2007
Status: offline
|
Thanks for your answer tcaud,
Hello, I got presented the login page of OWA (Exchange 2003) of my back-end and I receive the 500 error after my login. I think that I've got a trouble with IIS, in this windows (it's a example, not my real case) :http://www.developer.com/img/articles/2003/08/18/IIS6P33.gif In my properties are enabled : Enable anonymous access, Basic Authentication and Integrated Windows Authentication. What is the risk if I uncheck Integrated Windows Authentication? What is the function of it? Thanks for advance
|
|
|
|
|
RE: [URGENT] 500 - Internal server error - 23.Jan.2008 7:18:28 AM
|
|
|
tcaud
Posts: 119
Joined: 17.Sep.2004
From: Alabama
Status: offline
|
Integrated Windows Authentication is supposed to be enabled on the back-end. It is my understanding that the Front-end accepts your credentials, verifies them with the responsible server and then impersonates you when accessing the back-end similar to a proxy. If Integrated Windows Authentication is disbled, it could prevent you from being able to access your mailbox through OWA.
You stated previously that the back-end is a cluster. Take a look at this article and see if it applies to you: http://support.microsoft.com/kb/841561/en-us
Otherwise, make sure that, on the back-end, check the user account (probably IUSR_servername) that is running the web processes; is it locked out? Is it disabled? Check the Application Pools to see if they are started and that the Exchange parts of the website are in the correct App pool. All of the OWA related sites should be running in the ExchangeApplicationPool.
On the back-end cluster, make sure that the System Attendant service is running. You may have to restart it.
Do your event logs show any errors or warnings that may help pinpoint the problem?
_____________________________
Tony Caudill
MCSE, MCSA
|
|
|
|
|
RE: [URGENT] 500 - Internal server error - 29.Jan.2008 10:42:35 AM
|
|
|
user001
Posts: 170
Joined: 2.Jun.2007
Status: offline
|
quote:
If Integrated Windows Authentication is disbled
I must to enable this option on front-end or back-end server?
In IIS, this option must be enabled on "Default Website" or on a specific folder (Exchange, ...)?
quote:
on the back-end, check the user account (probably IUSR_servername) that is running the web processes; is it locked out? Is it disabled?
How I can to check it, I don't understand you.
I don't have specific events about it.
|
|
|
|
|
RE: [URGENT] 500 - Internal server error - 29.Jan.2008 11:23:12 AM
|
|
|
user001
Posts: 170
Joined: 2.Jun.2007
Status: offline
|
I looked in the back-end server in the event viewer the day which it was crashing and I saw a interesting event :
Event ID: 9152
Source: MSExhcnageSA
Type:Error
Category: General
Desc: Microsoft Exchange System Attendant reported an error '0xc1034a70' in its DS Monitoring thread.
|
|
|
|
|
RE: [URGENT] 500 - Internal server error - 29.Jan.2008 12:01:02 PM
|
|
|
tcaud
Posts: 119
Joined: 17.Sep.2004
From: Alabama
Status: offline
|
quote:
Integrated Windows Authentication is supposed to be enabled on the back-end. Some of the parts of the OWA website on the back-end also must be allowed to be viewed anonymously.
All IIS processes use an account on your copmputer to access pages anonymously - if anonymous viewing is enabled. This account is typically called IUSR_computername If the account gets locked out (bad password attempts - because IIS and the system will try to routinely change the account password) or disabled on the machine then the IIS processes cannot serve up the web page when viewing anonymously. You find out which account is being used by looking at the web site properties.
As far as your latest Event Viewer entry is concerned, it appears to be something that you can safely ignore. See http://support.microsoft.com/kb/287610/en-us for more information.
_____________________________
Tony Caudill
MCSE, MCSA
|
|
|
|
|
RE: [URGENT] 500 - Internal server error - 29.Jan.2008 12:26:34 PM
|
|
|
user001
Posts: 170
Joined: 2.Jun.2007
Status: offline
|
Only the problem occur when we restart the server.
Front-End (Default Website) :
Anonyme Access : Enabled (IUSR_USER0001)
Integrated Windows Authentication : Enabled
Basic Authentication : Enabled
Domain : empty
Note : This account IUSR_USER0001 is a local account, this machine is in the DMZ.
Back-End (Default Website) :
Anonyme Access : Disabled
Integrated Windows Authentication : Enabled
Basic Authentication : Enabled
Domain : My_domain
|
|
|
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
 Locked w/ New Messages |
 Locked w/o New Messages |
|
 Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
Printable Version
