Windows Phone Sync Error Codes

Windows Phones' sync application can produce a wide range of numeric error or "support" codes. This page documents the set of those codes that are reasonably well understood.

0x8502000f

This code is displayed when the phone can not make a connection to the sync service. It is usually associated with a lack of, or poor Internet connectivity to the phone, for example in marginal cell service areas.

0x85010017

This code is displayed when the sync service sends a fatal error response to the phone. Usually this indicates a configuration error on your account. For example if you enter an incorrect password for your email server, or for Toodledo, you'll see this support code because the service can't complete a folder list operation successfully and responds to the device with a fatal error.

0x80180001

This code is associated with a registry change made on the phone that affects the network used to sync. Symptoms of this problem are that the phone syncs fine up until some point, then this code is seen constantly. The phone will not contact the sync service once the code appears. Usually the onset of this code is associated with running an application that attempts to "optimize" the phone's communication configuration. Applications known to cause the problem are: Fring, GPRSWizard. The only known cure at present is to factory reset the phone.

0x80004005

This one is usually generated when the phone's sync client doesn't like something sent to it by the service. As such, it would normally be associated with a bug in the service. There is some evidence that this code can also be produced when email attachments are stored on a memory card, and that card is corrupt, or otherwise not working properly.

0x85030021

This error code doesn't appear in the sync app UI, but only in the sync log files (as : Heartbeat failed, hr = 0x85030021). It seems to be associated with devices that turn their cell data baseband capability off when sleeping, as described in this article

0x80072eff

This error code doesn't appear in the sync app UI, but only in the sync log files (as : Heartbeat failed, hr = 0x80072eff). It seems to be associated with unpleasant network behavior where the connection to the service is forcibly closed (TCP RST received). This may happen with a mis-configured firewall, or in an ISP network where P2P countermeasures that close long-lived connections are being used.

last modified by David Boreham on 2009/11/18 12:25

Creator: David Boreham on 2009/11/12 20:24
Copyright 2008-2011 Nuevasync, Inc
XWiki Enterprise