OBIEE 11g: Error: "Cannot initialize cryptographic mechanism" in Configuration Assistant when Creating the ASInstance (Doc ID 1520156.1)

Last updated on JANUARY 21, 2013

Applies to:

Business Intelligence Server Enterprise Edition - Version 11.1.1.6.0 and later
Business Intelligence Suite Enterprise Edition - Version 11.1.1.6.0 and later
Information in this document applies to any platform.

Symptoms

You are installing OBIEE 11.1.1.6.0 as a software only installation on MS Windows 2008 R2:  You have already installed JDK 7 and WebLogic Server 10.3.6.

The Configuration Assistant fails at the step to create the ASInstance, and you see the following error:

[as] [ERROR] [] [oracle.as.provisioning] [tid: ...] [ecid: ...] [[
oracle.as.provisioning.engine.CfgWorkflowException
...
Caused by: oracle.as.provisioning.util.ConfigException:
Error creating ASInstance instance1.
Cause:
An internal operation has failed: java.lang.ExceptionInInitializerError
Action:
See logs for more details.
...
Caused by: java.lang.ExceptionInInitializerError
...
Caused by: java.lang.SecurityException: Can not initialize cryptographic mechanism
at javax.crypto.JceSecurity.<clinit>(JceSecurity.java:86)
...
Caused by: java.lang.SecurityException: The jurisdiction policy files are not signed by a trusted signer!
...
]]

 

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