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

Installation and Upgrade Issues

  1. Last updated
  2. Save as PDF

Follow the suggestions in these topics to help resolve common issues associated with installing and upgrading your Pentaho system:

  • User Console Themes Render Improperly After Upgrade
  • Pentaho Server Does Not Start When Installed on a Virtual Machine
  • Context XML Changes Do Not Take Effect After Deploying a WAR

  • No Search Manager Configured for the Java Repository

  • Cannot Create Jackrabbit Tables in MySQL
  • Unable to Use the Database Init Scripts for PostgreSQL
  • JBoss Fails to Start 
  • Not Able to Login or Run Transformations

See Pentaho Troubleshooting articles for additional topics.

User Console Themes Render Improperly After Upgrade

If you are seeing unusual rendering problems in the User Console shortly after performing a Pentaho Server upgrade, the problem may be related to old JavaScript files being held in the browser cache.

To fix this problem, clear your web browser's cache, then reload the Pentaho User Console.

Pentaho Server Does Not Start When Installed on a Virtual Machine

The Pentaho Server does not start when installed on a Virtual Machine and deployed on the JBoss web application server.

To fix this problem, increase the amount of time JBoss allows for application deployment to 240 seconds or longer. For information on how to increase the amount of time, see Increase the Amount of Time JBoss Allows for Pentaho Deployment.

Context XML Changes Do Not Take Effect After Deploying a WAR

With a manual installation, if you deploy a WAR with a custom context.xml, the context.xml file may not be overwritten.

The location and naming convention for this file are: $CATALINA_HOME/conf/Catalina/<host>/<war name>.xml. An example of this file path is  /tomcat/conf/Catalina/localhost/pentaho.xml. If this file exists, you will have to delete it prior to deploying the pentaho.war if you have made any changes to context.xml.

No Search Manager Configured for the Java Repository

If you see a Javax.jcr.RepositoryException: no search manager configured for this workspace error message in your Pentaho Server log, then there was an error in the PDI upgrade process . Specifically, the SearchIndex XML nodes were not properly modified.

To fix this problem, refer to the Upgrade section and closely follow the instructions for modifying repository configuration files.

Cannot Create Jackrabbit Tables in MySQL

The Pentaho solution repository uses long text strings that require a longer maximum character limit than the default UTF-8 configuration allows. Using UTF-8 will prevent the MySQL initialization scripts from running during installation.

If your MySQL character set is configured to use UTF-8, you must change it to ASCII to use it as a Pentaho solution database.

Unable to Use the Database Init Scripts for PostgreSQL

The pg_hba.conf file contains host-based authentication information. If you cannot run the SQL scripts that generate the Jackrabbit and Quartz databases, it is probably because the default user accounts for each database do not have the right permissions.

To change these permissions, edit the file to ensure that connections from local users created by the Pentaho SQL scripts (such as pentaho_user) will be able to connect. The default on Debian-based systems is for local connections you use ident authentication, which means that database users must have local user accounts. In other words, to continue using ident, you would have to create a local pentaho_user account. An easier resolution might be to just change the authentication method to something less restrictive. Consult your IT manager to assess if this approach is possible.

JBoss Fails to Start

If JBoss fails to start, check to see if these conditions apply to your situation:

JBoss Fails to Start When the Pentaho HSQLDB Sample Database Is Running

This problem can also manifest as the Pentaho sample database refusing to start when the Pentaho Server is deployed to JBoss.

The Pentaho-supplied HSQLDB sample database operates on the default HSQLDB port of 9001. JBoss has its own HSQLDB instance running on the same port. This port collision will prevent the JBoss version from starting and cause the startup process to halt.

You can change the Pentaho sample database port by editing the start_hypersonic script and adding the -port 9002 switch to the last line, as shown in the following code sample:

"$_PENTAHO_JAVA" -cp $THE_CLASSPATH org.hsqldb.Server -port 9002 -database.0 $DIR_REL/hsqldb/sampledata -dbname.0 sampledata -database.1 $DIR_REL/hsqldb/hibernate -dbname.1 hibernate -database.2 $DIR_REL/hsqldb/quartz -dbname.2 quartz

JBoss Fails to Start After Manually Unpacking Pentaho WAR

If you unpack the WAR file to any other folder name, including pentaho without the .war extension, JBoss will fail to deploy the WAR without any meaningful warnings.

You must also name the resultant folder pentaho.war when manually unpacking the pentaho.war file.

Not Able to Login or Run Transformations

If you have manually upgraded to 8.0 from a previous version of Pentaho that used a DI Server and are not able to login or run transformations perform one or both of the following steps:

  1. Check the file size of the pentaho-solutions/system/pentaho.xml file. If the file size is 0 KB, then the file is corrupted and must be replaced. To resolve this issue, copy the file from your 7.1 DI server to the 8.0 Pentaho Server.
  2. Follow the instructions in Step 4: Previous Version Upgrades of the Pentaho Upgrade article.