Installation error messages

Installation error messages

Use the codes included in the error messages generated by IBM Connections to identify and resolve problems with installation.
The following installation error messages are generated by IBM Connections:

Message Cause Solution
CLFRP0001E: No existing WAS install detected. Please select the WAS install location manually. The installation wizard cannot find the install directory for WAS. Choose the directory where WebSphere Application Server is installed.
CLFRP0002E: WAS install location is not selected! The directory for the WAS is not specified. Specify the directory where WebSphere Application Server is installed.
CLFRP0003E: dmgr is not selected! The directory where the dmgr is installed is not specified. Specify the directory where the Deployment Manager is installed.
CLFRP0004E: Can not find dmgr profile! The installer cannot find the dmgr profile. Make sure the dmgr profile is complete and available.
CLFRP0005E: Can not get SSL certificate from dmgr! The installer cannot retrieve the SSL certificate from the dmgr. Make sure the SSL certificate is installed and available to the dmgr.
CLFRP0006E: Administrative security is not enabled on dmgr profile! The installation wizard checks to make sure that administrative security is enabled on the dmgr profile. Enable administrative security on the Deployment Manager profile.
CLFRP0007E: Application security is not enabled on dmgr profile! The installation wizard checks to make sure that application security is enabled on the dmgr profile. Enable application security on the Deployment Manager profile.
CLFRP0008E: Security checking script is missing, please check the install image! The installation wizard cannot detect the required checking script. The installation image might be corrupted. The installation image might be corrupted.
CLFRP0009E: Can not connect to the Deployment Manager! The installation wizard cannot connect to the dmgr. Make sure the dmgr is installed and available.
CLFRP0010E: No application server node detected under dmgr, IBM Connections need at least 1 node to proceed! The installation wizard requires at least one node under the dmgr. Make sure that a node under the Deployment Manager is available and install again.
CLFRP0011E: One or more applications you selected already exist in the WAS! Please go back and reselect applications. The installation wizard will not install duplicate applications. Go back and deselect applications that are already installed on the WAS.
CLFRP0012E: Please click "Detect WAS" button to continue. The installation wizard is searching for the WAS. Click "Detect WAS" to initiate a search for the WAS.
CLFRP0013E: Please click "Validate" button after all inputs was filled in. After providing input data for the installation, we must request the installation wizard validate the data. Click "Validate" to confirm the inputs.
CLFRP0014E: IBM Connections script is missing, please check the install image! The installation wizard cannot detect the required IBM Connections script. The installation image might be corrupted. Check the installation image.
CLFRP0015E: The WAS location is not correct. The directory for the WAS is not correct. Specify the directory where WebSphere Application Server is installed.
CLFRP0016E: The WebSphere Application Server version is not supported. We cannot install Connections on an unsupported version of WAS. Refer to the system requirements for supported versions of the WAS.
CLFRP0017E: Cluster name must not be empty! You must supply a cluster name. Specify a cluster name.
CLFRP0018E: Node selection must not be empty! You must supply a node name for the Connections application. Specify a node name.
CLFRP0019E: Cluster name for the application <IBM Connections application name> must not be empty! You must supply a cluster name for the Connections application Specify a cluster name.
CLFRP0020E: Node selection for the application <IBM Connections application name> must not be empty! You must supply a node name for the Connections application. Specify a node name.
CLFRP0021E: JDBC driver path is not valid! Could not validate the JDCB driver path. Check the JDBC driver path and try again.
CLFRP0022E: Can not load JDBC driver, please check the driver location! Failed to load the JDBC driver. Check the JDBC driver path and try again.
CLFRP0023E: Unknown <Connections application name> database error, please check database settings! Failed trying to connect to the Connections database. Check the settings for the Connections database, and try again.
CLFRP0024E: User ID for <Connections application name> contains invalid chars! The User ID for the Connections application contains invalid characters. Correct the user Id and try again.
CLFRP0025E: Password for <Connections application name> contains invalid chars! The password for the Connections application contains invalid characters. Change the password and try again.
CLFRP0026E: Can not connect to <Connections application name> database: JDBC driver error! Failed to connect to the Connections database. Check the log files for details.
CLFRP0027E: Can not connect to <Connections application name> database: wrong username/password! Could not validate the username and password supplied. Enter a valid username/password combination and try again.
CLFRP0028E: Can not connect to <Connections application name> database: database not exist! Failed to connect to the Connections database. Check the log files for details.
CLFRP0029E: Can not connect to database: network communication error! Failed to connect to the Connections database. Check the log files for details.
CLFRP0030E: Can not connect to database: launch error! Failed to connect to the Connections database. Check the log files for details.
CLFRP0031E: The path specified is empty! Could not validate the specified path. Specify a valid path and try again.
CLFRP0033E: Do not have write access to the path specified! Could not access the specified path. Make sure you have write access to the path and try again.
CLFRP0034E: The path specified is not valid! Cannot pass the validation of the specified path. Make sure the path is valid and try again.
CLFRP0035E: <Connections application name> failed to register. The specified application failed to register. There might be a previous installed IBM Connections on the same deployment manager. Check if the "registry.xml" is removed under dir <DM_profile_home>\config\cells\<cellname>.
CLFRP0036E: <Connections application name> failed to add server information. The specified application failed to add server information. Additional information relating to the failure can be found in the installation log file.
CLFRP0037E: <Connections application name> failed to be configured on WAS. The specified application was not successfully configured. Additional information relating to the failure can be found in the installation log file.
CLFRP0038E: <IBM Connections task name> failed to be configured on WAS. The specified application was not successfully configured. Additional information relating to the failure can be found in the installation log file.
CLFRP0039E: Cannot find the log file The installation wizard cannot find the log file.
CLFRP0040E: Empty log file The log file has no content. Make sure the installation log file or directory is not opened by another process.
CLFRP0042E: The open file number is less than 8192. We need to add the command "ulimit -n <number>" to your system user’s profile file to set a larger number. The Open File Descriptor limit is too low.

Open a command line and enter the following command to find the current open file limit: ulimit -n

Add the following line to the user's profile file: ulimit -n 8192
For a non-root user account to install Connections, ask the administrator to add the following line to the /etc/security/limits.conf file: <non-root_account> hard nofile 8192

DSRA8770I By default, the ReadOnly connection property is matched for shareable connections based on the original connection request rather than the current state of the connection. The connectionSharing data source custom property allows you to choose which connection sharing behavior you want. Verify the data source custom property is configured for the behavior you want.
SSL0166E Failed to load GSK library because the GSK toolkit is not installed. Install the libgsk7ssl.so GSK library. See following Support page: Failure attempting to load GSK library when using SSL with IBM HTTP Server.

Parent topic:
Error message reference

Related:

Update 4.0 and 4.5 databases to 5.0

Related:

Install Connections 5.0
Install a fix pack in interactive mode
Install a fix pack in silent mode
Install a fix pack in console mode

Message	Cause	Solution
CLFRP0001E: No existing WAS install detected. Please select the WAS install location manually.	The installation wizard cannot find the install directory for WAS.	Choose the directory where WebSphere Application Server is installed.
CLFRP0002E: WAS install location is not selected!	The directory for the WAS is not specified.	Specify the directory where WebSphere Application Server is installed.
CLFRP0003E: dmgr is not selected!	The directory where the dmgr is installed is not specified.	Specify the directory where the Deployment Manager is installed.
CLFRP0004E: Can not find dmgr profile!	The installer cannot find the dmgr profile.	Make sure the dmgr profile is complete and available.
CLFRP0005E: Can not get SSL certificate from dmgr!	The installer cannot retrieve the SSL certificate from the dmgr.	Make sure the SSL certificate is installed and available to the dmgr.
CLFRP0006E: Administrative security is not enabled on dmgr profile!	The installation wizard checks to make sure that administrative security is enabled on the dmgr profile.	Enable administrative security on the Deployment Manager profile.
CLFRP0007E: Application security is not enabled on dmgr profile!	The installation wizard checks to make sure that application security is enabled on the dmgr profile.	Enable application security on the Deployment Manager profile.
CLFRP0008E: Security checking script is missing, please check the install image!	The installation wizard cannot detect the required checking script. The installation image might be corrupted.	The installation image might be corrupted.
CLFRP0009E: Can not connect to the Deployment Manager!	The installation wizard cannot connect to the dmgr.	Make sure the dmgr is installed and available.
CLFRP0010E: No application server node detected under dmgr, IBM Connections need at least 1 node to proceed!	The installation wizard requires at least one node under the dmgr.	Make sure that a node under the Deployment Manager is available and install again.
CLFRP0011E: One or more applications you selected already exist in the WAS! Please go back and reselect applications.	The installation wizard will not install duplicate applications.	Go back and deselect applications that are already installed on the WAS.
CLFRP0012E: Please click "Detect WAS" button to continue.	The installation wizard is searching for the WAS.	Click "Detect WAS" to initiate a search for the WAS.
CLFRP0013E: Please click "Validate" button after all inputs was filled in.	After providing input data for the installation, we must request the installation wizard validate the data.	Click "Validate" to confirm the inputs.
CLFRP0014E: IBM Connections script is missing, please check the install image!	The installation wizard cannot detect the required IBM Connections script. The installation image might be corrupted.	Check the installation image.
CLFRP0015E: The WAS location is not correct.	The directory for the WAS is not correct.	Specify the directory where WebSphere Application Server is installed.
CLFRP0016E: The WebSphere Application Server version is not supported.	We cannot install Connections on an unsupported version of WAS.	Refer to the system requirements for supported versions of the WAS.
CLFRP0017E: Cluster name must not be empty!	You must supply a cluster name.	Specify a cluster name.
CLFRP0018E: Node selection must not be empty!	You must supply a node name for the Connections application.	Specify a node name.
CLFRP0019E: Cluster name for the application <IBM Connections application name> must not be empty!	You must supply a cluster name for the Connections application	Specify a cluster name.
CLFRP0020E: Node selection for the application <IBM Connections application name> must not be empty!	You must supply a node name for the Connections application.	Specify a node name.
CLFRP0021E: JDBC driver path is not valid!	Could not validate the JDCB driver path.	Check the JDBC driver path and try again.
CLFRP0022E: Can not load JDBC driver, please check the driver location!	Failed to load the JDBC driver.	Check the JDBC driver path and try again.
CLFRP0023E: Unknown <Connections application name> database error, please check database settings!	Failed trying to connect to the Connections database.	Check the settings for the Connections database, and try again.
CLFRP0024E: User ID for <Connections application name> contains invalid chars!	The User ID for the Connections application contains invalid characters.	Correct the user Id and try again.
CLFRP0025E: Password for <Connections application name> contains invalid chars!	The password for the Connections application contains invalid characters.	Change the password and try again.
CLFRP0026E: Can not connect to <Connections application name> database: JDBC driver error!	Failed to connect to the Connections database.	Check the log files for details.
CLFRP0027E: Can not connect to <Connections application name> database: wrong username/password!	Could not validate the username and password supplied.	Enter a valid username/password combination and try again.
CLFRP0028E: Can not connect to <Connections application name> database: database not exist!	Failed to connect to the Connections database.	Check the log files for details.
CLFRP0029E: Can not connect to database: network communication error!	Failed to connect to the Connections database.	Check the log files for details.
CLFRP0030E: Can not connect to database: launch error!	Failed to connect to the Connections database.	Check the log files for details.
CLFRP0031E: The path specified is empty!	Could not validate the specified path.	Specify a valid path and try again.
CLFRP0033E: Do not have write access to the path specified!	Could not access the specified path.	Make sure you have write access to the path and try again.
CLFRP0034E: The path specified is not valid!	Cannot pass the validation of the specified path.	Make sure the path is valid and try again.
CLFRP0035E: <Connections application name> failed to register.	The specified application failed to register.	There might be a previous installed IBM Connections on the same deployment manager. Check if the "registry.xml" is removed under dir <DM_profile_home>\config\cells\<cellname>.
CLFRP0036E: <Connections application name> failed to add server information.	The specified application failed to add server information.	Additional information relating to the failure can be found in the installation log file.
CLFRP0037E: <Connections application name> failed to be configured on WAS.	The specified application was not successfully configured.	Additional information relating to the failure can be found in the installation log file.
CLFRP0038E: <IBM Connections task name> failed to be configured on WAS.	The specified application was not successfully configured.	Additional information relating to the failure can be found in the installation log file.
CLFRP0039E: Cannot find the log file	The installation wizard cannot find the log file.
CLFRP0040E: Empty log file	The log file has no content.	Make sure the installation log file or directory is not opened by another process.
CLFRP0042E: The open file number is less than 8192. We need to add the command "ulimit -n <number>" to your system user’s profile file to set a larger number.	The Open File Descriptor limit is too low.	Open a command line and enter the following command to find the current open file limit: ulimit -n Add the following line to the user's profile file: ulimit -n 8192 For a non-root user account to install Connections, ask the administrator to add the following line to the /etc/security/limits.conf file: <non-root_account> hard nofile 8192
DSRA8770I	By default, the ReadOnly connection property is matched for shareable connections based on the original connection request rather than the current state of the connection.	The connectionSharing data source custom property allows you to choose which connection sharing behavior you want. Verify the data source custom property is configured for the behavior you want.
SSL0166E	Failed to load GSK library because the GSK toolkit is not installed.	Install the libgsk7ssl.so GSK library. See following Support page: Failure attempting to load GSK library when using SSL with IBM HTTP Server.