Article ID: 915834 - Last Review: July 19, 2006 - Revision: 1.0 FIX: You may receive an error message when you load the SQL Server 2000 Driver for JDBC and the SQL Server 2005 Driver for JDBC in the same application, you try to connect to a SQL Server 2005 database, and then you run a query
Bug#: 2059 (PSSWebData) On This PageSYMPTOMSConsider 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: [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. CAUSEThis 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://ConnectionString The
SQL Server 2000 Driver for JDBC should only accept connection string URLs
that start with
the following string:jdbc:microsoft:sqlserver://ConnectionString However, the SQL Server 2000 Driver for JDBC also accepts
connections that have the following format:jdbc:sqlserver://ConnectionString The
exception occurs because the SQL Server 2000 Driver for JDBC is not designed to
connect to a SQL Server 2005 database. RESOLUTIONA 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=support
(http://support.microsoft.com/contactus/?ws=support)
Note 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 table
WORKAROUNDTo work around this problem, follow these steps:
Building the connection URL http://msdn2.microsoft.com/en-us/library/ms378428.aspx (http://msdn2.microsoft.com/en-us/library/ms378428.aspx) Setting the connection properties http://msdn2.microsoft.com/en-us/library/ms378988.aspx (http://msdn2.microsoft.com/en-us/library/ms378988.aspx) STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are
listed in the "Applies to" section.
MORE INFORMATIONSteps to reproduce the problemCompile and then run the following Java code sample.
REFERENCES
For more information about JDBC, click the following article number to view the article in the Microsoft Knowledge Base:
313100
(http://support.microsoft.com/kb/313100/
)
How to get started with Microsoft JDBC
The 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.
| Other Resources Other Support Sites
CommunityArticle Translations |






Windows Live
Facebook
Twitter
Linkedin
Digg it
Yahoo
Delicious
StumbleUpon
Yammer
Reddit
Technorati
FriendFeed
Email

Back to the top