Exchange ActiveSync and OMA errors
1507, 1805, 3029, 3030 and 3031
Symptoms: 1. When using
Exchange ActiveSync, you will receive following errors: 1) “Your
account in Microsoft Exchange Server doest not have permission to
synchronize with your current settings. Contact your Exchange Server
administrator. Support Code : 0x85010001”
2) "Unable to connect to your mailbox on server
Servername. Please try again later. If the problem persists contact your
3) "A System error has
occurred while processing your request. Please try again. If the problem
persists, contact your administrator."
"Synchronization failed due to an error on the server. Try again. Error
2. The Event Viewer lists Event ID
3005 - Unexpected Exchange mailbox Server error: Server: [mail.chicagotech.local]
User: [email@example.com] HTTP status code: . Verify that the
Exchange mailbox Server is working correctly.
Event ID 1805 - Request from user UserA@domain.com
resulted in the Microsoft(R) Exchange back-end server <ServerName> returning
an HTTP error with status code 403:Forbidden.
4. Event ID 1507 -
An unknown error occurred while processing the current request: Exception of
type Microsoft.Exchange.OMA.DataProviderInterface.ProviderException was
5. Event ID 3029 -
The mailbox server [%1] has its [%2] virtual directory set to require SSL.
Exchange ActiveSync cannot access the server if SSL is set to be required.
Event ID: 3030 - The mailbox server [%1] has forms
based authentication enabled on its virtual server. Exchange ActiveSync
cannot access the server when Forms based authentication is enabled.
7. Event ID 3031 - The mailbox
server [%1] does not allow "Negotiate" authentication to its [%2] virtual
directory. Exchange ActiveSync can only access the server using this
Exchange Server ActiveSync and Exchange OMA use the Exchange virtual
directory to access the user's mailbox which is located on OWA templates and
DAV on Exchange back-end servers, Exchange running on SBS 2003 or single.
Server ActiveSync and OMA must access this virtual directory, /exchange-oma.
So you need to make sure ExchangeVDir points to /exchange-oma.
To fix these issues,
create a secondary virtual directory, for
example /exchange-oma, for Exchange that does not require SSL, and then
add a registry value to point to the new virtual
questions, comments, feedbacks and suggestions
Contact a consultant
ActiveSync and OMA errors
Creating a secondary virtual directory for
ActiveSync and OMA access
Add/modify a registry value to point to the
How did we setup our
Exchange for OWA, OMA, ActiveSync and RPC over HTTPS
Setup Default Web
Site for OWA, OMA, ActiveSync and RPC over HTTPS
Exchange-oma, ExchangeOMA, ExchDAV for OWA, OMA, ActiveSync and
RPC over HTTPS
Setup OMA folder for
Setup Remote for
OWA, OMA, ActiveSync and RPC over HTTPS
Setup RPC for RPC