Audit event 560 unexpectedly uses the 8.3 file name format to display the name of a deleted file in Windows 2000

This article has been archived. It is offered "as is" and will no longer be updated.
Symptoms
Consider the following scenario. You configure a Microsoft Windows 2000-based computer to audit files and folders. Then, at a command prompt, you delete a file that has a long file name. However, when you open audit event 560 in Event Viewer, you notice that the Object Name field unexpectedly uses the 8.3 file name format to display the name of the deleted file.

For example, audit event 560 may resemble the following in Event Viewer:

Event Type: Success AuditEvent Source: SecurityEvent Category: Object AccessEvent ID: 560Date: DateTime: TimeUser: UserNameComputer: ComputerNameDescription:Object Open:	Object Server: Security	Object Type: File	Object Name: Drive:\Path\Sample~1.EXE	New Handle ID: 92	Operation ID: {0,16979818}	Process ID: 1960	Primary User Name: administrator	Primary Domain: DomanName	Primary Logon ID: (0x0,0x19116)	Client User Name: -	Client Domain: -	Client Logon ID: -	Accesses DELETE		ReadAttributes	Privileges –

Note When you use Windows Explorer to delete a file that has a long file name, the Object Name field in audit event 560 displays the complete file name.
Resolution

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.

Prerequisites

You must have Windows 2000 Service Pack 4 installed to apply 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 file attributes) 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 item in Control Panel.
File nameFile versionFile sizeDateTimePlatform
Cmd.exe5.0.2195.6920236,30405-Apr-200418:06x86
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More information
For more information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:
816915 New file naming schema for Microsoft Windows software update packages
For more information, 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
Properties

Article ID: 839094 - Last Review: 11/02/2013 15:40:00 - Revision: 3.0

  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Professional Edition
  • Microsoft Windows 2000 Advanced Server
  • kbnosurvey kbarchive kbautohotfix kberrmsg kbbug kbfix kbhotfixserver kbqfe kbwin2000presp5fix KB839094
Feedback