# Troubleshooting possible installation and upgrade issues Use these fixes for common issues during Pentaho installation and upgrades. Issues covered: * User Console themes render improperly after upgrade * 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 * Cannot sign in or run transformations after upgrade * Error when using sample transformations or jobs * Missing Quartz library database error * Error when installing local license server on Red Hat Enterprise Linux in FIPS mode ### User Console themes render improperly after upgrade There are two common causes: * If you see unusual rendering problems shortly after upgrading, your browser may be using cached JavaScript files. Clear your browser cache. Reload the Pentaho User Console. * If the sign-in page is blank and all input fields are left-aligned, the theme name casing may be wrong. Stop the Pentaho Server. Edit `pentaho/server/pentaho-server/pentaho-solutions/system/pentaho.xml`. Set `` to lowercase only (for example, `ruby`, `crystal`, or `sapphire`). Save your changes. Start the Pentaho Server. ### Context XML changes do not take effect after deploying a WAR In a manual installation, redeploying a WAR might not overwrite your custom `context.xml`. Tomcat stores a deployed context file here: `$CATALINA_HOME/conf/Catalina//.xml` Example: `/tomcat/conf/Catalina/localhost/pentaho.xml` If this file exists, delete it before redeploying `pentaho.war`. ### No search manager configured for the Java repository If your Pentaho Server log shows `Javax.jcr.RepositoryException:no search manager configured for this workspace`, your PDI upgrade did not update the `SearchIndex` nodes correctly. Follow the repository configuration steps in [Post-upgrade tasks](https://docs.pentaho.com/install/legacy-redirects/pentaho-upgrade-redirects/post-upgrade-tasks-pentaho-ugrade-cp). ### Cannot create Jackrabbit tables in MySQL The Pentaho solution repository uses long text strings. MySQL’s default UTF-8 configuration can block the init scripts. If your MySQL character set uses UTF-8, change it to ASCII for the Pentaho solution database. ### Unable to use the database init scripts for PostgreSQL If you cannot run the SQL scripts that generate the Jackrabbit and Quartz databases, check `pg_hba.conf`. The default database users created by the Pentaho SQL scripts (such as `pentaho_user`) might not have permission to connect. Update `pg_hba.conf` so local users created by the Pentaho scripts can connect. On Debian-based systems, the default for local connections is often `ident`. With `ident`, each database user must also exist as a local OS user. If you keep `ident`, create a local `pentaho_user` account. Or switch to a less restrictive auth method if your security policy allows it. ### Cannot sign in or run transformations after upgrade This issue can happen after manually upgrading to 8.0 from a previous version that used a DI Server. 1. Check the file size of `pentaho-solutions/system/pentaho.xml`. If the file size is `0 KB`, the file is corrupted. 2. Copy `pentaho.xml` from your 7.1 DI Server to your 8.0 Pentaho Server. ### Error when using sample transformations or jobs If you run a shipped sample transformation (`.ktr`) or job (`.kjb`), you might see errors caused by older JAR files. Use the JAR files included with the same Pentaho release as the shipped samples. ### Missing Quartz library database error If you install 10.2.0.1 or later and the Quartz database is missing, you likely still have Quartz 1.x tables. Older versions use Quartz 1.x tables with a `QRTZ5_` prefix. 10.2.0.1 and later use Quartz 2.x tables with a `QRTZ6_` prefix. Create or migrate the scheduling database for Quartz, then restart the server. See [Mandatory Quartz upgrade for versions 10.2.0.1 and later](https://docs.pentaho.com/install/legacy-redirects/pentaho-upgrade-redirects/mandatory-quartz-upgrade-for-versions-10.2.0.1-and-later). ### Error when installing local license server on Red Hat Enterprise Linux in FIPS mode If you install a local license server on Red Hat Enterprise Linux with FIPS enabled, you might see `SHA1PRNG SecureRandom not available` in the installer output. Configure Java for FIPS: * [Configuring Red Hat build of OpenJDK 11 on RHEL with FIPS](https://docs.redhat.com/en/documentation/red_hat_build_of_openjdk/11/html-single/configuring_red_hat_build_of_openjdk_11_on_rhel_with_fips/index) * [Configuring Red Hat build of OpenJDK 17 on RHEL with FIPS](https://docs.redhat.com/en/documentation/red_hat_build_of_openjdk/17/html-single/configuring_red_hat_build_of_openjdk_17_on_rhel_with_fips/index#proc-providing-feedback-on-redhat-documentation) ### More troubleshooting See [Administer Pentaho Data Integration and Analytics](https://app.gitbook.com/o/PtpmPYUKgAsUWgv8SVUt/s/iFWuQjAZNxh1EoQbRnsT/) for additional troubleshooting.