Installation error messages (2.0) 

You can correct installation problems that are caused by configuration errors or database connection problems.

GSK_ERROR
If you see a 500 error when using HTTPS over the IBM HTTP Server to get to an application, HTTPS might not be configured correctly with the WebSphere Application Server plug-in. If this error occurs, check both your IBM HTTP Server and WebSphere Application Server logs to see if there is a GSK_ERROR. If the logs do not contain errors, examine the plug-in logs located in the following directory:
C:\ibm\HTTPServer\Plugins\logs\webserver1\http_plugin.log
The following error is generated if the WebSphere Application Server SSL certificate is not trusted by the WebSphere Application Server plug-in configured for the IBM HTTP Server:
ERROR: lib_stream: openStream: Failed in r_gsk_secure_soc_init:
GSK_ERROR_BAD_CERT(gsk rc = 414)
To fix this error, follow the instructions in the topic Configuring the IBM HTTP Server for SSLin the Installing section of the Lotus Connections 2 information center.

Database connection problems
A faulty JDBC driver or data source can prevent you from accessing a Lotus^® Connection feature. Here's how to test the connections and correct problems.

If you encounter a HTTP 500 - Internal Server Error when attempting to access a Lotus Connections feature for the first time, make sure that you are using the Web address. If the Web address is correct, test the validity of your database connection, by performing the following steps from the WebSphere Application Server Integrated Solutions Console:

• Verify the database connections by selecting Resources > JDBC > JDBC Providers > JDBC > Data Source.
• Select a Lotus Connections data source, and then click Test Connection.
• If the connections fails, use one of the following approaches to locate and resolve the problem:
• Data source problems – Select the data source and review the database server values to ensure they are correct. Check the port number, server name, and database name. If you discover an error, change the value, click OK and Save, and then retest the database connection.
• JDBC driver path problems – Check to ensure the path assigned to a feature's JDBC driver is correct. Select Environment > WebSphereVariables, and then review the path for the JDBC driver variable to make sure it is correct. The driver path is named using the syntax: _JDBC_DRIVER_HOME. Note that on Linux^® this path is case-sensitive. If the path is incorrect, change it, and then click OK and Save.
• JAAS credential problems – Check the JAAS J2C authentication settings by selecting Resources > JDBC > JDBC Providers > JDBC > datasource > > JAAS-J2C authentication data. Select JAASAauth, and then view the user ID and password credentials you entered during installation to verify that they are correct. If they are not correct, make any required changes.

Use the codes included in the error messages generated by IBM^® Lotus^® Connections to identify installation, configuration, or directory problems and find their solutions.
Table 1. Installation error messages with codes

Message	Cause	Solution
CLFRP0258E: The installation of feature {0} failed while creating WebSphere® Application Server Variables.	The installation failed while creating WebSphere Application Server Variables.	1. Check the detailed error message in the log file. 2. Find the root cause of error then try to fix it. 3. Run the uninstaller to uninstall the feature and then install the feature again.
CLFRP0253E: The installation of feature {0} failed while creating datasource.	The installation failed while creating while creating datasource.	1. Check the detailed error message in the log file. 2. Find the root cause of error then try to fix it. 3. Run the uninstaller to uninstall the feature and then install the feature again.
CLFRP0260E: The installation of feature {0} failed while deploying application.	The installation failed while deploying application.	1. Check the detailed error message in the log file. 2. Find the root cause of error then try to fix it. 3. Run the uninstaller to uninstall the feature and then install the feature again.
CLFRP0256E: The installation of feature {0} failed while doing server configuration.	The installation failed while doing server configuration.	1. Check the detailed error message in the log file. 2. Find the root cause of error then try to fix it. 3. Run the uninstaller to uninstall the feature and then install the feature again.
CLFRP0259E: The uninstallation of feature {0} failed while removing WebSphere Application Server Variables.	The uninstallation failed while removing WebSphere Application Server Variables.	1. Check the detailed error message in the log file to find the root cause. 2. Try to fix it and then uninstall the feature.
CLFRP0257E: The uninstallation of feature {0} failed while removing datasource.	The uninstallation failed while removing datasource.	1. Check the detailed error message in the log file to find the root cause. 2. Try to fix it and then uninstall the feature.
CLFRP0255E: The uninstallation of feature {0} failed while uninstalling application.	The uninstallation failed while uninstalling application.	1. Check the detailed error message in the log file to find the root cause. 2. Try to fix it and then uninstall the feature.
CLFRP0254E: The uninstallation of feature {0} failed while doing server configuration.	The uninstallation failed while doing server configuration.	1. Check the detailed error message in the log file to find the root cause. 2. Try to fix it and then uninstall the feature.
CLFRP0001E: Lotus Connections cannot use the WebSphere Application Server in: . Please refer to the following message log for additional information:	The WebSphere Application Server is insufficient for Lotus Connections.	Lotus Connections requires specific WebSphere Application Server features and component levels. Refer to the message log file to determine why the WebSphere Application Server is insufficient for Lotus Connections. Apply WebSphere Application Server changes as required to satisfy Lotus Connections requirements.
CLFRP0006E: The specified directory is not valid. Lotus Connections is already installed in this location.	The selected directory already has Lotus Connections installed.	Choose a different directory or remove Lotus Connections from the selected directory.
CLFRP0007E: Operating System prerequisite check failed. Refer to the message log file for additional information.	The operating system is not supported.	Install Lotus Connections on a supported operating system. If your operating system is a newer version of a supported platform, refer to the Lotus Connections support site or contact Customer Support to determine if the operating system level is supported.
CLFRP0060E: There were no profiles detected for the installed WAS and managed node selected.	There were no profiles detected under the installed WebSphere Application Server.	Make sure there are profiles under WebSphere Application Server.
CLFRP0061E: The profile selected cannot be validated. Please refer to the following logs for additional information:	Cannot pass the validation of the selected profile.	1. Check the detailed exception message below this error message in the log file to find the root cause. 2. Make sure the profile selected is valid and then try again.
CLFRP0061W: WebSphere Application Server security must be enabled.	WebSphere Application Server security is not enabled.	Make sure WebSphere Application Server security is enabled, then try again.
CLFRP0062E: There were no servers detected for the installed WebSphere Application Server.	There were no servers detected under the installed WebSphere Application Server.	Make sure there is a server instance under the WebSphere Application Server profile selected.
CLFRP0063E: The server selected cannot be validated. Please refer to the following logs for additional information:	The WebSphere AppServer server is not valid.	Make sure the WebSphere AppServer server is valid.
CLFRP0214E: The custom dependency checker rules directory you specified cannot be found, or does not contain all the required files. You must supply a different location for the custom dependency checker rules directory. The installer will now exit.	The custom dependency checker rules directory you specified cannot be found, or does not contain all the required files.	Check the value you supplied for the custom dependency checker rules directory. Look at the logs for the files that are required by the installer. Also make sure all the required dependency checker files exist in that directory.
CLFRP0251E: Installation of Change Password Application has failed.	Failure to install Change Password Application.	1. Check the detailed exception message below this error message in the log file to find the root cause. 2. Continue Lotus Connections Pilot installation. 3. After installation is completed, install the file, changePassword.ear from the following directory: Location>\installable Apps\
CLFRP0252E: The selected file does not have a correct format, please select a correct one.	The selected file does not have a correct format.	Check the format of the user file according to Lotus Connections information center, making sure it is correct.
CLFRP0299E: An error occurred installing 6.1.0.0-WS-WAS-IFPK38815.pak, please check log file .	Failure to install 6.1.0.0-WS-WAS-IFPK38815.pak.	1. Check the detailed exception message below this error message in the log file to find the root cause. 2. Continue Lotus Connections installation, referring to WebSphere Application Server information center to install the interim fix 6.1.0.0-WS-WAS-IFPK38815.pak manually once the Lotus Connections installation is complete.
CLFRP0300E: An error occurred installing WebSphere Application Server V6.1.0.3. For additional information, refer to the log file or .	Failure to install WebSphere Application Server.	1. Check the detailed exception message below this error message in the log file to find the root cause. 2. Cancel the Lotus Connections installation. 3. Uninstall WebSphere Application Server and DB2® manually. (Refer to WebSphere and DB2 information centers.) 4. Try to install Lotus Connections Pilot again.
CLFRP0301E: An error occurred installing 6.1.0.3-WS-WAS-IFPK34390.pak. For additional information, refer to the log file .	Failure to install 6.1.0.3-WS-WAS-IFPK34390.pak.	1. Check the detailed exception message below this error message in the log file to find the root cause. 2. Continue the Lotus Connections installation. 3. Refer to the WebSphere Application Server information center to install the interim fix 6.1.0.3-WS-WAS-IFPK34390.pak manually once the Lotus Connections installation is complete.
CLFRP0303E: An error occurred installing WebSphere Update Installer V6.1.0.1. For additional information, refer to the log file .	This error is encountered if there is a failure to install WebSphere Update installer.	1. Check the detailed exception message below this error message in the log file to find the root cause. 2. Continue the pilot installation. 3. After installation is completed, try to install WebSphere Update Installer manually. (Refer to the WebSphere Application Server information center.) 4. Install the 5 interim fixes mentioned in the Lotus Connections information center.
CLFRP0305W: WebSphere Application Server administrator passwords must match.	WebSphere Application Server administrator passwords don't match.	Make sure WebSphere Application Server administrator passwords match.
CLFRP0306W: DB2 Administrator password must match.	The DB2 Administrator password doesn't match.	Make sure the DB2 Administrator password matches.
CLFRP0307E: A previous version of Lotus Connections was found . This version only requires a Fix Pack to be applied. Refer to Lotus Connections information center for instructions on installing Fix Pack .	A previous version of Lotus Connections was installed on the server.	Either run upgrade installer for 1.0.2 or uninstall previous Lotus Connections, then run 1.0.2 installer to install again.
CLFRP0308W: DB2 Administrator password field cannot be empty.	The Administrator password field is empty.	Make sure the DB2 Administrator password field is not empty.
CLFRP0309E: An error occurred while installing IBM DB2 Express Edition fixpack1. For additional information, refer to the log file .	Failure to install IBM DB2 Express Edition fixpack 1.	1. Check the detailed exception message below this error message in the log file to find the root cause. 2. Stop the Lotus Connection Pilot installation and then remove DB2 manually. (Refer to the DB2 information center.) 3. Try to install Lotus Connection Pilot again.
CLFRP0310E: An error occurred uninstalling WebSphere Update Installer V6.1.0.1. For additional information, refer to the log file .	Failure to uninstall IBM WebSphere Update Installer V6.1.0.1.	1. Check the detailed exception message below this error message in the log file to find the root cause. 2. Continue uninstalling Lotus Connections. Refer to the WebSphere Application Server information center to uninstall WebSphere Update Installer V6.1.0.1 manually after the Lotus Connections installation is completed.
CLFRP0311E: feature already installed.	The feature has already been installed.	1. Run the uninstaller guide to uninstall the feature. 2. Try to install the feature again.
CLFRP0315E: An error occurred while uninstalling IBM WebSphere Application Server 6.1. For additional information, refer to the log file .	Failure to uninstall IBM WebSphere Application Server 6.1.	1. Check the detailed exception message below this error message in the log file to find the root cause. 2. Continue uninstalling Lotus Connections. 3. After uninstallation is completed, try to uninstall WebSphere Application Server manually. (Refer to the WebSphere information center.)
CLFRP0316E: An error occurred installing 6.1.0.3-WS-WAS-IFPK37124.pak. For additional information, refer to the log file .	Failure to install 6.1.0.3-WS-WAS-IFPK37124.pak.	1. Check the detailed exception message below this error message in the log file to find the root cause. 2. Continue installing Lotus Connections. 3. Refer to the WebSphere Application Server information center to install the interim fix 6.1.0.3-WS-WAS-IFPK37124.pak manually after the Lotus Connections installation is completed.
CLFRP0317E: An error occurred uninstalling WebSphere Application Server V6.1.0.3. For additional information, refer to the log file .	An error occurred while uninstalling WebSphere Application Server V6.1.0.3.	1. Check the detailed exception message below this error message in the log file to find the root cause. 2. Continue uninstalling Lotus Connections. 3. Refer to the WebSphere Application Server information center to uninstall WebSphere Application Server V6.1.0.3 manually after the Lotus Connections installation is completed.
CLFRP0318W: The WebSphere Application Server administrator User name field cannot be empty.	The WebSphere Application Server administrator User name field is empty.	Make sure the WebSphere Application Server administrator User name field is not empty.
CLFRP0319W: WebSphere Application Server administrator user name must be 30 characters or less.	WebSphere Application Server administrator user name has exceeded 30 characters.	Make sure the WebSphere Application Server administrator user name has 30 characters or less.
CLFRP0321E: An error occurred while uninstalling IBM Update Installer for WebSphere Software Installation. For additional information, refer to the log file .	An error occurred while uninstalling IBM Update Installer.	1. Check the detailed exception message below this error message in the log file to find the root cause. 2. Continue the uninstallation. 3. After uninstallation is completed, try to uninstall WebSphere Update Installer manually. (Refer to the WebSphere information center.)
CLFRP0322E: An error occurred while creating a user. For additional information, refer to the log file .	This error is encountered if there is a failure to start WebSphere Application Server or generate a user.	Check the detailed exception message below this error message in the log file to find the root cause. Try to fix it and then do the user creation again.
CLFRP0324E: Uninstallation of offerings has failed.	An error occurred while uninstalling offerings.	1. Check the detailed exception message below this error message in the log file to find the root cause. 2. Try to fix it and then uninstall again.
CLFRP1001E: db2jcc_license_cu.jar and db2jcc.jar do not exist in .	The directory you specified does not contain all the required files.	Make sure db2jcc_license_cu.jar and db2jcc.jar exist in the specified directory.
CLFRP1002E: ojdbc14.jar does not exist in .	Installer cannot locate ojdbc14.jar.	Make sure ojdbc14.jar is in the specified directory.
CLFRP1003E: Cannot connect to database using provided settings, please check again!	This error is encountered if the user provided settings are not correct.	Input the correct database properties and try again.
CLFRP1004E: At least one feature must be selected for uninstall.	This error is encountered if no feature is selected for uninstall.	Make sure at least one feature is selected for uninstall.
CLFRP1005E: At least one feature must be selected for install.	This error is encountered if no feature is selected for install.	Make sure at least one feature is selected for install.
CLFRP1006E: uninstallInfo.txt missing, unable to uninstall this product.	Cannot find uninstallInfo.txt under the directory: Location>// uninstall/profiles/ .	Try to recover uninstallInfo.txt, and perform the uninstallation again.
CLFRP1007E: Uninstall of the component: has failed or this component has already been uninstalled.	Failure to uninstall the component.	1. Check the detailed exception message below this error message in the log file to find the root cause. 2. Try to fix it and then uninstall again.
EJPIC0060E: There were no profiles detected for the installed WAS and managed node selected.	There must be at least one profile on the existing managed node to continue.	Retrieve the install logs for errors and make sure at least one profile exists on the existing managed node. Then try the installer again.

Table 2. Installation error messages without codes

Message	Cause	Solution
At least one feature must be selected for install.	The installer requires the selection of at least one feature for both production and pilot installations.	Please choose at least one feature.
At least one feature must be selected for uninstall.	The installer requires the selection of at least one feature for both production and pilot uninstallations.	Please choose at least one feature.
Cannot connect to database using provided settings, please check again!	The installer validates a JDBC connection to ensure that the Connections application installed will be able to communicate with the database. This connection has the following requirements: 1. JDBC Driver Library: A valid path to the jars that provide JDBC connectivity. 2. Application User Account: A valid user account for the database that hosts the Connections application data. This is the user that the Connections application will use. 3. Application User Account password: The password for the application user account. 4. Host: Host name of the machine that has the database server. 5. Port: Port number used to connect to the database. 6. Database name: The name of the database.	Make sure the correct values have been provided.
db2jcc_license_cu.jar and db2jcc.jar does not exists in	The installer validates a JDBC connection to ensure that the Connections application installed will be able to communicate with the database. This error message is stating that a valid JDBC connection is not possible as the required DB2 jars are not located at the location specified.	In the install panel requesting JDBC connection information, ensure that the path leading to the db2jcc_license_cu and db2jcc jars is valid.
ojdbc14.jar does not exists in	The installer validates a JDBC connection to ensure that the Connections application installed will be able to communicate with the database. This error message is stating that a valid JDBC connection is not possible as a required Oracle jar is not located at the location specified.	In the install panel requesting JDBC connection information, ensure that the path leading to the ojdbc14.jar is correct.
Uninstall of the component: has failed or this component has already been uninstalled.	The process of removing a Connections application has failed.	Please retrieve the uninstall log, lcuninstalllog.txt, from the temp directory. Locate errors and contact support.
The user did not provide the mandatory input parameter WAS userid in the command line.	The update installer will not continue and will print out the command usage help on screen.	User has to add userid to the command line.

Table 3. Configuration error message codes

CLFRO2001E: Error processing config file: , .	The server encountered an error while parsing the specified configuration file.	Ensure that XML configuration files in the LotusConnections-config folders are valid.
CLFRO2002E: Unable to find configuration with id: .	The server could not retrieve an XML configuration file with the requested ID in the LotusConnections-config folder hierarchy.	Report this problem to Customer Support.
CLFRO2003E: Error processing global configuration file	The server could not retrieve or successfully parse a LotusConnections-config.xml configuration file from the LotusConnections-config folder hierarchy.	Report this problem to Customer Support.
CLFRO2004E: Error: does not have an id attribute in its config element.	The specified XML configuration file does not have a value defined for the required id attribute of the element.	Report this problem to Customer Support.
CLFRO2006E: href attribute in service element	The specified XML configuration file does not have a valid value defined for the href attribute; it should be a value that can be converted into a URL.	Update the value of the href attribute to be a properly formed URL string.
CLFRO2009E: Entry for service does not exist in global config file .	The global configuration file does not have a service reference for the requested service name.	Report this problem to Customer Support.
CLFRO2010E: Cannot locate schema file .	The server cannot find an xsd file required to validate the schema validation in the folder /config/cells/ /LotusConnections-config.	Report this problem to Customer Support.

Table 4. Directory error message codes

CLFRK0002E: Unable to determine memberUUID for {0}.	The federated realm is not configured correctly or the wimconfig.xml file contains errors.	Follow the instructions provided in the Installation Guide for Setting up federated repositories. If you edited the wimconfig.xml file, revert to the original copy of the file.
CLFRK0003E: Unable to locate VMM Profile Service {0}.	The VMM component is not functioning properly.	Ensure that the system is configured as a 'federated realm' by following the instructions provided in the Installation Guide for Setting up federated repositories.
CLFRK0004E: Unable to locate LDAP Profile Service {0}.	The LDAP component is not functioning properly.	You may be trying to implement a configuration that is not currently supported by Lotus Connections. To prevent this error, you would have to configure the system as a 'standalone LDAP user registry,' which is currently not supported.
CLFRK0005E: Unable to locate Persona Profile Service {0}.	The Profiles Service Atom feed component is not functioning properly.	You may be trying to implement a configuration that is not currently supported by Lotus Connections. To prevent this error, you would have to configure the system to rely on the Profiles service Atom feed, which is not currently supported.
CLFRK0006E: Unable to locate Memory Profile Service {0}.	The memory model service of the Waltz component is not functioning properly.	You may be trying to implement a configuration that is not currently supported by Lotus Connections. To prevent this error, you would have to configure Tomcat as the memory model, which is an unsupported configuration.
CLFRK0007E: Unable to access directory settings for Lotus Connections {0}.	Lotus Connections cannot find the LotusConnection-config.xml file.	Make sure the LotusConnection-config.xml file is installed on the system.

Troubleshooting overview
Activities error messages
Blogs error messages
Communities error messages
Dogear error messages
Home page error messages
Portlet error messages
Profiles error messages