FMW 11g PFRD Config Fails With : Error creating ASComponent - Component Already Exists (Doc ID 1366347.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Fusion Middleware - Version 11.1.1.2.0 and later
Microsoft Windows x64 (64-bit)
***Checked for relevance on 16-Apr-2013***

Symptoms

Oracle Fusion Middleware (FMW) 11g Portal, Forms, Reports, Discoverer (PFRD) has been successfully installed and patched to the latest available Patch.

When an attempt is made to configure a domain and instance (called asinst_1), the configuration fails when attempting to start EM agent.

The following errors are written to the install[date/time].log:

[2011-10-07T09:14:27.152+01:00] [as] [NOTIFICATION] [] [oracle.as.provisioning] [tid: 15] [ecid: 0000JBTQvIrFc5kLSy0Fyc1EZf6W000006,0] Created component emagent_asinst_1
[2011-10-07T09:14:27.152+01:00] [as] [NOTIFICATION] [] [oracle.as.provisioning] [tid: 15] [ecid: 0000JBTQvIrFc5kLSy0Fyc1EZf6W000006,0] Trying to start the component emagent_asinst_1
[2011-10-07T09:14:37.152+01:00] [as] [WARNING] [] [oracle.as.config] [tid: 15] [ecid: 0000JBTQvIrFc5kLSy0Fyc1EZf6W000006,0] Failed to start component emagent_asinst_1[[
oracle.as.config.ProvisionException: HTTP status code = 204 : 0 of 1 processes started.
at oracle.as.config.impl.OracleASComponentBaseImpl.manageProcess(OracleASComponentBaseImpl.java:942)
at oracle.as.config.impl.OracleASComponentBaseImpl.start(OracleASComponentBaseImpl.java:1061)
at oracle.as.provisioning.fmwadmin.ASComponentProv.createComponent(ASComponentProv.java:133


The following errors are written to the install[date/time].out:

Instance asinst_1 already exists, continuing with component creation
C:\Oracle\Middleware\as_1 C:\Oracle\Middleware\asinst_1 asinst_1
oracle.as.config.ProvisionException: Failed to start the component
at oracle.as.provisioning.fmwadmin.ASComponentProv.createComponent(ASComponentProv.java:137)
at..


Note that these error messages are misleading. To see the real error it is necessary to check the EM Agent logs from <%Instance Home%>\EMAGENT\emagent\sysman\log.

emdctl.trc shows:

2011-10-07 10:14:29,433 Thread-5048 ERROR main: nmectla_agentctl: Error connecting to http://myhost.domain:5155/emd/main. Returning status code 1
2011-10-07 10:14:30,370 Thread-2748 ERROR main: nmectl.c: nmectl_validateTZRegion, agentTZoffset =120,and testTZoffset for +01:00:60 do not match


emagent.nohup shows multiple:

----- Fri Oct 7 10:14:36 2011::Mismatch detected between timezone in env (UTC) and in C:\Oracle\Middleware\asinst_1\EMAGENT\emagent_asinst_1/sysman/config/emd.properties (+01:00). Forcing value to latter.. -----
----- Fri Oct 7 10:14:36 2011::The agentTZRegion value in C:\Oracle\Middleware\asinst_1\EMAGENT\emagent_asinst_1/sysman/config/emd.properties is not in agreement with what agent thinks it should be.Please verify your environment to make sure that TZ setting has not changed since the last start of the agent.
If you modified the timezone setting in the environment, please stop the agent and exectute 'emctl resetTZ agent' and also execute the script mgmt_target.set_agent_tzrgn(<agent_name>, <new_tz_rgn>) to get the value propagated to repository -----

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