Microsoft KB Archive/268367

= FIX: Posting 4 Digit Dates to SQL Server Errorlog, SQL Executive Log, and Windows NT Application Log =

Article ID: 268367

Article Last Modified on 3/14/2006

-

APPLIES TO


 * Microsoft SQL Server 6.5 Standard Edition

-



This article was previously published under Q268367



SYMPTOMS
SQL Server version 6.5 writes 2-digit years to its own error log and to the Microsoft Windows NT Event log. Many system management applications may not work correctly when processing 2-digit years.

NOTE: Microsoft SQL Server is year 2000 compliant in the code logic and data type storage.



RESOLUTION
Install SQL Server 6.5 Service Pack 5a.



STATUS
Microsoft has confirmed this to be a problem in SQL Server 6.5. This problem has been corrected in Service Pack 5a for Microsoft SQL Server 6.5.For more information, click the following article number to view the article in the Microsoft Knowledge Base:

197177 INF: How to Obtain SQL Server 6.5 Service Pack 5a

For more information, contact your primary support provider.



MORE INFORMATION
You will find 2-digit dates in the following areas:
 * SQL Server error log.


 * SQL Server writing events to the Microsoft Windows NT Application Log.


 * Transact-SQL code writing events to the Microsoft Windows NT Application Log and SQL Server error log.


 * Log using the xp_logevent extended stored procedure and/or the RAISERROR WITH LOG statement.


 * SQL Executive Error Log (Sqlexec.out).

Additional query words: 2-digit dates, 4-digit SQL Server

Keywords: kbbug kbfix kbqfe KB268367

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.