CWSAN

CWSAN0001E: Cannot create ApplicationMetadataImpl object from the application manifest {0}.

Explanation

An application manifest, APPLICATION.MF, must contain both Application-SymbolicName and Application-Version headers.

Action

Edit the APPLICATION.MF file to add the missing header or headers.

CWSAN0002E: Invalid header split: {0}.

Explanation

The Deployed-Content header in the deployment manifest, DEPLOYMENT.MF, is not valid.

Action

If you provided this file, correct the contents of the Deployed-Content header.

CWSAN0004E: Cannot create ContentImpl object based on content: {0}.

Explanation

The application content is ambiguous or not valid.

Action

Check and correct the source of the content, if possible.

CWSAN0005E: The deployment content value is not valid, because it does not contain the deployed-version attribute: {0}.

Explanation

A deployment manifest, DEPLOYMENT.MF file, must contain a valid deployed-version header.

Action

If you provided the DEPLOYMENT.MF file, check that it contains a valid deployed-version header.

CWSAN0006E: Cannot create filter for {0}.

Explanation

A service has been declared with a filter expression that is not valid.

Action

Locate and correct the filter expression.

CWSAN0007E: The path {0} is not the location of a valid file or directory.

Explanation

A bundle manifest cannot be extracted because the location is not a valid file or directory.

Action

If you provided this location, check that it is valid and that it exists.

CWSAN0008E: Cannot parse the string because a quotation mark (") is missing: {0}.

Explanation

A bundle manifest cannot be processed because at least one element does not contain a required quotation mark.

Action

Locate and correct the specified bundle manifest.

CWSAN0009E: Cannot parse the version {0} because it does not comply with the OSGi version specification.

Explanation

A manifest header cannot be parsed because it contains a version attribute that is not valid.

Action

Locate and correct the version according to the OSGi version specification.

CWSAN0010E: Cannot parse the version because the version attribute is empty.

Explanation

A manifest header cannot be parsed because it contains an empty version attribute.

Action

Locate and correct the relevant header.

CWSAN0011E: Cannot parse {0} for the exact version.

Explanation

A file that must contain exact versions only, such as a deployment manifest, DEPLOYMENT.MF, contains a range of versions.

Action

Locate and correct the relevant header.

CWSAN0012E: Cannot create temporary output directory for file {0}.

Explanation

The product needs to create a temporary directory but cannot.

Action

Check that storage space exists, and that the product has the necessary permissions to create the directory.

CWSAN0013W: Cannot parse an Import-Service entry {0} in application {1}.

Explanation

An entry in the Import-Service header of the application manifest, APPLICATION.MF, is not valid.

Action

Locate and correct the relevant header.

CWSAN0014W: Cannot parse an Export-Service entry {0} in application {1}.

Explanation

An entry in the Export-Service header of the application manifest, APPLICATION.MF, is not valid.

Action

Locate and correct the relevant header.

CWSAN0015W: Cannot parse an Application-Roles entry {0}.

Explanation

An entry in the Application-Roles header of the application manifest, APPLICATION.MF, is not valid.

Action

Locate and correct the relevant header.

CWSAN0016W: An internal error occurred. Unable to create new security file {0} in the workspace.

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: https://ibm.biz/BdztgV WebSphere Application Server for z/OS Support page: https://ibm.biz/Bdqd4J .

CWSAN0017W: An internal error occurred. Unable to create new security file {0} in the workspace.

Explanation

This exception is unexpected. The cause is not immediately known.

Action

CWSAN0018E: Invalid header split: {0}.

Explanation

The Deployed-Use-Bundle header in the deployment manifest, DEPLOYMENT.MF is not valid.

Action

If you provided this file, correct the contents of the Use-Bundle header.

CWSAN0019E: Invalid header split: {0}.

Explanation

The Provision-Bundle header in the deployment manifest, DEPLOYMENT.MF is not valid.

Action

If you provided this file, correct the contents of the Provision-Bundle header.

CWSAN0020E: Duplicate bundle content was found in EBA {0} for WAB {1} at locations {2} and {3}.

Explanation

Two web application bundle (WAB) files in the enterprise bundle archive (EBA) file have the same bundle symbolic name, version, and Web-ContextPath.

Action

Ensure that the EBA file contains the correct WAB files.

CWSAN0021W: A bundle {0} in the EBA {1} has no bundle manifest.

Explanation

A bundle file in the enterprise bundle archive (EBA) file has no bundle manifest, MANIFEST.MF. This bundle cannot serve web content and might not operate correctly.

Action

Ensure that the bundle file contains a valid bundle manifest file.

CWSAN0022E: An internal error has occurred. There was an error searching for bundles in EBA {0}.

Explanation

This exception is unexpected. The cause is not immediately known.

Action

CWSAN0023W: Cannot read the manifest of the bundle {0} in the EBA {1}.

Explanation

The bundle manifest, MANIFEST.MF, for a bundle in the enterprise bundle archive (EBA) file cannot be read. This bundle cannot serve web content and might not operate correctly.

Action

Ensure that the bundle file contains a valid manifest file.

CWSAN0024E: DeployedService-Import header is not valid: {0}

Explanation

The DeployedService-Import header in a deployment manifest, DEPLOYMENT.MF, is not valid.

Action

If you provided the deployment manifest, correct the contents of the DeployedService-Import header.

CWSAN0025E: The Deployed-Content {0} in the DEPLOYMENT.MF file does not match the Application-Content {1} in the APPLICATION.MF file of the enterprise bundle archive (EBA).

Explanation

The bundles listed in the Deployed-Content header in the DEPLOYMENT.MF file must match the bundles listed in the Application-Content header in the APPLICATION.MF file. The bundle version in the Deployed-Content header in the DEPLOYMENT.MF file must be within the version range for the corresponding bundle in the Application-Content header in the APPLICATION.MF file.

Action

If you provided the deployment manifest, correct the contents of the Deployed-Content header in the DEPLOYMENT.MF file. Ensure that each bundle is listed in both the Deployed-Content header in the DEPLOYMENT.MF file and the Application-Content header in the APPLICATION.MF file, and that the bundle version in the Deployed-Content header in the DEPLOYMENT.MF file is within the version range for the corresponding bundle in the Application-Content header in the APPLICATION.MF file.

CWSAN0026E: The Deployed-Use-Bundle {0} in the DEPLOYMENT.MF file does not match the Use-Bundle {1} in the APPLICATION.MF file of the enterprise bundle archive (EBA).

Explanation

The bundles listed in the Deployed-Use-Bundle header in the DEPLOYMENT.MF file must also be listed in the Use-Bundle header in the APPLICATION.MF file. The bundle version in the Deployed-Use-Bundle header in the DEPLOYMENT.MF file must be within the version range for the corresponding bundle in the Use-Bundle header in the APPLICATION.MF file. The Use-Bundle header in the APPLICATION.MF file can list additional bundles that are not listed in the Deployed-Use-Bundle header of the DEPLOYMENT.MF file.

Action

If you provided the deployment manifest, correct the contents of the Deployed-Use-Bundle header in the DEPLOYMENT.MF file. Ensure that each bundle listed in the Deployed-Use-Bundle header in the DEPLOYMENT.MF file is also listed in the Application-Content header of the APPLICATION.MF file, and that the bundle version in the Deployed-Use-Bundle header of the DEPLOYMENT.MF file is within the version range for the corresponding bundle in the Use-Bundle header in the APPLICATION.MF file.

CWSAN0027E: Invalid header split: {0}.

Explanation

The WAS-Feature-Required header in the deployment manifest, DEPLOYMENT.MF, is not valid.

Action

If you provided the deployment manifest, correct the contents of the WAS-Feature-Required header.

CWSAN0030E: The Application-SymbolicName {0} in the DEPLOYMENT.MF does not match the Application-SymbolicName {1} in APPLICATION.MF.

Explanation

The Application-SymbolicName in the application manifest, APPLICATION.MF, and deployment manifest, DEPLOYMENT.MF, do not match.

Action

Check that the correct file is provided, and ensure the values of Application-SymbolicName in the APPLICATION.MF and DEPLOYMENT.MF are the same.

CWSAN0031E: The Application-Version {0} in the DEPLOYMENT.MF does not match the Application-Version {1} in APPLICATION.MF.

Explanation

The Application-Version in the application manifest, APPLICATION.MF, and deployment manifest, DEPLOYMENT.MF, do not match.

Action

Check that the correct file is provided, and ensure the values of Application-Version in the APPLICATION.MF and DEPLOYMENT.MF are the same.

CWSAN0032E: The Application-SymbolicName {0} and Application-Version {1} in the DEPLOYMENT.MF do not match the Application-SymbolicName {2} and Application-Version {3} in APPLICATION.MF.

Explanation

The Application-SymbolicName and Application-Version in the application manifest, APPLICATION.MF, and deployment manifest, DEPLOYMENT.MF, do not match.

Action

Check that the correct file is provided, and ensure the values of Application-SymbolicName and Application-Version in the APPLICATION.MF and DEPLOYMENT.MF are the same.

CWSAN0033E: An internal error occurred. Could not process application {0}. The byValue expansion directory is missing.

Explanation

This exception is unexpected. The cause is not immediately known.

Action

CWSAN0034E: An internal error occurred. Could not expand bundle {0} because it is not in the expected location.

Explanation

This exception is unexpected. The cause is not immediately known.

Action

CWSAN0035E: An internal error occurred. Could not expand bundle {0}.

Explanation

This exception is unexpected. The cause is not immediately known.

Action

CWSAN0036E: Could not expand bundle {0} for application {2}. Exception {1}

Explanation

The bundle needs to be expanded so that it can be used by another bundle that is referring to it by reference.

Action

Either change the application so that it does not refer to the bundle, or investigate the cause of the exception.

CWSAN0037E: An internal error occurred. Could not install bundle {0} for application root {1}.

Explanation

This exception is unexpected. The cause is not immediately known.

Action

CWSAN0038E: An internal error occurred. Could not create new security file {0} in the workspace.

Explanation

This exception is unexpected. The cause is not immediately known.

Action

CWSAN0039E: An internal error occurred. Could not create new Directory Mapping file {0}.

Explanation

This exception is unexpected. The cause is not immediately known.

Action

CWSAN0040E: An internal error occurred. Could not locate the global bundle cache.

Explanation

This exception is unexpected. The cause is not immediately known.

Action

CWSAN0041E: An internal error occurred. The file for bundle {0} at version {1} in the bundle cache does not appear to be a valid bundle.

Explanation

The internal bundle cache found a file for the bundle, but could not verify the bundle manifest in the file.

Action

Delete the failing bundle from the bundle cache and download it again. If the problem persists then check whether the bundle in the bundle repository is valid.

CWSAN0042E: An error occurred attempting to install a bundle with URL {0}

Explanation

The Apache Aries container could not install the bundle.

Action

Check previous Apache Aries messages for details of the failure.

CWSAN0043E: An error occurred attempting to install a bundle with URL {0}

Explanation

The deployment manifest for the bundle could not be parsed.

Action

Check that the deployment manifest is correctly formatted.

CWSAN0044E: The service import {0} in the deployment for application {1} at version {2} does not conform to the correct syntax.

Explanation

The deployment manifest for the application contains an incorrectly formatted service import.

Action

Check that the application correctly specifies the services that it imports, then try again to deploy the application.

CWSAN0045E: An internal error occurred. By reference bundle {0} is not expanded at location {1}.

Explanation

This exception is unexpected. The cause is not immediately known.

Action

CWSAN0046E: An internal error occurred. Multiple copies of the manifest file {0} were found using case-insensitive matching for the archive {1}.

Explanation

Manifest files in an EBA are case-insensitive. On case-sensitive systems this means that there can be multiple copies of the manifest, which is an error.

Action

Change any artefacts so that they do not contain multiple copies of the manifest file.

CWSAN1000W: When parsing Blueprint xml, the parser ignored an unknown top-level element {0} in the namespace https://www.ibm.com/appserver/schemas/8.0/blueprint/resourcereference.

Explanation

The top-level element in the resource reference namespace must be resource-reference.

Action

Check the Blueprint xml for possible misspellings, or remove the incorrect element.

CWSAN1001E: Not authorized to access the blueprint application

Explanation

Access is denied to a blueprint application for the current user.

Action

Ensure the current user has suitable credentials to access the blueprint application.

CWSAN2001E: An internal error has occurred. Duplicate symbolicName entry found in URL {0}.

Explanation

This exception is unexpected. The cause is not immediately known.

Action

CWSAN2002E: An internal error has occurred. Unexpectedly found a version entry without a preceding symbolicName entry in URL {0}.

Explanation

This exception is unexpected. The cause is not immediately known.

Action

CWSAN2003E: An internal error has occurred. Found a duplicate version entry in URL {0}.

Explanation

This exception is unexpected. The cause is not immediately known.

Action

CWSAN2004E: An internal error has occurred. Found a URL entry without preceding symbolicName and version entries in URL {0}.

Explanation

This exception is unexpected. The cause is not immediately known.

Action

CWSAN2005E: An internal error has occurred. Found an invalid loose config URL {0}.

Explanation

This exception is unexpected. The cause is not immediately known.

Action