Wanted: Network Administrators

See great job listings on the jobs Page

OWA and HTTP/1.1 500 Internal Server Error

I have read over other threads with no luck in resolving the issue I am seeing. I have an SBS 2003 server running Exchange 2003 SP2 with roughly 20 users. Recently I noticed that one user can not use his email on his iPhone. I have checked with other iPhones,
it's not the phone. He can sometimes use OWA via a web browser, but then other times receives the HTTP/1.1 500 Internal Server Error. He has never been able to get the account to retrieve email on his iPhone. It has to be a server issue. I detached the account
from the mailbox and reattached it, completely deleted his account and mailbox reinstalled it and still no luck. I have restarted IIS, restarted the Exchange System Attendant, restarted the server completely and a few other steps I can't remember right now.
Long story short, I have done everything I can think of and need some help. Every other user is fine, it's just this user. Yes the setting are correct on the iPhone (You can verify the account information, its just when you go to check the mail the "Cannot
Get Mail Connection to Server Failed Error". PLEASE HELP!

Need to support users over the internet? click here try our remote control online beta






June 6th, 2012 10:02pm
The '500 internal server error' message is one of the least helpful you'll encounter - it just means 'oops, something broke at the server end'. If it is something that IIS can figure out, it will give some more details when you are using OWA.
More usually, you will need to check the Event Logs, and see if something is logged there at the time the user encounters the problem - even then, you will not always find anything more specific to help you get started.Mobile OWA For Smartphone

www.leederbyshire.com

email a@t leederbyshire d.0.t c.0.m

There is an amazing pack of free network admin tools. click here to download it






June 7th, 2012 5:39am
The '500 internal server error' message is one of the least helpful you'll encounter - it just means 'oops, something broke at the server end'. If it is something that IIS can figure out, it will give some more details when you are using OWA.
More usually, you will need to check the Event Logs, and see if something is logged there at the time the user encounters the problem - even then, you will not always find anything more specific to help you get started.Mobile OWA For Smartphone

www.leederbyshire.com

email a@t leederbyshire d.0.t c.0.m

There is an amazing pack of free network admin tools. click here to download it






June 7th, 2012 5:41am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics