Solved

Exchange 2003 Active sync error 3007, 3005 AND 3014

Posted on 2014-10-16
8
1,637 Views
Last Modified: 2014-10-21
Exchange 2003 FE and BE (Enterprise Ed) SP2 patched and installed on Server 2003. (We are moving to a new exchange platform within a few weeks but need mail flowing to mobiles ASAP on current platform).

Office Outlook 2010 Client and 2003 Outlook Web Access and mail flow between all these and external flow in/out is fine, however no mobile phones Android / Windows / iPhone, etc.. are able to sync anything with the server, this is effecting all 550 mobiles the company uses, no common theme / manufacturer etc...

Sometimes rebooting the server starts mail syncing but swiftly stops again and errors and warnings resume in the event log.

This happened a few weeks ago and a simple re-booot solved the issue but no even the reboot only gets it working for a few mins then the errors and warnings resume

Also tried;

# Re-installing SP2 on both FE and BE Servers and web searching the issue heavily but nothing matches the issues

# Rebooting both FE and BE servers

# disabled on access AV scanning as a test on the FE server

# Disabling FBA forms based auth as a test

# Checked iis connection limits if any

Event log on FE Exchange server full of 3007, 3005 and 3014 Errors/Warnings

PLEASE HELP...
0
Comment
Question by:sustrans
  • 4
  • 4
8 Comments
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 40385561
Have you run the Activesync Test on https://testexchangeconnectivity.com?  Use the non-autodiscover test and specify manual server settings.

What are the results?

You may also need to update massync.dll which you can get from MS using the link on this page:

http://support.microsoft.com/kb/967046

Alan
0
 

Author Comment

by:sustrans
ID: 40386195
I have ran the exchange connectivity test and the tests time out

Capture.JPG
0
 
LVL 76

Accepted Solution

by:
Alan Hardisty earned 500 total points
ID: 40386244
The 401 error suggests either incorrect username / password entered, or IP Address restrictions on the FE server(s) on the microsoft-server-activesync virtual directory.

Have a look through my article and check your settings:

http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/A_1798-Exchange-2003-Activesync-Connection-Problems-FAQ.html

It doesn't specifically cover an FE / BE environment, but the FE servers have the IIS directories with SSL enabled and the BE servers have everything without SSL enabled.

Alan
0
Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

 

Author Comment

by:sustrans
ID: 40386481
Just working through the steps listed in the link, will report back if anything is not as expected.

Going through the logs I see;

Unexpected Exchange mailbox Server error: Server: [xxx] User: [xxx@xxx] HTTP status code: [409]. Verify that the Exchange mailbox Server is working correctly.  - Against Event ID 3005

AND

Exchange mailbox Server response timeout: Server: xxx] User: [xxx@xxx]. Exchange ActiveSync Server failed to communicate with the Exchange mailbox server in a timely manner. Verify that the Exchange mailbox Server is working correctly and is not overloaded.  - Against Event ID 3007
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 40386634
The 3005 errors can often be ignored but the 3007 errors can often be resolved by using the Hotfix I posted (all servers).
0
 

Author Comment

by:sustrans
ID: 40386717
After rebuilding virtual directories and re-confirming all items are as suggested from you article/guide I have mail flowing between mobiles again, however the event log is still being littered with 3005 and one or two 3007.

Is the Hot-fix designed for the issue I have - as it mentions 'Microsoft System Centre' which we don't use
0
 

Author Comment

by:sustrans
ID: 40386723
Also Active sync connectivity tester now completes OK
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 40386739
Excellent news about mail-flow.  The hotfix should fix the 3007 errors and may help get rid of some of the 3005 errors, but most of the time, those (the 3005 errors) can be safely ignored.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

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

In-place Upgrading Dirsync to Azure AD Connect
A list of top three free exchange EDB viewers that helps the user to extract a mailbox from an unmounted .edb file and get a clear preview of all emails & other items with just a single click on mailboxes.
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…
how to add IIS SMTP to handle application/Scanner relays into office 365.

831 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