|
Posted by Rob on January 17, 2006, 8:00 pm
Please log in for more thread options
To all,
I found a solution to the dreaded 85010014 server error. A few of my test
users were unable to sync their server content.
In short my exchange servers live in a child domain. Therefore all users
have email addresses automatically generated for the internal parent domain,
as well as the child domain. I am running E2k3 SP1 on W2k3 SP1, using WM5 on
a PPC6700 Smartphone.
I stumbled across the root cause for my problem when I was testing OMA for
the most recent tester, I realized that EAS was not syncing with the users
Primary SMTP address from the child domain, it was using the one from the
root domain. Turns out this is not bad, IF the address prefixes match. My
problem was the address from our parent domain was
FirstinitialLastname2@parentdomain.net. The Primary address was
firstnamelastname@childdomain.net. After I changed the address for the
parentdomain to FirstnameLastname@parentdomain.net, EAS (Exchange
ActiveSync) began working perfectly for the latest test user, as well as all
the others that were failing.
In short, review the exchange addresses tab closely,
Rob
| 
XML Sitemap