OBIEE 11g: Error: "Server not initialized. Please make sure the repository is ready." Opening BI Publisher Home Page (Doc ID 1602339.1)

Last updated on FEBRUARY 21, 2017

Applies to:

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

Symptoms

You have installed OBIEE 11g.  When you try to open the BI Publisher home page, using the URL:

http://<machine_name>:19000/xmlpserver/

you get the following error:

Server not initialized. Please make sure the repository is ready.

In bipublisher-1.log file you see the following error:

[2013-10-28T16:38:53.908-02:00] [AdminServer] [WARNING] [] [oracle.xdo] [tid: 13] [userId: <anonymous>] [ecid: 3f1e544d03028f9f:5c459859:1420022273b:-8000-00000000000005da,0] [APP: bipublisher#11.1.1] oracle.xdo.servlet.CreateException: Failed to retrieve a Config Provider. Make sure that your repository is correctly setup[[
at oracle.xdo.servlet.ReportException.fillInStackTrace(ReportException.java:124)
at java.lang.Throwable.<init>(Throwable.java:196)
at java.lang.Exception.<init>(Exception.java:41)
at oracle.xdo.servlet.ReportException.<init>(ReportException.java:36)
at oracle.xdo.servlet.CreateException.<init>(CreateException.java:18)
at oracle.xdo.servlet.security.BaseSecurityHandler.<init>(BaseSecurityHandler.java:155)
at oracle.xdo.servlet.security.XDOSecurityHandler.<init>(XDOSecurityHandler.java:41)
at oracle.xdo.servlet.security.SecurityHandler.createHandler(SecurityHandler.java:244)
at oracle.xdo.servlet.security.SecurityHandler.getHandler(SecurityHandler.java:185)
at oracle.xdo.servlet.XDOServlet.init(XDOServlet.java:152)
at oracle.xdo.servlet.init.ReInitializeServiceImpl.reinit(ReInitializeServiceImpl.java:55)
at oracle.xdo.servlet.init.InitCheckingFilter.doFilter(InitCheckingFilter.java:55)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:324)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:460)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:163)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)

You check the OBIEE components in Enterprise Manager, and can see that bipublisher(11.1.1) is running, but that bimad(11.1.1) is not running.

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