IBM Connections wiki
IBM Connections 3.0.1 Documentation
Custom Search Scope...
IBM Connections 4.0 documentation
You are currently viewing machine translated content. IBM translation might be available. Click
IBM Translated Product Documentation
to see what is available.
Core error messages
February 11, 2013
Use the codes included in the error messages generated by IBM® Connections to identify problems with IBM WebSphere® Portal infrastructure and IBM HTTP Server and find solutions.
The following error messages are generated by
Portal infrastructure and
Portal infrastructure error messages
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.
HTTP Server error messages
ERROR: lib_stream: openStream: Failed in r_gsk_secure_soc_init: GSK_ERROR_BAD_CERT(gsk rc = 414)
If you see a 500 error when using HTTPS over the
HTTP Server to get to an application, HTTPS might not be configured correctly with the
Application Server plug-in. The
Application Server SSL certificate might not be trusted by the
Application Server plug-in configured for the
If this error occurs, check both your
HTTP Server and
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:
To fix this error, follow the instructions in the topic,
Configuring the IBM HTTP Server for SSL
Edit the article to add or modify attachments.
Compare selected versions
Summary of changes
This version (1)
Feb 11, 2013 2:31:53 PM
Copy and paste this wiki markup to link to this article from another article in this wiki.