Upgrading your Jive on-premise instance is an important activity to be performed from time to time in order to take advantage of the latest fixes and service packs released by Jive.
Even though Jive On-Premise Upgrade Planning lies outside of the support scope and the Professional Services team can be engaged for the same, there are some known issues that you might run into during or after the upgrade. This article outlines these issues.
On-premise upgrades run into various issues related to mismatched JDK versions, database passwords, encrypted keys, maven artifact versions, issues related to CMR, EAE and other general errors.
These can broadly be divided into errors during an upgrade and errors after an upgrade.
Errors during upgrade
When upgrading Jive On-Premise to version 9.0.7 behind a private network with no access to the internet, the process may fail and trigger a null pointer exception as explained in Upgrading On-Premise to 9.0.7 Fails. This was a known issue and has been corrected in version 9.0.8. Therefore, upgrading to 9.0.8 or a newer version solves this problem.
An error is seen in Jive on-premise upgrades to v9.4 wherein there is an error for the ‘Update SAML Key Store Type’ task. This is explained in the article Jive On-Premise 9.4 Upgrade: The Error Message "java.io.IOException: DER length more than 4 bytes" Appears for the "Update SAML Key Store Type" Task.
When upgrading an On-Premise instance to 9.8 (from 9.6 or earlier), users may see 404 errors in the browser when trying to access Jive. This happens because a node might have failed to start. The article Upgrading On-Premise to 9.8 Fails - 404 Errors when trying to access Jive explains this.
Errors after upgrade
When using a custom built deployment compiled from Maven repository, Jive on-premise 9.5 instance installation fails to start after upgrading from 9.0.5 with the error Invocation of init method failed; nested exception is java.security.KeyStoreException: JCEKS not found. This happens because of a JDK version mismatch.
After a Jive instance upgrade, when starting an instance using mvn, some errors might be seen which are related to BCFIPS and other Java security-related exceptions. It is also possible that users may face an error logging in with Kerberos based Single Sign-on (SSO) after an upgrade. These are resolved by ensuring that the correct version of Amazon Corretto JDK is installed.
Some upgrades involve a database migration. When copying/moving data from one instance to another, the encrypted passwords stored in the database can also get copied across. This can lead to SQL Exceptions like "invalid username/password; logon denied" resulting in News Streams not getting displayed for users. This is explained in the article Jive -News Stream Not Showing - DB Logon Error after a Data Refresh or Migration whereby the solution is to reset the stored passwords in the database from encrypted to cleartext.
After upgrading your Jive instance, you may notice that the Community Manager Reports (CMR) page shows HTTP ERROR 500 when accessed. In this case, you will additionally see the error 'Initialization error: Failed installing or upgrading plugin 'community-manager-report's schema.' when accessing the Plugins page in Admin Console > System > Plugins. This occurs due to the versioning issues with the Community Manager Reports plugin during the upgrade and is explained in the article Community Manager Reports Fails to Load With HTTP ERROR 500 After Upgrade.
After upgrading to Jive 9.5, it is possible that the home page doesn't load. An error message appears with the text "An unexpected error has occurred". This happens due to an incompatibility of the Events extension with the Jive Events 9.5 plugin that was identified as having an issue. It can be resolved by installing the upgraded version of the extension. This is explained in the article Homepage Error After an Upgrade to 9.5.
After upgrading Jive to version 9.4, the activity engine server shows a status of Failing in the Admin Console > System > Settings > Activity Engine screen. To resolve this, the Jive RPM must be reinstalled on the activity engine server.
Sometimes, the existing users are not visible until they log in to Jive post upgrading. The article Existing Users Invisible After Upgrading to 9.0.7 provides the error logs encountered as well as the workarounds for them.