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. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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 | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The asset being imported already exists. |
Action | Because the asset already exists, you may not need to import the asset. If you want to import the asset, you can specify a different asset name to resolve the name confict. |
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. |
Explanation | The specified composition unit cannot be found. |
Action | Verify that the ID you specified is correct and identifies an existing composition unit. |
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. |
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. |
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. |
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. |
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. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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 | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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 | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This is an internal error. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An unexpected error occurred while attempting to obtain a document from the configuration repository. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An unexpected error occurred while reading configuration data for the specified composition unit. The configuration could be corrupted. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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 your configuration. |
Action | Discard the workspace and reattempt your configuration changes. |
Explanation | An unexpected error occurred while reading configuration data for the specified asset. The configuration could be corrupted. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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 your configuration. |
Action | Discard the workspace and reattempt your configuration changes. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
Explanation | No file exists at the specified location. This error applies only to development tools interoperating with WebSphere Application Server. |
Action | Report the problem to the provider of the development tool you are using. |
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. |
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. |
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. |
Explanation | The composition unit source ID must be a non-null, non-empty value. |
Action | Specify a valid composition unit source ID. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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". |
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. |
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. |
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. |
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 your configuration. |
Action | Discard the workspace and reattempt your configuration changes. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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. |
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. |
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 your configuration. |
Action | Discard the workspace. If possible, determine the cause leading to the failed operation, and retry. |
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. |
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. |
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. |
Explanation | A "match target" value must be "true" or "false". |
Action | Specify a "match target" value of "true" or "false". |
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. |
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. |
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, you must 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. |
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. |
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. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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. |
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. |
Explanation | An unexpected error occurred while reading asset reference configuration data for the specified asset. The configuration could be corrupted. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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 your configuration. |
Action | Discard the workspace and reattempt your configuration changes. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An unexpected error occurred while reading configuration data for the specified business-level application. The configuration could be corrupted. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An unexpected error occurred while reading asset configuration data. The configuration could be corrupted. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An unexpected error occurred while reading business-level application configuration data. The configuration could be corrupted. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An unexpected error occurred while reading composition unit configuration data. The configuration could be corrupted. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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. |
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 | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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 | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An error occurred while attempting to read Exclipse extension points. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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. |
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. |
Explanation | Informational message indicating that the specified business-level application was started successfully. |
Action | No action is necessary. |
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. |
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. |
Explanation | Informational message indicating that the specified business-level application was stopped successfully. |
Action | No action is necessary. |
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. |
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. |
Explanation | The default binding property specified is not supported by the composition unit's underlying asset. You 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. |
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. |
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. |
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. |
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 | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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 your configuration. |
Action | Discard the workspace and reattempt your configuration changes. |
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. |
Explanation | An unexpected error occurred while reading composition unit reference configuration data for the specified composition unit. The configuration could be corrupted. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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 your configuration. |
Action | Discard the workspace and reattempt your configuration changes. |
Explanation | Could not obtain business-level application status due to some unexpected error. Check FFDC log directory for additional diagnostic data. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | Could not list business-level applications due to some unexpected error. Check FFDC log directory for additional diagnostic data. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | A business-level application ID must be a non-null, non-empty value. |
Action | Specify a valid business-level application ID. |
Explanation | A composition unit ID must be a non-null, non-empty value. |
Action | Specify a valid composition unit ID. |
Explanation | An asset ID must be a non-null, non-empty value. |
Action | Specify a valid asset ID. |
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. |
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 | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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. |
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. |
Explanation | No value for the "contents" parameter was specified. |
Action | Specify a non-empty value for 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. |
Explanation | No value for the "contenturi" parameter was specified. |
Action | Specify a non-empty value for the "contenturi" parameter. |
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. |
Explanation | Assets specified in a dependency relationship must exist. |
Action | Specify existing assets as dependencies. |
Explanation | Composition units specified in a dependency relationship must exist. |
Action | Specify existing composition units as dependencies. |
Explanation | Either no target matches the specification or the specification is ambiguous. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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. |
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". |
Explanation | The file, looseconfig.xmi, does not exist at the specified location. This error applies only to development tools interoperating with WebSphere Application Server. |
Action | Report the problem to the provider of the development tool you are using. |
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 WebSphere Application Server. |
Action | Report the problem to the provider of the development tool you are using. |
Explanation | The "editAsset" command does not support assets imported with the "loose config" option. This error applies only to development tools interoperating with WebSphere Application Server. |
Action | Report the problem to the provider of the development tool you are using. |
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 WebSphere Application Server. |
Action | Report the problem to the provider of the development tool you are using. |
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 WebSphere Application Server. |
Action | Report the problem to the provider of the development tool you are using. |
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 | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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. |
Explanation | The value specified is not the correct format. The expansion value has to be an integer. |
Action | CSMG0002 |
Explanation | You are not assigned the roles required to execute the requested operation on the specified business-level application. |
Action | You must obtain the required role assignments before you can complete the requested operation. |
Explanation | You are not assigned the roles required to create a business-level application. |
Action | You must obtain the required role assignments before you can complete the requested operation. |
Explanation | You are not assigned the roles required to delete the specified business-level application. |
Action | You must obtain the required role assignments before you can complete the requested operation. |
Explanation | You are not assigned the roles required to import an asset. |
Action | You must obtain the required role assignments before you can complete the requested operation. |
Explanation | You are not assigned the roles required to delete the specified asset. |
Action | You must obtain the required role assignments before you can complete the requested operation. |
Explanation | The user is not assigned the roles required to update the specified asset. |
Action | You must obtain the required role assignments before you can complete the requested operation. |
Explanation | You are not assigned the roles required to execute the requested operation on the specified asset. |
Action | You must obtain the required role assignments before you can complete the requested operation. |
Explanation | You are not assigned the roles required to start or stop the specified business-level application. |
Action | You must obtain the required role assignments before you can complete the requested operation. |
Explanation | You are not assigned the roles required to execute the requested operation on the specified resource. |
Action | You must obtain the required role assignments before you can complete the requested operation. |
Explanation | The user is not assigned the roles required to edit the specified asset. |
Action | You must obtain the required role assignments before you can complete the requested operation. |
Explanation | You are not assigned the roles required to edit the specified business-level application. |
Action | You must obtain the required role assignments before you can complete the requested operation. |
Explanation | Informational message indicating that a startBLA command on the specified business-level application has been issued. |
Action | No action is necessary. |
Explanation | Informational message indicating that a stopBLA command on the specified business-level application has been issued. |
Action | No action is necessary. |
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. |
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. |
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. |
Explanation | No value for the required parameter was specified. |
Action | Provide a value for the specified parameter. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
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. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |