Explanation | The client is configured to use the policy of the provider service specified in the message using an HTTP GET request, but the request resulted in an exception. |
Action | Ensure that the endpoint address is correct and that the endpoint supports HTTP GET. The exception in the message may contain information to help diagnose the problem. |
Explanation | The client is configured to use the policy of the provider service specified in the message using a WS-MetadataExchange request, but the request resulted in an exception. |
Action | Ensure that the endpoint address is correct, that the endpoint supports WS-MetadataExchange, and that the endpoint and client have compatible security configurations. The exception in the message may contain information to help diagnose the problem. |
Explanation | The client is configured to use the policy of the provider service specified in the message using a WS-MetadataExchange GetMetadata request, but the provider endpoint does not support this request. |
Action | Ensure that the provider service is available and that it supports WS-MetadataExchange Version 1.1. If the provider does not support WS-MetadataExchange, an alternative is to configure the client to acquire the provider policy using an HTTP GET request. |
Explanation | The client is configured to use the policy of the provider service specified in the message using a WS-MetadataExchange GetMetadata request, with the WSDL inlined in the response itself. The response that the client received is not in the expected format. |
Action | Ensure that the provider service returns its metadata inlined in the GetMetadata response. If this is not possible, an alternative is to configure the client to acquire the provider policy using an HTTP GET request. |
Explanation | The client has successfully acquired the WSDL of the service provider. The WSDL file might not be valid, or might be in WSDL 1.0 format. |
Action | Check that the WSDL of the service provider is valid and in WSDL 1.1 format. |
Explanation | The client has successfully acquired the WSDL of the service provider. The received WSDL is not valid for the client service because it does not correspond to the structure (operation, service, ports) that the client expects. |
Action | Contact the administrator of the provider policy service to correct the policy in the WSDL of the provider. |
Explanation | The client has successfully acquired the WSDL of the service provider, but there is no policy information in that WSDL. The client assumes that there is no provider policy to apply to the client service. |
Action | If the client must acquire policy information from the WSDL of the provider service, ensure that the provider service is configured to publish policy configuration in its WSDL. |
Explanation | The client is configured to acquire the policy of the provider service using a WS-MetadataExchange GetMetadata request with message-level security, but the policy set specified to secure the request does not exist. |
Action | Reconfigure the client and specify a valid policy set for the WS-Metadata request. |
Explanation | The client is configured to acquire the policy of the provider service using a WS-MetadataExchange GetMetadata request with message-level security, but the policy set binding specified to secure the request does not exist. |
Action | Reconfigure the client and specify a valid policy set binding for the WS-Metadata request. |
Explanation | The client is configured to acquire the policy of the provider service using a WS-MetadataExchange GetMetadata request with message-level security, but either the policy set or the binding specified to secure the request is not valid. |
Action | Reconfigure the client and specify a valid policy set and binding for the WS-Metadata request. |
Explanation | The client is configured to acquire the policy of the provider service using a WS-MetadataExchange GetMetadata request with message-level security, but the policy set specified to secure the request does not contain any security policy. |
Action | If you require message-level security for the WS-MetadataExchange request, reconfigure the client and specify a policy set that contains security policy for the WS-MetadataExchange request. |
Explanation | The client cannot read the configuration file that defines how policy is configured. Usually, the application server administration or Rational Application Development tools generate this file automatically. |
Action | If the configuration file was edited directly, delete the file, use the administrative console or command line interfaces to configure the policy settings, then retry the application. If the problem is not resolved, or if the configuration file was not edited directly, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The client is configured to use the policy of the provider service specified in the message. The client has successfully acquired the WSDL of the provider, but the syntax of the policy in the WSDL does not conform to the WS-Policy specification. |
Action | If the application is programmed to refresh the provider policy, the refresh might resolve the problem. Alternatively, restart the client to refresh the provider policy that the client holds. If this does not resolve the problem, either configure the client so that it does not use the provider policy, or contact the administrator of the provider policy service to correct the policy in the WSDL of the provider. |
Explanation | The client is configured to use the policy of the provider service specified in the message. The client has successfully acquired the WSDL of the provider, but the WSDL contains a policy reference that the run time cannot resolve. |
Action | If the application is programmed to refresh the provider policy, the refresh might resolve the problem. Alternatively, restart the client to refresh the provider policy that the client holds. If this does not resolve the problem, either configure the client so that it does not use the provider policy, or contact the administrator of the provider policy service to correct the policy in the WSDL of the provider so that the policy does not contain the policy reference. |
Explanation | The client is configured to use the policy of the provider service specified in the message. The client run time cannot resolve all the imported parts of the WSDL of the provider. |
Action | If the application is programmed to refresh the provider policy, the refresh might resolve the problem. Alternatively, restart the client to refresh the provider policy that the client holds. If this does not resolve the problem, either configure the client so that it does not use the provider policy, or contact the administrator of the provider policy service to correct the policy in the WSDL of the provider. |
Explanation | The client is configured to use the policy of the provider service specified in the message. The client has successfully acquired the WSDL of the provider, but the client cannot support all of the policy assertions in that WSDL. |
Action | If the application is programmed to refresh the provider policy, the refresh might resolve the problem. Alternatively, restart the client to refresh the provider policy that the client holds. If this does not resolve the problem, consider whether the requirements of the provider side policy can be changed. If this is not possible, the client cannot communicate with the provider. |
Explanation | The client is configured to use the client policy set and the policy of the provider service specified in the message. The client has successfully acquired the WSDL of the provider, but the client cannot support all of the policy assertions in that WSDL, and the provider cannot support all of the policy assertions from the client policy set. |
Action | If the application is programmed to refresh the provider policy, the refresh might resolve the problem. Alternatively, restart the client to refresh the provider policy that the client holds. If this does not resolve the problem, consider whether the requirements of the provider side policy and the client policy set can be changed. If this is not possible, the client cannot communicate with the provider. |
Explanation | The client is configured to use the policy of the provider service specified in the message. The client has successfully acquired the WSDL of the provider, but the namespace of the policy in the WSDL does not match the namespace that the application server supports. |
Action | If the application is programmed to refresh the provider policy, the refresh might resolve the problem. Alternatively, restart the client to refresh the provider policy that the client holds. If this does not resolve the problem, contact the administrator of the provider service to ensure that the policy in the WSDL of the provider is at the correct version. |
Explanation | The client has successfully acquired the WSDL of the provider, but that WSDL does not contain any WS-Policy policy assertions. The client run time has tried to use the client policy set, but it cannot process this policy. |
Action | If the policy set file was edited directly, delete the file, use the administrative console or command line interfaces to configure the policy settings, then retry the application. If the problem is not resolved, or if the policy set file was not edited directly, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The client is configured to acquire its policy dynamically from the provider using ws-policy exchange. The client has successfully acquired the WSDL of the provider, but that WSDL specifies different effective policies for one or more operations. The client runtime cannot establish the correct policy to use for the request because the runtime is unable to determine the operation name of the request at runtime. This is likely to be because the client is a JAX-WS DII client. |
Action | The provider policy must be the same for each of its operations of the service. If the application is programmed to refresh the provider policy, the refresh might resolve the problem. Alternatively, restart the client to refresh the provider policy that the client has obtained. If this does not resolve the problem, consider whether the requirements of the provider side policy can be changed so that the policy is the same for all the operations of the service. If this is not possible, the client will not be able to establish an effective policy with the provider using dynamic ws-policy exchange so the policy of the client will need to be configured statically. |
Explanation | The client cannot calculate an effective policy using the policies of the client and the provider because there is a problem transforming the client policy set. |
Action | Examine the accompanying error messages to resolve the problem. |
Explanation | The client cannot calculate an effective policy using the policy of the service provider because there is a problem with the client binding information. |
Action | Examine the accompanying error messages to resolve the problem. |
Explanation | The client cannot establish the policy associated with the client because there is a problem with the client binding information. |
Action | Examine the accompanying error messages to resolve the problem. |
Explanation | The service provider specified in the message is configured to accept WS-MetadataExchange GetMetadata requests with message-level security from clients targeted at that service, but the policy set specified to secure these requests does not exist. |
Action | Reconfigure the service provider and specify a valid policy set for the WS-MetadataExchange request. |
Explanation | The service provider specified in the message is configured to accept WS-MetadataExchange GetMetadata requests with message-level security from clients targeted at that service, but the policy set binding specified to secure these requests does not exist. |
Action | Reconfigure the service provider and specify a valid policy set binding for the WS-MetadataExchange request. |
Explanation | The service provider specified in the message is configured to accept WS-MetadataExchange GetMetadata requests with message-level security from clients targeted at that service, but the policy set or binding specified to secure these requests is not valid. |
Action | Reconfigure the service provider and specify a valid policy set or binding for the WS-MetadataExchange request. |
Explanation | The service provider specified in the message is configured to accept WS-MetadataExchange GetMetadata requests with message-level security from clients targeted at that service, but the policy set or binding specified to secure these requests does not contain any security policy. |
Action | If you require message-level security for the WS-MetadataExchange request, reconfigure the service provider and specify a policy set that contains security policy for the WS-MetadataExchange request. |
Explanation | The service provider cannot read the configuration file that defines how policy is shared. Usually, the application server administration or Rational Application Development tools generate this file automatically. |
Action | If the configuration file was edited directly, delete the file, use the administrative console or command line interfaces to configure the policy settings, then retry the application. If the problem is not resolved, or if the configuration file was not edited directly, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The policy of the provider service is not expressed in WSDL that complies with the WS-PolicyAttachments specification. It is possible to configure policy in a policy set that cannot be published using WS-Policy policy attachments in WSDL. |
Action | Refer to the documentation for the application server. |
Explanation | The service provider cannot share its policy because there is a problem transforming the provider policy configuration. |
Action | Contact the administrator of the provider policy service to correct the policy in the WSDL of the provider. |
Explanation | The service provider cannot share its policy because there is a problem with the format of the policy configuration. |
Action | Contact the administrator of the provider policy service to correct the policy in the WSDL of the provider. |
Explanation | There was an unexpected error when the application server processed a WS-MetadataExchange GetMetadata request. |
Action | Examine the accompanying error messages to resolve the problem. If you cannot resolve the problem, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The service provider cannot share its policy because of an internal error. |
Action | Examine the accompanying error messages to resolve the problem. If you cannot resolve the problem, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | There was an unexpected error when the application server loaded the class that acquires policy from the provider. |
Action | If the file was edited directly, delete the file, use the administrative console or command line interfaces to configure the policy settings, then retry the application. If the problem is not resolved, or if the file was not edited directly, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | There was an unexpected error when the application server processed WS-Policy information. |
Action | See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |