MSDSS Migration Does Not Work If Multiple Naming Attributes Are Present for an Object

Article translations Article translations
Article ID: 270159 - View products that this article applies to.
This article was previously published under Q270159
This article has been archived. It is offered "as is" and will no longer be updated.
Notice
This article contains a reference to the MDSS utility, which is a utility that Microsoft Support provides as-is and does not support. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of the MDSS utility.
Expand all | Collapse all

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

Resolution

To 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.

Status

Microsoft 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.

More information

For additional information about how to install Windows 2000 and Windows 2000 hotfixes at the same time, click the article number below to view the article in the Microsoft Knowledge Base:
249149 Installing Microsoft Windows 2000 and Windows 2000 Hotfixes
The plus sign (+) indicates that the object is named by more than one naming attribute. Here, both the CN and the Bindery Type attributes are combined to create a unique object name. Therefore, the name is CN=x+Bindery Type=y. This object was given its name when it was migrated from the NetWare 3.x bindery to NDS. You can give other objects multiple naming attributes when you create them in NWAdmin by specifying the name in the form x+y, which would assign x to the CN attribute and x to the OU attribute, giving the object a name of CN=x+OU=y. You can set a plus sign in a name by escaping the character with a back slash (\). Names with a plus sign are migrated by MSDSS. MSDSS has been modified to log an error with the name of the object that causes the error.

Properties

Article ID: 270159 - Last Review: November 2, 2013 - Revision: 4.0
Applies to
  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
Keywords: 
kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbenv kbfix kbwin2000presp2fix KB270159

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