ADMN-705021 error when doing any configuration change on AS 10.1.2.x

(Doc ID 846150.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Enterprise Manager for iAS - Version: 10.1.2.0.2 to 10.1.2.3.0
Oracle Fusion Middleware - Version: 10.1.2.0.2 to 10.1.2.3.1   [Release: AS10gR2 to AS10gR2]
Information in this document applies to any platform.
Oracle Application Server 10g Enterprise Edition - Version: 10.1.2.0.2 to 10.1.2.3.1

Symptoms

Doing any configuration change using the Application Server Control (ASC) returns the following error in the ASC page :

Error saving Data Source properties :The configuration files for this Oracle Application Server
instance are inconsistent with the configuration stored in the repository. In order to protect
the repository,
no further configuration or deployment operations are allowed until the problem with the
configuration on the filesystem is resolved. This condition arises when a prior operation was
unsuccessful. The exception associated with this failed operation is: {0} . Please also check the
logs located at ORACLE_HOME/dcm/logs to determine why DCM was unsuccessful in updating the
configuration files on disk. Some possible causes are:
* permissions on files
* file contention issues on Windows NT
* internal Oracle error

After resolving the problem that prevented DCM from updating the configuration files, you may
use the dcmctl resyncInstance command to resolve the problem. Alternatively, you can stop and
then restart the active dcmctl or EMD process and resyncInstance will automatically be
performed. Resolution:
Base Exception:
java.net.ConnectException
Connection refused. Connection refused

'dcmctl updateconfig' command returns following error:

$ dcmctl updateconfig
ADMN-705021
The configuration files for this Oracle Application Server instance are inconsistent with the
configuration stored in the repository. In order to protect the repository,
no further configuration or deployment operations are allowed until the problem with the
configuration on the filesystem is resolved. This condition arises when a prior operation was
unsuccessful. The exception associated with this failed operation is:
{0}
. Please also check the logs located at
ORACLE_HOME/dcm/logs to determine why DCM was unsuccessful in updating
the configuration files on disk. Some possible causes are:

* permissions on files
* file contention issues on Windows NT
* internal Oracle error


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