Explanation | An IOException or a FileNotFoundException exception occurred. The policy set configuration file was not found or could not be read. |
Action | Verify that the policy set configuration file exists and is not corrupted. |
Explanation | An IOException exception occurred. The system could not write to the policy set configuration file. |
Action | Verify that the hard disk is not full. If you are writing to a new file, verify that directory that has been specified exists. |
Explanation | The system could not find the command that has been requested. |
Action | Verify that the command name is valid and spelled correctly. |
Explanation | The system does not allow you to edit the default policy sets. |
Action | No user action is required. |
Explanation | A policy set cannot be deleted if it is attached to an application. |
Action | Transfer the attachments for this policy set to another policy set or detach this policy set from all applications. |
Explanation | An unexpected exception occurred. |
Action | Examine the wrapped exception to determine the cause of the exception. |
Explanation | The command could not be processed because of an error. |
Action | Verify that the command name and parameters are valid and spelled correctly. |
Explanation | There is no repository context for the cell. |
Action | No user action is required. |
Explanation | The cell contains multiple repository contexts. |
Action | No user action is required. |
Explanation | The resources that have been specified are not valid web service resources. |
Action | Verify that the resources are specified correctly and ensure that the resources are valid web service resources. |
Explanation | Resources cannot be attached to an application if they are already attached. |
Action | Specify resources that are not attached to this application. |
Explanation | The system could not find the servicesIndex.xml file for the application name and module name that has been provided. |
Action | Verify that the application name and module name are specified correctly to ensure that the correct resources are found. |
Explanation | A resource must have a valid value. |
Action | Replace the empty or null value with a valid resource value. |
Explanation | The command is not allowed to write to the specified directory path. |
Action | Verify that the directory path has write permission. |
Explanation | The path name might not be valid or might not contain the correct syntax. |
Action | Verify that the path that has been specified in the message exists on the file system and is readable. |
Explanation | A policy set cannot be deleted if it is attached to a resource. |
Action | Transfer the attachments for this policy set to another policy set or detach this policy set from all resources. |
Explanation | The path name that has been specified is not a valid directory path. |
Action | Verify that the path name is a valid directory structure. |
Explanation | The path name that has been specified does not exist. |
Action | Verify that the path name exists and is spelled correctly. |
Explanation | The policy set directory that has been specified does not contain any sub-directories or files. |
Action | Create the policy set or verify that the policy set directory contains files and directories. |
Explanation | The output file name exists and could not be overwritten. |
Action | Specify a new output file name with a valid directory path. |
Explanation | The output file name does not specify a file in the directory path. |
Action | Specify an output file name that does not contain a directory name in the last part of the directory path. |
Explanation | The output file name does not contain any file separator slashes. It must contain at least one. |
Action | Specify at least one file separator slash in the output file name. |
Explanation | The attributes of the policy types that are listed are not valid and must be corrected. |
Action | Correct the contents and attributes of the policy types that are listed. |
Explanation | A character in the policy set name is not valid. |
Action | Specify valid characters in the policy set name, including alphanumeric characters or a space, hyphen ( - ), or underscore ( _ ) character. |
Explanation | The system created an unexpected error and could not initialize PolicySetManager MBean. |
Action | No user action is required. |
Explanation | The system created an unexpected error and could not access the implementation class for the policy type. |
Action | No user action is required. |
Explanation | The command can only process the policySet parameter or the bindingLocation parameter. Both parameters cannot be used simultaneously. |
Action | Specify a value for the binding location or the policy set name and retry the command. |
Explanation | This command requires that both input arguments are specified. |
Action | Specify values for both of the input arguments for this command. |
Explanation | The policy attachment file could not be found for the application that has been specified. |
Action | Verify that the application name and attachment type were specified correctly. |
Explanation | The client policy attachment file could not be found for the application that has been specified. |
Action | Verify that the application name and attachment type were specified correctly. |
Explanation | The system/trust policy attachment file could not be found. |
Action | Verify that the attachment type was specified correctly and that the attachment file exists and is not corrupted. |
Explanation | The application name must be specified. |
Action | Specify a value for the application name and retry the command invocation. |
Explanation | The attachment type that has been specified is not valid. |
Action | Specify a valid attachment type. |
Explanation | The dynamicClient parameter cannot be specified as true unless the attachment type is client. |
Action | Specify the client value for the attachment type with the dynamic client set to true, or set the value for the dynamic client as false. |
Explanation | The attachment ID that has been specified does not contain a custom binding reference. |
Action | Verify that the application name, attachment ID, and attachment type were specified correctly. |
Explanation | The policy set attachment file could not be created in your configuration. |
Action | Verify that the hard disk is not full and that the application directory exists. |
Explanation | The policy set attachment could not be created. The system created an error and could not retrieve the policy set ID. |
Action | Verify that the hard disk is not full and that the application directory exists. |
Explanation | The application name could not be determined from the file path for the attachment file. |
Action | Verify that the application directory exists and is valid. |
Explanation | The system could not find the policy attachment files for the application. |
Action | Verify that the application name was specified correctly. |
Explanation | An implementation class was not found for the policy type that has been specified. |
Action | Verify that the policy type was specified correctly. |
Explanation | If the bindingName parameter or the remove parameter is not specified, then you must specify a value for the attributes parameter. |
Action | Specify a value for either the bindingName or remove parameter, or specify a value for the attributes parameter. |
Explanation | The system created an error and could not edit the attributes for the policy type. |
Action | Check the log file for additional information, and verify that the attributes are valid. |
Explanation | The system created an error and could not edit the custom binding reference for the attachment. |
Action | Check the log file for additional error messages. |
Explanation | The system created an error and could not create or update the binding file. |
Action | Check the log file for additional information. |
Explanation | The bindingLocation parameter is missing a required property. |
Action | Verify that you have included the correct bindingLocation properties and that the properties are spelled correctly. |
Explanation | The application name is required with this attachment type. |
Action | Specify an application name and retry the command invocation. |
Explanation | The cell level binding cannot be removed. |
Action | No user action is required. |
Explanation | The policy type must be specified to remove a server-level binding. |
Action | Specify the policy type name and retry the command invocation. |
Explanation | The attachment ID that has been specified does not reference a custom binding. |
Action | Verify that the correct attachment ID is specified. |
Explanation | An error was created and the binding attributes for the specified policy type were not set. |
Action | Check the log file for additional information. |
Explanation | The binding could not be found. |
Action | Verify that the correct binding name has been specified and that the specified attachment references a valid binding. |
Explanation | The binding reference was removed from the attachment file. The binding file could not be found. |
Action | Verify that the correct binding name has been specified and that the attachment references a valid binding. |
Explanation | The policy set could not be found. |
Action | Verify that the correct policy set name has been specified. |
Explanation | The policy type could not be found. |
Action | Verify that the correct policy type name has been specified. |
Explanation | The default policy type could not be found. |
Action | Verify that the correct policy type name has been specified. |
Explanation | A policy set with the name that has been specified already exists. |
Action | Specify a new policy set name. |
Explanation | A policy type with the name that has been specified already exists. |
Action | Specify a new policy type name. |
Explanation | The policy attachment file that has been specified already exists. |
Action | No user action is required. |
Explanation | The client policy attachment file already exists. |
Action | No user action is required. |
Explanation | The application could not be found. |
Action | Verify that the correct application name has been specified. |
Explanation | The binding file could not be found. |
Action | Verify that the correct binding name has been specified. |
Explanation | The default cell-level binding file could not be found. |
Action | Verify that the correct policy type has been specified. |
Explanation | The default server-level binding file could not be found. |
Action | Verify that the correct policy type, node, and server have been specified. |
Explanation | The bindings.xml file could not be found. |
Action | Verify that the correct application name and policy type have been specified. |
Explanation | The policy set or policy attachment file name is null or empty. |
Action | Specify a valid file name. |
Explanation | A required parameter is null or empty. |
Action | Verify the command syntax and retry the command invocation. |
Explanation | A required parameter is null or empty. |
Action | Verify the command syntax and retry the command invocation. |
Explanation | The attachment ID that has been specified could not be found. |
Action | Verify that the application name, attachment ID, and attachment type are specified correctly. |
Explanation | No attachments were found for the application and attachment type that have been specified. |
Action | Verify that the application name and attachment type are specified correctly. |
Explanation | Duplicate attachment IDs were found for the application and attachment type that have been specified. |
Action | No user action is required. |
Explanation | The resource that has been specified already exists in the attachment. |
Action | Verify that the resource was specified correctly. If it is correct, no user action is required. |
Explanation | The resource does not exist in the attachment that has been specified. |
Action | Verify that the resource and the attachment ID were specified correctly. |
Explanation | The system cannot write to the policy set or policy set attachment because it is read only. |
Action | No user action is required. |
Explanation | The policy set type that has been specified is not a valid value. |
Action | Specify a valid value for the policy set type for the command invocation. |
Explanation | The attribute that has been specified is not a supported attribute for a policy set. |
Action | Specify a supported attribute for the command invocation. |
Explanation | The policy set name cannot be modified when updating a policy set. |
Action | Correct the attributes on the command invocation. |
Explanation | The policy type cannot be modified when updating policy type attributes. |
Action | Correct the attributes on the command invocation. |
Explanation | The policy set file name is not valid. |
Action | Verify that the policy set name is valid, and check the log file for additional information. |
Explanation | The policy type could not be found in the policy set. |
Action | Verify that the policy set name and the policy type name are correct. |
Explanation | The policy type exists in the policy set that has been specified. |
Action | Verify that the policy set name and the policy type name are correct. If they are correct, then no user action is required. |
Explanation | A required policy set attribute is missing from the policy set file. |
Action | Verify that the policy set file has not been corrupted. If the policy set file has been corrupted, you might need to recreate the file. |
Explanation | The command created an unexpected exception. |
Action | Examine the wrapped exception to determine the cause of the problem. |
Explanation | The binding configuration file that has been specified exists for the asset. |
Action | Verify that the binding name is correct. |
Explanation | The binding file could not be found. |
Action | Verify that the correct binding name has been specified. |
Explanation | The system/trust policy attachment file exists in your configuration. |
Action | No user action is required. |
Explanation | The policy set type is not a known system type. |
Action | Verify the contents of the policy set files. |
Explanation | The ending parenthesis or brace could not be found. |
Action | Verify that the variable definition syntax is correct and delimited by the percentage (%) character. |
Explanation | The specified variable occurs recursively. |
Action | Verify that the variables in the variable definition are correct. |
Explanation | The specified variable is not defined. |
Action | Verify that the variables in the variable definition are correct. |
Explanation | The repository cannot be initialized. |
Action | No user action is required. |
Explanation | The variable map cannot be initialized. |
Action | No user action is required. |
Explanation | The specified implementation class could not be loaded. |
Action | This is an internal error, but processing continues with the remaining policy type implementation classes. |
Explanation | The node could not be found. |
Action | Verify that the correct node name has been specified. |
Explanation | The server could not be found. |
Action | Verify that the correct server name has been specified. |
Explanation | The application file that has been specified could not be found. |
Action | Verify that the application has been installed correctly. |
Explanation | The compressed file specified must contain files. |
Action | Verify that the correct compressed file was specified and that it contains files. |
Explanation | The compressed file specified must contain directory path information. |
Action | Verify that the compressed file was created with the exportPolicySet command. |
Explanation | The compressed file does not contain the expected directory entries. |
Action | Verify that the compressed file was created with the exportPolicySet or exportBinding command. |
Explanation | The compressed file contains a policy set that is already defined. |
Action | Import a policy set that is not already defined on your system. |
Explanation | The compressed file contains multiple policy sets. |
Action | Import only one policy set from a compressed file. |
Explanation | The compressed file contains a policy which is not defined on this system. |
Action | Use the policyType parameter with the addPolicyType command to create the missing policy on this system. |
Explanation | The file name does not specify a file in the directory path. |
Action | Verify that a file name is specified in the last section of the directory path. |
Explanation | The compressed file does not contain a policy set. |
Action | Verify that the compressed file was created with the exportPolicySet command. |
Explanation | If you specify an asterisk (*) for the value of the attachment ID, then you must specify values for the bindingName and remove parameters. This command deletes the custom binding or removes the policy type from the custom binding specified by the bindingName parameter. |
Action | Specify a value for the bindingName parameter and set the remove parameter as true to delete the custom binding. If you do not want to delete the custom binding or the policy type from the custom binding, specify a different value for the attachment ID. |
Explanation | A binding cannot be deleted if it is referenced by an attachment. |
Action | Remove the binding from all attachments before attempting to delete the binding. |
Explanation | The system could not find the client policy attachment file for the bus and WSN service. |
Action | Verify that the bus name and WSN service name were specified correctly. |
Explanation | The system could not find the servicesIndex.xml file for the bus name and WSN service name that has been provided. |
Action | Verify that the bus name and WSN service name are specified correctly to ensure that the correct resources are found. |
Explanation | The bus name and WSN service name can only be specified for the client attachment type. |
Action | Correct the value for the attachmentType parameter and retry the command invocation. |
Explanation | The bus name and WSN service name must be specified. |
Action | Specify a value for the bus name and WSN service name and retry the command invocation. |
Explanation | Resources cannot be attached to a WSN service if they are already attached. |
Action | Specify resources that are not attached to this WSN service. |
Explanation | The WSN service could not be determined from the file path for the attachment file. |
Action | Verify that the WSN service directory exists and is valid. |
Explanation | The specified parameter must contain valid values. |
Action | Verify that the parameter contains values accepted by the command. |
Explanation | WSN service client attachments cannot contain module names in the resource. |
Action | Remove the module name from the resource and retry the command invocation. |
Explanation | WSReliableMessaging cannot be attached to an endpoint or operation within a web service. |
Action | Either attach the policy set at a higher level, or remove WSReliableMessaging from the policy set and retry the command invocation. |
Explanation | A policy set attachment for a WSN service client is not valid at an endpoint or operation layer within a web service. |
Action | Attach the policy set for a WSN service client at a higher level within the web service. |
Explanation | The bus could not be found. |
Action | Verify that the correct bus name has been specified. |
Explanation | The configuration service cannot be initialized. |
Action | No user action is required. |
Explanation | The current user role does not have access to the resource. |
Action | Retry the command with a higher level user. |
Explanation | The cell name cannot be found. |
Action | No user action is required. |
Explanation | Only one of the parameters can be specified. |
Action | Retry the command with the correct parameters. |
Explanation | The system could not locate the templates repository context. |
Action | Verify that the templates context exists. |
Explanation | The binding that has been specified does not match the attachment type or the binding type. |
Action | Specify a different binding name or a different attachment or binding type. |
Explanation | The binding directory that has been specified does not contain any sub-directories or files. |
Action | Create the binding or verify that the binding directory contains files and directories. |
Explanation | A binding with the name that has been specified already exists. |
Action | Specify a new binding name. |
Explanation | The compressed file does not contain a binding. |
Action | Verify that the compressed file was created with the exportBinding command. |
Explanation | The compressed file contains multiple bindings. |
Action | Import only one binding from a compressed file. |
Explanation | The compressed file contains a binding that is already defined. |
Action | Import a binding that is not already defined on your system. |
Explanation | The default bindings file that has been specified already exists. |
Action | No user action is required. |
Explanation | The command can only process the domainName parameter or the bindingLocation parameter. Both parameters cannot be used simultaneously. |
Action | Specify a value for the binding location or the domain name and retry the command. |
Explanation | The default bindings for provider or client cannot be set to the empty string for the global security domain. |
Action | Specify a valid value for the provider or client default binding and retry the command. |
Explanation | A binding cannot be deleted if it is referenced by an attachment. |
Action | Remove the binding from all attachments before attempting to delete the binding. |
Explanation | A binding cannot be deleted if it is a default binding. |
Action | Change the default binding for the specified domains before attempting to delete the binding. |
Explanation | A binding cannot be deleted if it is a default binding. |
Action | Change the default binding for the specified servers before attempting to delete the binding. |
Explanation | Either httpGet or wsMex must be specified. |
Action | Retry the command with either httpGet or wsMex. |
Explanation | The application specified did not have a WSPolicy control file. |
Action | Check the application name and verify it is correct. |
Explanation | The control file that has been specified exists. |
Action | No user action is required. |
Explanation | WSPolicy is not valid for at endpoint or operation layer within a web service. |
Action | Set the WSPolicy settings at a higher level within the web service. |
Explanation | Policy sharing requires a policy set attachment to share. |
Action | First attach a policy set then retry the command. |
Explanation | The resource does not contain any WSPolicy settings. |
Action | Retry the command specifying a different resource. |
Explanation | The imported policy set is not of the same type as verified in the command. |
Action | Retry the command specifying a policy set of the correct type. |
Explanation | The ability to get and set bindings by specifying the node and server properties in the bindingLocation parameter is deprecated. |
Action | Specify the bindingName parameter and an empty bindingLocation parameter and retry the command. |
Explanation | Multiple resources cannot be specified or used when provider policy set is enabled. |
Action | Specify a different resource or disable provider policy set. |
Explanation | Adding multiple resources as well as replacing resources is not valid when provider policy set is enabled. |
Action | Disable provider policy set to perform this action. |
Explanation | The application or provider attachment type must must be specified when the systemType property is specified. |
Action | Correct the value for the attachmentType parameter and retry the command invocation. |
Explanation | The property value that has been specified is not valid. |
Action | Specify a valid value for the property and retry the command invocation. |
Explanation | The policyset found within attachment file of application is not defined on the server yet. |
Action | Define the policyset on the server then redeploy the application. |
Explanation | Prior messages detail the cause of this failure. Typically, the error conditions include wrong server and node names that are specified as module targets during installation. |
Action | Read the error messages and rectify the problem. |
Explanation | An unexpected error occurred when saving the configuration documents of the application to the WebSphere repository during application installation. This message is preceded by a more detailed message regarding the failure. |
Action | Refer to the previous messages in the log file for a failure description. If no messages are displayed, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The specified attribute cannot be modified. |
Action | Correct the attributes on the command invocation. |
Explanation | The domain name value that has been specified is not valid. |
Action | Specify a valid value for the domain name and retry the command invocation. |
Explanation | The parameter is not valid at the application level of a Web Service. |
Action | Specify a lower level within the Web Service and retry the command invocation. |
Explanation | The domain of the binding is different than the domain of the attachment resource. |
Action | Specify a different binding for the attachment and retry the command invocation. |
Explanation | Provider policy set must be used with general bindings. |
Action | Either remove the provider policy set from the attachment, or assign general bindings. |
Explanation | The version that has been specified is not valid. |
Action | Specify a valid value for the version and retry the command invocation. |
Explanation | The version of the application does not allow general bindings. |
Action | Use a custom binding for the application attachment. |
Explanation | The imported binding is not of the same type as verified in the command. |
Action | Retry the command specifying a binding of the correct type. |
Explanation | The binding type that has been specified is not a valid value. |
Action | Specify a valid value for the binding type for the command invocation. |
Explanation | Only WSSecurity and WSAddressing are valid policy types for WSMex. |
Action | Specify a policy set with valid policy types and retry the command invocation. |
Explanation | The binding definition file for the binding that has been specified exists for the asset. |
Action | Verify that the binding name is correct. |
Explanation | The domain of the binding is different than the domain of the attachment resource. |
Action | Specify a valid value for the domain name and retry the command invocation. |
Explanation | The bindings for the application cannot be upgraded if the application is installed on a server that is not at the latest version. |
Action | Verify that the application name is correct. |
Explanation | The composition unit could not be found. |
Action | Verify that the correct composition unit name has been specified. |
Explanation | Resources cannot be attached to an asset if they are already attached. |
Action | Specify resources that are not attached to this asset. |
Explanation | The command can only process one of the specified parameters. Both parameters cannot be used simultaneously. |
Action | Specify a value for one of the parameters and retry the command. |
Explanation | The system could not find the servicesIndex.xml file for the asset name that has been provided. |
Action | Verify that the asset name is specified correctly to ensure that the correct resources are found. |
Explanation | The system could not find the policy attachment files for the asset. |
Action | Verify that the asset name was specified correctly. |
Explanation | The asset name could not be determined from the file path for the attachment file. |
Action | Verify that the asset directory exists and is valid. |
Explanation | Attachments for the specified asset cannot contain module names in the resource. |
Action | Remove the module name from the resource and retry the command invocation. |