Skip to main content
Version Pentaho
Hitachi Vantara Lumada and Pentaho Documentation

General Issues

  1. Last updated
  2. Save as PDF

Follow the suggestions in these topics to help resolve common software issues associated with Pentaho suite: 

See Pentaho Troubleshooting articles for additional topics.

JDBC Driver Issues

Before you begin troubleshooting suspected JDBC driver issues, make sure that the correct JDBC driver JARs are installed in the correct locations. You could install your drivers with our JDBC Distribution Tool to ensure they are placed in the correct locations. Also, make sure there are no conflicting driver versions installed. Confirm with your database or driver vendor if you suspect you have JDBC driver compatibility issues.

The Pentaho Server needs the appropriate driver to connect to the database that stores your data. You can download drivers from your database vendor's website. Check the JDBC Drivers Reference for a list of supported drivers and links to vendor websites.

Perform the following steps to install the appropriate driver for your Pentaho Server:

  1. Stop the Pentaho Server.
  2. Copy your driver into this location: <pentaho-install-directory>/server/pentaho-server/tomcat/lib.
  3. Start the Pentaho Server.

Data Conversion Issues With MySQL Driver 5.0.8

The MySQL JDBC driver version 5.0.8 may cause data conversion errors in the Pentaho Server. For example, SQL statements that convert a numeric field to a string are returned as a string in version 5.0.7, but return as a byte array in version 5.0.8.

To solve this problem, you must replace the mysql-connector-java-5.0.8.jar with the mysql-connector-java-5.0.7.jar in your client tool or application server's lib folder.

Fixing JTDS varchar(MAX) Limitations in MSSQL 2005

Creating a report that uses a column of type varchar(MAX) may result in a net.sourceforge.jtds.jdbc.ClobImpl@83cf00 error when using the JTDS SQL Server driver. This is caused by inherent limitations in older versions of the JTDS driver. Additionally, the SQL Server JDBC driver version 1.2.2828 also has issues accessing a varchar(MAX) column.

The solution is to upgrade the MSSQL 2005 JDBC driver to version 1.0.809.102 or later. Download and install the http://msdn.microsoft.com/en-us/sqlserver/aa937724 file from microsoft.com, then restart your MSSQL server.