Troubleshooting Oracle Business Intelligence Server Installation Errors

When the installation wizard encounters a problem, it shows the message The following component did not install successfully followed by the name of the installation component that failed to install. The following table provides a reference of the components, possible reasons for the component to fail installing, and steps for troubleshooting the installation failure.

Table 13-1 Oracle Business Intelligence Server Installation Errors

The Following Component Did Not Install Successfully Cause(s) Corrective Action(s)

  • Weblogic Installation

  • The port specified for Oracle WebLogic Node Manager is not open.

  • Incompatible Java version.

Verify that the port specified for Oracle WebLogic Node Manager, which is by default 9556, is open and not used.

Verify that the required Java version is installed on the server. The Oracle MICROS Enterprise Back Office Release Notes lists environment requirements for the release.

Review the root\temp\MM_Log.log log file and refer to the Oracle WebLogic help.

  • Obiee Install

  • Obiee Patch

  • Incorrect file structure for the installation files.

Verify that the file structure for the installation files matches the file structure in the downloaded installation archive.

Review the root\Program Files\Oracle\Inventory\logs log file and refer to the Oracle Business Intelligence Enterprise Edition help.

  • Nodemanager Start

  • The port specified for Oracle WebLogic Node Manager may not be open. The installation wizard allows you to continue after receiving this message.

Verify that the port specified for Oracle WebLogic Node Manager, which is by default 9556, is open and not used.

Review the following log files:

  • root\temp\MM_Log.log

  • install directory\Oracle\Middleware\wlserver_version\common\nodemanager

  • If the Microsoft Windows service failed, check the Microsoft Windows system log using the Event Viewer.

Refer to the Oracle WebLogic Node Manager help.

  • Domain Creation

  • Oracle WebLogic Node Manager failed or is not running.

  • Oracle WebLogic AdminServer failed or is not running.

In a web browser, navigate to http://WebLogic_AdminServer_Hostname:port/console where the default port is 7001.

If you cannot access the WebLogic console:

  • Verify that the port specified for the WebLogic AdminServer during installation is open and not used.

  • Review the root\temp\MM_Log.log log file.

  • If there is an issue regarding the AdminServer, review the logs in INSTALLATION_DIR\Oracle\Middleware\user_projects\domains\bifoundation_domain\servers\AdminServer\logs

  • Storing Configuration

  • Getting BI Server Name

  • App Cluster Creation

  • Remote Managed Server Creation

  • Node Manager Enrollment

  • JMS Creation (Add Modules, Add User, Add Policy)

  • JMS Server Creation

  • Enable Validate Basic Auth Credentials

  • Enable SSL (Portal, Obiee)

  • SAML EM Changes

  • Session Timeout

  • Oracle WebLogic AdminServer failed or is not running.

In a web browser, navigate to http://WebLogic_AdminServer_Hostname:port/console where the default port is 7001.

If you can access the WebLogic console, verify that the AdminServer(admin) server is running. Use the console to manually start the AdminServer if it is not running.

If you cannot access the WebLogic console:

  • Verify that the port specified for the WebLogic AdminServer during installation is open and not used.

  • Review the root\temp\MM_Log.log log file.

  • If there is an issue regarding the AdminServer, review the logs in INSTALLATION_DIR\Oracle\Middleware\user_projects\domains\bifoundation_domain\servers\AdminServer\logs

  • OBIEE Configuration

  • OBI server could not connect to Enterprise Back Office database server.

  • OBI server could not assign ports because they were closed or being used.

  • OBI server is using a dynamic IP address instead of a static IP address.

  • Java Development Kit installed in a folder containing spaces.

  • In cluster environments, non-primary server could not connect to the primary OBIEE server.

  • In cluster environments, the OBIEE managed server (bi_server) or OBIEE services are not running correctly on the primary OBIEE server.

Review the root\Program Files\Oracle\Inventory\logs log file.

  • If the log contains errors regarding the AdminServer, review the logs in INSTALLATION_DIR\Oracle\Middleware\user_projects\domains\bifoundation_domain\servers\AdminServer\logs

  • If the log contains errors regarding the bi_server, review the logs in INSTALLATION_DIR\Oracle\Middleware\user_projects\domains\bifoundation_domain\servers\bi_server\logs

Installation Stops Progressing at OBIEE Configuration contains information and instructions for cases where the installation stops progressing but does not add an error to the log files.

  • BI Cluster Configuration

  • SAML Enable SSO

  • SAML Primary Obiee

One or more of the following failed or is not running:

  • Oracle WebLogic Admin Server

  • Managed Servers

  • Oracle Process Manager (hostname_ORCLRNA) Server

In a web browser, navigate to http://WebLogic_AdminServer_Hostname:port/console where the default port is 7001.

If you can access the WebLogic console, verify that the AdminServer(admin) server and the bi_servernumber is running. Use the console to manually start the AdminServer and the bi_server if they are not running.

If you cannot access the WebLogic console:

  • Verify that the port specified for the WebLogic AdminServer during installation is open and not used.

  • Review the root\temp\MM_Log.log log file.

  • If there is an issue regarding the AdminServer, review the logs in INSTALLATION_DIR\Oracle\Middleware\user_projects\domains\bifoundation_domain\servers\AdminServer\logs

  • If the log contains errors regarding the bi_server, review the logs in INSTALLATION_DIR\Oracle\Middleware\user_projects\domains\bifoundation_domain\servers\bi_server\logs

  • If the log contains errors regarding the Oracle Process Manager, review the logs in INSTALLATION_DIR\Oracle\Middleware\instances\INSTANCE_NAME\diagnostics\logs, where INSTANCE_NAME can be ORCLRNA or HOSTNAME_ORCLRNA.

Refer to the Oracle WebLogic or the Oracle Business Intelligence Enterprise Edition help.

  • Restart Admin Server and BI Server

  • Restart AppServer

  • Restart BI Server

  • Oracle WebLogic AdminServer failed or is not running.

  • Managed Server failed or is not running.

  • The port specified for Oracle WebLogic AdminServer may not be open.

  • The port specified for Managed Servers may not be open.

In a web browser, navigate to http://WebLogic_AdminServer_Hostname:port/console where the default port is 7001.

If you can access the WebLogic console, verify that the AdminServer(admin) server and the bi_servernumber is running. Use the console to manually start the AdminServer and the bi_server if they are not running.

If you cannot access the WebLogic console:

  • Verify that the port specified for the WebLogic AdminServer during installation is open and not used.

  • Verify that the port specified for Managed Servers (bi_server and AppServer) are open and not used.

  • Review the root\temp\MM_Log.log log file.

  • If there is an issue regarding the AdminServer, review the logs in INSTALLATION_DIR\Oracle\Middleware\user_projects\domains\bifoundation_domain\servers\AdminServer\logs

  • If the log contains errors regarding the bi_server, review the logs in INSTALLATION_DIR\Oracle\Middleware\user_projects\domains\bifoundation_domain\servers\bi_server\logs

  • BIPChart DS creation

  • CoreDB DS creation

  • UserGroup DS creation

  • CoreDS creation

  • CEDS creation

  • Oracle WebLogic AdminServer failed or is not running.

  • Connection to database server failed.

  • Authentication for database user failed.

In a web browser, navigate to http://WebLogic_AdminServer_Hostname:port/console where the default port is 7001.

If you can access the WebLogic console, verify that the AdminServer(admin) server and the bi_servernumber is running. Use the console to manually start the AdminServer and the bi_server if they are not running.

If you cannot access the WebLogic console:

  • Verify that the port specified for the WebLogic AdminServer during installation is open and not used.

  • Review the root\temp\MM_Log.log log file.

  • If there is an issue regarding the AdminServer, review the logs in INSTALLATION_DIR\Oracle\Middleware\user_projects\domains\bifoundation_domain\servers\AdminServer\logs

  • SAML Create EM Roles

  • Oracle WebLogic AdminServer failed or is not running.

  • UserGroup data source created, but unable to connect to the database.

In a web browser, navigate to http://WebLogic_AdminServer_Hostname:port/console where the default port is 7001.

If you can access the WebLogic console, verify that the AdminServer(admin) server and the bi_servernumber is running. Use the console to manually start the AdminServer and the bi_server if they are not running.

If you cannot access the WebLogic console:

  • Verify that the port specified for the WebLogic AdminServer during installation is open and not used.

  • Review the root\temp\MM_Log.log log file.

  • If there is an issue regarding the AdminServer, review the logs in INSTALLATION_DIR\Oracle\Middleware\user_projects\domains\bifoundation_domain\servers\AdminServer\logs

  • SAML Configuration Portal Primary

  • SAML Configuration Portal Secondary
This error message occurs in cluster installations, and the component name identifies whether the error occurred on the primary OBI server or the non-primary OBI server.

  • The Oracle WebLogic AdminServer failed or is not running.

  • The Mapped Drive path for the OBIEE server installation is incorrect or inaccessible.

In a web browser, navigate to http://WebLogic_AdminServer_Hostname:port/console where the default port is 7001.

If you can access the WebLogic console, verify that the AdminServer(admin) server and the bi_servernumber is running. Use the console to manually start the AdminServer and the bi_server if they are not running.

If you cannot access the WebLogic console:

  • Verify that the port specified for the WebLogic AdminServer during installation is open and not used.

  • Verify that the port specified for Managed Servers (bi_server) is open and not used.

  • Review the root\temp\MM_Log.log log file.

  • If there is an issue regarding the AdminServer, review the logs in INSTALLATION_DIR\Oracle\Middleware\user_projects\domains\bifoundation_domain\servers\AdminServer\logs

  • If the log contains errors regarding the bi_server, review the logs in INSTALLATION_DIR\Oracle\Middleware\user_projects\domains\bifoundation_domain\servers\bi_server\logs

  • If the log contains errors regarding the AppServer, review the logs in INSTALLATION_DIR\Oracle\Middleware\user_projects\domain\servers\APPSERVER_NAME\logs, where APPSERVER_NAME is appServ1 or HOSTNAME_appServ1.

  • Start OPMN Service

  • Stop OPMN Service

  • Refer to the Oracle Process Manager and Notification help.

  • Review the root\temp\MM_Log.log log file.

  • If the log contains errors regarding the Oracle Process Manager, review the logs in INSTALLATION_DIR\Oracle\Middleware\instances\INSTANCE_NAME\diagnostics\logs, where INSTANCE_NAME can be ORCLRNA or HOSTNAME_ORCLRNA.

  • OBI DB Password Generation

  • Generate RPD Output File

  • Refer to the Oracle Database and the Oracle BI Repository (RPD) help.

  • Review the root\temp\MM_Log.log log file.

  • Add Policy to OBIEE Role

  • Oracle WebLogic Node Manager failed or is not running.

  • Oracle WebLogic AdminServer failed or is not running.

In a web browser, navigate to http://WebLogic_AdminServer_Hostname:port/console where the default port is 7001.

If you can access the WebLogic console, verify that the AdminServer(admin) server and the bi_servernumber is running. Use the console to manually start the AdminServer and the bi_server if they are not running.

If you cannot access the WebLogic console:

  • Verify that the port specified for the WebLogic AdminServer during installation is open and not used.

  • Review the root\temp\MM_Log.log log file.

  • If there is an issue regarding the AdminServer, review the logs in INSTALLATION_DIR\Oracle\Middleware\user_projects\domains\bifoundation_domain\servers\AdminServer\logs

  • Refresh GUID

  • Global Cache

  • Setup mail in OBIEE EM

  • RPD Deployment

  • WebCatalog Deployment

  • Oracle WebLogic AdminServer failed or is not running.

  • Oracle Process Manager failed or is not running.

In a web browser, navigate to http://WebLogic_AdminServer_Hostname:port/console where the default port is 7001.

If you can access the WebLogic console, verify that the AdminServer(admin) server and the bi_servernumber is running. Use the console to manually start the AdminServer and the bi_server if they are not running.

If you cannot access the WebLogic console:

  • Verify that the port specified for the WebLogic AdminServer during installation is open and not used.

  • Review the root\temp\MM_Log.log log file.

  • If there is an issue regarding the AdminServer, review the logs in INSTALLATION_DIR\Oracle\Middleware\user_projects\domains\bifoundation_domain\servers\AdminServer\logs

  • If the log contains errors regarding the bi_server, review the logs in INSTALLATION_DIR\Oracle\Middleware\user_projects\domains\bifoundation_domain\servers\bi_server\logs

  • If the log contains errors regarding the Oracle Process Manager, review the logs in INSTALLATION_DIR\Oracle\Middleware\instances\INSTANCE_NAME\diagnostics\logs, where INSTANCE_NAME can be ORCLRNA or HOSTNAME_ORCLRNA.

Refer to the Oracle WebLogic or the Oracle Process Manager help.

  • Portal Deployment

  • ObieeWebService Deployment

  • LogoutApp Deployment

  • AnalyticsRes Deployment

  • Undeploy Application

  • Undeploy Portal

  • Undeploy ObieeWebService

  • Undeploy LogoutApp

  • Undeploy AnalyticsRes

  • Oracle WebLogic AdminServer failed or is not running.

  • Installation wizard could not remove staged files.

In a web browser, navigate to http://WebLogic_AdminServer_Hostname:port/console where the default port is 7001.

If you can access the WebLogic console, verify that the AdminServer(admin) server is running. Use the console to manually start the AdminServer if it is not running.

If you cannot access the WebLogic console:

  • Verify that the port specified for the WebLogic AdminServer during installation is open and not used.

  • Review the root\temp\MM_Log.log log file.

  • If there is an issue regarding the AdminServer, review the logs in INSTALLATION_DIR\Oracle\Middleware\user_projects\domains\bifoundation_domain\servers\AdminServer\logs

If problems occur after attempting to remove or redeploy the application:

  • In the WebLogic console, verify that the AnalyticsRes, ObieeWebService, and LogoutApp web applications are Active in the Deployments list.

  • Review the logs in INSTALLATION_DIR\Oracle\Middleware\user_projects\domains\bifoundation_domain\servers\SERVER_NAME\logs to verify the deployment status of Reporting and Analytics.

  • Review the logs in INSTALLATION_DIR\Oracle\Middleware\user_projects\domains\bifoundation_domain\servers\bi_server\logs to verify the deployment status of the web applications.

Server Failed to Remove the Staged Files contains instructions for identifying and resolving the staged files issue.

Parent topic: Troubleshooting