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.

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


View products that this article applies to.

This article was previously published under Q234869

↑ Back to the top


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.

↑ Back to the top


Cause

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

↑ Back to the top


Resolution

Exchange Server 5.0

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft Exchange Server version 5.0 service pack that contains this hotfix.

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 about support costs, visit the following Microsoft Web site:NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

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

Component: Information Store

Collapse this tableExpand this table
File nameVersion
Store.exe5.0.1462.2
Mdbmsg.dll5.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, click the following article number to view the article in the Microsoft Knowledge Base:
191014� 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

Collapse this tableExpand this table
File nameVersion
Store.exe5.5.2632.0
Mdbmsg.dll5.5.2632.0
Netif.dll5.5.2632.0
Gapi32.dll5.5.2632.0
Dsamain.exe5.5.2600.0
Perfdsa.dll5.5.2600.0

↑ Back to the top


Status

Microsoft has confirmed that this is 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.

↑ Back to the top


Keywords: KB234869, kbqfe, kbfix, kbexchange500presp3fix, kbbug, kbqfe, kbhotfixserver

↑ Back to the top

Article Info
Article ID : 234869
Revision : 7
Created on : 10/26/2006
Published on : 10/26/2006
Exists online : False
Views : 357