Exchange Active Sync/OMA Problem... very frustrated...

Posted on 2008-11-12
Medium Priority
Last Modified: 2012-06-27
Hello all,  I'm new here so here goes...

I'm trying to enable active sync for my iPhone on Exchange 2003, SP2 stand alone server on Windows 2003 server.  Here is the error that I'm getting after trying a few things.  Seems like I'm really close... hopefully someone has seen this one before?

Unable to connect to your mailbox on server WINDOWS2003. Please try again later. If the problem persists contact your administrator.

When I look in Event Viewer here is what I'm seeing:

Event Type:      Error
Event Source:      MSExchangeOMA
Event Category:      (1000)
Event ID:      1805
Date:            11/13/2008
Time:            1:59:36 AM
User:            N/A
Computer:      WINDOWS2003
Request from user josh@Boddiford.com resulted in the Microsoft(R) Exchange back-end server WINDOWS2003 returning an HTTP error with status code 501

Content-Length: 0
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Date: Thu, 13 Nov 2008 06:59:35 GMT

Original Request:
Content-Type: text/xml
Depth: 0
Content-Length: 389
Expect: 100-continue
Host: windows2003

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Question by:Josh-Tampa
  • 2
LVL 12

Expert Comment

ID: 22947822

Here is what I have found on another site:

Anonymous (Last update 9/4/2007):
In our case, we were getting EventID 1776 from source Davex and EventID 1805 from source MSExchangeOMA. We were unable to activesync and browse OMA directory. We successfully ran the command regsvr32 msxml3.dll, and we were able to activesync.

Jim Gleason (Last update 7/20/2006):
I had this issue and I needed to recreate the virtual directories. See M883380 for details.

Mihai Andrei (Last update 11/9/2005):
As per Microsoft: "This event indicates that the request made by the Outlook Mobile Access browse user was not successful because the back-end Exchange server returned an HTTP error code". See MSEX2KDB for additional information about this event.

This problem can occur if you have reached the storage limit for your mailbox. See M842023 for details.

Ionut Marin (Last update 2/26/2004):
See M817379 and M822177 to see why this occurs and how to fix it.  

and here are the links for the article above:





Author Comment

ID: 22949700
Thanks so much for the reply.

I tried all suggestions that you provided but it has not made a difference unfortunately.  It seems that I'm getting different HTTP error codes for OMA versus ActiveSync.  When I look in event viewer it's showing the 501 error for OMA but it's showing the following for ActiveSync.

Event Type:      Error
Event Source:      Server ActiveSync
Event Category:      None
Event ID:      3005
Date:            11/13/2008
Time:            9:03:12 AM
User:            BODDIFORD\josh
Computer:      WINDOWS2003
Unexpected Exchange mailbox Server error: Server: [windows2003.Boddiford.com] User: [Josh@Boddiford.com] HTTP status code: [400]. Verify that the Exchange mailbox Server is working correctly.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
LVL 12

Accepted Solution

florin_s earned 1500 total points
ID: 22949740
For this event here is what I have found out:

Jerry Haskins (Last update 8/3/2008):
I started getting this error and mobile phones would not sync anymore after adding alias IP addresses to the server. After removing the alias IP addresses the error went away and mobile phones could sync with the Exchange server again.

Anonymous (Last update 9/10/2007):
In my case, these errors started when I implemented the use of host headers on my IIS web sites. I have two web sites on the Exchange server and started using host headers to distinguish them. To fix the issue I created an identity with a blank host header on the site hosting Exchange.

Mihai Andrei (Last update 7/4/2007):
This issue may occur if one or more following conditions are true:

1. The authentication method is incorrect for the virtual directories that are used by Microsoft ActiveSync.
2. The application name points to an incorrect entry in the Outlook Mobile Access virtual directory.
3. The application name points to an incorrect entry in the Microsoft-Server-ActiveSync virtual directory.
4. An incorrect application pool is associated with the virtual directories that are used by ActiveSync.

See M937635 for information on solving this problem.

Christian Egger (Last update 5/15/2007):
The meaning of this error depends on the HTTP Status Code it contains. 507 could mean that the users Mailbox is over its quota, which can cause a problem for Active Sync to save information in a hidden mailbox folder.

Bill Olah (Last update 2/4/2007):
This issue can appear if the security settings on the Virtual Directories are altered. Verify that the following settings are enabled for the front-end and back-end servers.

Front-end Exchange Server:

Default Web Site:  Basic Authentication
ExAdmin: Integrated Authentication
Exchange:  Basic Authentication
ExchWeb:  Anonymous
Active Sync:  Basic Authentication
OMA:  Basic Authentication (note: Default domain must be \)
Public:  Basic Authentication.

Back-end Exchange Server:

Default Web Site:  Anonymous, Integrated Authentication
ExAdmin: Integrated Authentication
Exchange:  Integrated Authentication, Basic Authentication
ExchWeb:  Anonymous
Active Sync:  Basic Authentication
OMA:  Anonymous, Integrated Authentication
Public:  Anonymous, Integrated Authentication.

Francois Couture (Last update 11/22/2006):
This solved our problem:

1. Right click on the virtual directory and click properties
2. Uncheck "Enable anonymous access" in Authentification method
3. Synchronize your PPC.

David Fosbenner (Last update 11/22/2006):
I got this event every 15 minutes on my Exchange 2003 system. The source of the error was a user's smartphone which was configured to use ActiveSync to synchronize with the Exchange Server. The smartphone had the Exchange server name and user credentials, but was not synchronizing successfully.  We decided to prevent the smartphone from using ActiveSync to sync with the server, and that eliminated the 3005 errors. Instead, the smartphone syncs using IntelliSync which came bundled with it.

Anonymous (Last update 11/12/2006):
For the past week or so, I have upgraded my domain to Windows 2003 native. My DCs were all previous running Windows 2000. The exchange server was running 2003 exchange on a 2000 server operating system. I upgraded my system to 2003 all of them without a hitch. I then installed SP2 for Exchange 2003. Everything seemed to work aside from ActiveSync. The weird thing is it worked half the time and the other half it did not. I would get an Active Sync HTTP_500 error on my palm and an EventID 3005 from source ActiveSync "Verify Exchange is working properly" on the server end.
For the past week, I have dedicated most of my time trying to fix this problem. I have tried every KB article I could find and every registry hack you could think of. I finally broke down and spent 100 bucks to contact Microsoft about the issue I noticed several other people on groups experienced. I figured I would post this to anyone else that might have this same problem with ActiveSync.

1. Open up Systems Manager (Start -> All Programs -> Microsoft Exchange Systems Manager).
2. Look for the "Servers" folder and drill down.
3. If you have a Front-End/Back-End (FE/BE) scenario like me you will have to do this fix to both machines.
4. Drill down to the server you want and then to "Protocols HTTP Exchange Virtual Server".
5. Once you have drilled down there, right click on the "Microsoft-Server-ActiveSync" and click Delete.
6. Right click on the "Exchange Virtual Server", click New, and then Virtual Directory.
7. Under Microsoft-Server-ActiveSync -> "Exchange Path" click "Exchange ActiveSync".
8. Then OK out of it.

Give it a shot, this worked for me.

Alaskowski (Last update 11/9/2004):
This problem is usually attributed to an Exchange situation involving excessive items in the users calendar. Refer to M842541 for hotfix.

Ger J. Kleinsman (Last update 7/14/2003):
This is an Exchange 2003 Pocket PC Server Activesync error.  

and here are the links:


Featured Post

Veeam Disaster Recovery in Microsoft Azure

Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking. It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This month, Experts Exchange sat down with resident SQL expert, Jim Horn, for an in-depth look into the makings of a successful career in SQL.
Eseutil Hard Recovery is part of exchange tool and ensures Exchange mailbox data recovery when mailbox gets corrupt due to some problem on Exchange server.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…
Suggested Courses
Course of the Month16 days, 12 hours left to enroll

864 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question