Article ID: 191768 - View products that this article applies to.
This article was previously published under Q191768
This article has been archived. It is offered "as is" and will no longer be updated.
When you view a print job spooled on another print server, such as Windows 9x or LAN Manager, from a Windows NT client, the date displayed in the print queue may be incorrect and possibly off by one year.
The system time on the print server is set to the year 2000 or higher.
Windows NT 4.0To 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:
(https://support.microsoft.com/kb/152734/EN-US/ )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.
Windows NT 3.51A supported fix that corrects this problem is now available from Microsoft, but has not been fully regression-tested and should be applied only to systems 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 and information on support costs, please go to the following address on the World Wide Web:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMSThe English version of this fix should have the following file attributes or later:
NOTE: Y2k351-i.exe and Y2k351-a.exe were updated on November 5, 1998.
Date Time Size File Name Platform ------------------------------------------------------------- 08/26/98 09:40p 72,896 Win32spl.dll (x86) 08/26/98 09:39p 110,352 Win32spl.dll (Alpha)
This hotfix has been posted to the following Internet location as Y2k351-i.exe (x86) and Y2k351-a.exe (Alpha):
Windows NT 4.0Microsoft 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.51Microsoft has confirmed this to be a problem in Windows NT versions 3.51.
For more information on what is fixed in Y2K2-fix, please see the following articles in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/175093/EN-US/ )User Manager Does Not Recognize February 2000 As a Leap Year
(https://support.microsoft.com/kb/183123/EN-US/ )Find Files Displays Garbled Date if Year is 2000 or Greater
(https://support.microsoft.com/kb/183125/EN-US/ )Shell Doc Property Dialog Custom Date Incorrect after Year 2000
(https://support.microsoft.com/kb/184132/EN-US/ )Err Msg: Value Entered Does Not Match with the Specified Type
(https://support.microsoft.com/kb/186669/EN-US/ )FPNW Logout.exe Incorrectly Reports Year After Jan. 1, 2000
(https://support.microsoft.com/kb/193056/EN-US/ )Problems in Date/Time after Choosing February 29 in a Leap Year
(https://support.microsoft.com/kb/193434/EN-US/ )Migration Changes NetWare Accounts Expiration Date
(https://support.microsoft.com/kb/194726/EN-US/ )FPNW Client Does Not Get Correct Time or Date After Y2K
(https://support.microsoft.com/kb/207799/EN-US/ )IBM PS/1 will not Boot on or After January 1, 2000
(https://support.microsoft.com/kb/216916/EN-US/ )NTBACKUP Writes Incorrect Year to Log File
Windows NT Server 4.0, Terminal Server EditionFor information on the Y2K2-fix for Windows NT 4.0, Terminal Server Edition, please see the following article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/196548/EN-US/ )Y2K Update for Windows NT 4.0, Terminal Server Edition
Article ID: 191768 - Last Review: February 23, 2014 - Revision: 3.2