Skip Headers
Oracle® Fusion Middleware Error Messages Reference
11g Release 1 (11.1.1.5.0)

Part Number E10113-08
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

25 CONF-30000 to CONF-35141

CONF-30000: Error creating Management Admin Server.
Cause: Oracle Instance directory {0} already exists.
Action: Provide a valid instance home path.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30001: Error creating Management Admin Server.
Cause: {0}
Action: See the log for more information.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30002: Error creating AS Component {0} of type {1}.
Cause: {0}
Action: See the log for more information.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30003: Error creating AS Component {0} of type {1}.
Cause: {0}
Action: See the log for more information.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30004: Error creating routing relationship to provider.
Cause: An internal error has occurred.
Action: See the log for more information.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30005: Error creating routing relationship to provider. Relation {0} already exists.
Cause: An internal error has occurred.
Action: See the log for more information.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30006: Timed out while waiting for Management Admin Server to start.
Cause: The process is taking more time or not listening at this time.
Action: See the log for more information.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30007: Management Admin Server appears to be unavailable.
Cause: {0}
Action: Make sure that the admin server is running and try again.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30008: Error creating routing relationship. Invalid user or provider components. User:{0}. Provider:{1}.
Cause: The user or provider components are not valid.
Action: Make sure that the user and providers are valid components.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30009: Cannot create Application Server. OracleInstance directory {0} already exists.
Cause: The oracle instance home exists
Action: Choose a different oracle instance home

Level: 1

Type: ERROR

Impact: Configuration

CONF-30010: An error occurred while provisioning an AS Instance (oracleInstance:{0} instanceName:{1}).
Cause: {0}
Action: See log for more information.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30011: Unable to access the Process Control Service.
Cause: Process Control Service is not available
Action: Try again after the process control service is available

Level: 1

Type: ERROR

Impact: Configuration

CONF-30012: Error occurred while starting {0} of type {1} in AS Instance {2}. See internal exception for details.
Cause: Internal error has happened.
Action: See log for more details

Level: 1

Type: ERROR

Impact: Configuration

CONF-30013: Error occurred while stopping {0} of type {1} in AS Instance {2}. See internal exception for details.
Cause: Some internal error has happened
Action: See error logs for more options

Level: 1

Type: ERROR

Impact: Configuration

CONF-30014: An unknown exception was generated while executing the configuration workflow. See internal exception for more details.
Cause: Workflow internal exception
Action: See logs for more information

Level: 1

Type: ERROR

Impact: Configuration

CONF-30015: Operation to provision an AS Instance (Instance Name:{0} Instance Home: {1}) timed out.
Cause: Timeout exception has happened
Action: See logs for more information

Level: 1

Type: ERROR

Impact: Configuration

CONF-30016: Failed to start an AS Instance (oracle instance:{0}, oracle home:{1}).
Cause: {0}
Action: See logs for more details

Level: 1

Type: ERROR

Impact: Configuration

CONF-30017: Error creating routing relationship. Relationship details { User:{0} Provider:{1} RelationshipName:{2} }.
Cause: {0}
Action: See logs for more details

Level: 1

Type: ERROR

Impact: Configuration

CONF-30018: Error creating AccessPoint {0}.
Cause: {0}
Action: See logs for more details

Level: 1

Type: ERROR

Impact: Configuration

CONF-30019: Unable to obtain the DeploymentManager. Deployment URI:{0}
Cause: Connected Deployment manager could not be found.
Action: See logs for more details

Level: 1

Type: ERROR

Impact: Configuration

CONF-30020: Error deploying a J2EE Application. See internal exception for details.
Cause: Internal Exception
Action: See logs for more details

Level: 1

Type: ERROR

Impact: Configuration

CONF-30021: Unable to locate the target for deployment.Target: {0}
Cause: The deployment target does not exist
Action: Make sure that the target exists

Level: 1

Type: ERROR

Impact: Configuration

CONF-30022: Error creating UnmanagedNetworkDevice {0}.
Cause: {0}
Action: See logs for more details

Level: 1

Type: ERROR

Impact: Configuration

CONF-30023: Error updating metric rule {0}.
Cause: {0}
Action: See logs for more details

Level: 1

Type: ERROR

Impact: Configuration

CONF-30024: Error Executing asctl command through ASconfig: {0}.
Cause: {0}
Action: See logs for more details

Level: 1

Type: ERROR

Impact: Configuration

CONF-30025: Unable to locate the endpoint - {0}.
Cause: The specified end point does not exist
Action: Specify a valid end point

Level: 1

Type: ERROR

Impact: Configuration

CONF-30026: Failed to start a MAS Transaction.
Cause: {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30027: Failed to commit a MAS Transaction.
Cause: {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30028: Failed to roll back a MAS Transaction.
Cause: {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30029: Failed to register an LDAP Server as an unmanaged topology node. LDAP Server name:{0} LDAP Server type:{1}
Cause: {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30030: Invalid LDAP Server Name. Specify a valid LDAP server name and try again.
Cause: Invalid LDAP server
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30031: Failed to register an LDAP Server as an unmanaged topology node.
Cause: Invalid LDAP Server Type {0}.
Action: Specify one of the following valid supported LDAP Server Types: \'UnmanagedLDAPServer\', \'UnmanagedOIDComponent\', \'UnmanagedActiveDirectory\'

Level: 1

Type: ERROR

Impact: Configuration

CONF-30032: Error while registering database schema {0} to MAS .
Cause: {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30033: Error while calling configuration assistant {0}
Cause: {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30034: Error occurred while trying restart {0} of type {1} in AS Instance {2}. See internal exception for details.
Cause: {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30035: Failed to create a routing relationship to provider.
Cause: {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30036: Error generating Provisioning workflow
Cause: Invalid FarmName
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30037: Error updating Bootstrap Credentials for IDStore
Cause: {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30038: Error updating Bootstrap Credentials for IDStore
Cause: {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30039: Error creating a Synchronized Group {0}.
Cause: {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30051: Error locating the ASInstance in the Farm with the given canonical path {0}
Cause: {0}
Action: Provide the correct canonical path for the ASInstance

Level: 1

Type: ERROR

Impact: Configuration

CONF-30052: Error locating the ASJ2EEApplication in the Farm with the given canonical path {0}
Cause: {0}
Action: Provide the correct canonical path for the ASJ2EEApplication

Level: 1

Type: ERROR

Impact: Configuration

CONF-30053: Error locating the SystemComponent in the Farm with the given canonical path {0}
Cause: {0}
Action: Provide the correct canonical path for the SystemComponent

Level: 1

Type: ERROR

Impact: Configuration

CONF-30054: Error obtaining InstanceHome location for {0}
Cause: {0}
Action: See logs for more details

Level: 1

Type: ERROR

Impact: Configuration

CONF-30055: Error obtaining the OracleHome associated with {}
Cause: {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30056: TopologyNode {0} does not exist in farm.
Cause: Invalid canonical path
Action: Provide a valid canonical path

Level: 1

Type: ERROR

Impact: Configuration

CONF-30057: An exception was generated while executing the provisioning workflow.
Cause: {0}
Action: See logs for more details

Level: 1

Type: ERROR

Impact: Configuration

CONF-30060: Error while calling validation assistant {0}
Cause: {0}
Action: See log for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30090: The given node is not a valid MDS schema. {0}
Cause: Invalid MDS schema
Action: Provide a valid MDS Schema.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30091: Error deploying a J2EE Application. {0}
Cause: Internal Exception
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30092: The process has been interrupted
Cause: The process has been interrupted
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30093: The application archive could not be loaded as a deployable object
Cause: Some deployment Exception has happened
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30094: File not found. The specified file {0} is not found.
Cause: File is not present
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30095: Configuration Exception happened. See the embedded exception for more details.
Cause: Internal Exception
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30096: Unable to get the deployment configuration.
Cause: The application archive {0} is a invalid archive.
Action: Check the archive and try again.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30097: Unable to locate application archive. "{0}"
Cause: The location to archive is not correct.
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30098: Unable to obtain the DeploymentManager. Deployment URI:{0}
Cause: Internal Exception
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30099: Unable to locate the target for deployment. Target: {0}
Cause: Invalid deployment target
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30100: Error creating an Oracle Load Balancer {0}.
Cause: {0}
Action: See logs for more details

Level: 1

Type: ERROR

Impact: Configuration

CONF-30101: Error associating ASInstance(s) with an Oracle Load Balancer {0}.
Cause: {0}
Action: Specify valid ASInstances.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30111: Error while registering unmanaged SSO Server to MAS .
Cause: {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30112: Failed to stop an AS Instance (oracle instance:{0}).
Cause: {0}
Action: See logs for more details

Level: 1

Type: ERROR

Impact: Configuration

CONF-30113: See logs for more details.
Cause:
Action:

Level: 1

Type: ERROR

Impact: Configuration

CONF-30114: See logs for more details.
Cause:
Action:

Level: 1

Type: ERROR

Impact: Configuration

CONF-30115: Error storing entries in Credential Store
Cause: {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30116: Error retrieving entries from Credential Store
Cause: {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30117: Error deleting entries from Credential Store
Cause: {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-30121: Error assigning AccessPoint {0} to {1}
Cause: {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35001: Invalid host value provided to config framework.
Cause: Invalid host value provided to config framework.
Action: Provide a valid host value to config framework

Level: 1

Type: ERROR

Impact: Configuration

CONF-35002: Invalid port value provided to config framework.
Cause: Invalid port value provided to config framework.
Action: Provide a valid port value to config framework

Level: 1

Type: ERROR

Impact: Configuration

CONF-35003: Error while creating the domain.
Cause: An internal operation has failed.
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35004: Error while creating Managed Server.
Cause: An internal operation has failed: {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35005: Error while starting the domain.
Cause: An internal WLST operation has failed.
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35006: Unable to connect to the AdminServer.
Cause: An internal operation has failed:{0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35007: Error while setting control flag {0}.
Cause: An internal operation has failed: {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35009: Error while stopping the domain.
Cause: An internal operation has failed: {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35010: Error while deploying the Application {0} .
Cause: An internal operation has failed: {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35011: Error while starting the Application {0} .
Cause: An internal operation has failed: {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35012: Error while stopping the Application {0} .
Cause: An internal operation has failed: {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35015: Error while creating Group {0} .
Cause: An internal operation has failed: {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35020: Error while creating DataSource {0} .
Cause: An internal operation has failed: {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35025: Error while creating JMSResource {0}.
Cause: An internal operation has failed: {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35030: Error while creating Authenticator {0}.
Cause: An internal operation has failed: {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35035: Error while executing WLS script located at {0}.
Cause: An internal operation has failed: {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35040: Error while creating Network Channel {0}.
Cause: An internal operation has failed: {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35075: Error creating ASInstance {0}.
Cause: An internal operation has failed: {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35076: Error creating ASComponent {0}.
Cause: An internal operation has failed: {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35080: Error Applying template.
Cause: A WLST Error occurred: {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35081: Error Applying template.
Cause: Domain Home cannot be empty.
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35082: Error creating Domain {0}.
Cause: A WLST Error occurred.
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35085: Error creating Cluster {0}.
Cause: See logs for more details.
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35090: Error while starting the domain.
Cause: Starting the Admin_Server timed out.
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35091: Error while starting the domain.
Cause: An error occurred while starting the domain.
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35092: Error Setting target for Startup class {0}.
Cause: An internal error has occurred.
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35095: Error setting target for Shutdown class {0}.
Cause: An internal error has occurred.
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35100: Error starting and enrolling Node Manager
Cause: An internal operation has failed.
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35105: Error Creating Multi Data Source {0}
Cause: An internal operation has failed
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35110: Error Extending Targets With JRF Template.
Cause: WLST Error. {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35111: Error Extending Targets With JRF Template.
Cause: Domain Home cannot be empty.
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35115: Error Setting target to Managed Server {0}.
Cause: Check the logs for details.
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35120: Error Starting Managed Server {0}.
Cause: An internal error has occurred : {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35122: Number Format Exception thrown when trying to get nodemanager port.
Cause: The Nodemanager Listen port entry is not present in the nodemanager.properties file or it is not set to numeric value.
Action: Add the Nodemanager port (for example, ListenPort=5556) to the nodemanager.properties file and press Retry button to continue the configuration.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35124: Stage Modes 'EXTERNAL_STAGE' and 'NOSTAGE' cannot be set simultaniously.
Cause: Both stage modes 'EXTERNAL_STAGE' and 'NOSTAGE' have been set.
Action: Use only 'EXTERNAL_STAGE' or 'NOSTAGE' mode for deployment

Level: 1

Type: ERROR

Impact: Configuration

CONF-35126: Node Manager Listen Port is set to a negative number.
Cause: Node Manager Listen Port is set to a negative number.
Action: Add the Nodemanager port(Eg: ListenPort=5556) to the nodemanager.properties file and press Retry button to continue the configuration.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35128: Unable to set Attribute 'StartScriptEnabled'.
Cause: Unable to set Attribute 'StartScriptEnabled' since the NodeManager is already running.The installer needs to set it to 'true'
Action: Stop the Node Manager and retry the installer.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35130: Unable to set Attribute 'StartScriptEnabled'.
Cause: Unable to set Attribute 'StartScriptEnabled' since the NodeManager is already running.The installer needs to set it to 'true'
Action: Stop the Node Manager and retry the installer.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35132: Unable to set Attribute 'NativeVersionEnabled'.
Cause: Unable to set Attribute 'NativeVersionEnabled' since the NodeManager is already running.The installer needs to set it to 'true'
Action: Stop the Node Manager and retry the installer.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35134: Unable to set Attribute 'NativeVersionEnabled'.
Cause: Unable to set Attribute 'NativeVersionEnabled' since the NodeManager is already running.The installer needs to set it to 'true'
Action: Stop the Node Manager and retry the installer.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35136: Error while starting the Managed Server.
Cause: An interanal WLST operation has failed.
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35137: Managed Server {0} started in FAILED state.
Cause: An internal error has occured : {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35140: Managed Server shutdown command Failed.
Cause: An internal error has occured : {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration

CONF-35141: Managed Server {0} shutdown timed out.
Cause: An internal error has occured : {0}
Action: See logs for more details.

Level: 1

Type: ERROR

Impact: Configuration