Express (Distributed operating systems), v8.0 > Reference > Messages
CWWMH
CWWMH0100E: The format of "{0}" is not a valid ID.
Explanation The specified value does not follow the expected ID syntax. Valid values for an asset ID include: <asset name>, assetname= <asset name>, and WebSphere:assetname= <asset name>; where <asset name> is the name of the asset. Action If the value was specified as input, specify a syntactically valid ID. Otherwise, the error may be an internal error.
CWWMH0101E: An internal error occurred. Error data: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMH0102E: Could not read configuration data for {0}.
Explanation An unexpected error occurred while reading configuration data for the specified object. The configuration could be corrupted. FFDC log entries might contain additional data about the root cause. Action More info at:
CWWMH0104E: Asset "{0}" already exists.
Explanation The asset being imported already exists. Action Because the asset already exists, you may not need to import the asset. To import the asset, you can specify a different asset name to resolve the name confict.
CWWMH0106E: Composition unit "{0}", specified in an asset dependency relationship declaration, already exists.
Explanation When you create a composition unit, you can specify assets which the new composition unit is dependent on. Each asset dependency is configured as a composition unit, and you can optionally specify the name of the composition unit. The name cannot conflict with any existing composition units. A composition unit name was specified as part of an asset dependency declaration, and the name conflicts with an existing composition unit. Action Specify a composition unit name that does not conflict with any existing composition units.
CWWMH0107E: Composition unit "{0}" does not exist.
Explanation The specified composition unit cannot be found. Action Verify that the ID you specified is correct and identifies an existing composition unit.
CWWMH0108E: The specified target "{0}" does not conform to the required syntax.
Explanation A target must be expressed as a target ID. Valid values for a target ID include: <server name>; server= <server name>; cluster= <cluster name>; WebSphere:server= <server name>,node= <node name>; and WebSphere:cluster= <cluster name>. If the target is a single server and the server name is not unique within the cell, the node name must be specified. Action Specify the target as a target ID.
CWWMH0109E: Class "{0}", specified through the content-depl-providers Eclipse extension point, is not a supported content handler class.
Explanation Business-level application content providers must configure an extension of com.ibm.wsspi.management.bla.framework.ContentHandler. The specified class is not an extension of com.ibm.wsspi.management.bla.framework.ContentHandler. The product is pre-configured with content handlers for certain types of assets such as Java EE applications and general Java archives. Product extensions can also configure content handlers to handle other types of assets. Action This error indicates a problem with a business-level application content provider added as a product extension. Contact the source of the problem content handler class for support.
CWWMH0110E: Class "{0}", specified through the content-depl-providers Eclipse extension point, could not be instantiated. Error data: {1}
Explanation Business-level application content providers must configure an extension of com.ibm.wsspi.management.bla.framework.ContentHandler. The specified content handler class could not be instantiated. The product is pre-configured with content handlers for certain types of assets such as Java EE applications and general Java archives. Product extensions can also configure content handlers to handle other types of assets. Action This error indicates a problem with a business-level application content provider added as a product extension. Contact the source of the problem content handler class for support.
CWWMH0111E: Class "{0}, specified through the operation-depl-providers Eclipse extension point, is not a supported operation handler class.
Explanation Business-level application content providers can configure an extension of com.ibm.wsspi.management.bla.framework.OperationHandler. The specified operation handler class is not an extension of com.ibm.wsspi.management.bla.framework.OperationHandler. The product is pre-configured with operation handlers for certain types of assets such as Java EE applications and general Java archives. Product extensions can also configure operation handlers to handle other types of assets. Action This error indicates a problem with a business-level application content provider added as a product extension. Contact the source of the problem operation handler class for support.
CWWMH0112E: Class "{0}", specified through the operation-depl-providers Eclipse extension point, could not be instantiated. Error data: {1}
Explanation Business-level application content providers must configure an extension of com.ibm.wsspi.management.bla.framework.OperationHandler. The specified operation handler class could not be instantiated. The product is pre-configured with operation handlers for certain types of assets such as Java EE applications and general Java archives. Product extensions can also configure operation handlers to handle other types of assets. Action This error indicates a problem with a business-level application content provider added as a product extension. Contact the source of the problem operation handler class for support.
CWWMH0113E: Unable to get Eclipse extension point using the extension point identifier "{0}".
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMH0114E: Unable to get Eclipse extension registry.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMH0115E: The value of the "save options" parameter passed to a DeployableObjectWriter is not valid.
Explanation This condition could be caused by an internal error or a problem with some business-level application content provider added as a product extension. Action More info at:
CWWMH0116E: The value of the "destination" parameter passed to a DeployableObjectWriter is not valid.
Explanation This condition could be caused by an internal error or a problem with some business-level application content provider added as a product extension. Action More info at:
CWWMH0118E: Unable to obtain ConfigRepositoryClient reference.
Explanation This is an internal error. Action More info at:
CWWMH0119E: Unable to obtain document from the configuration repository.
Explanation An unexpected error occurred while attempting to obtain a document from the configuration repository. Action More info at:
CWWMH0121E: Could not read configuration data for composition unit "{0}". Error data: {1}
Explanation An unexpected error occurred while reading configuration data for the specified composition unit. The configuration could be corrupted. Action More info at:
CWWMH0122E: Could not save configuration data for composition unit "{0}". Your workspace may be in an inconsistent state. Discard your workspace. Error data: {1}
Explanation Unexpected error occurred while saving composition unit configuration data to the workspace. Changes were made to the workspace which cannot be undone. Do not save the the workspace in this inconsistent state; otherwise, you will corrupt the configuration. Action Discard the workspace and reattempt the configuration changes.
CWWMH0123E: Could not read configuration data for asset ID "{0}". Error data: {1}
Explanation An unexpected error occurred while reading configuration data for the specified asset. The configuration could be corrupted. Action More info at:
CWWMH0124E: Could not save configuration data for asset "{0}". Your workspace may be in an inconsistent state. Discard your workspace. Error data: {1}
Explanation Unexpected error occurred while saving asset configuration data to the workspace. Changes were made to the workspace which cannot be undone. Do not save the the workspace in this inconsistent state; otherwise, you will corrupt the configuration. Action Discard the workspace and reattempt the configuration changes.
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.
Explanation The specified "type aspect" value does not conform to the required syntax. The syntax is: WebSphere:spec= <name>[,version= <version>]. The spec property is required; the version is optional. An example of a valid "type aspect" value is: WebSphere:spec=SomeSpecThatAssetImplements,version=1.0. Action Specify a "type aspect" value which conforms to the required syntax.
CWWMH0126E: The specified asset ID "{0}" does not conform to the required syntax.
Explanation The asset ID provided is syntactically incorrect. Examples of valid asset IDs include: myAsset.jar, assetname=myAsset.jar, and WebSphere:assetname=myAsset.jar. Action Specify an asset ID which conforms to the required syntax.
CWWMH0127E: The specified composition unit ID "{0}" does not conform to the required syntax.
Explanation The composition unit ID provided is syntactically incorrect. Examples of valid composition unit IDs include: myCompUnit, cuname=myCompUnit, and WebSphere:cuname=myCompUnit. Action Specify a composition unit ID which conforms to the required syntax.
CWWMH0128E: The specified business-level application ID "{0}" does not conform to the required syntax.
Explanation The business-level application ID provided is syntactically incorrect. Examples of valid business-level application IDs include: myBLA, blaname=myBLA, and WebSphere:blaname=myBLA. Action Specify a business-level application ID which conforms 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.
Explanation The specified asset ID matches multiple versions of an asset. Action Fully qualify the ID to select a specific asset version. The complete asset ID format is WebSphere:assetname= <name>,assetversion= <version>. An example of a fully-qualified asset ID is 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.
Explanation The specified business-level application ID matches multiple versions of a business-level application. Action Fully qualify the ID to select a specific business-level application version. The complete business-level application ID format is WebSphere:blaname= <name>,blaedition= <edition>. An example of a fully-qualified business-level application ID is 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.
Explanation The composition unit source ID specified matches both an asset name and a business-level application name. Action 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.
Explanation No file exists at the specified location. This error applies only to development tools interoperating with WAS. Action Report the problem to the provider of the development tool you are using.
CWWMH0133E: No file exists at the path specified by the "source" parameter value "{0}".
Explanation The "source" parameter value must specify the path of an existing file. Action Set the "source" parameter to the path of an existing file.
CWWMH0134E: The specified "storageType" parameter value "{0}" is not valid. Specify "FULL", "METADATA", or "NONE".
Explanation The specified "storageType" parameter value is not valid. Valid "storageType" parameter values include "FULL", "METADATA", and "NONE". Action Specify a valid "storageType" parameter value.
CWWMH0135E: No "filename" parameter value was specified.
Explanation The specified operation requires a non-empty value for the "filename" parameter. Either no value was specfied or the specified value was empty. Action Specify a non-empty "filename" parameter value.
CWWMH0136E: The value for the "cuSourceID" parameter cannot be empty or null.
Explanation The composition unit source ID must be a non-null, non-empty value. Action Specify a valid composition unit source ID.
CWWMH0137E: No asset or business-level application matches the ID "{0}" specified as the "cuSourceID" parameter value.
Explanation Cannot find an asset or business-level application which matches the specified ID. Action Verify that the ID you specified is correct and identifies an existing asset or business-level application.
CWWMH0138E: No asset matches the ID "{0}" specified as the "assetID" parameter value.
Explanation Cannot find an asset which matches the specified asset ID. Action Verify that the ID you specified is correct and identifies an existing asset.
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.
Explanation The specified asset ID matches multiple versions of an asset. Action Fully qualify the ID to select a specific asset version. The complete asset ID format is WebSphere:assetname= <name>,assetversion= <version>. An example of a fully-qualified asset ID is WebSphere:assetname=myAsset.jar,assetversion=1.0.
CWWMH0140E: An asset''s storage type cannot be changed from "{0}" to "{1}".
Explanation Storage type values indicate how much of the asset is stored in the product configuration repository. Storage type values in decreasing order include "FULL", "METADATA", and "NONE". Storage types other than "FULL" typically are used by development tools based on the product. The storage type for an asset can be decreased, such as from "FULL" to "METADATA", but not the reverse. Action The asset can be imported again with the desired storage type. If the asset is not deleted from the product's configuration repository first, it must be imported again with another name in order to avoid a name conflict.
CWWMH0141E: Asset "{0}" cannot be removed because the following composition units are based on it: {1}.
Explanation Asset specified cannot be removed because it has been configured as a composition unit in one or more business-level applications. Action Given that business-level applications are using the asset, removal of the asset might not be appropriate. If you decide that removing the asset is appropriate, first remove the composition units based on the asset from their respective business-level applications.
CWWMH0142E: No composition matches the ID "{0}" specified as the "cuID" parameter value.
Explanation Cannot find a composition unit which matches the specified composition unit ID. Action Verify that the ID you specified is correct and identifies an existing composition unit.
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.
Explanation The specified composition unit ID matches multiple editions of a composition unit. Action Fully qualify the ID to select a specific composition unit edition. The complete composition unit ID format is WebSphere:cuname= <name>,cuedition= <edition>. An example of a fully-qualified composition unit ID is WebSphere:cuname=myCompUnit,cuedition=1.0.
CWWMH0144E: Cannot export asset because its storage type is "{0}".
Explanation The asset file for an asset with a storage type of METADATA or NONE is not stored in the product configuration repository. Therefore, the asset cannot be exported. Action Export only assets with a storage type of "FULL".
CWWMH0145E: No business-level application matches the ID "{0}" specified as the "blaID" parameter value.
Explanation Cannot find a business-level application which matches the specified business-level application ID. Action Verify that the ID you specified is correct and identifies an existing business-level application.
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.
Explanation The specified business-level application ID matches multiple editions of a business-level application. Action Fully qualify the ID to select a specific business-level application edition. The complete business-level application ID format is WebSphere:blaname= <name>,blaedition= <edition>. An example of a fully-qualified business-level application ID is 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.
Explanation A business-level application which contains composition units cannot be deleted. All of its composition units must be deleted before it can be deleted. Action Delete the delete business-level application's composition units, and then delete the delete 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}
Explanation Unexpected error occurred while saving business-level application configuration data to the workspace. Changes were made to the workspace which cannot be undone. Do not save the the workspace in this inconsistent state; otherwise, you will corrupt the configuration. Action Discard the workspace and reattempt the configuration changes.
CWWMH0151E: Business-level application "{0}" cannot be removed because the following composition units are based on it: {1}.
Explanation Business-level application specified cannot be removed because it is configured as a composition unit in one or more other business-level applications. Action Given that composition units are based on the business-level application, removal of the business-level application might not be appropriate. If you decide that removing the business-level application is appropriate, first remove the composition units based on the business-level application from their respective business-level applications.
CWWMH0152E: The specified asset relationship "{0}" does not conform to the required asset ID syntax.
Explanation An asset relationship must be expressed as an asset ID. Valid values for an asset ID include: <asset name>, assetname= <asset name>, and WebSphere:assetname= <asset name>; where <asset name> is the name of the asset. Action Specify the relationship as an asset ID.
CWWMH0153E: The composition unit relationship "{0}" does not conform to the required syntax.
Explanation A composition unit relationship must be expressed as a composition unit ID. Valid values for a composition unit ID include: <composition unit name>, cuname= <composition unit name>, and WebSphere:cuname= <composition unit name>; where <composition unit name> is the name of the composition unit. Action Specify the relationship as a composition unit ID.
CWWMH0154E: Business-level application "{0}" already exists.
Explanation A new business-level application cannot be created with the same name as an existing business-level application. Action Choose a name which does not conflict with an existing business-level application.
CWWMH0155E: Business-level application "{0}" does not exist.
Explanation No business-level application with the specified name can be found. Action Verify that the ID you specified is correct and identifies an existing business-level application.
CWWMH0156E: The activation plan "{0}" does not conform to the required syntax.
Explanation An activation plan must be expressed as a series of runtime component IDs separated by a "plus" sign (+). Valid values for a runtime component ID include: <spec name>, specName= <spec name>, WebSphere:specName= <spec name>, and WebSphere:specName= <spec name>,specVersion= <version>; where <spec name> is the name of the runtime component and <version> is the version of the runtime component. An example of a valid activation plan value is: WebSphere:specName=SomeRuntimeComponent,version=1.0. Action Specify the relationship which conforms to the described syntax.
CWWMH0157E: Control operation "{0}" is already defined on composition unit "{1}".
Explanation The specified control operation already exists for the composition unit being configured. Action This error indicates a problem with the product extension associated with the asset you are trying to configure as a composition unit. Contact the provider of the product extension associated with the asset for support.
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: \/,#$@:;"*? <>|=+&%''
Explanation The specified business-level application name is not valid. The error message lists restrictions to business-level application names. Action Specify a name which does not violate any of the stated restrictions.
CWWMH0159E: Could not find step "{0}" in config data repository.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMH0160E: Input file "{0}" for "importAsset" operation is not recognized by any content handler configured in the product.
Explanation Files imported as assets must be recognized by some content handler. The product is pre-configured with content handlers for certain types of assets such as Java EE applications and general Java archives. Product extensions can also configure content handlers to handle other types of assets. No content handler recognized the file you are trying to import as an asset. Action If the file you are trying to import is not recognizable by any configured content handler, you cannot import that file. The error could also indicate a problem with the product extension associated with the file you are trying to import. In this case, contact the provider of the product extension associated with the file for support.
CWWMH0163E: Asset "{0}" is configured with no type aspects. Assets must be configured with at least one type aspect.
Explanation The content handler which recognizes the specified asset did not configure any type aspects for the asset. An asset must have at least one type aspect. The product is pre-configured with content handlers for certain types of assets such as Java EE applications and general Java archives. Product extensions can also configure content handlers to handle other types of assets. Action This error indicates a problem with the product extension associated with the specified asset. Contact the provider of the product extension associated with the asset for support.
CWWMH0164E: The operation "{0}" failed, leaving the workspace in an inconsistent state. Discard your workspace.
Explanation The specified operation did not complete successfully and changes were made to the workspace which cannot be undone. Do not save the the workspace in this inconsistent state; otherwise, you will corrupt the configuration. Action Discard the workspace. If possible, determine the cause leading to the failed operation, and retry.
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: \/,#$@:;"*? <>|=+&%''
Explanation The specified asset name is not valid. The error message lists restrictions to asset names. Action Specify a name which does not violate any of the stated restrictions.
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: \/,#$@:;"*? <>|=+&%''
Explanation The specified composition unit name is not valid. The error message lists restrictions to composition unit names. Action Specify a name which does not violate any of the stated restrictions.
CWWMH0167E: Composition unit "{0}" already exists.
Explanation A composition unit with the specified name already exists. Action Specify a composition name that is not already that of an existing composition unit.
CWWMH0168E: The specfied "match target" value is not valid. Specify a value of "true" or "false".
Explanation A "match target" value must be "true" or "false". Action Specify a "match target" value of "true" or "false".
CWWMH0169E: The file name extension of "{0}" does not match that of the original asset name "{1}".
Explanation The extension in the asset name must match the file name extension of the asset being imported. Action Specify an asset file name with an extension which matches the asset file being imported.
CWWMH0170E: Composition unit "{0}" requires target nodes of version {1} or higher, but the following target nodes are lower versions: {2}.
Explanation The specified composition unit cannot run on nodes lower than the specified version. The composition is being targeted to a node lower than the minumum supported version. If the target is a cluster, the specified node or nodes contain members of the cluster. Action Choose a target that includes only nodes which are at the required level or higher.
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.
Explanation The updateAssociatedCUs specification optionally can be included in the AssetOptions step in the updateAsset command for Java EE assets. The updateAssociatedCUs option requires a value of "NONE" or "ALL". A value of "ALL" updates all composition units backed by the asset being updated. Depending on the asset updates, you might need to edit updated composition units. A value of "NONE", or not specifying this option at all, does not update any composition units. If composition units are not updated, they cannot use the updated asset. For a composition unit to use an updated Java EE asset, update the asset with this option set to "ALL". Action Specify a value of either "NONE" or "ALL", or do not specify the option to choose the default behavior.
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}".
Explanation A control operation definition was created with an attributed value which is not valid. Action This error indicates a problem with the product extension associated with the asset you are trying to configure as a composition unit. Contact the provider of the product extension associated with the asset for support.
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}".
Explanation A control operation definition contains a parameter definition with an attribute value which is not valid. Action This error indicates a problem with the product extension associated with the asset you are trying to configure as a composition unit. Contact the provider of the product extension associated with the asset for support.
CWWMH0175E: Client notifier not set.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
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.
Explanation The starting weight value must be an integer value between 0 and 2,147,483,647, inclusive. Start order is according to starting weight in ascending order. Action Specify a starting weight between 0 and 2,147,483,647.
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.
Explanation The specified parameter is an optional parameter which requires a value of "true" or "false". Action 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}
Explanation An unexpected error occurred while reading asset reference configuration data for the specified asset. The configuration could be corrupted. Action More info at:
CWWMH0179E: Could not save asset reference data for asset "{0}". Your workspace may be in an inconsistent state. Discard your workspace. Error data: {1}
Explanation Unexpected error occurred while saving asset reference configuration data to the workspace. Changes were made to the workspace which cannot be undone. Do not save the the workspace in this inconsistent state; otherwise, you will corrupt the configuration. Action Discard the workspace and reattempt the configuration changes.
CWWMH0180E: Internal error. Scheduler is null.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMH0181E: Could not import Java EE asset.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMH0182E: Could not read configuration data for business-level application ID "{0}". Error data: {1}
Explanation An unexpected error occurred while reading configuration data for the specified business-level application. The configuration could be corrupted. Action More info at:
CWWMH0183E: Configuration file URI "{0}" is not valid.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMH0184E: Unexpected error occurred while reading asset configuration data. Error data: "{0}"
Explanation An unexpected error occurred while reading asset configuration data. The configuration could be corrupted. Action More info at:
CWWMH0185E: Unexpected error occurred while reading business-level application configuration data. Error data: "{0}"
Explanation An unexpected error occurred while reading business-level application configuration data. The configuration could be corrupted. Action More info at:
CWWMH0186E: Unexpected error occurred while reading composition unit configuration data. Error data: {0}
Explanation An unexpected error occurred while reading composition unit configuration data. The configuration could be corrupted. Action More info at:
CWWMH0187E: URI "{0}" length is greater than Windows limit of 259 characters.
Explanation Some versions of Windows operating systems limit file pathname lengths to 259 characters. A file related to a business-level application is exceeding that limit. Action Various user-chosen names can influence the overall length of pathnames of files stored in the configuration repository. Such names include the product installation directory pathname and the cell name. Also, individual business-level application artifact names, including names for assets, composition units, and Java EE application names, affect the pathname length of respective files. Try using names which are not excessively long with respect to the 259 character limit.
CWWMH0188E: Content cannot be saved in the form of a Java EE module.
Explanation A Java archive which is a Java EE module is being saved to the configuration repository. This archive format is not supported. The failure could be caused by an internal error or a problem with some business-level application content provider added as a product extension. Action More info at:
CWWMH0189E: Could not access Eclipse extension registory object for the "{0}" extension point type. Error data: {1}
Explanation An error occurred attempting to access some extension of the specified extension point type. The failure, while not fatal, could cause some operations related to business-level applications to not function correctly. The failure could be caused by an internal error or a problem with some business-level application content provider added as a product extension. Action More info at:
CWWMH0191E: Unexpected error occurred while attempting to access the "{0}" Eclipse extension point. Error data: {1}
Explanation An error occurred while attempting to read Exclipse extension points. Action More info at:
CWWMH0193E: Class "{0}, specified through the content-depl-data-change-listeners extension point, is not a supported configuration data listener class.
Explanation Business-level application content providers can configure an extension of com.ibm.wsspi.management.bla.cdr.ConfigDataListener. The specified configuration data listener class is not an extension of com.ibm.wsspi.management.bla.cdr.ConfigDataListener. The product is pre-configured with configuration data listeners for certain types of assets such as Java EE applications and general Java archives. Product extensions can also configure operation handlers to handle other types of assets. Action This error indicates a problem with a business-level application content provider added as a product extension. Contact the source of the problem configuration data listener class for support.
CWWMH0194E: Class "{0}", specified through the content-depl-data-change-listeners Eclipse extension point, could not be instantiated.
Explanation Business-level application content providers must configure an extension of com.ibm.wsspi.management.bla.cdr.ConfigDataListener. The specified configuration data listener class could not be instantiated. The product is pre-configured with configuration data listeners for certain types of assets such as Java EE applications and general Java archives. Product extensions can also configure configuration data listeners to handle other types of assets. Action This error indicates a problem with a business-level application content provider added as a product extension. Contact the source of the problem configuration data listener class for support.
CWWMH0196I: Business-level application "{0}" was started successfully.
Explanation Informational message indicating that the specified business-level application was started successfully. Action No action is necessary.
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.
Explanation Not all modules in the specified business-level application could be started. It is possible some modules are not running. Action Refer to the FFDC log for more details on any failures encountered.
CWWMH0198I: Control operation "{0}" not executed on composition unit "{1}" in business-level application "{2}" because the composition unit has no targets.
Explanation A composition unit in a business-level application cannot be started or stopped unless it is configured to have a target. When a business-level application is started or stopped, composition units with no targets are ignored. Action No action is necessary. In order to make the composition unit runnable, configure it with a target server or cluster.
CWWMH0199I: Business-level application "{0}" was stopped successfully.
Explanation Informational message indicating that the specified business-level application was stopped successfully. Action No action is necessary.
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.
Explanation Not all modules in the specified business-level application could be stopped. It is possible some modules are still running. This message can also occur when the server which hosts a module is not running. Action Refer to the FFDC log for more details on any failures 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.
Explanation The value specified for defaultBindingOptions parameter is incorrect. Make sure that the values are specified in a <prop>= <value> format with each property-value pair separated by a pound sign (#). Action Retry the command with the correct value for defaultBindingOptions parameter.
CWWMH0205E: Invalid property "{0}" specified in defaultBindingOptions parameter. The property specified must applicable to the type of asset being configured.
Explanation The default binding property specified is not supported by the composition unit's underlying asset. We can specify only those properties which can be used for that particular type of asset. Action Retry the command with the correct value for defaultBindingOptions parameter.
CWWMH0206E: Unexpected error occurred while obtaining default Java EE binding data. Error message received: {0}
Explanation There was some problem analyzing the Java EE application file being imported as an asset. Default binding options could not be determined due to some unexpected error. The mesage for the unexpected error is included in this error message for additional information. Action Refer to the message associated with the unexpected error for more details about the origin of the problem.
CWWMH0207E: Source "{0}" for "addCompUnit" operation is not recognized by any content handler configured in the product.
Explanation The source for a composition unit being created must be recognized by some content handler. The product is pre-configured with content handlers for certain types of assets such as Java EE applications and general Java archives. Product extensions can also configure content handlers to handle other types of assets. No content handler recognized the source you are trying to configure as a composition unit. Action The error is possibly caused by a problem with the product extension associated with the source you are trying to configure as a composition unit. In this case, contact the provider of the product extension associated with the source for support.
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.
Explanation The "deplUnit" parameter value, if specified, must include only the names of deployable units which are part of the asset you are configuring as a composition unit. Action Retry the command with a valid "deplUnit" parameter value.
CWWMH0210E: Could not read reference configuration data for business-level application "{0}". Error data: {1}
Explanation An unexpected error occurred while reading business-level application reference configuration data for the specified business-level application. The configuration could be corrupted. Action More info at:
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}
Explanation Unexpected error occurred while saving business-level application reference configuration data to the workspace. Changes were made to the workspace which cannot be undone. Do not save the the workspace in this inconsistent state; otherwise, you will corrupt the configuration. Action Discard the workspace and reattempt the configuration changes.
CWWMH0215W: Cleanup processing for this business-level application command failed. Check FFDC log directory for additional diagnostic data.
Explanation Cleanup processing for a business-level application command failed. Cleanup processing occurs whether the command execution ends successfully or unsuccessfully. The exact nature of cleanup processing varies with the individual command and data being processed by the command. Action Examine FFDC log entries for additional diagnostic data.
CWWMH0216E: Could not read reference configuration data for composition unit "{0}". Error data: {1}
Explanation An unexpected error occurred while reading composition unit reference configuration data for the specified composition unit. The configuration could be corrupted. Action More info at:
CWWMH0217E: Could not save reference data for composition unit "{0}". Your workspace may be in an inconsistent state. Discard your workspace. Error data: {1}
Explanation Unexpected error occurred while saving composition unit reference configuration data to the workspace. Changes were made to the workspace which cannot be undone. Do not save the the workspace in this inconsistent state; otherwise, you will corrupt the configuration. Action Discard the workspace and reattempt the configuration changes.
CWWMH0218E: Error occurred while obtaining business-level application status.
Explanation Could not obtain business-level application status due to some unexpected error. Check FFDC log directory for additional diagnostic data. Action More info at:
CWWMH0219E: Error occurred while listing business-level applications.
Explanation Could not list business-level applications due to some unexpected error. Check FFDC log directory for additional diagnostic data. Action More info at:
CWWMH0220E: Business-level application ID cannot be empty or null.
Explanation A business-level application ID must be a non-null, non-empty value. Action Specify a valid business-level application ID.
CWWMH0221E: Composition unit ID cannot be empty or null.
Explanation A composition unit ID must be a non-null, non-empty value. Action Specify a valid composition unit ID.
CWWMH0222E: Asset ID cannot be empty or null.
Explanation An asset ID must be a non-null, non-empty value. Action Specify a valid asset ID.
CWWMH0223E: Value "{0}" for restart behavior on update is not valid. Valid values are "ALL", "NONE", and "DEFAULT".
Explanation A value other than "ALL", "NONE", or "DEFAULT" was specified for restart behavior on update. Action Specify a valid value for restart behavior on update.
CWWMH0224E: Session ID cannot be null.
Explanation The reported condition could be a product internal error or a problem with a third-party content provider plug-in designed to handle specific asset types. Action More info at:
CWWMH0225E: Cannot define a dependency relationship from asset "{0}" to asset "{1}" because doing so would create a circular dependency.
Explanation You are trying to define a dependency relationship from an asset to a second asset where the second asset already has a dependency relationship defined on the first asset. Circular dependency relationships are not allowed. Action Avoid circular dependency relationships. Consider combining the two mutually-dependent assets into one single asset.
CWWMH0226E: Asset "{0}" cannot be removed because the following assets declare it as a dependency: {1}.
Explanation Asset specified cannot be removed because it is declared as a dependency by other assets. Action Given that dependencies on the asset exist, removal of the asset might not be appropriate. If you decide that removing the asset is appropriate, first remove the dependency relationships from the dependent assets or specify a "force" parameter value of "true" to force the removal of those dependency relationships.
CWWMH0227E: A non-empty value for the "contents" parameter is required when the value for the operation parameter is "{0}".
Explanation No value for the "contents" parameter was specified. Action Specify a non-empty value for the "contents" parameter.
CWWMH0230E: No file exists at the path specified by the "contents" parameter.
Explanation The "contents" parameter value must be the pathname to an existing file. No file was found at that path. Action Specify the pathname to an existing file.
CWWMH0231E: A non-empty value for the "contenturi" parameter is required when the value for the operation parameter is "{0}".
Explanation No value for the "contenturi" parameter was specified. Action Specify a non-empty value for the "contenturi" parameter.
CWWMH0233E: Composition unit "{0}" cannot be removed because the following composition units declare it as a dependency: {1}.
Explanation The specified composition unit cannot be removed because it is declared as a dependency by other composition units. Action Given that dependencies on the composition unit exist, removal of the composition unit might not be appropriate. If you decide that removing the composition unit is appropriate, first remove the dependency relationships from the dependent composition units or specify a "force" parameter value of "true" to force the removal of those dependency relationships.
CWWMH0234E: The following assets were specified as dependencies but do not exist: {0}.
Explanation Assets specified in a dependency relationship must exist. Action Specify existing assets as dependencies.
CWWMH0235E: The following composition units were specified as dependencies but do not exist: {0}.
Explanation Composition units specified in a dependency relationship must exist. Action Specify existing composition units as dependencies.
CWWMH0236E: The target "{0}" failed validation.
Explanation Either no target matches the specification or the specification is ambiguous. Action More info at:
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.
Explanation A Java EE asset must be accessible when it is added to a business-level application as a composition unit. An asset imported with a storage type of "NONE" does not reside in the product's configuration repository. The only means of access in this case is through the destination URI, which is specified when the asset is imported. If such an asset cannot be accessed through its destination URI, it cannot be configured as anything but a shared library. Action The asset in its present state cannot be configured. To make the asset configurable, make it accessible through its destination URI when it is configured. Alternatively, the asset can be imported with a storage type of "FULL" so that it is accessible from the product configuration repository.
CWWMH0238E: The specified "operation" parameter value of "{0}" is not valid. Valid values are "merge", "replace", "add", "addupdate", "update", and "delete".
Explanation The "operation" parameter value specified on an "updateAsset" command invocation is not valid. Action Specify an "operation" parameter value of "merge", "replace", "add", "addupdate", "update", or "delete".
CWWMH0239E: The file, looseconfig.xmi, does not exist at the specified location "{0}".
Explanation The file, looseconfig.xmi, does not exist at the specified location. This error applies only to development tools interoperating with WAS. Action Report the problem to the provider of the development tool you are using.
CWWMH0240E: The asset "{0}" cannot be imported with the "loose config" option with a storage type other than "NONE".
Explanation In order for an asset to be imported with the "loose config" option, the storage type must be "NONE". This error applies only to development tools interoperating with WAS. Action Report the problem to the provider of the development tool you are using.
CWWMH0241E: The "editAsset" command is not supported for the asset "{0}" because it was imported with the "loose config" option.
Explanation The "editAsset" command does not support assets imported with the "loose config" option. This error applies only to development tools interoperating with WAS. Action Report the problem to the provider of the development tool you are using.
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.
Explanation When the "updateAsset" command with an "operation" parameter value of "merge" is executed on an asset imported with the "loose config" option, the command parameter "ADTCommandProps" must also be specified and must include a table which includes lists of added, removed, and/or updated content URIs. This error applies only to development tools interoperating with WAS. Action Report the problem to the provider of the development tool you are using.
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".
Explanation When the "updateAsset" command with an "operation" parameter value of "replace", "add", "addupdate", or "update", is executed on an asset imported with the "loose config" option, the command "ADTCommandProps" table parameter must be specified and must include a "contents.loose.config" property setting, the value of which is the path of the input content file. No file was found with the specified path. This error applies only to development tools interoperating with WAS. Action Report the problem to the provider of the development tool you are using.
CWWMH0250E: Configuration data repository entry "{0}" in scope "{1}" does not exist.
Explanation Command step data could not be found in the configuration data repository when attempting to update it after user interaction. This condition is the result of an internal error. Action More info at:
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.
Explanation A business-level application can be added as a composition unit to another business-level application. It is therefore possible to create a hierarchy of business-level applications of two or more levels. However, the same business-level application cannot occur in more than one level in any path of the hierarchy. Action Avoid cyclic business-level application hierarchies.
CWWMH0261E: Invalid value {0} for expansion key. Fail to save Composition unit.
Explanation The value specified is not the correct format. The expansion value has to be an integer. Action CSMG0002
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.
Explanation You are not assigned the roles required to execute the requested operation on the specified business-level application. Action We must obtain the required role assignments before you can complete the requested operation.
CWWMH0271E: Authorization failure. Insufficient authority to create a business-level application. This operation requires "deployer" or "configurator" role on the cell.
Explanation You are not assigned the roles required to create a business-level application. Action We must obtain the required role assignments before you can complete the requested operation.
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.
Explanation You are not assigned the roles required to delete the specified business-level application. Action We must obtain the required role assignments before you can complete the requested operation.
CWWMH0273E: Authorization failure. Insufficient authority to import an asset. This operation requires "deployer" or "configurator" role on the cell.
Explanation You are not assigned the roles required to import an asset. Action We must obtain the required role assignments before you can complete the requested operation.
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.
Explanation You are not assigned the roles required to delete the specified asset. Action We must obtain the required role assignments before you can complete the requested operation.
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.
Explanation The user is not assigned the roles required to update the specified asset. Action We must obtain the required role assignments before you can complete the requested operation.
CWWMH0276E: Authorization failure. Insufficient authority to access asset "{0}". This operation requires "monitor" role on the cell or on the asset.
Explanation You are not assigned the roles required to execute the requested operation on the specified asset. Action We must obtain the required role assignments before you can complete the requested operation.
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.
Explanation You are not assigned the roles required to start or stop the specified business-level application. Action We must obtain the required role assignments before you can complete the requested operation.
CWWMH0279E: Authorization failure. Insufficient authority to access the resource "{0}". This operation requires "{1}" role on the cell or on the resource.
Explanation You are not assigned the roles required to execute the requested operation on the specified resource. Action We must obtain the required role assignments before you can complete the requested operation.
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.
Explanation The user is not assigned the roles required to edit the specified asset. Action We must obtain the required role assignments before you can complete the requested operation.
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.
Explanation You are not assigned the roles required to edit the specified business-level application. Action We must obtain the required role assignments before you can complete the requested operation.
CWWMH0300I: Starting business-level application "{0}".
Explanation Informational message indicating that a startBLA command on the specified business-level application has been issued. Action No action is necessary.
CWWMH0301I: Stopping business-level application "{0}".
Explanation Informational message indicating that a stopBLA command on the specified business-level application has been issued. Action No action is necessary.
CWWMH0410E: Cannot set target autostart for composition unit "{0}" because it is a Java EE type composition unit.
Explanation Composition units created as a by-product of enterprise application installation cannot be configured for target autostart. Action Configure the enterprise application associated with the composition unit to set the target autostart option.
CWWMH0411E: The "targetID" parameter value "{0}" does not match any targets for composition unit "{1}".
Explanation The selected composition unit does not have the specified target. Action Verify that the composition unit and target you specified are correct. View the composition unit configuration for target data.
CWWMH0412E: The "targetID" parameter value "{0}" matches multiple targets for composition unit "{1}".
Explanation The target was partially specified and matches multiple targets for the selected composition unit.. Action Provide complete target specification. For example, instead of specifying only a server name, specify both the server name and node name.
CWWMH0413E: Parameter "{0}" requires a value but no value was provided.
Explanation No value for the required parameter was specified. Action Provide a value for the specified parameter.
CWWMH1001W: Unexpected error occurred during synchronization of configuration files associated with business-level applications. Error data: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CWWMH1002E: Unable to invoke NotificationService MBean in {0} process to emit business-level application distribution notifications.
Explanation Business-level application distribution status events are emitted through the NotificationService MBean. Because a reference to the NotificationService MBean cannot be obtained or the MBean invocation failed, some application distribution notifications cannot be sent. Any listeners for those events will not receive them. Action See FFDC for more information.
CWWMH1004W: Unable to access configuration file "{0}" during synchronization.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at: