Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
XFOR: A Single-Step Migration from GroupWise Does Not Work If a User Has a Field That Contains Multiple Values
Article ID: 299716 - View products that this article applies to.
This article was previously published under Q299716
If you use the Migration Wizard to migrate Novell GroupWise user objects to Exchange 2000 Server, you may receive the following error message:
Event 15002 - MS Exchange MIG - Directory import failure, the number of fields in the value does not match the number of attributes in the header.
This problem may occur if a GroupWise user object contains an entry with multiple lines that are separated by carriage returns. The Migration Wizard parses the multiple lines and reads the carriage returns as separate fields. If this problem occurs, the migration does not work because the user object contains too many properties to migrate to Exchange 2000 user attributes.
To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/301378/EN-US/ )XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
The English version of this fix has the file attributes (or later) 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.
Collapse this tableExpand this table
NOTE: Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 1.
WORKAROUNDTo work around this problem, before you run the Migration Wizard, open the user object in the GroupWise administrator console, and then change the property so that there are no carriage returns in the description of the property.
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 2.