The NTBackup.exe tool stops responding if there are lots of registry entries under the FilesNotToBackup subkey on a Windows Server 2003-based computer

Consider the following scenario:

• On a Windows Server 2003-based computer, you use the Backup tool (NTBackup.exe) to perform a backup.
• This backup does not include the system state data.

In this scenario, the backup process stops responding when the following status message is displayed: Therefore, you cannot complete the backup. Additionally, the following event may be logged in the Application log:

Event Type: Error
Event Source: Application Hang
Event Category: (101)
Event ID: 1002
Date: <Date>
Time: <Time>
User: N/A
Computer: <Computer name>
Description:
Hanging application ntbackup.exe, version 5.2.3790.3959, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

This problem occurs if the registry entries under the following subkey total more than 65,536 characters:This situation typically occurs when there are lots of registry entries under the FilesNotToBackup subkey. In a typical scenario, these registry entries are generated by the Distributed File System Replication (DFSR) service.

This problem occurs because the NTBackup.exe tool incorrectly indexes registry entries under the FilesNotToBackup subkey. If there are too many registry entries exist under the FilesNotToBackup subkey, this may trigger an overflow situation.

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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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

To apply this hotfix, you must have Windows Server 2003 Service Pack 1 or Windows Server 2003 Service Pack 2 installed. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Restart requirement

You do not have to restart the 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.

Windows Server 2003 with Service Pack 1, x86-based versions

Windows Server 2003 with Service Pack 2, x86-based versions

Windows Server 2003 with Service Pack 1, Itanium-based versions

Windows Server 2003 with Service Pack 2, Itanium-based versions

Windows Server 2003, x64-based versions

Windows Server 2003 with Service Pack 2, x64-based versions

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

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