Shell Doc Property Dialog Custom Date Incorrect after Year 2000 (183125)



The information in this article applies to:

  • Microsoft Windows NT Server 4.0 Terminal Server Edition
  • 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 Q183125

SYMPTOMS

When you use the document Properties viewer to define a custom property to include a date type in a file, the year may not be saved correctly. For example, if you select a Microsoft Project data file (*.mpp) in a folder window, chose Properties on the Explorer window File menu, click the Custom tab click Date in the Type field, enter a value of 01/01/01, and then click Add, the date appears as 01/01/1901 rather than 01/01/2001.

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 the Microsoft 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 locations.

STATUS

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.

MORE INFORMATION

For more information on what is fixed in Y2K2-fix, please see the following articles in the Microsoft Knowledge Base:

175093 User Manager Does Not Recognize February 2000 As a Leap Year

180122 After Changing the Time, Windows NT May Skip a Day

183123 Find Files Displays Garbled Date if Year is 2000 or Greater

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

216916 NTBACKUP Writes Incorrect Year to Log File

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


Modification Type:MinorLast Reviewed:9/23/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix KB183125