KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q191768: Date of Print Job May Be Displayed Incorrectly in Print Queue

Article: Q191768
Product(s): Microsoft Windows NT
Version(s): winnt:3.51,4.0,4.0a
Operating System(s): 
Keyword(s): kbYear2000 kbWinNT400sp4fix sbs
Last Modified: 20-MAY-2002

-------------------------------------------------------------------------------
The information in this article applies to:

- Microsoft Windows NT Server versions 3.51, 4.0 
- Microsoft Windows NT Workstation versions 3.51, 4.0 
- Microsoft Windows NT Server, Enterprise Edition version 4.0 
- Microsoft BackOffice Small Business Server versions 4.0, 4.0a 
- Microsoft Windows NT Server version 4.0, Terminal Server Edition 
-------------------------------------------------------------------------------

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,
please see the following article in the Microsoft Knowledge Base:

  Q152734 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.

  http://www.microsoft.com/ntserver/nts/downloads/archive/NT4y2kpostSP3/default.asp

  ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT40/hotfixes-postSP3/y2k2-fix/


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:

  http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

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

  ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT351/hotfixes-postSP5/y2k-fix/


STATUS
======

Windows NT 4.0
--------------

Microsoft has confirmed this to be 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:

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

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

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

  Q183125 Shell Doc Property Dialog Custom Date Incorrect after Year 2000

  Q184132 Err Msg: Value Entered Does Not Match with the Specified Type

  Q186669 FPNW Logout.exe Incorrectly Reports Year After Jan. 1, 2000

  Q193056 Problems in Date/Time after Choosing February 29 in a Leap Year

  Q193434 Migration Changes NetWare Accounts Expiration Date

  Q194726 FPNW Client Does Not Get Correct Time or Date After Y2K

  Q207799 IBM PS/1 will not Boot on or After January 1, 2000

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

  Q196548 Y2K Update for Windows NT 4.0, Terminal Server Edition

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

======================================================================
Keywords          : kbYear2000 kbWinNT400sp4fix sbs 
Technology        : kbWinNTsearch kbWinNTWsearch kbWinNTW400 kbWinNTW400search kbWinNT351search kbWinNT400search kbWinNTW351search kbWinNTW351 kbWinNTSsearch kbWinNTSEntSearch kbWinNTSEnt400 kbWinNTS400search kbWinNTS400 kbWinNTS351 kbNTTermServ400 kbNTTermServSearch kbWinNTS351search kbAudDeveloper kbSBServSearch kbSBServ400 kbSBServ400a
Version           : winnt:3.51,4.0,4.0a
Hardware          : ALPHA x86
Issue type        : kbbug
Solution Type     : kbfix

=============================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.