- CWRCV0001I: A message was received from the exception queue "{0}".
- Explanation: This is an informational message. A message was received from the exception queue by the recovery message driven bean.
- User Action: No further user action is required.
- CWRCV0002I: A failed event with the message ID "{0}" was saved successfully.
- Explanation: This is an informational message. A message with the specified ID was captured by the recovery message driven bean and was saved as a failed event.
- User Action: Use the failed event manager to view and manage the failed event.
- CWRCV0003I: The total failed events count is "{0}".
- Explanation: This is an informational message. A total number of failed events is obtained.
- User Action: Use the failed event manager to list the failed events and manage them.
- CWRCV0004E: The count of failed events cannot be retrieved.
- Explanation: The problem might be that the database is not available or that the recovery application is stopped.
- User Action: In the administrative console, locate the data source with the Java Naming and Directory Interface (JNDI) name jdbc/WPSDB, and make sure that the test connection is successful. If it is not successful, check that the data source properties indicate the correct database information, and also check that the database server is running. If it is successful, in Enterprise Applications, find the recovery application name that starts with wpsFEMgr, and make sure the application is installed and deployed to this server or cluster, and is started. If the application is not installed or deployed to this server or cluster, the recovery is not configured correctly. Check the log and trace information when the profile is created for standalone profiles, or when the server or cluster is configured to run Service Component Architecture applications for Network Deployment environment. If the application is not started, start it in Enterprise Applications. Change the log detail level to "Recovery=all" and try again to obtain more detailed tracing information. If the problem persists, see the problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
- CWRCV0005I: All failed events were returned.
- Explanation: This is an informational message. All of the failed events were retrieved and returned successfully.
- User Action: No further user action is required.
- CWRCV0006W: No failed events were returned. The page size parameter "{0}" is less than zero.
- Explanation: The page size parameter sets the maximum number of rows returned. If the page size is zero, all of the rows matching the search criteria are returned. The page size parameter must be zero or greater; if the parameter is less than zero, no records are returned.
- User Action: Change the page size parameter to a number that is zero or greater and try searching the failed events again.
- CWRCV0007E: The failed events cannot be retrieved.
- Explanation: The problem might be that the database is not available or that the recovery application is stopped.
- User Action: In the administrative console, locate the data source with the Java Naming and Directory Interface (JNDI) name jdbc/WPSDB, and make sure that the test connection is successful. If it is not successful, check that the data source properties indicate the correct database information, and also check that the database server is running. If it is successful, in Enterprise Applications, find the recovery application name that starts with wpsFEMgr, and make sure the application is installed and deployed to this server or cluster, and is started. If the application is not installed or deployed to this server or cluster, the recovery is not configured correctly. Check the log and trace information when the profile is created for standalone profiles, or when the server or cluster is configured to run Service Component Architecture applications for Network Deployment environment. If the application is not started, start it in Enterprise Applications. Change the log detail level to "Recovery=all" and try again to obtain more detailed tracing information. If the problem persists, see the problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
- CWRCV0008I: The failed events for the destination with the following conditions have been retrieved: destination module: "{0}", destination component: "{1}", destination method: "{2}".
- Explanation: This is an informational message. The failed events search was successful.
- User Action: No further user action is required.
- CWRCV0010E: The failed events for the destination with the following conditions cannot be retrieved: destination module: "{0}", destination component: "{1}", destination method: "{2}".
- Explanation: The problem might be that the database is not available or that the recovery application is stopped.
- User Action: In the administrative console, locate the data source with the Java Naming and Directory Interface (JNDI) name jdbc/WPSDB, and make sure that the test connection is successful. If it is not successful, check that the data source properties indicate the correct database information, and also check that the database server is running. If it is successful, in Enterprise Applications, find the recovery application name that starts with wpsFEMgr, and make sure the application is installed and deployed to this server or cluster, and is started. If the application is not installed or deployed to this server or cluster, the recovery is not configured correctly. Check the log and trace information when the profile is created for standalone profiles, or when the server or cluster is configured to run Service Component Architecture applications for Network Deployment environment. If the application is not started, start it in Enterprise Applications. Change the log detail level to "Recovery=all" and try again to obtain more detailed tracing information. If the problem persists, see the problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
- CWRCV0011I: The failed events for the source with the following conditions have been retrieved: source module: "{0}", source component: "{1}".
- Explanation: This is an informational message. The failed events search was successful.
- User Action: No further user action is required.
- CWRCV0013E: The failed events for the source with the following conditions cannot be retrieved: source module: "{0}", source component: "{1}".
- Explanation: The problem might be that the database is not available or that the recovery application is stopped.
- User Action: In the administrative console, locate the data source with the Java Naming and Directory Interface (JNDI) name jdbc/WPSDB, and make sure that the test connection is successful. If it is not successful, check that the data source properties indicate the correct database information, and also check that the database server is running. If it is successful, in Enterprise Applications, find the recovery application name that starts with wpsFEMgr, and make sure the application is installed and deployed to this server or cluster, and is started. If the application is not installed or deployed to this server or cluster, the recovery is not configured correctly. Check the log and trace information when the profile is created for standalone profiles, or when the server or cluster is configured to run Service Component Architecture applications for Network Deployment environment. If the application is not started, start it in Enterprise Applications. Change the log detail level to "Recovery=all" and try again to obtain more detailed tracing information. If the problem persists, see the problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
- CWRCV0014I: The failed events for the source with the following dates have been retrieved: from the date "{0}" to the date "{1}".
- Explanation: This is an informational message. The failed events search was successful.
- User Action: No further user action is required.
- CWRCV0016E: The failed events for the following time period cannot be retrieved: from the date "{0}" to the date "{1}".
- Explanation: The problem might be that the database is not available or that the recovery application is stopped.
- User Action: In the administrative console, locate the data source with the Java Naming and Directory Interface (JNDI) name jdbc/WPSDB, and make sure that the test connection is successful. If it is not successful, check that the data source properties indicate the correct database information, and also check that the database server is running. If it is successful, in Enterprise Applications, find the recovery application name that starts with wpsFEMgr, and make sure the application is installed and deployed to this server or cluster, and is started. If the application is not installed or deployed to this server or cluster, the recovery is not configured correctly. Check the log and trace information when the profile is created for standalone profiles, or when the server or cluster is configured to run Service Component Architecture applications for Network Deployment environment. If the application is not started, start it in Enterprise Applications. Change the log detail level to "Recovery=all" and try again to obtain more detailed tracing information. If the problem persists, see the problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
- CWRCV0017I: The business object type names for all failed events were returned.
- Explanation: This is an informational message. The failed events search was successful.
- User Action: No further user action is required.
- CWRCV0018W: No business object type names were returned. The page size parameter "{0}" is less than zero.
- Explanation: The page size parameter must be zero or greater; if the parameter is less than zero, no records are returned.
- User Action: Change the page size parameter to a number that is zero or greater and try searching the business object type names again.
- CWRCV0019E: The business object type names of all failed events cannot be retrieved.
- Explanation: The problem might be that the database is not available or that the recovery application is stopped.
- User Action: In the administrative console, locate the data source with the Java Naming and Directory Interface (JNDI) name jdbc/WPSDB, and make sure that the test connection is successful. If it is not successful, check that the data source properties indicate the correct database information, and also check that the database server is running. If it is successful, in Enterprise Applications, find the recovery application name that starts with wpsFEMgr, and make sure the application is installed and deployed to this server or cluster, and is started. If the application is not installed or deployed to this server or cluster, the recovery is not configured correctly. Check the log and trace information when the profile is created for standalone profiles, or when the server or cluster is configured to run Service Component Architecture applications for Network Deployment environment. If the application is not started, start it in Enterprise Applications. Change the log detail level to "Recovery=all" and try again to obtain more detailed tracing information. If the problem persists, see the problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
- CWRCV0020I: The failed events with the business object type "{0}" were retrieved.
- Explanation: This is an informational message. The failed events search was successful.
- User Action: No further user action is required.
- CWRCV0022E: The failed events with the business object type "{0}" cannot be retrieved.
- Explanation: The problem might be that the database is not available or that the recovery application is stopped.
- User Action: In the administrative console, locate the data source with the Java Naming and Directory Interface (JNDI) name jdbc/WPSDB, and make sure that the test connection is successful. If it is not successful, check that the data source properties indicate the correct database information, and also check that the database server is running. If it is successful, in Enterprise Applications, find the recovery application name that starts with wpsFEMgr, and make sure the application is installed and deployed to this server or cluster, and is started. If the application is not installed or deployed to this server or cluster, the recovery is not configured correctly. Check the log and trace information when the profile is created for standalone profiles, or when the server or cluster is configured to run Service Component Architecture applications for Network Deployment environment. If the application is not started, start it in Enterprise Applications. Change the log detail level to "Recovery=all" and try again to obtain more detailed tracing information. If the problem persists, see the problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
- CWRCV0023I: Events that failed with the following exception were retrieved: "{0}".
- Explanation: This is an informational message. The failed events search was successful.
- User Action: No further user action is required.
- CWRCV0025E: The events that failed with the following exception cannot be retrieved: "{0}".
- Explanation: The problem might be that the database is not available or that the recovery application is stopped.
- User Action: In the administrative console, locate the data source with the Java Naming and Directory Interface (JNDI) name jdbc/WPSDB, and make sure that the test connection is successful. If it is not successful, check that the data source properties indicate the correct database information, and also check that the database server is running. If it is successful, in Enterprise Applications, find the recovery application name that starts with wpsFEMgr, and make sure the application is installed and deployed to this server or cluster, and is started. If the application is not installed or deployed to this server or cluster, the recovery is not configured correctly. Check the log and trace information when the profile is created for standalone profiles, or when the server or cluster is configured to run Service Component Architecture applications for Network Deployment environment. If the application is not started, start it in Enterprise Applications. Change the log detail level to "Recovery=all" and try again to obtain more detailed tracing information. If the problem persists, see the problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
- CWRCV0026I: The message information was returned for failed events with the message ID "{0}".
- Explanation: This is an informational message. The failed events search was successful.
- User Action: No further user action is required.
- CWRCV0027E: Message information for the failed event with the message ID "{0}" cannot be retrieved.
- Explanation: The problem might be that the database is not available or that the recovery application is stopped.
- User Action: In the administrative console, locate the data source with the Java Naming and Directory Interface (JNDI) name jdbc/WPSDB, and make sure that the test connection is successful. If it is not successful, check that the data source properties indicate the correct database information, and also check that the database server is running. If it is successful, in Enterprise Applications, find the recovery application name that starts with wpsFEMgr, and make sure the application is installed and deployed to this server or cluster, and is started. If the application is not installed or deployed to this server or cluster, the recovery is not configured correctly. Check the log and trace information when the profile is created for standalone profiles, or when the server or cluster is configured to run Service Component Architecture applications for Network Deployment environment. If the application is not started, start it in Enterprise Applications. Change the log detail level to "Recovery=all" and try again to obtain more detailed tracing information. If the problem persists, see the problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
- CWRCV0028I: All failed events were deleted successfully.
- Explanation: This is an informational message. The failed events deletion was successful.
- User Action: No further user action is required.
- CWRCV0029E: The process for deleting all failed events stopped.
- Explanation: The problem might be that the database is not available or that the recovery application is stopped.
- User Action: In the administrative console, locate the data source with the Java Naming and Directory Interface (JNDI) name jdbc/WPSDB, and make sure that the test connection is successful. If it is not successful, check that the data source properties indicate the correct database information, and also check that the database server is running. If it is successful, in Enterprise Applications, find the recovery application name that starts with wpsFEMgr, and make sure the application is installed and deployed to this server or cluster, and is started. If the application is not installed or deployed to this server or cluster, the recovery is not configured correctly. Check the log and trace information when the profile is created for standalone profiles, or when the server or cluster is configured to run Service Component Architecture applications for Network Deployment environment. If the application is not started, start it in Enterprise Applications. Change the log detail level to "Recovery=all" and try again to obtain more detailed tracing information. If the problem persists, see the problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
- CWRCV0030I: The following number of failed events was deleted successfully: "{0}".
- Explanation: This is an informational message. The failed events deletion was successful.
- User Action: No further user action is required.
- CWRCV0031E: The failed event was not deleted because it does not have a valid message ID.
- Explanation: To delete a failed event, the event message ID cannot be null.
- User Action: Change the message ID to a valid value and try deleting the failed event again.
- CWRCV0032W: The following number of failed events had errors during deletion: "{0}".
- Explanation: If the failed event manager indicates that the failed event has been deleted, no user action is required. If the failed event cannot be deleted, the problem might be that the database is not available or that the recovery application is stopped.
- User Action: In the administrative console, locate the data source with the Java Naming and Directory Interface (JNDI) name jdbc/WPSDB, and make sure that the test connection is successful. If it is not successful, check that the data source properties indicate the correct database information, and also check that the database server is running. If it is successful, in Enterprise Applications, find the recovery application name that starts with wpsFEMgr, and make sure the application is installed and deployed to this server or cluster, and is started. If the application is not installed or deployed to this server or cluster, the recovery is not configured correctly. Check the log and trace information when the profile is created for standalone profiles, or when the server or cluster is configured to run Service Component Architecture applications for Network Deployment environment. If the application is not started, start it in Enterprise Applications. Change the log detail level to "Recovery=all" and try again to obtain more detailed tracing information. If the problem persists, see the problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
- CWRCV0033I: The following number of failed events was resubmitted successfully: "{0}".
- Explanation: This is an informational message. The failed events resubmission was successful.
- User Action: No further user action is required.
- CWRCV0034E: The resubmitted failed event "{0}" is not valid.
- Explanation: The resubmitted failed event list parameter is null, or the failed event parameter in the list is of incorrect type. Correct failed event types for resubmission are FailedEvent, FailedEventWithParameters or message ID as String.
- User Action: Correct the failed event list parameter try resubmitting them again.
- CWRCV0035W: The following number of failed events encountered errors during resubmission: "{0}".
- Explanation: If the failed event manager indicates that the failed event has been resubmitted, no user action is required. If the failed event cannot be resubmitted, the problem might be that the database is not available or that the recovery application is stopped.
- User Action: In the administrative console, locate the data source with the Java Naming and Directory Interface (JNDI) name jdbc/WPSDB, and make sure that the test connection is successful. If it is not successful, check that the data source properties indicate the correct database information, and also check that the database server is running. If it is successful, in Enterprise Applications, find the recovery application name that starts with wpsFEMgr, and make sure the application is installed and deployed to this server or cluster, and is started. If the application is not installed or deployed to this server or cluster, the recovery is not configured correctly. Check the log and trace information when the profile is created for standalone profiles, or when the server or cluster is configured to run Service Component Architecture applications for Network Deployment environment. If the application is not started, start it in Enterprise Applications. Change the log detail level to "Recovery=all" and try again to obtain more detailed tracing information. If the problem persists, see the problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
- CWRCV0036I: The activation specification "{0}" was created successfully.
- Explanation: This is an informational message. An activation specification must be created when you are configuring recovery for a server or cluster in WebSphere Application Server Network Deployment.
- User Action: No further user action is required.
- CWRCV0037I: The activation specification "{0}" already exists.
- Explanation: This is an informational message. The activation specification might have been created by an earlier configuration action or administrative task. The activation specification will be reused.
- User Action: No further user action is required.
- CWRCV0038E: The activation specification "{0}" was not created.
- Explanation: The problem might be that the resource adapter does not exist or is not in the correct scope.
- User Action: In the administrative console, in the panel Resource adapters, check that Platform Messaging Component SPI Resource Adapter exists in the server or cluster scope. If it is not listed, check that the server or cluster is configured for Service Component Architecture. If it is listed, change the log detail level to "Recovery=all", and execute the configRecoveryForServer or configRecoveryForCluster admin task in the WebSphere Application Server Network Deployment environment. If the problem persists, see the problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
- CWRCV0039I: The Recovery MBean was activated successfully.
- Explanation: This is an informational message. The Recovery MBean must be configured when you are configuring recovery for a server or cluster in WebSphere Application Server Network Deployment.
- User Action: No further user action is required.
- CWRCV0040E: The Recovery MBean was not activated.
- Explanation: The Recovery MBean must be activated on the server or cluster member that the recovery application is deployed. The problem might be that recovery application checking on the server or cluster member encounters errors.
- User Action: In the administrative console, find the recovery application name that starts with wpsFEMgr, and check whether the recovery application is deployed to the server or cluster. If the application is not deployed, the recovery is not configured correctly. Check the log and trace information when the profile is created for standalone profiles, or when the server or cluster is configured to run Service Component Architecture applications for Network Deployment environment. Change log detail levels to "Recovery=all" and try starting the server or cluster again to see more detailed tracing information. If the problem persists, see the problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
- CWRCV0041I: The recovery application was installed successfully.
- Explanation: This is an informational message. The recovery application must be installed when you are configuring recovery for a server or cluster in WebSphere Application Server Network Deployment.
- User Action: No further user action is required.
- CWRCV0042E: The recovery application was not installed.
- Explanation: The problem might be that the installable Enterprise Archive (EAR) file wpsFEMgr.ear was not found.
- User Action: Make sure that the installable EAR file wpsFEMgr.ear exists in the installableApps folder of the WebSphere Process Server installation directory. Change the log detail level to "Recovery=all", and execute the configRecoveryForServer or configRecoveryForCluster admin task in the WebSphere Application Server Network Deployment environment. If the problem persists, see the problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
- CWRCV0043I: The failed event destination "{0}" was created successfully.
- Explanation: This is an informational message. The failed event destination must be created when you are configuring recovery for a server or cluster in WebSphere Application Server Network Deployment.
- User Action: No further user action is required.
- CWRCV0044E: The failed event destination "{0}" was not created.
- Explanation: The problem might be that the Service Component Architecture (SCA) system bus is missing or the messaging engine is not configured. The failed event destination must be created after the server or cluster is added as a SCA system bus member.
- User Action: In the administrative console, check that the SCA system bus is created and that the messaging engine is configured. If the SCA system bus is not created or the messaging engine is configured, configure Service Component Architecture for the server or cluster first. Change the log detail level to "Recovery=all", and execute the configRecoveryForServer or configRecoveryForCluster admin task in the WebSphere Application Server Network Deployment environment. If the problem persists, see the problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
- CWRCV0045I: The recovery deployment task for "{0}" is in progress.
- Explanation: This is an informational message. The recovery process performs configuration tasks when deploying a Service Component Architecture (SCA) module.
- User Action: No further user action is required.
- CWRCV0046I: The recovery deployment task for "{0}" completed successfully.
- Explanation: This is an informational message. The recovery process completed the configuration tasks required when deploying a Service Component Architecture (SCA) module.
- User Action: No further user action is required.
- CWRCV0047E: The recovery deployment task for "{0}" failed.
- Explanation: The problem might be that the exception destination property of the Service Component Architecture (SCA) module destinations was not modified successfully.
- User Action: Change the log detail level to "Recovery=all", and try deploying the Service Component Architecture module again. If the problem persists, see the problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
- CWRCV0048I: The number of failed events with session ID "{0}" is "{1}".
- Explanation: This is an informational message. The failed events search was successful.
- User Action: No further user action is required.
- CWRCV0049E: The count of failed events with the session ID "{0}" cannot be retrieved.
- Explanation: The problem might be that the database is not available or that the recovery application is stopped.
- User Action: In the administrative console, locate the data source with the Java Naming and Directory Interface (JNDI) name jdbc/WPSDB, and make sure that the test connection is successful. If it is not successful, check that the data source properties indicate the correct database information, and also check that the database server is running. If it is successful, in Enterprise Applications, find the recovery application name that starts with wpsFEMgr, and make sure the application is installed and deployed to this server or cluster, and is started. If the application is not installed or deployed to this server or cluster, the recovery is not configured correctly. Check the log and trace information when the profile is created for standalone profiles, or when the server or cluster is configured to run Service Component Architecture applications for Network Deployment environment. If the application is not started, start it in Enterprise Applications. Change the log detail level to "Recovery=all" and try again to obtain more detailed tracing information. If the problem persists, see the problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
- CWRCV0050I: The failed events with the session ID "{0}" were retrieved.
- Explanation: This is an informational message. The failed events search was successful.
- User Action: No further user action is required.
- CWRCV0052E: The failed events with the session ID "{0}" cannot be retrieved.
- Explanation: The problem might be that the database is not available or that the recovery application is stopped.
- User Action: In the administrative console, locate the data source with the Java Naming and Directory Interface (JNDI) name jdbc/WPSDB, and make sure that the test connection is successful. If it is not successful, check that the data source properties indicate the correct database information, and also check that the database server is running. If it is successful, in Enterprise Applications, find the recovery application name that starts with wpsFEMgr, and make sure the application is installed and deployed to this server or cluster, and is started. If the application is not installed or deployed to this server or cluster, the recovery is not configured correctly. Check the log and trace information when the profile is created for standalone profiles, or when the server or cluster is configured to run Service Component Architecture applications for Network Deployment environment. If the application is not started, start it in Enterprise Applications. Change the log detail level to "Recovery=all" and try again to obtain more detailed tracing information. If the problem persists, see the problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
- CWRCV0053E: The business data cannot be displayed correctly for failed events with the message ID "{0}".
- Explanation: The original artifacts are required to restore the XML format data to the business object. The problem might be that the Service Component Architecture (SCA) module is not installed or cannot be accessed outside the WebSphere Application Server cell.
- User Action: In the administrative console, check that the SCA module is deployed. If it is not deployed, install the SCA module. If you obtain the business data outside of the WebSphere Application Server cell, check the Java system properties or the input parameter that required information (connection type, host name and port, etc) is included to connect to the WebSphere Application Server cell. Change the log detail level to "Recovery=all" and try again to obtain more detailed tracing information. If the problem persists, see the problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
- CWRCV0054E: The connection type "{0}" that is specified in the administrative client properties is not supported.
- Explanation: Supported connection types are "SOAP" and "RMI".
- User Action: In the the input parameter, specify the correct connection type and try obtaining the failed event parameters again.
- CWRCV0055E: The connector host name is not specified in the administrative client properties.
- Explanation: The connector host name must be specified for the administrative client properties.
- User Action: Add the connector host name property in the administrative client properties and try obtaining the failed event parameters again.
- CWRCV0056E: The connector port number is not specified in the administrative client properties.
- Explanation: The connector port number must be specified for the administrative client properties.
- User Action: Add the connector port number property in the administrative client properties and try obtaining the failed event parameters again.
- CWRCV0057I: The failed events count is "{0}".
- Explanation: This is an informational message. the number of queried failed events is obtained.
- User Action: Use the failed event manager to list the failed events and manage them.
- CWRCV0058E: The count of failed events cannot be retrieved with the following conditions: Module: "{0}", Component: "{1}", Operation: "{2}", Event type: "{3}", Event status: "{4}", Begin time: "{5}", End time: "{6}", Deployment target: "{7}".
- Explanation: The problem might be that the database is not available or that the recovery application is stopped.
- User Action: In the administrative console, locate the data source with the Java Naming and Directory Interface (JNDI) name jdbc/WPSDB, and make sure that the test connection is successful. If it is not successful, check that the data source properties indicate the correct database information, and also check that the database server is running. If it is successful, in Enterprise Applications, find the recovery application name that starts with wpsFEMgr, and make sure the application is installed and deployed to this server or cluster, and is started. If the application is not installed or deployed to this server or cluster, the recovery is not configured correctly. Check the log and trace information when the profile is created for standalone profiles, or when the server or cluster is configured to run Service Component Architecture applications for Network Deployment environment. If the application is not started, start it in Enterprise Applications. Change the log detail level to "Recovery=all" and try again to obtain more detailed tracing information. If the problem persists, see the problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
- CWRCV0059I: The failed events were retrieved with the conditions: Module: "{0}", Component: "{1}", Operation: "{2}", Event type: "{3}", Event status: "{4}, Begin time: "{5}", End time: "{6}", Deployment target: "{7}".
- Explanation: This is an informational message. The failed events search was successful.
- User Action: No further user action is required.
- CWRCV0060E: The failed events with the following conditions cannot be retrieved: Module: "{0}", Component: "{1}", Operation: "{2}", Event type: "{3}", Event status: "{4}", Begin time: "{5}", End time: "{6}", Deployment target: "{7}".
- Explanation: The problem might be that the database is not available or that the recovery application is stopped.
- User Action: In the administrative console, locate the data source with the Java Naming and Directory Interface (JNDI) name jdbc/WPSDB, and make sure that the test connection is successful. If it is not successful, check that the data source properties indicate the correct database information, and also check that the database server is running. If it is successful, in Enterprise Applications, find the recovery application name that starts with wpsFEMgr, and make sure the application is installed and deployed to this server or cluster, and is started. If the application is not installed or deployed to this server or cluster, the recovery is not configured correctly. Check the log and trace information when the profile is created for standalone profiles, or when the server or cluster is configured to run Service Component Architecture applications for Network Deployment environment. If the application is not started, start it in Enterprise Applications. Change the log detail level to "Recovery=all" and try again to obtain more detailed tracing information. If the problem persists, see the problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
- CWRCV0061E: The filter name "{0}" set for query filters is invalid.
- Explanation: The filter name set for query filters is invalid. Valid names of single filter include MODULE_NAME, COMPONENT_NAME, OPERATION_NAME, BEGIN_TIME, END_TIME and DEPLOYMENT_TARGET. Valid names of filter array include EVENT_STATUS and EVENT_TYPE.
- User Action: Correct filter name and try again.
- CWRCV0062E: The filter value "{0}" set for query filter "{1}" is invalid.
- Explanation: The filter value for query filters is invalid. Valid type for BEGIN_TIME and END_TIME is java.util.Date; java.lang.Integer for EVENT_STATUS; java.lang.String for MODULE_NAME, COMPONENT_NAME, OPERATION_NAME and DEPLOYMENT_TARGET. The format of DEPLOYMENT_TARGET filter value is "node=nodeName,server=serverName" or "cluster=clusterName".
- User Action: Correct filter value and try again.
- CWRCV0063I: The message information was returned for failed events with the message ID "{0}".
- Explanation: This is an informational message. The failed events search was successful.
- User Action: No further user action is required.
- CWRCV0064E: Message information for the failed event with the message ID "{0}" cannot be retrieved.
- Explanation: The problem might be that the database is not available or that the recovery application is stopped.
- User Action: In the administrative console, locate the data source with the Java Naming and Directory Interface (JNDI) name jdbc/WPSDB, and make sure that the test connection is successful. If it is not successful, check that the data source properties indicate the correct database information, and also check that the database server is running. If it is successful, in Enterprise Applications, find the recovery application name that starts with wpsFEMgr, and make sure the application is installed and deployed to this server or cluster, and is started. If the application is not installed or deployed to this server or cluster, the recovery is not configured correctly. Check the log and trace information when the profile is created for standalone profiles, or when the server or cluster is configured to run Service Component Architecture applications for Network Deployment environment. If the application is not started, start it in Enterprise Applications. Change the log detail level to "Recovery=all" and try again to obtain more detailed tracing information. If the problem persists, see the problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
- CWRCV0065E: Message information for the BPC failed event with the message ID "{0}" cannot be retrieved.
- Explanation: The problem might be that the BPC not configured successfully or that the recovery application is stopped.
- User Action: In the administrative console, please check the BPC configuration, and make sure that BPC can work well. If it is successful, in Enterprise Applications, find the recovery application name that starts with wpsFEMgr, and make sure the application is installed and deployed to this server or cluster, and is started. If the application is not installed or deployed to this server or cluster, the recovery is not configured correctly. Check the log and trace information when the profile is created for standalone profiles, or when the server or cluster is configured to run Service Component Architecture applications for Network Deployment environment. If the application is not started, start it in Enterprise Applications. Change the log detail level to "Recovery=all" and try again to obtain more detailed tracing information. If the problem persists, see the problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
- CWRCV0066E: Message information for the BFM Hold failed event with the message ID "{0}" cannot be retrieved.
- Explanation: The problem might be that the BPC not configured successfully or that the recovery application is stopped.
- User Action: In the administrative console, please check the BPC configuration, and make sure that BPC can work well. If it is successful, in Enterprise Applications, find the recovery application name that starts with wpsFEMgr, and make sure the application is installed and deployed to this server or cluster, and is started. If the application is not installed or deployed to this server or cluster, the recovery is not configured correctly. Check the log and trace information when the profile is created for standalone profiles, or when the server or cluster is configured to run Service Component Architecture applications for Network Deployment environment. If the application is not started, start it in Enterprise Applications. Change the log detail level to "Recovery=all" and try again to obtain more detailed tracing information. If the problem persists, see the problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.