The Windows 2000 Ntbackup Program May Stop Responding (291562)


The information in this article applies to:

  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Professional
  • Microsoft Windows NT Server 4.0
  • Microsoft Windows NT Workstation 4.0
  • Microsoft Windows NT Server, Enterprise Edition 4.0
This article was previously published under Q291562

SYMPTOMS

If you enable detailed logging, the Ntbackup program may stop responding during a backup operation. The Windows NT backup graphical user interface (GUI) seems to display a file in the process of being backed up, however, Task Manager displays information that the Ntbackup program is not responding. You can use Task Manager to end the Ntbackup task. If you attempt to restore any information from the tape that you just created, the restore process is unsuccessful. However, if you switch the logging level to "summary" or "none", the backup process runs without any errors.

CAUSE

This problem can occur because there is a file with an invalid file name on the drive that is being backed up. The Ntbackup program can backup the file successfully, but the program is unable to write the file name to the log file.

RESOLUTION

To work around this problem, lower the backup logging level to "summary" or disable the logging, which can enable the Ntbackup program to complete without any errors. A more permanent solution is to rename or delete the file with the invalid file name. When the backup process stops responding, it can display a file name in the status window. The backup process can seem to be backing up that file. Typically, the file that is displayed is not the file that causes the problem. The file that causes the problem is usually the next file (going by alphabetical order) in the same folder as the file that is displayed. You can use Windows Explorer to rename this file or you can temporarily move it to a different drive, and then test if the backup process has completed successfully.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Modification Type:MinorLast Reviewed:1/27/2006
Keywords:kbprb KB291562
©2004 Microsoft Corporation. All rights reserved.