General installation problems and limitations
Some of the problems that you might encounter while installing Jazz™ for Service Management are described along with solutions, and workaround if any.
- IBM Installation Manager fails at database credentials validation
IBM® Installation Manager fails when invoked through launchpad tools option while validating the database credentials. - While installing Jazz for Service Management using Launchpad Custom flow, in SUSE Linux Enterprise Server (SLES) the installation always fails during Prerequisite Scanner
While installing Jazz for Service Management using Launchpad Custom flow, in SUSE Linux Enterprise Server (SLES) the installation always fails during Prerequisite Scanner. - Full installation of Jazz for Service Management does not recognize DB2 installers
Full installation of Jazz for Service Management does not recognize DB2 installers except ESE. - Installation as a non-administrator user fails for all Jazz for Service Management services
Installation as a non-administrator user fails for all Jazz for Service Management services . - While upgrading Jazz for Service Management the Installation Manager hangs
While upgrading to Jazz for Service Management, from any older version of Jazz for Service Management, the IBM Installation Manager hangs. - Tivoli Common Reporting Version 3.1.2.1 rollback fails through IBM Installation Manager
Tivoli® Common Reporting Version 3.1.2.1 rollback fails through IBM Installation Manager. - Data Migration steps for Tivoli Common Reporting Version 3.1.2.1 do not work
Data Migration steps for Tivoli Common Reporting from Version 3.1.0.x to Version 3.1.2.1 do not work. - Reporting Services option is not available through IBM Installation Manager for rollback in Version 3.1.2.1
Rollback of Reporting Services cannot be performed when Custom update of Jazz for Service Management Version 1.1.2 on an already existing version of Jazz for Service Management including Tivoli Common Reporting using full install flow. - Unable to start or stop the Jazz for Service Management server after upgrading IBM WebSphere Application Server from Version 8.5.0.1 to Version 8.5.5.4
Unable to start or stop the Jazz for Service Management server after upgrading IBM WebSphere® Application Server from Version 8.5.0.1 to Version 8.5.5.4 - After rollback of Tivoli Common Reporting Version 3.1.2.1 the dispatcher fails to initialize
After rollback of Tivoli Common Reporting Version 3.1.2.1 the dispatcher fails to initialize. - Full installation of Jazz for Service Management with DB2 version 10.5.0.5 fails
Full installation of Jazz for Service Management with DB2 version 10.5.0.5 fails. - Failure of Jazz for Service Management full installation with DB2 Version 10.5 installer
Jazz for Service Management full installation with DB2® Version 10.5 installer fails. - Installation of Tivoli Common Reporting Version 3.1.2.0 as a non-root user fails
Installation of Tivoli Common Reporting Version 3.1.2.0 as a non-root user fails. - While installing Jazz for Service Management using Launchpad Custom flow, it does not update DB2 from Version 10.1 to Version 10.5
While installing Jazz for Service Management using Launchpad Custom flow, it does not update IBM DB2 from Version 10.1 to Version 10.5. - Failure of Jazz for Service Management installation with DB2 version 10.1 AESE
Failure of Jazz for Service Management installation with DB2 version 10.1 AESE. - Failure of Jazz for Service Management full installation with DB2 version 10.5 installer
Jazz for Service Management full installation with DB2 version 10.5 installer fails - Multi-level rollbacks are not supported for Reporting Services rollback
Multi-level rollbacks are not supported for Reporting Services rollback - Liberty profile while installing Administration Services in Jazz for Service Management Version 1.1.2.1 is not supported
Unable to configure Liberty profile while installing Administration Services in Jazz for Service Management with WebSphere Application Server Version 8.5.5.4 - Limitations of Jazz for Service Management installation in SanDisk or mount locations
- Limitation of Cognos content store database usage during rollback
Limitation of Cognos content store database usage during rollback. - Launchpad Text fields for DB2, WAS and Cognos location in Custom Flow becomes uneditable sometimes.
Launchpad Text fields for DB2, WAS and Cognos location in Custom Flow becomes uneditable sometimes. - For an existing Jazz for Service Management profile in the Korean locale, the custom installation using launchpad does not work
- Inconsistency in the way TCRCognos location is used while installing Jazz for Service Management Version 1.1.2.1 using Launchpad and Installation Manager
- While installing Jazz for Service Management from the command line, an error occurs
- The Browse directory functionality does not work on Launchpad for operating system with Mozilla FireFox Version less than 10.0
- Failure of Jazz for Service Management installation due to antivirus program
Antivirus programs can interfere with the installation of Jazz for Service Management and cause it to fail. - Launchpad cannot be run from a mapped Windows network drive
You cannot run the launchpad from a mapped Windows network drive - Cannot create the Registry Services database in DB2 as a non-instance owner
When you attempt to create the Registry Services database in DB2 as a non-instance owner, the database creation fails. - Unable to install Administration Services in a Liberty profile
- Unable to run the launchpad
- Installation Manager 1.6.1 does not render Thai locale correctly
- Unable to install integration services
- Cannot uninstall Jazz for Service Management extension for WebSphere and integration services in the same flow
- Uninstalling WebSphere Application Server does not remove the installation directory
- Uninstalling WebSphere Application Server does not remove its program group
- Uninstalling Jazz for Service Management does not remove all files
- Registry keys with incorrect WebSphere Application Server version
- Inconsistent registry keys generated on installing WebSphere Application Server
- Registry keys are not removed on uninstalling WebSphere Application Server
- WebSphere Application Server installation on Windows 2012 displays a warning
- Launchpad does not display the Next button
- Installation Manager does not display the option to logon to Dashboard Application Services Hub
- The login page for Dashboard Application Services Hub is not displayed
- Administration service provider is not unregistered when Administration Services in uninstalled
- Cannot use arrow keys for navigation in the launchpad
- WebSphere Application Server fails to restart after installing integration services
- Cannot run the launchpad because of the security zone level
- Unable to update all packages by using Installation Manager 1.6.1
- Registry Services installation as a domain user fails on Windows
- WebSphere Application Server stops on log off
- Installation Manager does not display the Configuration feature for Registry Services Schema
- WebSphere Application Server credentials validation fails during custom workflow
- DB2 configuration limitations for IBM Cognos Content Store
- Launchpad does not install correct version of the offering
- Username in Japanese not accepted
- Multibyte characters not supported
- Launchpad does not render Hebrew locale
- JAWS reads launchpad buttons incorrectly
- Drop Database check box status not displayed on AIX
- Security warning displayed when installing from a mapped network drive
Parent topic: Troubleshooting installations