OBIEE 11g Error: "Error while starting the domain. Cause: Starting the Admin_Server timed out." During Configuration Stage of Installation (Doc ID 1488714.1)

Last updated on DECEMBER 04, 2014

Applies to:

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

Symptoms

Installed JDK, installed  WebLogic, Installed OBIEE software only

The configuration of OBIEE 11g (11.1.1.6), it is failing with an error that the AdminServer timed out  while starting.

The Oracle Installer log files (install<date-timestamp>.out shows:

 Creating a new AdminServer Object ...
 AdminServer port is 7001
 Starting the domain ...

oracle.as.provisioning.util.ConfigException:
Error while starting the domain.
Cause:
An error occurred while starting the domain.
Action:
See logs for more details.

...

...

Caused by: oracle.as.provisioning.util.ConfigException:
Error while starting the domain.
Cause:
Starting the Admin_Server timed out.
Action:
See logs for more details.

..

..

The AdminServer.log shows the following error:



####<Aug 28, 2012 3:19:26 AM EDT> <Warning> <RMI> <amdc-obiee-ux01> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1346138366759> <BEA-080003> <RuntimeException thrown by rmi server: weblogic.management.remote.iiop.IIOPServerImpl.newClient(Ljava.lang.Object;)

java.lang.NullPointerException.
java.lang.NullPointerException
at org.apache.harmony.security.Util.equalsIgnoreCase(Util.java:46)
at org.apache.harmony.security.fortress.PolicyUtils.getPolicyURLs(PolicyUtils.java:429)
at org.apache.harmony.security.fortress.DefaultPolicy$1.run(DefaultPolicy.java:324)
at org.apache.harmony.security.fortress.DefaultPolicy$1.run(DefaultPolicy.java:317)
at java.security.AccessController.doPrivileged(AccessController.java:202)
at org.apache.harmony.security.fortress.DefaultPolicy.refreshImpl(DefaultPolicy.java:317)
at org.apache.harmony.security.fortress.DefaultPolicy.<init>(DefaultPolicy.java:218)
at org.apache.harmony.security.fortress.DefaultPolicy.<init>(DefaultPolicy.java:211)
at org.apache.harmony.security.fortress.DefaultPolicy.<init>(DefaultPolicy.java:198)
at java.security.Policy.getDefaultProvider(Policy.java:485)
at java.security.Policy.getAccessiblePolicy(Policy.java:524)
at java.security.ProtectionDomain.implies(ProtectionDomain.java:199)
at java.security.AccessController.checkPermission(AccessController.java:98)
at com.sun.jmx.remote.security.SubjectDelegator.checkRemoveCallerContext(SubjectDelegator.java:135)
at javax.management.remote.rmi.RMIConnectionImpl.<init>(RMIConnectionImpl.java:127)
at weblogic.management.remote.iiop.IIOPServerImpl.makeClient(IIOPServerImpl.java:69)
at javax.management.remote.rmi.RMIServerImpl.doNewClient(RMIServerImpl.java:242)
at javax.management.remote.rmi.RMIServerImpl.newClient(RMIServerImpl.java:191)
at weblogic.management.remote.iiop.IIOPServerImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)

 

 

 

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