CWWMH

CWWMH0100E: The format of "{0}" is not a valid ID.
CWWMH0101E: An internal error occurred. Error data: {0}
CWWMH0102E: Could not read configuration data for {0}.
CWWMH0104E: Asset "{0}" already exists.
CWWMH0106E: Composition unit "{0}", specified in an asset dependency relationship declaration, already exists.
CWWMH0107E: Composition unit "{0}" does not exist.
CWWMH0108E: The specified target "{0}" does not conform to the required syntax.
CWWMH0109E: Class "{0}", specified through the content-depl-providers Eclipse extension point, is not a supported content handler class.
CWWMH0110E: Class "{0}", specified through the content-depl-providers Eclipse extension point, could not be instantiated. Error data: {1}
CWWMH0111E: Class "{0}, specified through the operation-depl-providers Eclipse extension point, is not a supported operation handler class.
CWWMH0112E: Class "{0}", specified through the operation-depl-providers Eclipse extension point, could not be instantiated. Error data: {1}
CWWMH0113E: Unable to get Eclipse extension point using the extension point identifier "{0}".
CWWMH0114E: Unable to get Eclipse extension registry.
CWWMH0115E: The value of the "save options" parameter passed to a DeployableObjectWriter is not valid.
CWWMH0116E: The value of the "destination" parameter passed to a DeployableObjectWriter is not valid.
CWWMH0118E: Unable to obtain ConfigRepositoryClient reference.
CWWMH0119E: Unable to obtain document from the configuration repository.
CWWMH0121E: Could not read configuration data for composition unit "{0}". Error data: {1}
CWWMH0122E: Could not save configuration data for composition unit "{0}". Your workspace may be in an inconsistent state. Discard your workspace. Error data: {1}
CWWMH0123E: Could not read configuration data for asset ID "{0}". Error data: {1}
CWWMH0124E: Could not save configuration data for asset "{0}". Your workspace may be in an inconsistent state. Discard your workspace. Error data: {1}
CWWMH0125E: The specified "type aspect" value "{0}" is not valid. Type aspects have a format of: WebSphere:spec=<name>[,version=<version>]. The spec property is required and the version property is optional.
CWWMH0126E: The specified asset ID "{0}" does not conform to the required syntax.
CWWMH0127E: The specified composition unit ID "{0}" does not conform to the required syntax.
CWWMH0128E: The specified business-level application ID "{0}" does not conform to the required syntax.
CWWMH0129E: Ambiguous asset ID "{0}" specified as the composition unit source. Specify a single asset version by using a fully-qualified asset ID, for example, WebSphere:assetname=myAsset.jar,assetversion=1.0.
CWWMH0130E: Ambiguous business-level application ID "{0}" specified as the composition unit source. Specify a single business-level application edition by using a fully-qualified business-level application ID, for example, WebSphere:blaname=myBLA,blaedition=1.0.
CWWMH0131E: Ambiguous ID "{0}" specified as the composition unit source. The source matches both an asset name and a business-level application name. Use a more specific ID format, such as assetname=myApp or blaname=myApp.
CWWMH0132E: No file exists at the path specified by the "source.loose.config" property value "{0}" within the "ADTCommandProps" parameter value.
CWWMH0133E: No file exists at the path specified by the "source" parameter value "{0}".
CWWMH0134E: The specified "storageType" parameter value "{0}" is not valid. Specify "FULL", "METADATA", or "NONE".
CWWMH0135E: No "filename" parameter value was specified.
CWWMH0136E: The value for the "cuSourceID" parameter cannot be empty or null.
CWWMH0137E: No asset or business-level application matches the ID "{0}" specified as the "cuSourceID" parameter value.
CWWMH0138E: No asset matches the ID "{0}" specified as the "assetID" parameter value.
CWWMH0139E: Ambiguous asset ID "{0}" specified as the "assetID" parameter value. Specify a single asset version by using a fully-qualified asset ID, for example, WebSphere:assetname=myAsset.jar,assetversion=1.0.
CWWMH0140E: An asset''s storage type cannot be changed from "{0}" to "{1}".
CWWMH0141E: Asset "{0}" cannot be removed because the following composition units are based on it: {1}.
CWWMH0142E: No composition matches the ID "{0}" specified as the "cuID" parameter value.
CWWMH0143E: Ambiguous composition unit ID "{0}" specified as the "cuID" parameter value. Specify a single composition unit edition by using a fully-qualified composition unit ID, for example, WebSphere:cuname=myCompUnit,cuedition=1.0.
CWWMH0144E: Cannot export asset because its storage type is "{0}".
CWWMH0145E: No business-level application matches the ID "{0}" specified as the "blaID" parameter value.
CWWMH0146E: Ambiguous business-level application ID "{0}" specified as the "blaID" parameter value. Specify a single business-level application edition by using a fully-qualified business-level application ID, for example, WebSphere:blaname=myBLA,blaedition=1.0.
CWWMH0149E: Cannot delete business-level application "{0}" because it contains composition units. Delete all composition units which belong to the business-level application, and then delete the business-level application.
CWWMH0150E: Could not save configuration data for business-level application "{0}". Your workspace may be in an inconsistent state. Discard your workspace. Error data: {1}
CWWMH0151E: Business-level application "{0}" cannot be removed because the following composition units are based on it: {1}.
CWWMH0152E: The specified asset relationship "{0}" does not conform to the required asset ID syntax.
CWWMH0153E: The composition unit relationship "{0}" does not conform to the required syntax.
CWWMH0154E: Business-level application "{0}" already exists.
CWWMH0155E: Business-level application "{0}" does not exist.
CWWMH0156E: The activation plan "{0}" does not conform to the required syntax.
CWWMH0157E: Control operation "{0}" is already defined on composition unit "{1}".
CWWMH0158E: The specfied name "{0}" is not a valid business-level application name. The name must be non-empty, cannot have leading or trailing blanks or a leading dot, and cannot contain any of the following characters: \/,#$@:;"*?<>|=+&%''
CWWMH0159E: Could not find step "{0}" in config data repository.
CWWMH0160E: Input file "{0}" for "importAsset" operation is not recognized by any content handler configured in the product.
CWWMH0163E: Asset "{0}" is configured with no type aspects. Assets must be configured with at least one type aspect.
CWWMH0164E: The operation "{0}" failed, leaving the workspace in an inconsistent state. Discard your workspace.
CWWMH0165E: The specfied name "{0}" is not a valid asset name. The name must be non-empty, cannot have leading or trailing blanks or a leading dot, and cannot contain any of the following characters: \/,#$@:;"*?<>|=+&%''
CWWMH0166E: The specfied name "{0}" is not a valid composition unit name. The name must be non-empty, cannot have leading or trailing blanks or a leading dot, and cannot contain any of the following characters: \/,#$@:;"*?<>|=+&%''
CWWMH0167E: Composition unit "{0}" already exists.
CWWMH0168E: The specfied "match target" value is not valid. Specify a value of "true" or "false".
CWWMH0169E: The file name extension of "{0}" does not match that of the original asset name "{1}".
CWWMH0170E: Composition unit "{0}" requires target nodes of version {1} or higher, but the following target nodes are lower versions: {2}.
CWWMH0172E: The value "{1}" for option "{0}" is not valid. Specify a value of "ALL" to update all composition units backed by this asset. Specify "NONE" to not update any composition units.
CWWMH0173E: A control operation definition was created with an attribute value of null or empty string. The control operation definition attribute values are: name: "{0}", description: "{1}", operation handler ID: "{2}".
CWWMH0174E: A parameter definition (part of a control operation definition) was created with an attribute value of null or empty string.. The specified parameter definition attribute values are: name: "{0}", description: "{1}".
CWWMH0175E: Client notifier not set.
CWWMH0176E: The specified starting weight value of "{0}" is not valid. The starting weight must be an integer value between 0 to 2,147,483,647, inclusive.
CWWMH0177E: The value "{1}" for parameter "{0}" is not valid. Specify a value of either "true" or "false", or leave the value empty to choose the default value.
CWWMH0178E: Could not read asset reference configuration data for asset "{0}". Error data: {1}
CWWMH0179E: Could not save asset reference data for asset "{0}". Your workspace may be in an inconsistent state. Discard your workspace. Error data: {1}
CWWMH0180E: Internal error. Scheduler is null.
CWWMH0181E: Could not import Java EE asset.
CWWMH0182E: Could not read configuration data for business-level application ID "{0}". Error data: {1}
CWWMH0183E: Configuration file URI "{0}" is not valid.
CWWMH0184E: Unexpected error occurred while reading asset configuration data. Error data: "{0}"
CWWMH0185E: Unexpected error occurred while reading business-level application configuration data. Error data: "{0}"
CWWMH0186E: Unexpected error occurred while reading composition unit configuration data. Error data: {0}
CWWMH0187E: URI "{0}" length is greater than Windows limit of 259 characters.
CWWMH0188E: Content cannot be saved in the form of a Java EE module.
CWWMH0189E: Could not access Eclipse extension registory object for the "{0}" extension point type. Error data: {1}
CWWMH0191E: Unexpected error occurred while attempting to access the "{0}" Eclipse extension point. Error data: {1}
CWWMH0193E: Class "{0}, specified through the content-depl-data-change-listeners extension point, is not a supported configuration data listener class.
CWWMH0194E: Class "{0}", specified through the content-depl-data-change-listeners Eclipse extension point, could not be instantiated.
CWWMH0196I: Business-level application "{0}" was started successfully.
CWWMH0197E: Problems were encountered while attempting to start business-level application "{0}". It is possible that the business-level application is not running or is only partially running. Please refer to FFDC log entries for details on any failures which were encountered.
CWWMH0198I: Control operation "{0}" not executed on composition unit "{1}" in business-level application "{2}" because the composition unit has no targets.
CWWMH0199I: Business-level application "{0}" was stopped successfully.
CWWMH0200W: Problems were encountered while attempting to stop business-level application "{0}". It is possible that the business-level application is still partially running. Please refer to FFDC log entries for details on any failures which were encountered.
CWWMH0204E: Invalid value "{0}" for "defaultBindingOptions" parameter. The value should be in the form of <prop>=<value>[#<prop>=<value>]..., where <prop> is the property name and <value> is the property value.
CWWMH0205E: Invalid property "{0}" specified in defaultBindingOptions parameter. The property specified must applicable to the type of asset being configured.
CWWMH0206E: Unexpected error occurred while obtaining default Java EE binding data. Error message received: {0}
CWWMH0207E: Source "{0}" for "addCompUnit" operation is not recognized by any content handler configured in the product.
CWWMH0209E: The specified "deplUnit" parameter value of "{0}" includes the deployable unit name "{1}", but the asset being configured has no deployable unit with that name.
CWWMH0210E: Could not read reference configuration data for business-level application "{0}". Error data: {1}
CWWMH0211E: Could not save reference data for business-level application "{0}". Your workspace may be in an inconsistent state. Discard your workspace. Error data: {1}
CWWMH0215W: Cleanup processing for this business-level application command failed. Check FFDC log directory for additional diagnostic data.
CWWMH0216E: Could not read reference configuration data for composition unit "{0}". Error data: {1}
CWWMH0217E: Could not save reference data for composition unit "{0}". Your workspace may be in an inconsistent state. Discard your workspace. Error data: {1}
CWWMH0218E: Error occurred while obtaining business-level application status.
CWWMH0219E: Error occurred while listing business-level applications.
CWWMH0220E: Business-level application ID cannot be empty or null.
CWWMH0221E: Composition unit ID cannot be empty or null.
CWWMH0222E: Asset ID cannot be empty or null.
CWWMH0223E: Value "{0}" for restart behavior on update is not valid. Valid values are "ALL", "NONE", and "DEFAULT".
CWWMH0224E: Session ID cannot be null.
CWWMH0225E: Cannot define a dependency relationship from asset "{0}" to asset "{1}" because doing so would create a circular dependency.
CWWMH0226E: Asset "{0}" cannot be removed because the following assets declare it as a dependency: {1}.
CWWMH0227E: A non-empty value for the "contents" parameter is required when the value for the operation parameter is "{0}".
CWWMH0230E: No file exists at the path specified by the "contents" parameter.
CWWMH0231E: A non-empty value for the "contenturi" parameter is required when the value for the operation parameter is "{0}".
CWWMH0233E: Composition unit "{0}" cannot be removed because the following composition units declare it as a dependency: {1}.
CWWMH0234E: The following assets were specified as dependencies but do not exist: {0}.
CWWMH0235E: The following composition units were specified as dependencies but do not exist: {0}.
CWWMH0236E: The target "{0}" failed validation.
CWWMH0237E: Asset "{0}" cannot be configured as a composition unit because it is a Java EE asset which was imported with a storage type of "NONE" and is not accessible through the destination URI specified when it was imported.
CWWMH0238E: The specified "operation" parameter value of "{0}" is not valid. Valid values are "merge", "replace", "add", "addupdate", "update", and "delete".
CWWMH0239E: The file, looseconfig.xmi, does not exist at the specified location "{0}".
CWWMH0240E: The asset "{0}" cannot be imported with the "loose config" option with a storage type other than "NONE".
CWWMH0241E: The "editAsset" command is not supported for the asset "{0}" because it was imported with the "loose config" option.
CWWMH0242E: An "updateAsset" command with the "operation" parameter set to "merge" is being used to update an asset which was imported with the "loose config" option, but the "ADTCommandProps" parameter table entry "{0}" is not specified.
CWWMH0243E: An "updateAsset" command with the "operation" parameter set to "{0}" is being used to update an asset which was imported with the "loose config" option, and no file exists at the path "{1}", specified by the "ADTCommandProps" parameter table entry, "contents.loose.config".
CWWMH0250E: Configuration data repository entry "{0}" in scope "{1}" does not exist.
CWWMH0260E: Cannot add business-level application "{0}" as a composition unit to business-level application "{1}" because doing so would create a cycle in the business-level application hierarchy.
CWWMH0261E: Invalid value {0} for expansion key. Fail to save Composition unit.
CWWMH0270E: Authorization failure. Insufficient authority to access business-level application "{0}". This operation requires "monitor" role on the cell or on the business-level application.
CWWMH0271E: Authorization failure. Insufficient authority to create a business-level application. This operation requires "deployer" or "configurator" role on the cell.
CWWMH0272E: Authorization failure. Insufficient authority to delete business-level application "{0}". This operation requires "deployer" or "configurator" role on the cell, or "deployer" role on the business-level application.
CWWMH0273E: Authorization failure. Insufficient authority to import an asset. This operation requires "deployer" or "configurator" role on the cell.
CWWMH0274E: Authorization failure. Insufficient authority to delete asset "{0}". This operation requires "deployer" or "configurator" role on the cell, or "deployer" role on the asset.
CWWMH0275E: Authorization failure. Insufficient authority to update asset "{0}". This operation requires "deployer" or "configurator" role on the cell, or "deployer" role on the asset.
CWWMH0276E: Authorization failure. Insufficient authority to access asset "{0}". This operation requires "monitor" role on the cell or on the asset.
CWWMH0277E: Authorization failure. Insufficient authority to start or stop business-level application "{0}". This operation requires "operator" role on the cell, business-level application, or all composition unit targets for the business-level application.
CWWMH0279E: Authorization failure. Insufficient authority to access the resource "{0}". This operation requires "{1}" role on the cell or on the resource.
CWWMH0282E: Authorization failure. Insufficient authority to edit asset "{0}". This operation requires "deployer" or "configurator" role on the cell, or "deployer" role on the asset.
CWWMH0283E: Authorization failure. Insufficient authority to edit business-level application "{0}". This operation requires "deployer" or "configurator" role on the cell, or "deployer" role on the business-level application.
CWWMH0300I: Starting business-level application "{0}".
CWWMH0301I: Stopping business-level application "{0}".
CWWMH0410E: Cannot set target autostart for composition unit "{0}" because it is a Java EE type composition unit.
CWWMH0411E: The "targetID" parameter value "{0}" does not match any targets for composition unit "{1}".
CWWMH0412E: The "targetID" parameter value "{0}" matches multiple targets for composition unit "{1}".
CWWMH0413E: Parameter "{0}" requires a value but no value was provided.
CWWMH1001W: Unexpected error occurred during synchronization of configuration files associated with business-level applications. Error data: {0}
CWWMH1002E: Unable to invoke NotificationService MBean in {0} process to emit business-level application distribution notifications.
CWWMH1004W: Unable to access configuration file "{0}" during synchronization.


Terms and conditions for information centers | Feedback

Last updated: November 13, 2013 05:41 AM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=com.ibm.ws.management.bla.resources.BLAMessages.dita
File name: com.ibm.ws.management.bla.resources.BLAMessages.html