Configuration Wizard Hangs Indefinately And Error Is Noted In The AdminServer.log File From A Failed Attempt To Start The AdminServer: "JPS-06514: Opening of file based keystore failed, Caused By: java.security.InvalidKeyException: Illegal key size" (Doc ID 2111703.1)

Last updated on AUGUST 17, 2017

Applies to:

Primavera Gateway - Version 15.2.0.0 and later
Information in this document applies to any platform.

Symptoms

When attempting to create a new Primavera Gateway domain using the configuration wizard, the wizard hangs indefinitely and does not progress past creation of the WebLogic domain. 

The install$TIMESTAMP.out Oracle Inventory log file shows the following error:

PRM-Waiting to connect...
Connecting to t3://$ADMINSERVERNAME:$ADMINPORT with userid weblogic ...
This Exception occurred at $TIMESTAMP.
javax.naming.CommunicationException: t3://$ADMINSERVERNAME:$ADMINPORT: Destination ADMINSERVERIP, ADMINPORT unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination [Root exception is java.net.ConnectException: t3://$ADMINSERVERNAME:$ADMINPORT: Destination ADMINSERVERIP, ADMINPORT unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination]
PRM-Failed to connect. Will retry in 20 seconds
PRM-Waiting to connect...

  

The AdminServer.log file shows the following exception when the configuration wizard was attempting to start the AdminServer (or when attempting to start the AdminServer manually):

java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.management.provider.internal.EditAccessService
at org.jvnet.hk2.internal.Collector.throwIfErrors(Collector.java:88)
at org.jvnet.hk2.internal.ClazzCreator.resolveAllDependencies(ClazzCreator.java:269)
...
Caused By: weblogic.security.SecurityInitializationException: The loading of an OPSS java security policy provider failed due to an exception. See the exception stack trace or the server log file for the root cause. If there is no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: null
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1487)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.preInitialize(CommonSecurityServiceManagerDelegateImpl.java:1090)
at weblogic.security.service.SecurityServiceManager.preInitialize(SecurityServiceManager.java:925)
...
Caused By: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
...
Caused By: oracle.security.jps.JpsException: JPS-06514: Opening of file based keystore failed. Reason oracle.security.jps.service.keystore.KeyStoreServiceException: Failed to perform cryptographic operation
at oracle.security.jps.internal.config.OpssCommonStartup.start(OpssCommonStartup.java:211)
at oracle.security.jps.wls.JpsWlsStartup.start(JpsWlsStartup.java:80)
at oracle.security.jps.JpsStartup.start(JpsStartup.java:186)
...
Caused By: java.security.InvalidKeyException: Illegal key size

  

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms