Justin Goo
asked on
ActiveSync 0x85010014 over the air
Hi gang,
I've got a client, who is using a Verizon mobile phone running Windows Mobile 6 on it. We set it up so that he could connect to the Exchange Server over the air. The server is a Windows 2003 SBS machine running Exchange 2003.
Everything was working perfectly. Until he decided he wanted to back up his files onto his PC. So when he connected the PC USB Cable, he set up a second sync source (the PC).
Now when he tries to ActiveSync over the air, we get an error code: 0x85010014
We tried deleting both sync sources and recreating the Exchange sync, but it didn't fix the problem.
We took it down to Verizon and tried a hard reset of the phone, but again it didn't fix the problem. Verizon even tried configuring some brand new phones, but it didn't work, so they are saying the problem is on our end. But our end WAS working, so I don't really think it's a problem with the Exchange Server.
Anyone got any ideas? It's really frustrating him.
I've got a client, who is using a Verizon mobile phone running Windows Mobile 6 on it. We set it up so that he could connect to the Exchange Server over the air. The server is a Windows 2003 SBS machine running Exchange 2003.
Everything was working perfectly. Until he decided he wanted to back up his files onto his PC. So when he connected the PC USB Cable, he set up a second sync source (the PC).
Now when he tries to ActiveSync over the air, we get an error code: 0x85010014
We tried deleting both sync sources and recreating the Exchange sync, but it didn't fix the problem.
We took it down to Verizon and tried a hard reset of the phone, but again it didn't fix the problem. Verizon even tried configuring some brand new phones, but it didn't work, so they are saying the problem is on our end. But our end WAS working, so I don't really think it's a problem with the Exchange Server.
Anyone got any ideas? It's really frustrating him.
/Exchange has SSL required in IIS?
ASKER
I tried it both ways, with required SSL turned on, and then tried turning it off. It didn't work either way. So I turned it back on again.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yes, but it didn't work when I turned it off either.
Plus the sync was working before.
Plus the sync was working before.
Double check your server settings against this document from alanhardisty: http://www.it-eye.co.uk/faqs/readQuestion.php?qid=1
there is no need to make any registry changes to make this work.
If your using a self signed SSL certificate then you will run in to problems. Godaddy.com have some great offers on SSL certificates at the moment.
If you don't have an SSL Certificate and you turn SSL on then it won't work!
there is no need to make any registry changes to make this work.
If your using a self signed SSL certificate then you will run in to problems. Godaddy.com have some great offers on SSL certificates at the moment.
If you don't have an SSL Certificate and you turn SSL on then it won't work!
MS KB 817379
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I ran the connectivity test at https://testexchangeconnectivity.com
Here are the results:
Testing Exchange ActiveSync
Exchange ActiveSync test Failed
Test Steps
Attempting to resolve the host name lkhawaii.com in DNS.
Host successfully resolved
Additional Details
IP(s) returned: 64.65.85.74
Testing TCP Port 443 on host lkhawaii.com to ensure it is listening and open.
The port was opened successfully.
Testing SSL Certificate for validity.
The certificate passed all validation requirements.
Test Steps
Validating certificate name
Successfully validated the certificate name
Additional Details
Found hostname lkhawaii.com in Certificate Subject Common name
Validating certificate trust for Windows Mobile Devices
The test passed with some warnings encountered. Please expand additional details.
Additional Details
Certificate is only trusted on Windows Mobile 5.0 AKU2 (MSFP) and later. Windows Mobile 5.0 devices will not be able to sync. Root = E=info@valicert.com, CN=http://www.valicert.com/, OU=ValiCert Class 2 Policy Validation Authority, O="ValiCert, Inc.", L=ValiCert Validation Network
Testing certificate date to ensure validity
Date Validation passed. The certificate is not expired.
Additional Details
Certificate is valid: NotBefore = 7/31/2009 1:36:57 AM, NotAfter = 7/31/2011 1:36:57 AM"
Testing Http Authentication Methods for URL https://lkhawaii.com/Microsoft-Server-Activesync/
Http Authentication Methods are correct
Additional Details
Found all expected authentication methods and no disallowed methods. Methods Found: Basic
Attempting an ActiveSync session with server
Errors were encountered while testing the ActiveSync session
Test Steps
Attempting to send OPTIONS command to server
OPTIONS response was successfully received and is valid
Additional Details
Headers received: MicrosoftOfficeWebServer: 5.0_Pub
Pragma: no-cache
Public: OPTIONS, POST
Allow: OPTIONS, POST
MS-Server-ActiveSync: 6.5.7638.1
MS-ASProtocolVersions: 1.0,2.0,2.1,2.5
MS-ASProtocolCommands: Sync,SendMail,SmartForward ,SmartRepl y,GetAttac hment,GetH ierarchy,C reateColle ction,Dele teCollecti on,MoveCol lection,Fo lderSync,F olderCreat e,FolderDe lete,Folde rUpdate,Mo veItems,Ge tItemEstim ate,Meetin gResponse, ResolveRec ipients,Va lidateCert ,Provision ,Search,No tify,Ping
Content-Length: 0
Date: Tue, 27 Oct 2009 00:13:11 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Attempting FolderSync command on ActiveSync session
FolderSync command test failed
Tell me more about this issue and how to resolve it
Additional Details
Exchange ActiveSync returned an HTTP 500 response.
Here are the results:
Testing Exchange ActiveSync
Exchange ActiveSync test Failed
Test Steps
Attempting to resolve the host name lkhawaii.com in DNS.
Host successfully resolved
Additional Details
IP(s) returned: 64.65.85.74
Testing TCP Port 443 on host lkhawaii.com to ensure it is listening and open.
The port was opened successfully.
Testing SSL Certificate for validity.
The certificate passed all validation requirements.
Test Steps
Validating certificate name
Successfully validated the certificate name
Additional Details
Found hostname lkhawaii.com in Certificate Subject Common name
Validating certificate trust for Windows Mobile Devices
The test passed with some warnings encountered. Please expand additional details.
Additional Details
Certificate is only trusted on Windows Mobile 5.0 AKU2 (MSFP) and later. Windows Mobile 5.0 devices will not be able to sync. Root = E=info@valicert.com, CN=http://www.valicert.com/, OU=ValiCert Class 2 Policy Validation Authority, O="ValiCert, Inc.", L=ValiCert Validation Network
Testing certificate date to ensure validity
Date Validation passed. The certificate is not expired.
Additional Details
Certificate is valid: NotBefore = 7/31/2009 1:36:57 AM, NotAfter = 7/31/2011 1:36:57 AM"
Testing Http Authentication Methods for URL https://lkhawaii.com/Microsoft-Server-Activesync/
Http Authentication Methods are correct
Additional Details
Found all expected authentication methods and no disallowed methods. Methods Found: Basic
Attempting an ActiveSync session with server
Errors were encountered while testing the ActiveSync session
Test Steps
Attempting to send OPTIONS command to server
OPTIONS response was successfully received and is valid
Additional Details
Headers received: MicrosoftOfficeWebServer: 5.0_Pub
Pragma: no-cache
Public: OPTIONS, POST
Allow: OPTIONS, POST
MS-Server-ActiveSync: 6.5.7638.1
MS-ASProtocolVersions: 1.0,2.0,2.1,2.5
MS-ASProtocolCommands: Sync,SendMail,SmartForward
Content-Length: 0
Date: Tue, 27 Oct 2009 00:13:11 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Attempting FolderSync command on ActiveSync session
FolderSync command test failed
Tell me more about this issue and how to resolve it
Additional Details
Exchange ActiveSync returned an HTTP 500 response.
ASKER
It did turn out to be KB817379.
Which really makes no sense, because it WAS working about 2 months ago. I have no idea what changed, but after going through the KB again, it started working again. So I'm confused. But as long as it's working I'm fine...
Thanks Guys.
Which really makes no sense, because it WAS working about 2 months ago. I have no idea what changed, but after going through the KB again, it started working again. So I'm confused. But as long as it's working I'm fine...
Thanks Guys.