Installation and upgrade issues
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
To fix this problem, clear your web browser's cache, then reload the Pentaho User Console.
- If the login page appears blank with all input fields left-justified:
To fix this problem, stop the Pentaho Server. Navigate to the pentaho/server/pentaho-server/pentaho-solutions/system directory and open the pentaho.xml file with any text editor. Edit the <default-theme> parameter so that only lower-case letters are used in the parameter value (for example,
sapphire). Save and close the file. Start the Pentaho Server.
Pentaho Server does not start when installed on a virtual machine
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 Step 1: Increase the amount of time JBoss allows for Pentaho Server deployment.
Context XML changes do not take effect after deploying a WAR
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
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
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
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
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
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
.warextension, 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
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.
Follow the instructions in the Step 4: Review previous version upgrades and customizations article.