An update is available to configure Exchange ActiveSync in Exchange Server 2003 Service Pack 1 to no longer validate fields that a client device synchronizes

Article translations Article translations
Article ID: 885465 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

On This Page

INTRODUCTION

This article discusses a software update that you can apply to configure Exchange ActiveSync in Exchange Server 2003 Service Pack 1 (SP1) to no longer validate fields that a client device synchronizes. After you apply this software update, Exchange Server 2003 SP1 behaves like the original release version of Exchange 2003, with regard to the Microsoft Exchange ActiveSync protocol.

The Exchange ActiveSync protocol is designed to let a user synchronize a contact list between a client device and the computer that is running Exchange 2003. When a contact is updated on the device and a synchronization operation is performed, the device must send the contents of every field that it supports, not just the changed fields. If data for a particular field is missing, Exchange 2003 determines that the client device wants to remove that data from the server. However, because the information in the Body field of a contact can be very large, the information may not be able to be stored completely on the device. Additionally, this process uses additional network bandwidth to synchronize contact information that was not updated. Therefore, the Exchange ActiveSync protocol was designed with special support for the Body field to avoid having data truncated on the server. If the Body field is not sent from the client device to the Exchange computer when a contact is updated, the server retains the existing information in the Body field of that contact instead of removing it.

The Exchange ActiveSync protocol lets a client device negotiate with the server regarding the fields that the device supports. If a device does not support all the fields that are available in the Exchange ActiveSync protocol, it can notify Exchange 2003 during the initial device synchronization. During this initial synchronization, the client device tells Exchange 2003 which fields the client device supports. If the client device does not perform this optional negotiation, Exchange 2003 determines that this device supports all the fields in the Exchange ActiveSync protocol. For more information about the latest service pack for Exchange Server 2003, click the following article number to view the article in the Microsoft Knowledge Base:
836993 How to obtain the latest service packs for Exchange Server 2003

More information

The original release version of Exchange 2003 has a problem with how the field negotiation commands interact with features that are designed to prevent the truncation of data in the Body field. In the original release version of Exchange 2003, if a client device indicates that it supports the Exchange ActiveSync Body field during the negotiation phase of the synchronization process, Exchange 2003 incorrectly determines that the client device will send the Body field of the contact on every synchronization operation. This error condition prevents the client device from sending only the Body field of a contact if the information in that Body field is updated.

To work around this problem in the original release version of Exchange 2003, you must configure the client device to notify Exchange 2003 that the client device does not support the Exchange ActiveSync Body field. In this scenario, Exchange 2003 behaves correctly. After you perform this workaround, Exchange 2003 lets the client device send the Body field if the device determines that this is required. But if the device does not send the Body field, the original release version of Exchange 2003 retains the existing information in the Body field of that contact.

Exchange Server 2003 SP1 has a new feature to make sure that the Exchange client device only sends the fields that the client device had indicated that it supports. In this scenario, if the client device sends a field that it had not indicated that it supports, the synchronization of that record is not successful. When this issue occurs, a status code 6 error result is returned. A status code 6 error result has the following description:
Error in client/server conversion
Consider the following scenario:
  • You have a device that negotiates the Exchange ActiveSync fields that it supports with the Exchange 2003 computer.
  • You want to synchronize the Body field of a contact from the device to Exchange 2003.
  • You do not want Exchange 2003 to truncate the information from the Body field of the contact if you do not change the information in the Body field of that contact.
This Exchange Server 2003 SP1 feature does not enable this scenario to be successfully completed.

This update is intended to resolve this issue by causing Exchange Server 2003 SP1 to have the same behavior as the original release version of Exchange 2003, with regard to the Exchange ActiveSync protocol.

Update information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

Because of file dependencies, you must be running Exchange Server 2003 SP1 to install this update. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
836993 How to obtain the latest service packs for Exchange Server 2003

Restart requirement

You do not have to restart your computer after you apply this update.

Update replacement information

This update does not replace any other updates.

File information

The English version of this update has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version           Size     File name
   ----------------------------------------------------------
   11-Nov-2004  21:11  3.0.4216.0        518,656  Massync.dll

Update installation information

After you install this update, Exchange Server 2003 SP1 no longer tries to validate the Exchange ActiveSync fields that a client device sends to Exchange Server 2003 SP1.

More information

For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
817903 New naming schema for Exchange Server software update packages

Properties

Article ID: 885465 - Last Review: November 1, 2013 - Revision: 5.0
Applies to
  • Microsoft Exchange Server 2003 Service Pack 1
Keywords: 
kbnosurvey kbarchive kbautohotfix kbqfe kbhotfixserver kbfix kbbug KB885465

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com