Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Troubleshooting: "java.sql.SQLException" Name of SQL Server 2005 driver differs from SQL Server 2000

Updated on September 13, 2021

Symptom

Process Commander supports Microsoft SQL Server 2005 as the host software for the PegaRULES database and can connect to external databases that use SQL Server 2005 using Rule-Connect-SQL rules.

However, Microsoft changed the driver class name for SQL Server 2005. This can be a difficult-to-debug source of confusion and error.

If you use the old driver name, the code for SQL Server 2000 will run. The following error appears when the system attempts to connect to SQL Server 2005 using SQL Server 2000 drivers.

SQLState HY000, Error code 8009: java.sql.SQL
Exception:
[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.

Solution

The Microsoft SQL Server 2000 driver class name is:

"com.microsoft.jdbc.sqlserver.SQLServerDriver";

When setting the connection to the database for SQL Server 2005, use the following class name:

"com.microsoft.sqlserver.jdbc.SQLServerDriver";

 

 
  • Previous topic Troubleshooting: "Unexpected character +" exception with truncated property name
  • Next topic Troubleshooting: "maximum row size" error for pr4_rule table in V4.2 installation (SQL Server)

Tags

Pega Platform 7.1.1 - 8.3.1 System Architect System/Cloud Ops Administrator System Administration

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us