from the oops-they-may-have-done-it-again department…
I just got an e-mail from a former coworker reporting a problem with synchronizing some, but not all, iOS 7.0.x devices with Exchange 2010 SP2. There are four users (Alex, Eric, James, and Peter, let’s say) with shiny new iPhone 5s devices. Two of them get the same error when syncing: the Provision verb is returning a status of 110 and throwing an exception from Microsoft.Exchange.Security.Compliance.MessageDigestForNonCryptographicPurposes.HashCore. This seems to point to a problem with crypto negotiation with the devices, but I haven’t been able to look at a trace of the conversation between the device and the server to check.
James’ device works fine. Alex’s device works fine. Peter’s device does not work, either with his own account or Alex’s. Eric’s device does not work with his account; no other accounts have been tested. This seems to indicate that the problem is not (necessarily) with the account. Peter and Eric have both wiped their devices, deleted their Exchange accounts, rebooted the devices, and done all the other stuff you might try when faced with this problem, but to no avail.
This Apple support forum thread seems to indicate that a few others who have the same problem, but none of the recommended fixes have worked for Alex or Peter. My working theory is that this is due to an unwanted interaction of some kind between Exchange 2010 SP2 and iOS 7.x, but I can’t prove that yet. As far as I can tell, Exchange 2013 CU2 doesn’t have the same problem.
I’m posting this in hope that it might come to the attention of anyone else who’s having a similar problem so I can get a sense of its scope and nature.
More news when there is news…
Paul's Down-Home Page 
What about Exchange 2010 sp3?
I have only seen this reported by sites on 2010 SP2. I was hoping to find out if any SP3+ sites had run into the same problem.
My company has a product that acts as a reverse proxy sitting in front of Exchange and I troubleshoot ActiveSync most of the day (basically proving or disproving our fault).
So far I haven’t seen Exchange SP3 hit by it, but would love to have more details.
Yes, with Exchange 2010 SP3 the same problem arises. However, our user had the same problem before he upgraded his iPhone from iOS 6 to iOS 7. So that leaves me completely puzzled. Because we never changed any settings on the Exchange server and his iPhone has been working fine for months since I connected it to our server, and then one day all of a sudden it stopped sync’ing.
Well iOS 7 is one of the best OS from apple. It has some drawbacks but for the mail active sync you need to confirm from your hosting provider. because they can provide you best setting for your phone. different company has different ip login password also confirm with your data service provider. I am using activesync of MailEnable (http://www.mailenable.com/activesync.asp). and i am using this servie from last 6 month now its working fine.
We are experiencing the same issue with around 10% of our phones. We are also an Exchange 2010 SP2 shop. We have found that going into the mail profile’s advanced settings and disabling SSL, saving, and then enabling SSL again, temporarily fixes the issue. It’s as if something is corrupted on the profile. I don’t know why it wasn’t working for you by deleting and recreating the profile, but try the SSL trick.
I have a follow-up post in the queue addressing this issue; I hadn’t heard of the SSL fix but I’ll definitely add a mention of it.