Directory Service Access Audits for a SAM Object Server Have Incomplete Object Names

This article was previously published under Q319672
This article has been archived. It is offered "as is" and will no longer be updated.
Audit events (event ID 565) for directory service access may contain truncated distinguished names for the Object Name entries. This problem may occur if the object server is "Security Account Manager."

This is an example of an audit with a truncated object name:
Event Type: Success Audit
Event Source: Security
Event Category: Directory Service Access
Event ID: 565
Date: 25/02/2002
Time: 13:19:39
Object Open:
Object Server: Security Account Manager
Object Type: SAM_SERVER
Object Name: CN=Server,CN=Syst
New Handle ID: 11698960
Operation ID: {0,174552766}
Process ID: 324
Primary User Name: SAMPLEDCNAME$
Primary Domain: SAMPLEDOM
Primary Logon ID: (0x0,0x3E7)
Client User Name: SAMPLEDCNAME$
Client Domain: SAMPLEDOM
Client Logon ID: (0x0,0x3E7)
In this example, the object name is truncated to "CN=Server,CN=Syst. It should be "CN=Server,CN=System,DC=domainname,DC=com."
The object name length is set to the number of characters, instead of to the number of bytes. The distinguished name is stored as Unicode, which causes only half of the string to be processed.

Service Pack Information

To resolve this problem, obtain the latest service pack for Microsoft 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

Hotfix Information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. The English version of this fix should have the following file attributes or later:
   Date         Time   Version        Size     File name   --------------------------------------------------------   15-Apr-2002  14:46  5.0.2195.4959  123,664  Adsldp.dll   29-Jan-2002  17:52  5.0.2195.4851  130,832  Adsldpc.dll   29-Jan-2002  17:52  5.0.2195.4016   62,736  Adsmsext.dll   15-Apr-2002  14:46  5.0.2195.5201  356,624  Advapi32.dll   15-Apr-2002  14:46  5.0.2195.4985  135,952  Dnsapi.dll   15-Apr-2002  14:46  5.0.2195.4985   95,504  Dnsrslvr.dll   15-Apr-2002  14:46  5.0.2195.5246  145,680  Kdcsvc.dll   22-Mar-2002  16:50  5.0.2195.5246  199,952  Kerberos.dll   07-Feb-2002  12:35  5.0.2195.4914   71,024  Ksecdd.sys   06-Apr-2002  17:13  5.0.2195.5544  503,568  Lsasrv.dll   06-Apr-2002  17:14  5.0.2195.5544   33,552  Lsass.exe   07-Dec-2001  17:05  5.0.2195.4745  107,280  Msv1_0.dll   15-Apr-2002  14:46  5.0.2195.4917  306,960  Netapi32.dll   15-Apr-2002  14:46  5.0.2195.4979  360,208  Netlogon.dll   15-Apr-2002  14:46  5.0.2195.5561  917,264  Ntdsa.dll   15-Apr-2002  14:46  5.0.2195.5585  386,832  Samsrv.dll   29-Jan-2002  17:52  5.0.2195.4874  128,784  Scecli.dll   15-Apr-2002  14:46  5.0.2195.5582  299,792  Scesrv.dll   15-Apr-2002  14:46  5.0.2195.5525   48,400  W32time.dll   02-Apr-2002  17:51  5.0.2195.5525   56,592  W32tm.exe   15-Apr-2002  14:46  5.0.2195.5011  125,712  Wldap32.dll				

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 Microsoft Windows 2000 Service Pack 4.
More information
For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:
265173 The Datacenter Program and Windows 2000 Datacenter Server Product
For additional information about how to install multiple hotfixes with only one reboot, click the article number below to view the article in the Microsoft Knowledge Base:
296861 Use QChain.exe to Install Multiple Hotfixes with One Reboot

Article ID: 319672 - Last Review: 10/26/2013 08:08:00 - Revision: 5.0

  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
  • kbnosurvey kbarchive kbautohotfix kbhotfixserver kbqfe kbdirservices kbwin2ksp4fix kbbug kbfix kbwin2000presp4fix KB319672