0x85010014 error in Active Sync - possible corrupted messages/items

We have been getting this error code: 0x85010014 - when sync'ing with Active Sync. We have been able to determine that it is most likely a corrupted item somewhere in the mailbox. So aside from doing a mailbox move (which would remove the corrupted item, but is invasive to the end user) is there any tools out there and we can use to determine which item(s) is corrupted? This tool can either run against the mailbox, or perhaps against the .ost file (we run in cached mode) - ofcourse this is affecting VIP's and is of urgent nature...uggg :D
fc-exchangeAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

LeeDerbyshireCommented:
There's a good list of A/S errors here:

http://www.pocketpcfaq.com/faqs/activesync/exchange_errors.php

You don't have SSL and/or Forms-Based Auth required on your OWA installation, by any chance.  That will break A/S:

http://support.microsoft.com/kb/817379
0
fc-exchangeAuthor Commented:
We have both FBA and AS in place with SSL running via ISA servers. This is not the issue as we have some 700+ users running AS with various PDA's and there are only two instances of the issue described above.

However, I have been successfull in getting AS/with FBA to work - there is a vir dir that you need to make etc etc etc...anyway, thank you for the post.
0
LeeDerbyshireCommented:
Ah, right.  Well, to see if it's a problem with a specific mailbox, try using one of the affected devices to open another mailbox that works okay.

You might try ISINTEG to check the integrity of your IS:
http://www.msexchange.org/tutorials/Exchange-ISINTEG-ESEUTIL.html
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
opy01Commented:
I actually had a similar problem and I found out purely by accident after several days that my default email address was cusing this issue.  We use an outside email service and our default email addresses are different that the exchange address for internal mail(not very eficient I know).  If you havent changed your default email address in the user properties then this probably isnt your problem but its worth a try to check and see.
0
Computer101Commented:
Forced accept.

Computer101
EE Admin
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.