Exchange ActiveSync Error 3005 Status Code 422

[Marc]

Hi all,

I have a problem with an Exchange 2003 SP2 Frontend Server.

The following Error is logged in the Application Event Log:
________________________________
Event ID: 3005
Source: Server ActiveSync

Unexpected Exchange mailbox Server error: Server: (Servername.domain.com) User: (user.name@domain.com) HTTP status code [422]. Verify that the Exchange mailbox server is working correctly.
________________________________

I have verified that the mailbox server is working correctly, and the users are not having any problems with their mobile devices. My boss wants me to clear out this error anyway.

I did some research and figured out, that error 422 means "422 Unprocessable Entity". I have no idea what that is.

All servers are running Exchange 2003 SP2, the Domain is 2003 native.
There is one front end server, and the back end is an Exchange 2003 Cluster, Active/Passive.

Ideas anyone?

Thanks for your help in advance!

Greetings
Marc

[AndyJG247]

Not heard of that error before but have you run the bpa to see if that shows anything.

Seen this too?
http://forums.microsoft.com/TechNet/...8768&SiteID=17

Are they all running the same service packs etc?
Are the windows updates all installed too (the fairly current ones remove the tcp chimney issues for example).

[Marc]

Hi Andy,

thanks for the Link, there are some clues I did not try before.

I will keep you informed.

Cheers
Marc

[AndyJG247]

No probs, let us know how you get on

[Marc]

I have found this on the Microsoft KB:
http://support.microsoft.com/default...b;en-us;937635

But I am not sure, if this article applies to my problem.
I have read the solution, and found that I do not have the folder "Exchange-OMA" in the IIS.
Is this folder only in SBS, or should it be on the "normal" Exchange Server, too?

Cheers
Marc

[Sembee]

The exchange-oma directory is only created by default on SBS. If you are using full product then you have to create it yourself.

Furthermore, it only applies to single server deployments, not fe/be that you have. Therefore it doesn't apply.

The error you originally posted I have seen where the mailbox does not have an email address in the default domain. For example, if your WINDOWS domain is domain.local then the mailbox does not have an email address in that domain. It does not have to the default address.

Simon.

[knottyrope]

Just had the same thing happen to me a month ago and figured it out today.

lots in exchange logs only from two users.

Unexpected Exchange mailbox Server error: Server: [Mail.domain.com] User: [user@domain.com] HTTP status code: [422]. Verify that the Exchange mailbox Server is working correctly.


I have hunted high and low and finally grabbed the users phone and found that there were items in the outbox that could not be sent and there were a few old drafts. Looks like the outgoing mail that was stuck was the culprit.

So I asked if I could delete them and no errors in 30 minutes so far from that user.