Troubleshooting 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 12-1 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.

  • 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

  • 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)

  • 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

  • Restart Admin Server

  • Restart AppServer

  • 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 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.

  • Verify that the port specified for Managed Servers (AppServer) 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

  • Portal Deployment

  • Undeploy Portal

  • 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, 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.

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

Parent topic: Troubleshooting