19 EM-00251 to EM-02674

EM-00251: No connection to the WebLogic managed server {0}.

Cause: The WebLogic managed server was down.

Action: Verify that the managed server is up and running.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00252: Error in accessing proxy MBean for this system component in WebLogic managed server {0}

Cause: Component was down

Action: Start the component, or verify that the component has been deployed on the managed server.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00268: Error in querying ports configuration for system component {0}

Cause: Component was down

Action: Start the component.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00301: Error in fetching data from target application.

Cause: Target application is down.

Action: Ensure target application is running.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00302: Error fetching data from target server in the Oracle WebLogic Server domain.

Cause: The target WebLogic server is down.

Action: Make sure the target server is up and running.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00303: Error in discovering web service endpoints for target application.

Cause: Target application is down.

Action: Ensure target application is running.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00351: Unable to connect to Oracle WSM Policy Manager.

Cause: The Oracle WSM Policy Manager was down or not accessible.

Action: Make sure Oracle WSM Policy Manager (wsm-pm application) is up and accessible. Also, ensure you have right roles to access the Service.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00426: Unable to save changes to registered service

Cause: The service repository is unavailable.

Action: Ensure that the service repository is up and running.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00428: Unable to delete registered service

Cause: The service is no longer valid.

Action: Ensure that the service is valid and is registered. Make sure the endpoint and WSDL for the service are accessible.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00430: Unable to register service due to duplicate service name

Cause: The service name is already registered.

Action: Ensure that the service name is unique.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00432: Invalid WSIL URL

Cause: The WSIL URL is invalid. The URL is unreachable or doesn't contain a valid WSIL.

Action: Ensure that the WSIL URL is valid and available.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00434: Invalid WSIL File

Cause: The WSIL file is invalid. The file is not a valid WSIL document.

Action: Ensure that the uploaded file is a valid WSIL document.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00440: Service repository operation failed

Cause: Service repository is unavailable.

Action: Ensure that the service repository is up and running.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00451: Failed to access WSDL

Cause: Invalid WSDL location or WSDL is not accessible

Action: Make sure you provide a valid WSDL location. If the location is valid, make sure it is accessible. Also, make sure you have proper privileges to access the WSDL with username and password.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00452: Failed to parse WSDL file

Cause: Invalid WSDL content

Action: Ensure that the WSDL is syntactically and semantically correct.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00453: Failed to invoke operation

Cause: Invalid input arguments

Action: Make sure you provide the required input argument values, and that the values are the proper type (for example, integer, string, and so on).

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00454: Failed to invoke operation

Cause: Unable to read SOAP action for selected operation

Action: Make sure right SOAP Action value is set.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00455: Failed to change view from 'XML View' to 'Tree View'

Cause: Invalid payload contents in XML format

Action: Make sure you provide a valid payload to parse and check if any required tag is missing or broken.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00456: Failed to change view from 'XML View' to 'Tree View'

Cause: Invalid input argument

Action: Make sure you provide the required input argument values, and that the values are the proper type (for example, integer, string, and so on).

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00457: Failed to load key aliases from the keystore

Cause: Invalid keystore information

Action: Make sure you provide a valid keystore location and password.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00458: Failed to get compatible client policies from the WSDL

Cause: The WSDL is not accessible or you do not have the privilege to get policies.

Action: Make sure you have the privilege to get the client policies.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00459: Failed to update the URL with the server IP address.

Cause: The IP address of the server is not available due to database connection failure or missing target information.

Action: Make sure you have the target discovered successfully with the server IP address.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00501: TopLink Sessions were not found

Cause: TopLink MBeans were not found

Action: Ensure that the application has been accessed to register the MBeans. Make sure that "-Declipselink.register.dev.mbean=true" and "-Declipselink.register.run.mbean=true" are part of $JAVA_OPTIONS

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00601: Error in getting WSDL for Web service client.

Cause: Target web service application is down.

Action: Ensure target web service application is running.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00602: Error in attaching/detaching policies.

Cause: Target application or Oracle WSM Policy Manager is down.

Action: Ensure target application and Oracle WSM Policy Manager is running.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-00603: Error in getting policy subject from target application.

Cause: Target web service application is down.

Action: Ensure target Web service application is running.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-01052: Error in querying OPSS application policy MBean object name.

Cause: The WebLogic managed server was down.

Action: Verify that the managed server is up and running.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-01053: Application stripe entry {0} does not exist in policy store.

Cause: Application stripe ID used to access policies from policy store did not have any data.

Action: Check the application stripe ID data provided in configuring Fusion MiddleWare control application deployment wizard security task.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-01055: Error in querying OPSS system policy MBean object name.

Cause: The WebLogic managed server was down.

Action: Verify that the managed server is up and running.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-01061: Error in querying OPSS credential store MBean object name.

Cause: The WebLogic managed server was down.

Action: Verify that the managed server is up and running.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-01321: Cannot obtain application information

Cause: The application is not active

Action: Make sure that the application is active or running

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-01322: Cannot obtain MDS information for selected application

Cause: MDS is not properly configured for the application

Action: Make sure that MDS config mbean is accessible on the mbean server. If it is not, verify that appropriate MDS configuration file (web.xml) contains ADFConfigRuntimeLifeCycleCallBack listener to register MDS config mbean and MDS is configured properly in adf-config.xml.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-01323: Error while performing MDS runtime (import, export or purge) operation

Cause: MDS runtime mbean is not found on runtime mbean server

Action: Make sure that the MDS runtime mbean is accessible on runtime mbean server. If it is not, verify that appropriate MDS configuration file (weblogic-application.xml) contains WLLifecycleListener listener to register MDS runtime mbean.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-01324: Error while retrieving data from page cache

Cause: JavaBean stored in the session has expired or was destroyed

Action: Start a fresh session by logging into EM again.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-01325: Cannot obtain MDS target repository information

Cause: MDS target repository is not configured

Action: Verify the MDS configuration by checking the contents of the configuration files (for example, adf-config.xml and mds-config.xml).

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02006: Error retrieving Configuration MBeans for ADFConnectionMBeans {0}.

Cause: The ADF Connection and Configuration MBean is not available or accessible.

Action: Configuration options currently unavailable. The application might be down, did not start properly, or is incorrectly packaged. Check the log files for further details.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02056: Error getting DAD MBean.

Cause: The DAD MBean is not available or accessible.

Action: Configuration options currently unavailable. The application might be down, did not start-up properly, or is incorrectly packaged. Check the log files for further detail.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02057: Error getting Cache MBean Object Name.

Cause: The Cache MBean is not available or accessible.

Action: Configuration options currently unavailable. The application might be down, did not start-up properly, or is incorrectly packaged. Check the log files for further detail.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02058: Error getting Middle Tier MBean Object Name.

Cause: The Middle Tier MBean is not available or accessible.

Action: Configuration options currently unavailable. The application might be down, did not start-up properly, or is incorrectly packaged. Check the log files for further detail.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02063: Error getting Portal site URL.

Cause: Wiring MBean Could not connect to the Portal repository.

Action: The Portal Database maybe down or the Portal DAD has incorrect username, password or connect string information. Check the log files for further detail.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02201: Error connecting to the Domain Runtime MBean Server.

Cause: The admin server is not working properly.

Action: Ensure the target admin server is running properly.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02202: Error getting the list of folders from the credential store.

Cause: There are issues with the JPS credential store MBean.

Action: Ensure the JPS credential store MBean is registered and working properly through the System MBean Browser.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02203: Error obtaining the UMS server information.

Cause: The UMS server is down, or not started properly, or not deployed on the target.

Action: Ensure the UMS server is running properly.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02251: Error connecting to Forms Config MBeans

Cause: The managed server that hosts the Forms application was down, or the Forms application was down or not deployed on this server.

Action: Depending on the specific cause, start the managed server if it is down, start the Forms application if it is down, or deploy the Forms application on this domain if haven't been deployed already.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02652: error while initializing data for the BI Instance {0}

Cause: The server for Fusion Middleware Control failed to correctly communicate with the server for the BI Instance.

Action: Ensure that the server for the BI Instance is running.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02653: error while initializing data for the BI Instance {0}

Cause: The server for Fusion Middleware Control failed to correctly communicate with the server for the BI Instance.

Action: Ensure that the server for the BI Instance is running.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02658: The {1} operation can not be performed on the {0} component.

Cause: The specified Oracle Business Intelligence component failed to respond to the operation.

Action: See the log files for the Oracle Business Intelligence component to determine the cause of the error.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02668: The configuration for BI Instance can not be locked.

Cause: The BI Instance was already locked by another user.

Action: Determine which user has locked the BI Instance and request that it be released.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02669: The changes to the BI Instance can not be committed.

Cause: The BI Instance failed to commit all recent changes.

Action: See the log files for the BI Instance to determine the cause of the error.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02670: The changes to the BI Instance can not be reverted.

Cause: The BI Instance failed to revert all recent changes.

Action: See the log files for the BI Instance to determine the cause of the error.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02672: The BI Instance can not be started.

Cause: The BI Instance could not respond correctly to the start command.

Action: See the log files for the BI Instance to determine the cause of the error.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02673: The BI Instance can not be stopped.

Cause: The BI Instance could not respond correctly to the stop command.

Action: See the log files for the BI Instance to determine the cause of the error.

Level: 1

Type: ERROR

Impact: Enterprise Manager

EM-02674: The BI Instance can not be restarted.

Cause: The BI Instance could not respond correctly to the restart command.

Action: See the log files for the BI Instance to determine the cause of the error.

Level: 1

Type: ERROR

Impact: Enterprise Manager