asked on

Exchange 2003 Event ID 3005 ActiveSync Error

After applying some updates to the server (SBS2003) and rebooting I am gettings a lot of Event ID 3005 Errors in the Application Event Log. It is an ActiveSync Error and the result is that users cannot send or receive email. This seems to be an intermittent problem where they can connect sometimes to send/receive, but not others. It is causing major problems. Anybody had this problem before? I have tried to go through the IIS settings (as suggested in one of the answers I googled) but no luck.

Thanks,
Gordon

Simon Butler (Sembee)

Error number on its own is close to useless.
You need to post the actual text in the error.

Unless the server was very badly out of date, then applying updates on their own shouldn't have caused the problems. Exchange 2003 hasn't receive an update for years.

There is no single fix for the problem. If the problem is intermittent then it is probably outside of Exchange. Firewalls can cause sync issues, as can AV software.

Ultimately you need to plan an upgrade. The more modern ActiveSync devices will start to cause problems with Exchange 2003 as the server, simply because it is out of support and most companies will no longer even test against it.

Simon.

SM_exchange

kindly go ahead with system system restore and restore the previous and plan for upgrade to 2k10.

helinutgman

ASKER

Simon, my apologies for not including the text. This is the exact text of the error:

Event Type:      Error
Event Source:      Server ActiveSync
Event Category:      None
Event ID:      3005

Unexpected Exchange mailbox Server error: Server: [servername.domainname.local] User: [someuser@externaldomain.com] HTTP status code: [500]. 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.

As for external causes, I guess anything is possible, but the server was working before with the same firewall, etc.

I would agree with you on the update to a newer version, but that is not my decision. So I am stuck supporting an old server for now. Thanks for the input.

Regards,
Gordon

Simon Butler (Sembee)

@ SM_exchange - that is very poor advice which would probably break Exchange completely. System restore on Exchange is not a recommended method to resolve problems.

Does the error occur with all users?
The main cause of that error is lack of a local email address. If your WINDOWS domain is domain.local then the user needs to have two email addresses, user@example.com and user@domain.local.

Simon.

ASKER CERTIFIED SOLUTION

helinutgman

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

helinutgman

ASKER

Was a strange problem. Happy to get it working again.
Reason: I finally figured it out on my own.