Installing fixpack fails with exception 'CWPKI0032E: Error creating a self-signed certificate'

Technote (troubleshooting)


Problem

Upgrading Portal fails with the exception 'CWPKI0032E: Error creating a self-signed certificate', system cannot find the path specified

Symptom

Looking at the stopServer.log:
[4/25/11 11:27:42:733 CDT] 0000000a CertificateMa E CWPKI0032E: Error creating a self-signed certificate. The exception that occurred is:
\opt\app\AppServer\profiles\wp_profile\etc\key.p12 (The system cannot find the path specified.).
[4/25/11 11:27:42:733 CDT] 0000000a KeyStoreManag E CWPKI0031E: Error creating a client keystore or truststore during initialization. The exception that occurred is: CWPKI0032E: Error creating a self-signed
certificate. The exception that occurred is:
\opt\app\AppServer\profiles\wp_profile\etc\key.p12 (The system cannot find the path specified.)..
...
[4/25/11 11:27:43:202 CDT] 0000000a WsServerStop E ADMU3007E: Exception com.ibm.websphere.management.exception.ConnectorException: ADMC0053E:
The system cannot create a SOAP connector to connect to host CHI-WS-1625.na.newedge.int at port 10033 with SOAP connector security enabled.
[4/25/11 11:27:43:202 CDT] 0000000a WsServerStop A ADMU3007E: Exception com.ibm.websphere.management.exception.ConnectorException: ADMC0053E: The system cannot create a SOAP connector to connect to host <hostname> at port 10033 with SOAP connector security enabled.
at
com.ibm.websphere.management.AdminClientFactory.createAdminClient(AdminClientFactory.java:495)
at
com.ibm.ws.management.tools.LaunchUtils.getAdminClient(LaunchUtils.java:372)
...
Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:67)
...
Caused by: com.ibm.websphere.management.exception.ConnectorNotAvailableException:
[SOAPException: faultCode=SOAP-ENV:Client; msg=Error opening socket: javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.h: No trusted certificate found; targetException=java.lang.IllegalArgumentException: Error opening socket: javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.h: No trusted certificate found]
at
com.ibm.ws.management.connector.soap.SOAPConnectorClient.reconnect(SOAPConnectorClient.java:354)
...
Caused by: [SOAPException: faultCode=SOAP-ENV:Client; msg=Error opening socket: javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.h: No trusted certificate found;
targetException=java.lang.IllegalArgumentException: Error opening socket: javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.h: No trusted certificate found]
at
org.apache.soap.transport.http.SOAPHTTPConnection.send(SOAPHTTPConnection.java:449)
...

Cause

Portal is looking for the certificate in an unix location:

\opt\app\AppServer\profiles\wp_profile\etc\key.p12

But the key exists at this location:


C:\IBM\WebSphere\wp_profile\etc\key.p12


Diagnosing the problem

run serverStatus.bat -all found in the profile's bin folder.


The script finds the WebSphere_Portal and server1 server and then asks to copy the signer but it is looking in a unix file system location not the C:\IBM\WebSphere\wp_profile\etc directory for the key and trust .p12 files.

Resolving the problem

Go to the C:\IBM\WebSphere\wp_profile\properties directory and edit the ssl.client.props file.


Change the user.root to the appropriate profile (ie. C:\IBM\WebSphere\wp_profile) and then try the serverStatus command again.

When prompted for credentials again the command will complete successfully.

Run the Portal installer again to install fixpack/fix.



Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere Portal

Software version:

6.1, 7.0

Operating system(s):

AIX, Linux, Solaris, Windows

Reference #:

1497897

Modified date:

2013-07-10

Translate my page

Machine Translation

Content navigation