很高兴能够找到一个比较全的关于ActiveSync的ErrorCode及解决办法.
支持PPC2002,2003, SmartPhone2002,2003, WM5.0, WM6.0, WM6.1.
希望该列表能够帮助到大家
WM2002_2003_Error | WM_5_Error | Possible_Cause | Possible_Resolution | User_Action |
---|---|---|---|---|
N/A | 85002000 | The device ran out of storage even after the system closed other processes. | Delete excess files and mail from the device. | |
N/A | 85002001 | An unknown synchronization application error occurred on the device. | Try again later. | |
DEV_1 | 85002002 | The device ran out of storage even after the system closed other processes. | Delete excess files and mail from the device. | |
DEV_2 | 85002003 | The device timed out while waiting to establish a connection with the server. | Try again later.?Ensure device is able to browse Internet sites. Additionally, verify the value of the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ MasSync\Parameters\ExchTimeoutThreshold |
|
DEV_3 | 85002004 | The user manually ended the synchronization process from the device. | Try again. | |
DEV_6 | 85002007 | The synchronization failed because of a problem on the server but no server-originated error codes (or any other unknown server errors) were received by the device. | Verify that the server is available and supports synchronization with a mobile device, and then try again later. Ensure the proper server name has been entered. | |
DEV_7 | 85002008 | An error occurred while ActiveSync was writing an item抯 properties to the database on the device (per-item error). | Try again. | |
DEV_8 | 85002009 | The synchronization key data on the device is not valid because a data removal failed. | Try again.?May require user to de-select sync items (Inbox, Contacts, Calendar, Tasks) and re-select them to reset the sync key. | |
DEV_9 | 8500200A | The connection failed due to missing server information or user credentials. Tap Options, and then the Server tab to verify that your server name is correct. Then, tap Advanced to verify that your user credentials are correct and try again | Verify the server information and credentials on the device. | |
DEV_11 | 8500200C | The device could not shut down the send/receive thread after the user requested the synchronization to stop. The synchronization application on the device was forced to close. | ||
DEV_12 | 8500200D | The device timed out while waiting for a response from the user. | Try again. | |
DEV_13 | 8500200E | A failure occurred on the device that is not indicated to the user. | ||
DEV_14 | 8500200F | The device timed out while waiting for a response from the server. | Verify that the server is available and try again later. | |
N/A | 85002010 | The device抯 last error is displayed. | ||
HTTP | 85010000 | An unknown HTTP communication or protocol error occurred. | Ensure device is able to browse Internet sites. | |
HTTP_400 | 85010001 | An invalid HTTP communication or protocol syntax occurred. | ||
HTTP_401 | 85010002 | An unauthorized HTTP communication or protocol was used. - OR - Unable to connect to sync server due to authentication failure. Check your connection configuration. - OR - Access was denied. Check your server username and password in ActiveSync Options |
The credentials provided to access the server are incorrect or you are not enabled for synchronization or your password has expired. User Action: 1. On the device, go to ActiveSync, Tools, Server, verify that the server name is correct. Click on Advanced and verify the username, password and domain information. Please contact your administrator and make sure that you are enabled for synchronization |
See How to troubleshoot server ActiveSync HTTP error codes |
HTTP_402 | 85010003 | Payment is required for HTTP communication. | ||
HTTP_403 | 85010004 | A forbidden HTTP communication or protocol was used. - OR - Your account does not have permission to sync with your current settings. Contact your Microsoft Exchange administrator. |
Remove the item from the synchronization list. 1. The Microsoft-Server-ActiveSync virtual directory on your server is configured to require SSL and you are using a device without SSL. 2. The Exchange virtual directory on your mailbox server is configured to require SSL. 3. This error could occur if host headers are being used and the request goes to the wrong Web site. |
1. a. On your Pocket PC 2003-based device, click Start, ActiveSync, Tools, Options, Server and check the box 揟his server uses an SSL connection? 2. On your Smartphone 2003-based device, click Start, ActiveSync, Menu, Options, Server Settings, Connection and check the box 揟his server uses an SSL connection? 3. Verify that host headers are configured correctly. 4. Also, see Microsoft KB Article 817379 for information on configuring the Exchange virtual directory. 5. See Error message when you try to synchronize a mobile device with Exchange Server 2003: "HTTP_403" 6. XCSI/PRE/E2K3/Unable to synchronize with Exchange server using Active Sync |
HTTP_404 | 85010005 | An object was not found by the HTTP communication or protocol. - OR - The server you are synchronizing with is not an Exchange ActiveSync server, or is running incompatible software. Specify the correct server in ActiveSync options. |
Verify that the object exists, and then try again. If this error occurs again, remove the item from the synchronization list. The server name specified on the device resolves to the IP address of a server that does not have Exchange installed on it. | 1. Verify the server name and DNS configuration. 2.See How to troubleshoot server ActiveSync HTTP error codes |
HTTP_405 | 85010006 | The method is not allowed for use with an HTTP communication or protocol. | ||
HTTP_406 | 85010007 | No response acceptable to the client was found for HTTP communication or protocol to proceed. | ||
HTTP_407 | 85010008 | Proxy authentication is required for HTTP communication or protocol to proceed. | Verify proxy credentials and try again. | Store the username and password for the proxy server in Pocket Internet Explorer by visiting the internet. This is applicable to ISA 2000 Server. Also, you can specify the username and password in the Connection Manager for connections that are part of Work. |
HTTP_408 | 85010009 | The server timed out while waiting for the request for an HTTP communication. This error occurs when a request is sent but never gets a response, typically in low signal conditions. Generally, it is a temporary or recoverable situation. | Try again later. | |
HTTP_409 | 8501000A | The user should resubmit the HTTP communication with more information. | Verify the information and settings associated with the HTTP communication and try again. | |
HTTP_410 | 8501000B | The HTTP resource is no longer available. | Ensure the server is available. | |
HTTP_411 | 8501000C | The server refused to accept the HTTP communication request without a length. | ||
HTTP_412 | 8501000D | The precondition given in the HTTP communication request failed. | Verify Internet settings and try again. | |
HTTP_413 | 8501000E | The HTTP communication request entity was too large. | ||
HTTP_414 | 8501000F | The requested HTTP Universal Resource Identifier (URI) was too long. | ||
HTTP_415 | 85010010 | An unsupported HTTP media type was used. | ||
HTTP_416 | 85010011 | An HTTP communication or protocol error occurred. | ||
HTTP_417 | 85010012 | An HTTP communication or protocol error occurred. | ||
HTTP_449 | 85010013 | An HTTP communication or protocol error occurred. | ||
HTTP_500 | 85010014 | An internal HTTP server error occurred. - OR - Synchronization failed due to an error on the server. Try again. - OR - An authentication error occurred connecting to the server. - OR - You changed the IP address of the Exchange Server |
Verify that the HTTP server is available and try again. May require user to de-select sync items (Inbox, Contacts, Calendar, Tasks) and re-select them to reset the sync key. 1. Windows Integrated Authentication is not enabled on the Exchange virtual directory on the Exchange server. The Server ActiveSync component uses Kerberos authentication when communicating with the Exchange server. 2. Windows Integrated Authentication is enabled on the Exchange virtual directory on the Exchange server, but Kerberos is disabled via the IIS metabase. 3. Kerberos is enabled, but IIS may return HTTP Status 401 every 30 Days when using Kerberos on Windows 2000. 4. Sync is attempted while the mailbox is being moved. 5. User attempting sync is a member of more than 200 groups. 6. The Left Hand Side(LHS) and Right Hand Side(RHS) of the user抯 primary SMTP address are both different from the SMTP address based on the default recipient policy. (Fixed with Exchange 2003 Service Pack2) 7. 燭he Exchange virtual directory on the Exchange Server is configured to require Secure Sockets Layer (SSL). Server ActiveSync communicates with the Exchange Server over port 80. 8. Windows SharePoint?has been installed on the Exchange server 9. The user composes e-mail on the device and attempts a sync when mailbox limits have been reached on the Exchange server. 10. Anonymous authentication is enabled on the Microsoft-Server-ActiveSync virtual directory on the server. 11. IIS Default Web Sites\Exchange-Oma virtual server retained the previous IP address in the Directory Security \ IP Address and domain name restrictions. |
1. To enable Integrated Windows Authentication on the Exchange virtual root 2. Re-enable Kerberos on the Exchange server by following the instructions in the KB Article 215383. HOW TO: Configure IIS to Support Both Kerberos and NTLM Authentication 3. If you are using Exchange 2003 on Windows 2000, obtain the hot fix outlined in KB 329938 by calling Microsoft Product Support Services. 4. Attempt sync later. 5. Reduce the group membership or obtain the QFE fix outlined in KB 818526 by calling Microsoft Product Support Services. 6. Add a registry key. Use Regedt32 and locate HKLM\System\CurrentControlSet\Services\MasSync\Parameters. Under the Parameters key create a Reg_SZ value called SMTPProxy. Set the value to the domain defined by the default recipient policy. For example, Microsoft.com. Restart the IIS Admin service. If you are using a front-end/back-end configuration this registry key needs to be added on the front-end server. 7. To configure the Exchange virtual directory to not require SSL 8. Configure Windows SharePoint to use Kerberos authentication by following the steps in KB 832769 HOW TO: Configure Windows SharePoint Services to Use Kerberos Authentication 9. Try to delete items in your mailbox to bring it within limits or contact your Exchange administrator to change the limits on your mailbox. 10. Uncheck anonymous authentication on the Microsoft-Server-ActiveSync virtual directory on the server. Basic authentication should be enabled. 11. See KB 817379: Exchange ActiveSync and Outlook Mobile Access errors occur when SSL or forms-based authentication is required for Exchange Server 2003 if you are using SSL or forms-based authentication. 12. Change the IIS Default Web Sites\Exchange-Oma virtual server IP address to deny all except the server's new IP address. 13. You receive an HTTP_500 error message when you synchronize your mobile device with Microsoft Exchange Server 2003 http://support.microsoft.com/default.aspx?scid=kb;en-us;886346 14.. See How to troubleshoot server ActiveSync HTTP error codes 15. XCCC: Server ActiveSync Fails with HTTP_500 If SSL Is Enabled on Exchange Server Virtual Directory |
HTTP_501 | 85010015 | The required protocol is not supported. | Install Update Rollup 3 for Exchange Server 2007. | See The synchronization session of the mobile device fails, and you receive error code "0X85010015" when you try to synchronize a mobile device by using Exchange ActiveSync in Exchange Server 2007 |
HTTP_502 | 85010016 | An error response was received from the HTTP gateway. - OR - Synchronization failed due to an error on the server.?/font> |
Verify that the gateway is available and try again. 1. The device is using a proxy server to connect to the Exchange Server. The proxy server encountered an error. |
1. Please use a different proxy or report the issue to the proxy server administrator. 2. See How to troubleshoot server ActiveSync HTTP error codes |
HTTP_503 | 85010017 | The device is temporarily overloaded. - OR - Synchronization failed due to an error on the server. Try again. |
Try again later. 1. The Web service is unavailable. The service may have been stopped temporarily. |
1. Attempt sync later |
HTTP_504 | 85010018 | The device timed out while waiting for the HTTP gateway - OR - Synchronization failed because of a server error. Try again. |
Try again later. 1. The device is using a proxy server to connect to the Exchange Server. The proxy server connection timed out. |
1. Use a different proxy or report the issue to the proxy server administrator |
HTTP_505 | 85010019 | The HTTP version is not supported. | ||
HTTP_507 | 8501001A | HTTP is out of disk space. | ||
CONNMGR_0 | 85020000 | The connection status is unknown in the Connection Manager. | ||
CONNMGR_16 | 85020001 | The connection is open in the Connection Manager. | ||
CONNMGR_32 | 85020002 | The connection is disconnected in the Connection Manager. | ||
CONNMGR_33 | 85020003 | The connection failed and cannot be reestablished by the Connection Manager. - OR - Unable to connect. Verify you have network coverage and try again |
1. Try restarting the device and verify connectivity settings on the device. 2. There is no connection available for the device to communicate with the server |
1. Verify the connectivity settings on your device 2. Ensure the device can access Internet sites. |
CONNMGR_34 | 85020004 | The user ended the connection. | See Synchronization times out and error "DEV_10" or "CONMGR_34" occurs on a Pocket PC device when you try to synchronize with Exchange Server 2003 | |
CONNMGR_35 | 85020005 | The Connection Manager is ready to connect but the connection is disabled.?/font> | ||
CONNMGR_36 | 85020006 | The Connection Manager could not find a path to the destination. - OR - Unable to connect. Verify your dialup or proxy settings are correct, and try again |
1. Verify server name is entered correct. 2. There is no connection available for the device to communicate with the server. 3. The user has more than 372 top level folders in their mailbox and is using a Windows Mobile 2002-based device. |
1. Verify the connectivity settings on your device. 2. Reduce the number of top level folders to 372 or less by moving some top level folders to be subfolders or use a Windows Mobile 2003-based device 3. Ensure the device can access Internet sites. |
CONNMGR_37 | 85020007 | The Connection Manager is waiting for a path to the destination. - OR - Unable to connect. Verify you have network coverage, and try again. If the problem persists, contact your network administrator |
1. There is no connection available for the device to communicate with the server. | 1. Verify the data connectivity settings (GPRS/dial-up settings) on your device 2. Ensure the device can access Internet sites. |
CONNMGR_38 | 85020008 | A voice call is in progress. | Try synchronizing again after the voice call is finished. | |
CONNMGR_64 | 85020009 | The Connection Manager is attempting to connect. | Ensure the device can access Internet sites. | |
CONNMGR_65 | 8502000A | Another connection is using the resource. | Try again later. | |
CONNMGR_66 | 8502000B | The Connection Manager could not find a path to the destination. | Ensure the device can access Internet sites. | |
CONNMGR_128 | 8502000C | The connection is being brought down. | Ensure the device can access Internet sites. | |
CONNMGR_129 | 8502000D | The Connection Manager is stopping the attempt to connect. | ||
N/A | 85030000 | No synchronization occurred while roaming. | ||
N/A | 85030001 | The ActiveSync application is not supported. | Upgrade the version of ActiveSync on the desktop computer and try again. | |
N/A | 85030002 | The ActiveSync application is not implemented. | ||
N/A | 85030003 | No synchronization is scheduled in the ActiveSync application. | ||
N/A | 85030004 | The ActiveSync application is not initialized. | Restart the ActiveSync application and try again. | |
N/A | 85030005 | Mutex failed on the ActiveSync application. | ||
N/A | 85030006 | The listview window in the ActiveSync application was not created. | ||
N/A | 85030007 | The document was not sent in the synchronization context. | ||
N/A | 85030008 | The synchronization document is not valid. | ||
N/A | 85030009 | The proxy window in the ActiveSync application was not created. | ||
N/A | 8503000A | The device failed to send a message to the ActiveSync application. | ||
N/A | 8503000B | The ActiveSync application failed to start in a timely fashion. | ||
N/A | 8503000C | The device failed to find the ActiveSync window. | ||
N/A | 8503000D | The device failed to get the ActiveSync process handle. | ||
N/A | 8503000E | The device failed to send the Extensible Markup Language (XML) document to the synchronization application. | ||
N/A | 8503000F | An invalid collection type was used. | ||
N/A | 85030010 | A DPA error occurred. | ||
N/A | 85030011 | A POOM failure occurred. | ||
N/A | 85030012 | A POOM Provider DSA error occurred. | ||
N/A | 85030013 | No device address exists in the ActiveSync application. | Verify that the device has an IP address and that it has a partnership with the desktop computer. | |
N/A | 85030014 | ActiveSync failed to configure the account to synchronize as new items arrive.?/font> | Contact the Microsoft Exchange administrator. | |
N/A | 85030015 | The account could not be configured to synchronize as new items arrive.?/font> | Select a different ActiveSync mobile schedule or contact the Microsoft Exchange administrator. | |
N/A | 85030016 | A silent retry error occurred in the ActiveSync application. | ||
N/A | 85030017 | A retry level information error occurred in the ActiveSync application. | ||
N/A | 85030018 | A retry level error occurred in the ActiveSync application. | ||
N/A | 85030019 | The radio/phone is off. | If using a Pocket PC device, try again after turning on the phone. | |
N/A | 8503001A | The response was compressed but had an invalid gzip header. | ||
N/A | 8503001B | An error is returned by the zlib decompression function. | ||
INTERNET_1 | 80072EE1 | No more handles could be generated at this time. | ||
INTERNET_2 | 80072EE2 | The request has timed out. It is generally a temporary or recoverable situation. | Try again later. | |
INTERNET_3 | 80072EE3 | An extended error was returned from the server. This error is typically caused by a string or buffer containing a verbose error message.?/font> | Retrieve the error text from the Verbose log file. | |
INTERNET_4 | 80072EEC | An internal error has occurred. It is generally a temporary or recoverable situation. | Try again later. | |
INTERNET_5 | 80072EE5 | The Uniform Resource Locator (URL) is invalid. This error is caused by a temporary server overload. | Try again after verifying the URL. | |
INTERNET_6 | 80072EE6 | The URL scheme could not be recognized or is not supported. This situation is caused by temporary issues, such as insufficient temporary memory. | Close one or more programs and try again. | |
INTERNET_7 | 80072EE7 | The server name could not be resolved. - OR - Synchronization failed. Verify that you have entered the correct server name and try again |
Verify the server name on the device and try again. | 1. Verify the server information on your device. |
INTERNET_8 | 80072EE8 | The requested protocol could not be located. | Verify that the protocol is supported by the device and by the desktop computer, and then try again. | |
INTERNET_9 | 80072EE9 | A request to InternetQueryOption or InternetSetOption specified an invalid option value. | ||
INTERNET_10 | 80072EEA | The length of an option supplied to InternetQueryOption or InternetSetOption is incorrect for the type of option specified. | ||
INTERNET_11 | 80072EEB | The request option cannot be set, only queried. | ||
INTERNET_12 | 80072EEC | The Microsoft Win32?Internet function support is being shut down or unloaded. | ||
INTERNET_13 | 80072EED | The request to connect and log on to a File Transfer Protocol (FTP) server could not be completed because the supplied user name is incorrect. | Try again after verifying the server name and the user name. Also, try contacting the server administrator. | |
INTERNET_14 | 80072EEE | The request to connect and log on to an FTP server could not be completed because the supplied password is incorrect. | Try again after verifying the server name, user name, and password. Also, try contacting the server administrator. | |
INTERNET_15 | 80072EEF | The request to connect to and log on to an FTP server failed. | Try again after verifying the server name, user name, and password. Also, try contacting the server administrator. | |
INTERNET_16 | 80072EF2 | The requested operation is invalid. | ||
INTERNET_17 | 80072EF1 | The operation was canceled, usually because the handle on which the request was operating was closed before the operation completed. | ||
INTERNET_18 | 80072EF2 | The type of handle supplied is incorrect for this operation. | ||
INTERNET_19 | 80072EF3 | The requested operation cannot be carried out because the handle supplied is not in the correct state. Generally, this is a temporary and recoverable situation. - OR - Synchronization failed due to a device software error. Contact your network administrato |
Try again later. 1. This could be caused by transient network issues. |
1. Attempt the sync later |
INTERNET_20 | 80072EF4 | The request cannot be made through a proxy. | Change to a different type of connection and then try to reconnect to the synchronization resource. | |
INTERNET_21 | 80072EF5 | A required registry value could not be located. | Verify the registry settings for ActiveSync, the mobile device, and the desktop computer. | |
INTERNET_22 | 80072EF6 | A required registry value was located but it is an incorrect type or has an invalid value. | Verify the registry settings for ActiveSync, the mobile device, and the desktop computer. | |
INTERNET_23 | 80072EF7 | Direct network access cannot be made at this time. | Verify that the network is available and that the user has permissions to access the network from a mobile device, and then try again later. | |
INTERNET_24 | 80072EF8 | An asynchronous request could not be made because a zero context value was supplied. | ||
INTERNET_25 | 80072EF9 | An asynchronous request could not be made because a callback function has not been set. | ||
INTERNET_26 | 80072EFA | The required operation could not be completed because one or more requests are pending. | Try again later. | |
INTERNET_27 | 80072EFB | The format of the request is invalid. | Verify the configuration settings for ActiveSync, the mobile device, and the desktop computer, and then try again later. | |
INTERNET_28 | 80072FFC | The requested item could not be located. This error is similar to an 揌TTP 404 Page Not Found?error in Internet Explorer. It may be caused by temporary server load conditions. | Try again later.Ensure the device can access Internet sites. | |
INTERNET_29 | 80072EFD | The attempt to connect to the server failed because a connection to the network was not detected. - OR - Synchronization failed. Information cannot be synchronized because a connection to the network was not detected. Check your device connection settings |
If using a desktop passthrough connection to synchronize to an ActiveSync server, make sure that the device is in the cradle or otherwise connected to the desktop computer. If using a wireless connection to the desktop computer, verify that the connection settings are configured correctly. Try again after verifying the server name, user name, and password. Also, try contacting the server administrator. 1. There is no connectivity to the server 2. A certificate is not installed on the server. 3. The configuration settings on the device for Exchange ActiveSync are incorrect. |
1. If you are using desktop pass through, make sure the device is in the cradle. If you are using an 802.11 card, make sure the connection settings are configured correctly. Check to see if your device has a valid IP address. Verify that you have Internet connectivity by browsing a Web site. Freeware utilities are available for Windows Mobile-based devices to assist in determining your IP address and verifying basic network connectivity. 2. If you are using a Windows Mobile 2002-based device, install a valid certificate on the server. 3. Verify that you have entered the server name correctly on your device. If you have a front-end/back-end configuration use the name of the front-end server and not the mailbox server. |
INTERNET_30 | 80072EFE | The connection with the server has been stopped. | Verify that the server is available and try again. | |
INTERNET_31 | 80072EFF | The connection with the server has been reset. - OR - Synchronization failed due to a communications failure. Try again |
Verify that the server is listening on the SSL port and that the device can connect to the server over SSL. 1. The connection with the server was reset. You are using a Windows Mobile 2002-based device or a Windows Mobile 2003-based device with SSL. However an SSL connection could not be established and the connection was reset. |
1. Verify that the server you are connecting is listening on the SSL port. Ensure that you can connect to the server over SSL using Internet Explorer on the device. |
INTERNET_32 | 80072F00 | This error calls for the Win32 Internet function to redo the request. | ||
INTERNET_33 | 80072F01 | The request to the proxy was invalid. It may be caused by temporary load conditions. | Verify proxy settings and try again later. | |
INTERNET_33 | 80072EFC | The request to the proxy was invalid. It may be caused by temporary load conditions. | Verify proxy settings and try again later. | |
INTERNET_36 | 80072F04 | The request failed because the handle already exists. | ||
INTERNET_37 | 80072F05 | The SSL certificate date that was received from the server indicates that the certificate has expired. - OR - Synchronization failed. The security certificate on the server has expired. Check that the date and time on your device are correct and try again |
Verify that the date and time on the device are correct. If the date and time are correct, then contact the server administrator to update the certificate. | 1. On your device, click Start, Settings, System, Clock, and set the correct date and time. 2. See Error message when you try to synchronize a Windows Mobile-based device by using Exchange ActiveSync for Exchange 2003 or for Exchange 2007: "Synchronization failed" |
INTERNET_38 | 80072F06 | The SSL certificate common name (host name field) is incorrect. - OR - Synchronization failed due to an incorrect SSL certificate common name. |
Verify certificate settings. 1. The name of the Exchange server specified on the device does not match the common name on the certificate.? |
1. On your device, click Start, ActiveSync, Tools, Options, Server, and make sure that the correct server name is entered. |
INTERNET_39 | 80072F07 | The application is moving from a non-SSL to an SSL connection because of a redirection. | ||
INTERNET_40 | 80072F08 | The application is moving from an SSL to a non-SSL connection because of a redirection. | ||
INTERNET_41 | 80072F09 | The content is not entirely secure. Some of the content being viewed may have come from unsecured servers. | ||
INTERNET_42 | 80072F0A | The application is posting and attempting to change multiple lines of text on a server that is not secure. | ||
INTERNET_43 | 80072F0B | The application is posting data to a server that is not secure. | ||
INTERNET_44 | N/A | The server is requesting client authentication. | Enter authentication credentials. | |
INTERNET_45 | N/A | Synchronization failed. The security certificate on the server is invalid. Contact your system administrator or ISP to install a valid certificate on the server and try again. | The sync client does certificate validation and has detected that an invalid certificate is installed. | 1. Attempt sync after a valid certificate is installed on the server. The following root certificates are installed by default on Pocket PCs with Windows Mobile 2002 software. ?Verisign/RSA Secure Server ?Verisign Class 1 Public Primary CA ?Verisign Class 2 Public Primary CA ?Verisign Class 3 Public Primary CA ?Verisign Class 3 Public Primary CA (2028) ?GTE Cybertrust ROOT ?GTE Cybertrust Solutions ROOT ?Thawte Server CA ?Thawte Premium Server CA ?Entrust.net Secure Server ?Entrust.net CA (2048 bit) 2. If you are using a certificate that is not trusted, you can disable certificate validation on the device by running the CertChk.exe tool. The Disable Certificate Validation tool is part of the Exchange 2003 All-in-one Tools package available from http://www.microsoft.com/downloads/details.aspx?FamilyId=E0F616C6-8FA4-4768-A3ED-CC09AEF7B60A&displaylang=en Please see the readme that is provided with the tool for more information. 3. Root certificates can also be added to the Pocket PCs with Windows Mobile 2002 softwareby using the process outlined in KB 322956 Sample to Add Root Certificates to Pocket PC 2002. |
INTERNET_55 | N/A | Synchronization failed. If the problem continues contact your Network Administrator | The sync client does certificate validation and has detected that an invalid certificate is installed. | 1. Attempt sync after a valid certificate is installed on the server. The following root certificates are installed by default on Pocket PC 2003 devices. ?Equifax Secure Certificate Authority ?Verisign Class 2 Public Primary CA ?Verisign Class 3 Public Primary CA ?GTE Cybertrust ROOT ?GTE Cybertrust Solutions ROOT ?Thawte Server CA ?Thawte Premium Server CA ?Entrust.net Secure Server ?Entrust.net CA (2048 bit) ?GlobalSign Root CA 2. If you are using a certificate that is not trusted, you can disable certificate validation on the device by running the CertChk.exe tool. The Disable Certificate Validation tool is part of the Exchange 2003 All-in-one Tools package available from http://www.microsoft.com/downloads/details.aspx?FamilyId=E0F616C6-8FA4-4768-A3ED-CC09AEF7B60A&displaylang=en Please see the readme that is provided with the tool for more information. 3. Root certificates can also be added to the Pocket PC 2003-based device. Copy the .DER file for your root certificate to the Pocket PC 2003-based device. Then browse to the file and just click on it. Pocket PC 2003-based devices will prompt you to add the certificate to the root store. |
INTERNET_152 | N/A | Synchronization failed due to a communications failure. Try again. | 1. An invalid response was received from the server. This could occur if a problem was encountered while the server was in the midst of transmitting data. This could occur if there was a proxy in between the device and server that did not honor the HTTP Keep-Alive setting. This could also occur if the default Web site has been stopped.?/font> | 1. Attempt the sync again. Configure the proxy to enable the HTTP Keep-Alive setting. If the default Web site was stopped, Click Start, Programs, Administrative Tools, and then click Internet Services Manager. Click to expand your server object, right-click Default Web site, and then click Start. |
N/A | N/A | The phone is off. | If using a Pocket PC device, try again after turning on the phone. | |
N/A | N/A | The connection link disconnected prematurely. | Verify that the resource is available and try again. | |
N/A | N/A | The connection could not be established because it would split an exclusive connection. | Wait until the exclusive connection is no longer being used, and then try again. Or cancel the current activity on the exclusive connection and then try again. | |
N/A | N/A | The server or desktop computer failed to authenticate the user. | Verify the user抯 credentials. If the credentials are correct, verify that the user has permissions to synchronize with the server or desktop computer from a mobile device. | |
INTERNET_150 | 80072F76 | The requested header could not be located. | ||
INTERNET_151 | 80072F77 | The server did not return any headers. | ||
INTERNET_153 | 80072F79 | The supplied header was invalid. | ||
INTERNET_156 | 80072F7C | The redirection failed because either the scheme changed (for example, HTTP to FTP) or all attempts made to redirect failed (default is five attempts). | ||
DEV_1 | N/A | Synchronization failed. You do not have enough free memory on your device to synchronize information. Delete unused files from your device or close programs that are running to free up memory, and then try again | Insufficient memory. | 1. The storage memory holds all the applications that are loaded in RAM on the device. The program memory is used by programs that are running. The shell adjusts allocation of storage and program memory. The shell will close applications to free program memory. You can also close applications manually by clicking Settings, System, Memory, Running Programs, and stopping the unnecessary applications. To free up storage memory remove unnecessary programs that have been loaded |
DEV_3 | N/A | You have stopped synchronization. | This error is reported when you disconnect the connection that was being used for synchronization. For example, if you were using a CDPD modem for connectivity and you clicked on Disconnect in the middle of an ActiveSync session, you could get this error. | 1. Reconnect and attempt the sync. |
DEV_4 | N/A | Synchronization failed. If the problem continues, contact your network administrator | This error is caused by corruption in the data store. | 1. Unselect the datatypes on the device by clicking Start, ActiveSync, Server, and then reselect them. This will delete all the data on the device. On the subsequent sync, all selected items will be synchronized to the device. |
DEV_10 | 8500200B | Synchronization failed because the device timed out waiting for the server to respond. Try again later. | This error is reported when the device times out while trying to establish a connection with the server. The error is reported after around 4 minutes. . | 1. Attempt the sync later 2. See Synchronization times out and error "DEV_10" or "CONMGR_34" occurs on a Pocket PC device when you try to synchronize with Exchange Server 2003 |
0x80042256 | N/A | Synchronization failed because the user aborted connection. | 1. User clicked Stop when the sync was in progress. | 1. In ActiveSync, click Sync to initiate the server sync. |
0x80070008 | N/A | Synchronization failed. If the problem continues, contact your network administrator | 1. Obtain the latest Pocket PC End User Update from your service provider. | |
0x8007000e | N/A | Synchronization failed. You do not have enough free memory on your device to synchronize information. Delete unused files from your device or close programs that are running to free up memory, and then try again. | 1. a. Attempt to sync a meeting request that contains an attendee list that exceeds 16K characters. b. Attempt to sync a calendar item that contains a large number of exceptions. c. Make sure you have enough free memory on the device. |
1. Obtain the latest Pocket PC End User Update from your service provider. 2. Try a soft reset of the device |
0x80004005 | N/A | Synchronization failed due to a device software error. Contact your network administrator. | 1. Obtain the latest Pocket PC End User Update from your service provider. | |
0x80830003 | N/A | Synchronization failed. If the problem continues, contact your network administrator. | 1. The Exchange server is configured to require client certificates. | 1. On the Exchange server, launch Internet Services Manager. Right click on the Microsoft-Server-ActiveSync virtual directory and choose Properties. Select the Directory Security tab. Click the Edit button in the Secure Communications section and select the option to 揑gnore client certificates.?br>See "0x80830003" error message when you use Exchange Server 2003 ActiveSync to synchronize a mobile device |
MIS_3 | N/A | Sync key mismatch error. To restart sync, disable and re-enable Server ActiveSync on the device for the particular data type that failed (for example, Calendar, Contacts, or Inbox). | 1. This error can be reported if the device was restored from an older backup or the user抯 Exchange account was restored or moved to a different server. | 1. Disable and then re-enable ActiveSync for the data types that are being synchronized by clicking on Start, ActiveSync, Tools, Options, Server |
SYNC_3 | N/A | A critical error has occurred and sync failed. The next time you sync, you will be prompted to overwrite the data on your device with data from the server. You will lose only the changes made since your last successful sync. | 1. This error could occur if host headers are being used and the request goes to the wrong Web site. | 1. Verify that host headers are configured correctly. |
MIS_5 | N/A | Synchronization failed due to a server software error. If the problem continues, contact your network administrator.?/font> | 1. Windows Integrated Authentication is not enabled on the Exchange virtual directory on the Exchange server. The Exchange ActiveSync component uses Kerberos authentication when communicating with the Exchange server. 2. Windows Integrated Authentication is enabled on the Exchange virtual directory on the Exchange server, but Kerberos is disabled via the IIS metabase.? 3. Kerberos is enabled, but IIS may return HTTP Status 401 every 30 Days when using Kerberos on Windows 2000. 4. The TMP/TEMP environment variable on the Exchange server is not pointing to a valid directory or there is not enough disk space or the user performing sync does not have access to the TMP/TEMP folder on the Exchange server. For large sync requests, IIS uses temporary storage. 5. Large sync requests could exceed the default size limits for requests sent to IIS. 6. Sync state on the device is corrupt. 7. Synchronization cannot be completed successfully because of a server software error. Contact your network administrator. 8. These errors may occur if you are using a newer version of the sync ROM that is not compatible with the version of Microsoft Server Active Sync (MSAS) on your server. |
1. To enable Integrated Windows Authentication on the Exchange virtual root 2. Re-enable Kerberos on the Exchange server by following the instructions in the KB Article 215383 HOW TO: Configure IIS to Support Both Kerberos and NTLM Authentication 3. If you are using Exchange 2003 with Windows 2000, obtain the hot fix outlined in KB 329938 by calling Microsoft Product Support Services. 4. Verify the TMP/TEMP configuration. 5. The MaxClientRequestBuffer can be increased as outlined in the KB 260694 Description of the MaxClientRequestBuffer Registry Value 6. Deselect the datatype(usually calendar) and then reselect the datatype. |
MIS_8 | N/A | Synchronization of |
1. This error can occur if the synchronization server is unable to open the inbox folder on the Exchange server. This can occur with calendar and contacts as well. 2. The PUT verb is blocked on the Exchange server. |
1. A recovery sync will be performed automatically during a subsequent sync. 2. If UrlScan is configured on the Exchange server, make sure that this verb is allowed on the Exchange server. |
MIS_9 | N/A | Synchronization failed. There is not enough space on your Microsoft Exchange mailbox to synchronize information. Delete old items to increase space and try again. | 1. This error can occur if you are approaching the mailbox limits set on your Exchange server. 2. The TMP/TEMP environment variable on the Exchange server is not pointing to a valid directory or there is not enough disk space or the user performing sync does not have access to the TMP/TEMP folder on the Exchange server. For large sync requests, IIS uses temporary storage. 3. Large sync requests could exceed the default size limits for requests sent to IIS. |
1. Try to delete items in your mailbox to bring it within limits. Contact your Exchange administrator to change the limits on your mailbox. 2. Verify the TMP/TEMP configuration. 3. The MaxClientRequestBuffer can be increased as outlined in the KB 260694 Description of the MaxClientRequestBuffer Registry Value. |
MIS_20 | N/A | A critical error has occurred and sync failed. When you next sync, you will be prompted to overwrite the data on your device with data from the server. This may take several minutes. | 1. This error could occur if there are multiple front-end servers and some of them have not been upgraded. | 1. Sync should recover on its own. |
INTERNET_28 | 80072EF4 | The requested item could not be located. This error is similar to an 揌TTP 404 Page Not Found?error in Internet Explorer. It may be caused by temporary server load conditions. | Try again later.Ensure the device can access Internet sites. | |
SYNC_5 | N/A | Synchronization failed due to a server software error. If the problem continues, contact your network administrator.?/font> | 1. Windows Integrated Authentication is not enabled on the Exchange virtual directory on the Exchange server. The Exchange ActiveSync component uses Kerberos authentication when communicating with the Exchange server. 2. Windows Integrated Authentication is enabled on the Exchange virtual directory on the Exchange server, but Kerberos is disabled via the IIS metabase.? 3. Kerberos is enabled, but IIS may return HTTP Status 401 every 30 Days when using Kerberos on Windows 2000. 4. The TMP/TEMP environment variable on the Exchange server is not pointing to a valid directory or there is not enough disk space or the user performing sync does not have access to the TMP/TEMP folder on the Exchange server. For large sync requests, IIS uses temporary storage. 5. Large sync requests could exceed the default size limits for requests sent to IIS. 6. Sync state on the device is corrupt. |
1. To enable Integrated Windows Authentication on the Exchange virtual root 2. Re-enable Kerberos on the Exchange server by following the instructions in the KB Article 215383 HOW TO: Configure IIS to Support Both Kerberos and NTLM Authentication 3. If you are using Exchange 2003 with Windows 2000, obtain the hot fix outlined in KB 329938 by calling Microsoft Product Support Services. 4. Verify the TMP/TEMP configuration. 5. The MaxClientRequestBuffer can be increased as outlined in the KB 260694 Description of the MaxClientRequestBuffer Registry Value 6. Deselect the datatype(usually calendar) and then reselect the datatype. |
N/A | 86000209 | The error code has to do with the sync key of the folder hierarchy. When you sync a number is exchanged between the device and data end. If you make say 10 changes between 10 different sync's than the device will send 10 back. What is happening is the device is sending back a number that is way off, say 4. | The most common cause of this is resetting the device without adequately flushing the flash file system's RAM cache. To avoid this in the future, press the suspend button before resetting the device. When the device goes into hibernate mode the cache is flushed. (you may want to wait a few seconds after hitting the button to allow the cache to be written). With the smartphone, always turn off the phone, and never yank the battery. The ram cache is flushed to flash during the power off process. |
Try unselecting mail for sync. Then re-enabling it. |
N/A | 80072F17 | Unspported Digital Certificate installed. If you installed a digital certificate that supports wildcards from a certifying digital certificate provider, this certificate will install however using the certificate is not supported. | Replace the digital certificate with one that does not use wildcards and is listed in the root certificate store on the device. | Contact your network administrator for assistance. |
N/A | 85020013 | You see the error message "Your current sync schedule requires a cellular data connection. Please set up a cellular data connection as described in online Help or change the sync schedule." | You are synchronizing via Wi-Fi or Ethernet with a Windows Mobile 5.0 device with AKU2 installed. | The default schedule is to sync Peak and Non-Peak As Items Arrive. Change the setting to Manually for both. Or Configure the cellular connection to provide internet access for synchronization. This requires a data plan and Exchange Server 2003 SP2. |
N/A | 86000108 | "ActiveSync encountered a problem on the server." The device is missing the root digital certificate that is installed on the server.. This is known to have occured with a Verisign digital certificate. or Microsoft ActiveSync cannot synchronize a mailbox if the Microsoft Exchange Server 2003 store contains a corrupted e-mail item. You can see the corrupted item in Microsoft Office Outlook and in Microsoft Office Outlook Web Access. or By design, you receive a "0x86000108" error message when the Read status of a task or a message on a Windows Mobile 5.0 mobile device changes. |
1. Install the Verisign digital certificate on the Windows Mobile 5.0 device. 2. Perform a manual synchronization or complete the task or delete the message. |
1. Copy the certificate to the device. Then navigate to the file and click on it to install the certificate. 2. See ActiveSync cannot synchronize a mailbox if the Exchange Server 2003 store contains a corrupted e-mail item 3. See The Exchange ActiveSync process is unsuccessful, and an error code is returned to the mobile device in Exchange Server 2003 Error message when you use a Windows Mobile 5.0 device to synchronize tasks or messages with a mailbox on Exchange Server 2003 Service Pack 2: "0x86000108" |
N/A | 85030027 | The client is missing the personal digital certificate required to synchronize with Exchange. | Install the personal digital certificate on the Windows Mobile Device. | 1. See the Digital Certificates FAQ for information on how to install the digital certificate. If you have a Windows Mobile 5.0 device with AKU 2.x, contact your OEM for a rom upgrade. 2. See Error message when you use ActiveSync to synchronize a Windows Mobile-based device to Exchange 2003: "0x85030027 -- The Exchange Server requires certificates to log on" |
80070057 | Synchronization failed. If the problem continues, contact your network administrator. | The Exchange server is configured to require client certificates. | On the Exchange server, launch Internet Services Manager. Right click on the Microsoft-Server-ActiveSync virtual directory and choose Properties. Select the Directory Security tab. Click the Edit button in the Secure Communications section and select the option to 揑gnore client certificates.?/font> | |
DEV_5 | N/A | Skippable code errors: error inside device side AirSync protocol, failed to sync an individual items. | Retry synchronization | |
MIS_0 | N/A | SYNC_STATUS_CODE_INVALID | ||
MIS_1 | N/A | SYNC_STATUS_CODE_SUCCESS | ||
MIS_2 | N/A | SYNC_STATUS_CODE_PROTOCOL_VER = AirSync protocol version mismatch | These errors may occur if the client and the server are not using the same protocol version. | 1. Make sure that the Server Sync client update on the device is intended for use with the version of Mobile Information Server on the server. Install either ActiveSyncUpdate.cab from the Pocket PC directory on the MIS 1.5 Enterprise Edition CD-ROM or the latest Pocket PC 2002 update from the maker of your Pocket PC computer. |
MIS_4 | N/A | SYNC_STATUS_CODE_PROTOCOL = AirSync protocol error | Synchronization cannot be completed successfully because of a server software error. Contact your network administrator. | |
MIS_6 | N/A | SYNC_STATUS_CODE_CONVERSION = Error in the Client/Server conversion | ||
MIS_7 | N/A | SYNC_STATUS_CODE_CONFLICT = Conflict between the matching Client and Server object | ||
HTTP_505 | N/A | E_HTTP_VERSION_NOT_SUP | ||
INTERNET_49 | N/A | ERROR_INTERNET_DIALOG_PENDING | ||
INTERNET_48 | N/A | ERROR_INTERNET_REDIRECT_SCHEME_CHANGE | ||
INTERNET_47 | N/A | ERROR_INTERNET_ASYNC_THREAD_FAILED | ||
INTERNET_46 | N/A | ERROR_INTERNET_CLIENT_AUTH_NOT_SETUP | ||
INTERNET_50 | N/A | ERROR_INTERNET_RETRY_DIALOG | ||
INTERNET_52 | N/A | ERROR_INTERNET_HTTPS_HTTP_SUBMIT_REDIR | ||
INTERNET_53 | N/A | ERROR_INTERNET_INSERT_CDROM | ||
N/A | 80072F0D | The security certificate on the server is invalid. Contact your Exchange Server administrator or ISP to install a valid certificate on the server. | This issue occurs because an intermediate certification authority (CA) certificate is not present on the device or on the Exchange Server server with which you are synchronizing. Windows Mobile-based devices do not generally contain intermediate CA certificates in their certificate store. Internet Information Services (IIS) will send the whole certificate chain to the device. However, IIS will do this only if it can verify the whole chain. By default, the device does not contain these certificates. Therefore, the server must send them. The device must contain only the root certificate in its certificate store. Frequently, this issue occurs with GoDaddy certificates because either the root CA certificate or the intermediate CA certificate is missing from the certificate store on the server that is running Windows Server 2003. Frequently, this issue occurs with VeriSign certificates because the intermediate CA certificate in the certificate store on the Windows Server 2003 server is expired. |
1. See Error message when you try to synchronize a Windows Mobile-based device by using Exchange ActiveSync for Exchange 2003 or for Exchange 2007: "Synchronization failed" 2. See Error message when you use ActiveSync to synchronize a Windows Mobile 5.0-based device: "The security certificate on the server is invalid" |
Errors received after a synchronization.
attempt on the device have error codes appended to them. These codes help determine the source of the error. The errors are one of the following types:
Error code | Descirption |
DEV_errorcode | This error code indicates that the error was from the Server ActiveSync client on the device. |
MIS_errorcode | This error code indicates that the error was from the Mobile Information Server with the Server ActiveSync component installed |
SYNC_errorcode | This error code indicates that the error was from the Exchange 2003 server. MIS_errorcode errors were replaced with SYNC_errorcode errors on Windows Mobile 2003-based devices. |
HTTP_errorcode | Standard HTTP error (Internet related) |
CONNMGR_errorcode | Connection Manager error |
INTERNET_errorcode | Standard WinInet error (Internet related) |
HEX errorcode |
Author:冯峰(AppleSeeker)
Date:2008-12-11