Article ID: 915834
Bug#: 2059 (PSSWebData)
Consider the following scenario. You load the Microsoft SQL Server 2000 Driver for JDBC in an application. Then, you load the Microsoft SQL Server 2005 JDBC Driver in the same application. In this scenario, when you try to connect to a SQL Server 2005 database by using a SQL Server 2005 JDBC Driver URL, the connection is established by using the Microsoft SQL Server 2000 Driver for JDBC. If you subsequently run a query, you receive the following error message:
If you establish a connection to a SQL Server 2000 database, you may not receive any error message, and the fact that the wrong driver is being used may be unnoticed. You experience this problem when the SQL Server 2000 Driver for JDBC is loaded before the Microsoft SQL Server 2005 JDBC Driver is loaded in the application.
[Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter 1 (""): Data type 0x38 is unknown.
This problem occurs because faulty name resolution occurs in the SQL Server 2000 JDBC driver. The SQL Server 2000 JDBC driver accepts connection URLs from the SQL Server 2005 JDBC Driver. The SQL Server 2005 JDBC Driver connection string URLs start with the following string:
jdbc:sqlserver://ConnectionStringThe SQL Server 2000 Driver for JDBC should only accept connection string URLs that start with the following string:
jdbc:microsoft:sqlserver://ConnectionStringHowever, the SQL Server 2000 Driver for JDBC also accepts connections that have the following format:
jdbc:sqlserver://ConnectionStringThe exception occurs because the SQL Server 2000 Driver for JDBC is not designed to connect to a SQL Server 2005 database.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2000 Driver for JDBC service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Collapse this tableExpand this table
To work around this problem, follow these steps:
Building the connection URL
Setting the connection properties
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.
Steps to reproduce the problemCompile and then run the following Java code sample.
Note To use this code sample, replace the following placeholders:
For more information about JDBC, click the following article number to view the article in the Microsoft Knowledge Base:
313100The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.
(https://support.microsoft.com/kb/313100/ )How to get started with Microsoft JDBC
Article ID: 915834 - Last Review: June 20, 2014 - Revision: 2.0
Retired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.