FIX: The SQLWarning class does not return an error code or a valid SQL state for a 3604 error when you use the SQL Server 2000 Driver for JDBC (894562)
The information in this article applies to:
- Microsoft SQL Server 2000 Driver for JDBC
SYMPTOMSConsider the following scenario: - You use the Microsoft SQL Server 2000 Driver for JDBC to connect your program to a Microsoft SQL Server 2000 database.
- SQL Server 2000 generates a 3604 error code.
- You use the SQLWarning.getErrorCode method to retrieve the error code.
In this scenario, the SQLWarning class only receives the warning message. Additionally, the SQLWarning class returns the error code as 0 (zero) and does not return the SQL state. You expect the SQLWarning class to return the valid error code together with the correct SQL state. Note In a similar scenario, the SQL Server 2000 ODBC driver returns this error as an SQL_ERROR result instead of as a warning. The SQL Server 2000 ODBC driver returns an error result because the severity level is 16. RESOLUTIONTo resolve this problem, install SQL Server 2000 Driver for JDBC Service Pack 3. To obtain this service pack, visit the following Microsoft Web site: STATUS Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.
This problem was corrected in SQL Server 2000 Driver for JDBC Service Pack 3.
REFERENCES
For more information about JDBC, click the following article number to view the article in the Microsoft Knowledge Base:
313100
How to get started with Microsoft JDBC
Modification Type: | Major | Last Reviewed: | 11/28/2005 |
---|
Keywords: | kbBug kbtshoot kbfix KB894562 kbAudDeveloper |
---|
|