MSDSS Migration Does Not Work If Multiple Naming Attributes Are Present for an Object (270159)
The information in this article applies to:
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
This article was previously published under Q270159 SYMPTOMS
When you perform a migration from Novell Directory Services (NDS) to Active Directory by using Microsoft Directory Synchronization Services (MSDSS), the migration process may stop unexpectedly and you may receive the following error message:
Windows cannot run the initial reverse synchronization or migration session, the ADSI path was not found.
CAUSE
This problem occurs when MSDSS encounters an object with multiple naming attributes set. For example, this problem can occur if the following naming attributes are set for the object:
CN=Obj1+Bindery Type=1
OU=SubOU2
OU=OU1
O=ORG
RESOLUTIONTo resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
The English-language version of this fix should have the following file attributes or later:
Date Time Version Size File name
--------------------------------------------------------
10/15/2000 6:51PM 5.0.2195.2487 40.2KB Ndsread.dll
WORKAROUND
Use the following procedure to identify all of the objects with +Bindery set, and move them to an OU that will be excluded from the migration.
To find all objects that have a "Bindery Type" attribute, click the tree root ([Root]) in the Novell NetWare Administrator program (Nwadmin.exe), and then click Search on the Object menu. In the Attributes box, click the Bindery Type attribute, and then click Search for all of the objects that contain that attribute. Depending on your local area network (LAN) or wide area network (WAN) setup, this procedure can take hours or, in some cases, days; however, most of these objects should be in the primary Bindery Context container, which is typically the root "O" container.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 2.
Modification Type: | Minor | Last Reviewed: | 9/26/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbbug kbenv kbfix kbWin2000PreSP2Fix KB270159 |
---|
|