XADM: Multi-Valued String Array MAPI Property is Not Being Copied from Store to Store

ID: Q234869

The information in this article applies to:

Microsoft Exchange Server, versions 5.0, 5.5

SYMPTOMS

When a message containing a multi-valued string array MAPI property is moved or copied from one information store database to another, the MAPI property values are not properly copied. If the message has a custom-form that relies on the data carried in the MAPI property, the form may be displayed with unexpected results.

CAUSE

The information store that is the source of the move is not properly handling empty array elements.

RESOLUTION

Exchange Server 5.0

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Microsoft Exchange Server version 5.0 service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp

The English version of this fix should have the following file attributes or later:

Component: Information Store

File name	Version
Store.exe	5.0.1462.2
Mdbmsg.dll	5.0.1462.2

Exchange Server 5.5

To resolve this problem, obtain the latest service pack for Exchange Server version 5.5. For additional information, please see the following article in the Microsoft Knowledge Base:

Q191014 XGEN: How to Obtain the Latest Exchange Server 5.5 Service Pack

The English version of this fix should have the following file attributes or later:

Component: Information Store

File name	Version
Store.exe	5.5.2632.0
Mdbmsg.dll	5.5.2632.0
Netif.dll	5.5.2632.0
Gapi32.dll	5.5.2632.0
Dsamain.exe	5.5.2600.0
Perfdsa.dll	5.5.2600.0

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.0 and 5.5. This problem was first corrected in Exchange Server 5.5 Service Pack 3.

Additional query words:

Keywords : exc5 exc55
Version : winnt:5.0,5.5
Platform : winnt
Issue type : kbbug