Microsoft KB Archive/191768

From BetaArchive Wiki

Article ID: 191768

Article Last Modified on 11/1/2006



APPLIES TO

  • Microsoft Windows NT Server 4.0, Terminal Server Edition
  • Microsoft Windows NT Server 3.51
  • Microsoft Windows NT Server 4.0 Standard Edition
  • Microsoft Windows NT Workstation 3.51
  • Microsoft Windows NT Workstation 4.0 Developer Edition
  • Microsoft Windows NT Server 4.0 Enterprise Edition
  • Microsoft BackOffice Small Business Server 4.0
  • Microsoft BackOffice Small Business Server 4.0a



This article was previously published under Q191768

SYMPTOMS

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.

CAUSE

The system time on the print server is set to the year 2000 or higher.

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.

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 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:

The English version of this fix should have the following file attributes or later:

   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)
                

NOTE: Y2k351-i.exe and Y2k351-a.exe were updated on November 5, 1998.

This hotfix has been posted to the following Internet location as Y2k351-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 this to be a problem in Windows NT versions 3.51.

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


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


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


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



Additional query words: 2K y2k year kb2000 smallbiz win95 win98 4.00

Keywords: kbbug kbfix KB191768