E1: SVM: Server Manager Management Console (SMMC) Will not install: Failed at "Could not get DeploymentManager" (Doc ID 985079.1)

Last updated on AUGUST 18, 2015

Applies to:

JD Edwards EnterpriseOne Tools - Version 8.98 and later
Information in this document applies to any platform.

Symptoms

Scenario 1 - Server Manager Management Console (SMMC) install fails.  Port is in use. Error "Could Not Get DeploymentManager"

Server Manager Console install fails. (In the information below, the install is going directly under the C drive.  In your install, it will depend on your install location.)

There is a pop-up error on screen that says to check this log file for details: . c:\jde_home\smmc_install.log

The smmc_install.log says:

(error code = 601; message="err"; additional data = [Errors found in: C:\jde_home\logs\MCDeploy_stderr.log])

The MCDeploy_stderr.log file says:

Failed at "Could not get DeploymentManager".
This is typically the result of an invalid deployer URI format being supplied, the target server not being in a started state or incorrect authentication details being supplied.
More information is available by enabling logging -- please see the Oracle Containers for J2EE Configuration and Administration Guide for details.

...then it says the management console install failed and the console is not started.
OC4J does not install.  A few directories are created, the OC4J install fails, and then the SMMC installer rolls back its install. It orphans a few directories.  It is fairly obvious that it does not leave all the directories that would be needed for the SMMC install.

 

Scenario 2 - Installing Management Console Fails With Error "Could Not Get DeploymentManager". Windows Server 2008. Administrator privileges required.

Installing Server Manager Console on Windows Server 2008 Standard SP 2, 64 bit fails. You get the following error on the screen:

Errors occurred during installation.
An error occurred and the production installation failed.  Look at the log in c:\jde_home\logs\smmc_install.log for details.

In the MCDeploy_stderr.log you have the following errors:

Failed at "Could not get DeploymentManager".


This is typically the result of an invalid deployer URI format being supplied, the target server not being in a started state or incorrect authentication details being supplied.
More information is available by enabling logging -- please see the Oracle Containers for J2EE Configuration and Administration Guide for details.

Error occurred during deployment of MC. Exitcode = 1
The service is not responding to the control function.

In the smmc_install.log you have the following errors repeatedly:

(May 11, 2010 3:43:05 PM), Install, com.installshield.wizard.platform.win32.Win32ProductServiceImpl, msg1, uninstalling Create Directory (createTargetDir1)
(May 11, 2010 3:43:06 PM), Install, com.installshield.wizard.platform.win32.Win32ProductServiceImpl, err, An error occurred and product uninstallation failed. Look at the log file C:\jde_home\logs\smmc_install.log for details.
(May 11, 2010 3:43:06 PM), Install, com.installshield.product.actions.CreateDirectory, err, ProductException: (error code = 601; message="err"; additional data = [Can not delete : C:\jde_home\targets : ServiceException: (error code = -30020; message = "The directory is not empty.
(145)"; severity = 0)])

STACK_TRACE: 12
ProductException: (error code = 601; message="err"; additional data = [Can not delete : C:\jde_home\targets : ServiceException: (error code = -30020; message = "The directory is not empty.
(145)"; severity = 0)])

Changes

This is a new install of the Server Manager Management Console (SMMC).

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