Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. How to troubleshoot server ActiveSync HTTP error codes

How to troubleshoot server ActiveSync HTTP error codes

View products that this article applies to.

Introduction

When you synchronize a Pocket PC device with a computer that is running Microsoft Mobile Information Server, you may receive a synchronization error code. Or, the NexTags log file may list error codes. This article describes some of the common HTTP_error_code errors and the methods to resolve these errors.

↑ Back to the top

More information

The following error codes are standard HTTP errors:
  • HTTP_401

    This error code corresponds to the E_HTTP_DENIED error. This is described as the following error message:
    Unable to connect to sync server due to authentication failure. Check your connection configuration.
    This issue may occur if the credentials that are provided to access the server are incorrect. Or this issue may occur if the user is not enabled for synchronization.

    To troubleshoot this issue, follow these steps:
    1. On the Pocket PC device, clickStart, clickActiveSync, clickOptions on the Tools menu, and then click the Server tab. Make sure that the correct server information appears in the Server Name box.
    2. Click theAdvanced tab, and then make sure that the correct user name, password, and domain information is located in the corresponding boxes.
    3. On the domain controller, right-click the user account, and then click Properties.
    4. Click the Wireless Mobility tab, and then click to select the Allow this user to synchronize Microsoft Exchange data with their device using Mobile Information Server check box.
    5. Click Apply, and then click OK.
  • HTTP_404

    This error code corresponds to the E_HTTP_NOT_FOUND error. This error code may not appear on the Pocket PC device. However, it may appear in the NexTags log file when you use the NexTags tool to configure the logging to be generated by the Server ActiveSync component of Outlook Mobile Access.

    The Pocket PC Sync Log displays the following information: 
     =-=-=-= Server Response =-=-=-
HTTP/1.1 500 Internal Server Error
    The NexTags log file displays information that is similar to the following: 
    04/23/02 11:34:51 Dump of HTTP request.
	PROPFIND /exchange/Firstname.Lastname2/ HTTP/1.1
	Host: Server1
	User-Agent: Microsoft-Server-ActiveSync/1.0.1806.0
	Brief: t
	Accept-Language: en-us
	Content-Type: text/xml
	Depth: 0
	Content-Length: 250
	Connection: Keep-Alive

04/23/02 11:34:52 Dump of HTTP response.
	HTTP/1.1 404 Resource Not Found
	Server: Microsoft-IIS/5.0
	Date: Tue, 23 Apr 2002 11:34:52 GMT
	Connection: close
	WWW-Authenticate: Negotiate	Content-Type: text/html
	Content-Length: 53
	MS-WebStorage: 6.0.5762
    The user account information may be similar to the following:
    ProxyAddresses:
    SMTP:Firstname.Lastname2@example.com;
    smtp:Firstname.Lastname@domain.example.com;
    smtp:flastname-w@domain.example.com;
    x500:/O=ORG/OU=FIRST ADMINISTRATIVE GROUP/CN=RECIPIENTS/CN=flastname;
    x500:/O=ORG/OU=FIRST ADMINISTRATIVE GROUP/CN=RECIPIENTS/CN= flastname -w; X500:/O=Exchange/OU=Mobile/cn=Recipients=/cn=lastname;
    X400:c=us;a= ;p=org;o=Exchange;s=Lastname;g=Firstname;
    userPrincipalName: flastname-w@domain.example.com;
    mail: Firstname.Lastname2@example.com;
    The "HTTP_404 - Resource Not Found" error message indicates that an issue may exist with the user account. To troubleshoot this issue, follow these steps:
    1. Make sure that the user has an e-mail address that matches the Exchange default recipient policy and is the same as NexTags log reports. For example,
      NexTags log: PROPFIND /exchange/Firstname.Lastname2/ HTTP/1.1
      Default Recipient Policy: @domain.example.com
      This information indicates that the wireless user flastname-w must have an SMTP address of Firstname.Lastname2@domain.example.com. The Server ActiveSync uses the bit to the left of the @ symbol in the primary SMTP address, appends the default recipient policy, and then searches for that user and their associated mailbox.
    2. Make sure that the user can log on to the mailbox by using Microsoft Outlook Web Access (OWA).
  • HTTP_500

    This error code corresponds to the E_HTTP_SERVER_ERROR error. This is described as the following error message:
    Synchronization failed due to an error on the server. Try again.
    This behavior may occur for one or more of the following reasons:
    • The Internet Information Service is unavailable.
    • Windows Integrated Authentication is not enabled on the Exchange Server virtual directory of the server where the mailbox of the user resides.
    • Synchronization is tried when the mailbox is being moved.
    To resolve this issue, use one of the following methods:
    • Retry the synchronization later.
    • Restart the Exchange server to reset user authentication.
    Additionally, when you use a Pocket PC device together with Microsoft Exchange 2003, the NexTags.log file displays information that is similar to the following: 
    02/16/05 12:05:42 Dump of HTTP response for user UserName HTTP/1.1 400 Bad Request
	Content-Type: text/html
	Date: Wed, 16 Feb 2005 12:05:37 GMT
	Connection: close
	Content-Length: 46
	 
	Bad Request (Request Header Too Long)
    Typically, this issue occurs when the user is a member of more than 120 groups in Active Directory. In this case, the user may be unable to authenticate because the Kerberos token that is generated during the authentication attempt has a fixed maximum size. When the buffer that is determined by the MaxTokenSize registry value is not large enough, the user cannot be authenticated. Then, the user may receive the following error message:
    Out of memory
    Note In the original release of Microsoft Windows 2000 Server, the MaxTokenSize value is 8,000 bytes. In Windows 2000 Server with Service Pack 2 (SP2) and in Microsoft Windows Server 2003, the MaxTokenSize value is 12,000 bytes.

    To resolve this issue, use the Tokensz.exe utility to determine the MaxTokenSize value of a user. If the Max Token size is greater than 12,000,set the MaxTokenSize value to a bigger value. For more information about how to use the Tokenz.exe utility to determine the maximum token and to download the Tokenz.exe utility, visit the following Microsoft Web site:
    http://www.microsoft.com/downloads/details.aspx?FamilyID=4a303fa5-cf20-43fb-9483-0f0b0dae265c&DisplayLang=en
    For more information about how to change the MaxTokenSize registry value, click the following article number to view the article in the Microsoft Knowledge Base:
    327825 New resolution for problems that occur when users belong to many groups


    Moreover, when Exchange Server Active Sync is not completed, you can receive an HTTP 500 error code.

    Exchange Server ActiveSync and Exchange Outlook Mobile Access (OMA) use the /Exchange virtual directory to access OWA templates and Distributed Authoring and Versioning (DAV) on the Exchange back-end server. This is where the mailbox of the user is located. Server ActiveSync and OMA cannot access this virtual directory if one of the following conditions is true:
    • The /Exchange virtual directory on an Exchange back-end server is configured to require Secure Socket Layer (SSL).
    • Forms-based authentication is enabled.
    This issue does not occur when you enable these settings on the /Exchange virtual directory on a front-end server

    To resolve this issue, use the Metaedit tool. For more information about how to obtain and install the Metadata tool, click the following article number to view the article in the Microsoft Knowledge Base:
    232068 How to download, install, and remove the IIS Metaedit 2.2 utility
    To resolve this issue, follow these steps:
    1. Open the Metabase Editor (MetaEdit) tool. To do this, click Start, point to Programs, point to Administrative Tools, and then click Metaedit.
    2. In Metaedit, expand theLM/W3SVC/1/Root/Exchange folder, and then click Exchange,
    3. On the Metabase menu, click Export Text File, and then click Yes in the Metaedit dialog box.
    4. In the file name box, type Exchange-OMA, and then click Save.
    5. In the Metaedit dialog box, click Yes.
    6. In the Metaedit dialog box, click OK.
    7. Locate and then open the Exchange-OMA.txt file.
    8. Locate the line that resembles the following: [/LM/W3SVC/1/Root/Exchange]. This is line number 6.
    9. Type -OMA after Exchange so that the line resembles the following:
      [/LM/W3SVC/1/Root/Exchange-OMA]
    10. On the File menu, click Save.
    11. On the File menu, click Exit.
    12. In Metabase Editor, click the following folder:
      LM/W3SVC/1/Root/Exchange
    13. On the Metabase menu in Metabase Editor, click Import Text File.
    14. In the Metaedit dialog box, click Yes.
    15. In the Open dialog box, click the Exchange-OMA file, and then click Open.
    16. In the Metaedit dialog box, click No.
    17. In the Metaedit dialog box, click Yes.
    18. In the Metaedit dialog box, click OK.
    19. Expand the following folder:
      LM/W3SVC/1/Root/Exchange
    20. Verify that the following folders exist in the Exchange folder:
      LM/W3SVC/1/Root/Exchange/Exchange-OMA
    21. Open Internet Information Server (IIS) Manager, and then verify that the Exchange-OMA folder exists under Default Web site.
  • HTTP_502

    This error code corresponds to the E_HTTP_BAD_GATEWAY error. This is is described as the following error message:
    Synchronization failed due to an error on the server.
    This issue may occur if the Pocket PC device uses a proxy server to connect to the ActiveSync Server, and then the proxy server experiences an error.

    To resolve this issue, connect to the ActiveSync Server by using a different proxy server.Or troubleshoot connection issues on the proxy server.
For additional information about error messages in Microsoft Mobile Information Server, obtain the Errors.chm file. To download this file, visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?familyid=3c573d9e-e868-4d3b-b004-beded85b9fbd&displaylang=en
To view the updated release notes for Mobile Information Server 2002, visit the following Microsoft Web site:
ttp://www.microsoft.com/downloads/details.aspx?FamilyID=3C573D9E-E868-4D3B-B004-BEDED85B9FBD&displaylang=en
For more information about other HTTP error codes, click the following article number to view the article in the Microsoft Knowledge Base:
318380 Description of Microsoft Internet Information Services (IIS) 5.0 and 6.0 status codes

↑ Back to the top

Keywords: KB330463, kbinfo, kbtshoot

↑ Back to the top

Article Info
Article ID : 330463
Revision : 7
Created on : 10/25/2007
Published on : 10/25/2007
Exists online : False
Views : 524