OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
More MS Y2K non-compliance... (fwd)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

More MS Y2K non-compliance... (fwd)


  • To: NTBUGTRAQLISTSERV.NTBUGTRAQ.COM
  • Subject: More MS Y2K non-compliance... (fwd)
  • From: Steven Kastl <skastlWIRETRIP.NET>
  • Date: Wed, 25 Mar 1998 10:04:00 -0600
  • Reply-To: Steven Kastl <skastlWIRETRIP.NET>
  • Sender: Windows NT BugTraq Mailing List <NTBUGTRAQLISTSERV.NTBUGTRAQ.COM>

---------- Forwarded message ----------
Date: Wed, 25 Mar 1998 10:00:41 -0600 (CST)
From: Steven Kastl <skastlwiretrip.net>
To: NTGUBTRAQLISTSERV.ORG
Cc: BUGTRAQNETSPACE.ORG
Subject: More MS Y2K non-compliance...

This is a bug, not an exploit

Product(s):

MSSQL Server 6.5 (SP3)
Windows NT 4.0 (SP3)

Problem:

Y2K is a leap year (before we go any further on this issue, check your
sources, because it is...).

A scheduled backup job for 02-29-2000 cannot be entered.  Dates 02-28 and
03-01 can be entered, and the day of week is appropriately changed (i.e.
from Monday 02-28 to Wednesday 03-01).

No other functionality of SQL Server seems to be impaired (all other tests
passed).

Microsoft has been notified.

I have looked in the MS KB and found nothing relating to this issue.

Comments welcome

Regards,

--Steve Kastl

----------------------------------------------------
MCP, Windows NT 3.51/4.0  |  please reply to:
Certified UNIX Sysadmin   |  skastlmcs.net
Network Systems Engineer  |  skastlwiretrip.net
----------------------------------------------------