Knowledge Base

You receive a "There is a naming violation" error message when you try to rename a user's name in an LDAP provider

Article ID: 834541

Article Last Modified on 10/26/2006

APPLIES TO

Microsoft Windows 2000 Server
Microsoft Windows 2000 Professional Edition
Microsoft Windows 2000 Advanced Server

SYMPTOMS

If you type an LDAP special character (such as a back-slash) when you try to rename a user's name in an LDAP provider, you may receive the following error message:

There is a naming violation

CAUSE

This problem may occur after you install Windows 2000 Service Pack 4 (SP4). In versions of Windows 2000 before SP4, you must use a back-slash character to escape an LDAP special character.

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

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 usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

You must install Microsoft Windows 2000 Service Pack 3 before installing this hotfix.

Restart requirement

You do not have to restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix 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.

   Date         Time   Version        Size       File name
   ----------------------------------------------------------
   08-Jan-2004  23:38  5.0.2195.6890    124,688  Adsldp.dll       
   08-Jan-2004  23:38  5.0.2195.6890    132,368  Adsldpc.dll      
   08-Jan-2004  23:38  5.0.2195.6890     63,760  Adsmsext.dll     
   08-Jan-2004  23:38  5.0.2195.6876    381,712  Advapi32.dll     
   08-Jan-2004  23:38  5.0.2195.6866     69,904  Browser.dll      
   08-Jan-2004  23:38  5.0.2195.6824    136,464  Dnsapi.dll       
   08-Jan-2004  23:38  5.0.2195.6876     96,528  Dnsrslvr.dll     
   08-Jan-2004  23:38  5.0.2195.6883     47,376  Eventlog.dll     
   08-Jan-2004  23:38  5.0.2195.6890    148,240  Kdcsvc.dll       
   08-Dec-2003  23:28  5.0.2195.6881    206,096  Kerberos.dll     
   21-Sep-2003  00:32  5.0.2195.6824     71,888  Ksecdd.sys
   08-Dec-2003  23:30  5.0.2195.6881    511,248  Lsasrv.dll       
   08-Dec-2003  23:30  5.0.2195.6881     33,552  Lsass.exe        
   17-Oct-2003  00:33  5.0.2195.6866    114,960  Msv1_0.dll       
   08-Jan-2004  23:38  5.0.2195.6866    307,984  Netapi32.dll     
   08-Jan-2004  23:38  5.0.2195.6883    361,744  Netlogon.dll     
   08-Jan-2004  23:38  5.0.2195.6884    931,600  Ntdsa.dll        
   08-Jan-2004  23:38  5.0.2195.6876    392,464  Samsrv.dll       
   08-Jan-2004  23:38  5.0.2195.6824    113,936  Scecli.dll       
   08-Jan-2004  23:38  5.0.2195.6824    259,856  Scesrv.dll       
   06-Nov-2003  22:29  5.0.2195.6870  5,847,552  Sp3res.dll       
   08-Jan-2004  23:38  5.0.2195.6824     48,912  W32time.dll      
   21-Sep-2003  00:32  5.0.2195.6824     57,104  W32tm.exe        
   08-Jan-2004  23:38  5.0.2195.6869    126,224  Wldap32.dll      
   08-Jan-2004  23:50                    14,196  Kb834541.cat

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.

MORE INFORMATION

If the new user name contains an escaped LDAP special character, you may receive the following error message:

for decimal 8247 / hex 0x2037 : ERROR_DS_NAMING_VIOLATION winerror.h # There is a naming violation. # 1 matches found for "8247"

Note This error occurs in the IADsContainer::MoveHere method.

LDAP special characters include the following characters:

A space at the start of a string
A space at the end of a string
A number sign (#) at the beginning of a string
Any one or more of the following characters anywhere in the string:
- comma (,)
- plus sign (+)
- double quote (")
- backslash (\)
- angle brackets (< or >)
- semicolon (;)

For additional information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:

816915 New naming schema for Microsoft Windows software update packages

For additional information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Keywords: kbhotfixserver kbqfe kbbug kbfix kbwin2000presp5fix kbqfe KB834541

Microsoft KB Archive/834541

Contents