NTBACKUP Writes Incorrect Year to Log File

This article was previously published under Q216916
This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
When you set the Long Date Style or Short Date Style in the Regional Settings to use a four digit year, the Ntbackup.exe tool may substitute the year 1900 in the backup log file when the system date is set for the year 2000.
RESOLUTION

Windows NT 4.0

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack

The English version of this post-SP3 hotfix has been posted to the following Internet location.

Windows NT 3.51

A supported fix that corrects this problem is now available from Microsoft,but has not been fully regression tested and should be applied only tosystems experiencing this specific problem.

To resolve this problem immediately, download the fix as described below.For a complete list of Microsoft Product Support Services phone numbers andinformation on support costs, please go to the following address on theWorld Wide Web:
The English version of this fix should have the following file attributesor later:

   Date      Time                 Size    File Name     Platform   -------------------------------------------------------------   02/15/99  03:27p               675,984 Ntbackup.exe  (x86)   02/15/99  03:29p             1,077,008 Ntbackup.exe  (Alpha)				
NOTE: Y2k351-i.exe and Y2k351-a.exe were updated on November 5, 1998.

This hotfix has been posted to the following Internet location asY2k351-i.exe (x86) and Y2k351-a.exe (Alpha):


STATUS

Windows NT 4.0

Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.

Windows NT 3.51

Microsoft has confirmed that this is a problem in Microsoft Windows NT version 3.51.
MORE INFORMATION
For more information on what is fixed in Y2K2-fix, please see the followingarticles in the Microsoft Knowledge Base:

175093 User Manager Does Not Recognize February 2000 As a Leap Year
183123 Find Files Displays Garbled Date if Year is 2000 or Greater
183125 Shell Doc Property Dialog Custom Date Incorrect after Year 2000
184132 Err Msg: Value Entered Does Not Match with the Specified Type
186669 FPNW Logout.exe Incorrectly Reports Year After Jan. 1, 2000
191768 Date of Print Job May Be Displayed Incorrectly in Print Queue
193056 Problems in Date/Time after Choosing February 29 in a Leap Year
193434 Migration Changes NetWare Accounts Expiration Date
194726 FPNW Client Does Not Get Correct Time or Date After Y2K
207799 IBM PS/1 will not Boot on or After January 1, 2000

Windows NT Server 4.0, Terminal Server Edition

For information on the Y2K2-fix for Windows NT 4.0, Terminal Server Edition, please see the following article in the Microsoft Knowledge Base:
196548 Y2K Update for Windows NT 4.0, Terminal Server Edition
4.00 Y2K MM/dd/yyyy m/d/yyyy dddd, MMMM dd, yyyy dd MMMM,
Properties

Article ID: 216916 - Last Review: 10/14/2013 19:32:40 - Revision: 3.3

Microsoft Windows NT Server 4.0, Terminal Server Edition, Microsoft Windows NT Workstation 3.51, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 3.51, Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT 4.0 Service Pack 1, Microsoft Windows NT 4.0 Service Pack 2, Microsoft Windows NT 4.0 Service Pack 3, Microsoft Windows NT Server 4.0 Enterprise Edition

  • kbnosurvey kbarchive kbbug kbfix KB216916
Feedback