Microsoft officially 425 years behind the times
Tuesday, March 4th, 2008[Quote:]
In the wake of our story about Exchange 2007 failing to realize that February 29 is a real day, one astute Reg reader pointed out that Microsoft has no excuse for allowing its software to behave this way. “The rules of the Gregorian calendar aren’t really that difficult to grasp,” said someone called MacroRodent. “They are not trade secrets. And they have been available for centuries.”
Nonetheless, the SQL Server 2008 “community technology preview” was brought down by the dreaded Leap Year Day bug just 48 hours after Microsoft unveiled it. “We have recently discovered an issue with SQL Server 2008 CTPs that result in SQL Server 2008 not starting on Feb 29 GMT only,” read a statement from the company. “We recommend that you do not run or install this CTP on Feb 29 GMT to minimize any impact in your environment. You can install starting on March 1 GMT.”
And there was a very similar problem with Windows Small Business Server. On Leap Year Day, Windows SBS was unable to issue itself certificates because it stamped each certificate with the date February 29, 2013. So, it failed to recognize the correct date. And it replaced the correct date with a date that doesn’t exist.
