CWWKR

CWWKR0001E: Configuration for appState feature is missing required attributes
CWWKR0002E: Application state file failed to be created at {0}
CWWKR0200E: The {0} server does not exist.
CWWKR0201E: The configuration for the {0} service does not exist.
CWWKR0202E: The {0} service is not bound to the {1} server.
CWWKR0203E: The {0} service does not exist.
CWWKR0204E: The {0} service configuration does not use the {1} variable.
CWWKR0205E: You are not logged in to IBM Bluemix. Use the "bluemixUtility login" command to log in to Bluemix.
CWWKR0206E: IBM Bluemix authentication failed. The provided credentials are incorrect.
CWWKR0207E: The {0} space does not exist in the {1} organization.
CWWKR0208E: The {0} organization does not exist.
CWWKR0209E: An unexpected error occurred when performing an IBM Bluemix operation. Error: {0}
CWWKR0210E: The {0} service plan does not exist.
CWWKR0211E: The {0} service offering does not exist.
CWWKR0212E: A space name is not set for your IBM Bluemix connection. Use the "bluemixUtility switch" command to set the space name.
CWWKR0213E: An organization name is not set for your IBM Bluemix connection. Use the "bluemixUtility switch" command to set the organization name.
CWWKR0214E: Unable to log in to IBM Bluemix. The authentication endpoint is missing.
CWWKR0215E: The {0} API endpoint is not a valid web address. Error: {1}.
CWWKR0216E: The {0} API endpoint must be an HTTPS or HTTP web address.
CWWKR0217E: An unexpected error occurred while communicating with the configuration service. Error: {0}
CWWKR0218E: The {0} service must have one or more service keys.
CWWKR0219E: The {0} service key does not exist.
CWWKR0220E: Unable to get variable information from {0} file. Error {1}.
CWWKR0221E: An unexpected error occurred while performing service registry operation. Error: {0}
CWWKR0222E: The {0} directory was not created.
CWWKR0223E: The {1} file cannot be created outside of the {0} directory.
CWWKR0224E: An unexpected error occurred while reading the configuration for the {0} service. Error: {1}.
CWWKR0225E: An unexpected error occurred while writing the configuration for the {0} service. Error: {1}.
CWWKR0226E: An error occurred while encoding password information for the {0} service. Error: {1}.
CWWKR0227E: Unable to resolve the host name of the configuration service. Error: {0}.
CWWKR0228E: Unable to establish a connection with the configuration service. Error: {0}.
CWWKR0229E: A timeout error occurred while communicating with the configuration service. Error: {0}.
CWWKR0230E: Unable to reach the configuration service. Error: {0}.
CWWKR0231E: Unable to download the {0} file because the host name was not resolved. Error: {1}.
CWWKR0232E: Unable to download the {0} file because the connection to the host was not established. Error: {1}.
CWWKR0233E: A timeout error occurred while downloading {0} file. Error: {1}.
CWWKR0234E: Unable to download the {0} file because the host was not reached. Error: {1}.
CWWKR0235E: An error occurred while downloading the {0} file. Error: {1}.
CWWKR0236E: Unable to resolve the host name of the IBM Bluemix API endpoint. Error: {0}.
CWWKR0237E: Unable to establish a connection with the IBM Bluemix API endpoint. Error: {0}.
CWWKR0238E: A timeout error occurred while communicating with IBM Bluemix. Error: {0}.
CWWKR0239E: Unable to reach the IBM Bluemix API endpoint. Error: {0}.
CWWKR0240E: The service configuration was not generated. Verify that the specified parameters are valid. Error: {0}
CWWKR0241E: Supported services cannot be listed because of the following error: {0}
CWWKR0242E: Service with name {0} already exists. Delete the existing service or choose another service name.
CWWKR0243E: The {0} service is a built-in service and additional instances cannot be created.
CWWKR0244E: The {0} service is a built-in service and cannot be deleted.
CWWKR0400I: The server was registered with the {0} service on the specified URL {1}.
CWWKR0401W: The server cannot be registered. Server registration with the {0} service will be attempted again within {1} minutes. The following exception occurred: {2}
CWWKR0402W: The server cannot be registered. Server registration with the {0} service will be attempted again within {1} minutes. The following response was received from the {0} service: {2}
CWWKR0403E: The server cannot be registered with the {0} service. Registration cannot complete until the problem is corrected. The following error occurred: {1}
CWWKR0404E: The server cannot be registered with the {0} service. The following internal error prevented the server from registering: {1}
CWWKR0405E: The <usageMetering> element is missing the {0} required attribute.
CWWKR0406E: The product version files are missing or corrupted. The usageMetering feature did not start. The following exception occurred: {0}
CWWKR0407E: The usageMetering feature was unable to start because of missing product information. The server does not have an international program license agreement (IPLA) and cannot be registered with the {0} service.
CWWKR0408W: The server was unable to process the {0} product information file. The following exception occurred: {1}
CWWKR0409W: The usageMetering feature encountered an exception when collecting product usage. The following exception occurred: {0}
CWWKR0410I: The usageMetering feature does not support the {0} metric for the {1} OS on the {2} software developers kit.
CWWKR0411W: The {0} program cannot run on the {1} operating system. The following exception occurred: {2}
CWWKR0412E: The server cannot be registered with the {0} service. Ensure the configuration contains a valid API key and URL.
CWWKR0413E: The server cannot be registered with the {0} service. The server was unable to communicate with the service due to incorrect SSL configuration.
CWWKR0414E: The <usageMetering> element {0} is malformed.
CWWKR0415E: The <usageMetering> element url is incorrect. The protocol must be https.
CWWKR0416W: The {0} group name contains one or more invalid characters, so this server will be registered without any group membership. To add the server to a group, ensure that the group name contains only valid characters, which include letters, numbers, hyphens, periods, colons, and underscores.
CWWKR0417W: The {0} group name is not valid because it begins with WAS_, which is a reserved term. This server will be registered without any group membership. To add the server to a group, specify a valid group name.
CWWKR0418E: The usageMetering feature encountered an exception when retrieving an access token from the {0} service. The following exception occurred: {1}
CWWKR0419W: The {0} group name is not unique, so this server will be registered without any group membership. To add the server to a group, ensure that each group name is unique.
CWWKR0420E: The server cannot be registered with the {0} service. The SSL configuration is missing.
CWWKR0421I: Neither the usageMetering sslRef property nor a trustStore property were defined in the server configuration, so the following keystore was used: {0}.
CWWKR0422E: Both a sslRef and a trustStore property were defined in the usageMetering configuration.
CWWKR0423E: The keystore file at {0} could not be found.
CWWKR0424E: The application server process has insufficient privileges to read the keystore file at {0}.
CWWKR0425E: The value of the httpsProtocol property is not valid: {0} Valid protocols include: {1}
CWWKR0426W: The {0} value of the {1} property is not valid. The value must be a number.
CWWKR0427I: The number of processor cores reported to the usage metering service is overridden and is now {0}.
CWWKR0428W: The usageMetering feature has ignored the ''{0}'' value for the ''{1}'' metric type reported by the {2} product. The metric type or a definition of the metric type was not provided during product registration.
CWWKR0429W: The usageMetering feature has ignored the ''{0}'' value for the ''{1}'' metric type reported by the {2} product. The metric value is not valid.
CWWKR0430W: The usageMetering feature encountered an exception when sending product usage. The following exception occurred: {0}
CWWKR0431W: The usageMetering feature encountered an exception when collecting product usage for the {0} product. The following exception occurred: {1}
CWWKR0432W: The usageMetering feature encountered an exception when resetting usage data collection for the {0} product. The following exception occurred: {1}
CWWKR0433W: The usageMetering feature encountered an exception when enabling usage data collection for the {0} product. The following exception occurred: {1}
CWWKR0434W: The usageMetering feature could not set a registration listener for the {0} product.
CWWKR0435W: The usageMetering feature could not obtain registration information for the {0} product.
CWWKR0436W: The usageMetering feature was unable to send metrics for the last {0} collection intervals. Metrics for each {1} minute collection interval are aggregated until the {2} service can be reached.
CWWKR0437W: During the deactivation of the usageMetering feature, task {0} was not properly stopped or canceled. If the server is not already stopping, it is recommended to restart the server.
CWWKR0438W: Collection of usage metrics for the usageMetering feature did not occur at the scheduled time, {0} minutes ago. To avoid inaccurate metric data, the usage data for the missed collection interval is discarded and the future usage metric collection is rescheduled.
CWWKR0439W: The {0} product has an unsupported metric cap group identifier of {1}. The metric cap group configuration is ignored. Supported types are {2}.
CWWKR0440E: Usage metering failed to determine a unique server identity. If multiple server instances report the same identity, they display as one server on the dashboard.
CWWKR0441W: The usageMetering feature encountered an exception when retrieving an access token from the {0} service. This exception might be resolved when the usageMetering feature attempts to retrieve the access token at a later time. The following exception occurred: {1}
CWWKR0443W: The {0} product has an unsupported cap metric type value of {1}. The cap metric configuration is ignored. Supported types are {2}.
CWWKR0444W: The usage metering feature encountered an exception when logging metering data. The following exception occurred: {0}
CWWKR0445W: The usage metering <optionalMetrics> configuration element value contains the following unsupported metric identifiers: {0}. The unsupported identifiers are ignored. Supported metric identifiers are {1}.
CWWKR0446W: The usage metering <optionalMetrics> configuration contains the {0} special values in combination with other metric identifiers. These special values are ignored.
CWWKR0447W: The usage metering feature is stabilized and is scheduled to be discontinued in the {0} fix pack.
CWWKR0448W: The usage metering feature is deprecated and is scheduled to be discontinued in the {0} fix pack.