Skip Headers
Oracle® Fusion Middleware Error Messages Reference
11g Release 1 (11.1.1.5.0)

Part Number E10113-08
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

96 WSM-00004 to WSM-09024

WSM-00004: WS-Security Exception : {0}
Cause: The system encountered a generic failure in security.
Action: Contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Security

WSM-00005: Error in sending the request.
Cause: Failure occurred while trying to send the request message, possibly due to a failure in security code.
Action: Retry the operation for a maximum of 3 times. If the problem persists, contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Security

WSM-00006: Error in receiving the request: {0}.
Cause: Failure occurred while processing the request message, possibly due to a failure in security checks.
Action: Refer to the policy for the expected nature of the request message and retry the operation.

Level: 1

Type: ERROR

Impact: Security

WSM-00007: JPS exception
Cause: The error was most likely due to an invalid JPS configuration.
Action: Correct the JPS configuration and retry the operation.

Level: 1

Type: ERROR

Impact: Security

WSM-00008: Web service authentication failed.
Cause: Authentication failed at the server end.
Action: Resend valid credentials.

Level: 1

Type: ERROR

Impact: Security

WSM-00009: The password policy does not match. Expected: {0}, Received:{1}.
Cause: The expected and actual password types did not match.
Action: Refer to the policy to determine the allowed password type value.

Level: 1

Type: ERROR

Impact: Security

WSM-00010: Message rejected as the nonce element in the WS-Security header is missing.
Cause: Nonce was required according to policy requirements, but was not found.
Action: Resend the request with valid value of nonce.

Level: 1

Type: ERROR

Impact: Security

WSM-00011: The wsu:Created element is required.
Cause: The Created element was required, but was not found.
Action: Resend the request with valid value of the Created element with the UTC timestamp of the instance in which the request was created.

Level: 1

Type: ERROR

Impact: Security

WSM-00012: The password is ignored, as it is not required by the policy.
Cause: The password was sent in the <UsernameToken>, when it was not required.
Action: The password type prescribed by the policy is None, so password should not be sent.

Level: 1

Type: WARNING

Impact: Security

WSM-00013: The nonce is ignored, as it is not required by the policy.
Cause: The nonce was sent in the <UsernameToken>, when it was not required.
Action: Because the policy does not require the nonce, it should not be sent.

Level: 1

Type: WARNING

Impact: Security

WSM-00014: The creation timestamp is ignored, as it is not required by the policy.
Cause: The creation timestamp was sent in the <UsernameToken>, when it was not required.
Action: Because the policy does not require the creation timestamp inside <UsernameToken>, it should not be sent.

Level: 1

Type: WARNING

Impact: Security

WSM-00015: The user name is missing.
Cause: Username was expected but was not found.
Action: Either the username element or the username inside the username element is missing. Resend the request with a valid username.

Level: 1

Type: ERROR

Impact: Security

WSM-00016: The username/password credentials or certificates {0} are missing.
Cause: It is possible that username/password or certificate is missing.
Action: Resend valid credentials.

Level: 1

Type: ERROR

Impact: Security

WSM-00017: The <bindings> element for {0}:{1} is missing.
Cause: It is likely that the bindings element is missing inside policy.
Action: Re-create the policy with valid bindings.

Level: 1

Type: ERROR

Impact: Configuration

WSM-00018: There is more than one security header with the same role {0}.
Cause: More than one security header was found with the same role associated.
Action: Refer to the WS-Security 1.0 or 1.1 specifications. Do not send more than one security header having the same role.

Level: 1

Type: ERROR

Impact: Security

WSM-00019: The version of SOAP used is not supported: {0}.
Cause: An envelope was obtained that conforms to an unsupported version of SOAP.
Action: Use a supported version. SOAP 1.1 and 1.2 are supported.

Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00020: Error sending the response.
Cause: A failure occurred while building the response.
Action: Retry a maximum of three times. If the retry attempts fail, contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Other

WSM-00021: Error receiving the response.
Cause: A failure occurred while processing the response, most likely due to a failure in the security check.
Action: Retry sending the response to the client.

Level: 1

Type: ERROR

Impact: Security

WSM-00022: Error sending a fault.
Cause: A failure occurred while sending the fault.
Action: Retry for a maximum of three times. If the retry attempts fail, contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Other

WSM-00023: Error receiving a fault.
Cause: A failure occurred while processing the fault, most likely due to a failure in the security check.
Action: Retry the operation. If the problem persists, contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Security

WSM-00024: The SAML token is missing from the security header. Ensure that there is a SAML token policy attached on the client side. Tokens found in the security header are :- {0}.
Cause: The SAML assertion that was expected inside the security header was not found.
Action: Insert valid SAML assertions and resend the request.

Level: 1

Type: ERROR

Impact: Security

WSM-00025: SAML token verification failure.
Cause: SAML token verification failed.
Action: Check the validity period of the SAML assertion using Conditions, or determine whether the assertion must be signed. Ensure that the SAML token conforms to the requirements of the SAML 1.0 specification.

Level: 1

Type: ERROR

Impact: Security

WSM-00026: The SAML token cannot be added to the security header.
Cause: A failure occurred while adding the SAML token to the security header.
Action: Check the log file for a possible cause.

Level: 1

Type: ERROR

Impact: Other

WSM-00027: The configuration parameter {0} contains an invalid value [{1}].
Cause: The configuration settings were invalid.
Action: Check the configuration and retry the operation.

Level: 1

Type: ERROR

Impact: Configuration

WSM-00028: Failure in getting user credentials from client.
Cause: Failure occurred while extracting user credentials from the client side.
Action: Check Keystore/Username and the Password/CSF configuration.

Level: 1

Type: ERROR

Impact: Configuration

WSM-00029: The algorithms used to encrypt the data do not match those specified in the policy. : Expected : {0}, Actual : {1}.
Cause: The expected and actual data encryption algorithms did not match.
Action: Check the policy to determine the permitted values for the data encryption algorithm.

Level: 1

Type: ERROR

Impact: Security

WSM-00030: The encryption method key wrap algorithms do not match : Expected : {0}, Actual : {1}.
Cause: The expected and actual key wrap encryption algorithms did not match.
Action: Check the policy to determine the permitted values for the key wrap encryption algorithm. In addition, refer to WS-Security Policy 1.1 for a list of allowed values.

Level: 1

Type: ERROR

Impact: Security

WSM-00031: The digest algorithms do not match.
Cause: The actual digest algorithms for the signature did not match the expected algorithms.
Action: Check the policy to determine the permitted values for the signature digest algorithms.

Level: 1

Type: ERROR

Impact: Security

WSM-00033: The encrypted message elements or parts do not comply with the policy. The following headers/elements (<name space: local name>) or attachments (<attachment ID: attachment type>) must be encrypted:- {0}
Cause: Parts or elements to be encrypted according to policy were different from those in the SOAP message.
Action: Refer to the policy and WS-Security specifications to ensure that all encryption requirements mandated by the policy and the specifications are met.

Level: 1

Type: ERROR

Impact: Security

WSM-00034: Error in Encryption reference mechanism compliance : Expected : {0} , Actual : {1}. Ensure that a compatible policy is attached at the client side.
Cause: The expected and actual encryption reference mechanisms did not match.
Action: Check the policy to determine the permitted values for the encryption reference mechanism.

Level: 1

Type: ERROR

Impact: Security

WSM-00035: Error in Signature reference mechanism compliance : Expected : {0} , Actual : {1}. Ensure that a compatible policy is attached at the client side.
Cause: The expected and actual signature reference mechanisms did not match.
Action: Check the policy to determine the allowed value of the signature reference mechanism.

Level: 1

Type: ERROR

Impact: Security

WSM-00036: The signed message elements or parts do not comply with the policy. The following headers/elements (<name space: local name>) or attachments (<attachment ID: attachment type>) must be signed:- {0}
Cause: Parts or elements to be signed according to policy were different from those in the soap message.
Action: Refer to the policy and WS-Security specifications to make sure that all the signature requirements mandated by the policy and the specifications are met.

Level: 1

Type: ERROR

Impact: Security

WSM-00037: Error in signature confirmation compliance.
Cause: The error could have occurred because the response signature confirmation element was not signed.
Action: Check that all the signature confirmations in the response are signed and referenced in the response signature.

Level: 1

Type: ERROR

Impact: Security

WSM-00039: Timestamp element is not found in the message in accordance with policy.
Cause: Timestamp policy compliance failed.
Action: Check the policy to find out whether a timestamp is required. If the policy indicates that the timestamp is not required, it should not be present; if timestamp is required, it should be present.

Level: 1

Type: ERROR

Impact: Security

WSM-00042: The request must be made over SSL.
Cause: The request was expected to be sent over SSL, but it was not.
Action: Check the SSL port and send the request over SSL.

Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00043: No peer certificates are present from the HTTP request.
Cause: A certificate in the trust chain is missing.
Action: Ensure that the complete certificate chain is propagated in the request, if certificates signed by CA are used.

Level: 1

Type: ERROR

Impact: Security

WSM-00044: The HTTP authorization header is missing.
Cause: The authorization Header was not found.
Action: For basic over HTTP authentication, ensure that the request HTTP headers contain an authorization header.

Level: 1

Type: ERROR

Impact: Security

WSM-00045: HTTP authentication/authorization failure.
Cause: Failure occurred in basic authentication.
Action: Use the appropriate Base64 encoded combination of a valid username and password.

Level: 1

Type: ERROR

Impact: Security

WSM-00046: Error in advertisement of WS-Policy.
Cause: An error occurred while advertising ORAWSDL to WS-Policy.
Action: Contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Other

WSM-00047: Invalid key referencing mechanism: {0}.
Cause: The sign or encryption key reference mechanism used was invalid.
Action: Valid supported values are direct, issuerserial, SKI, or thumbprint.

Level: 1

Type: ERROR

Impact: Configuration

WSM-00048: The signature confirmation value is invalid. Expected : {0}, Actual : {1}.
Cause: Signature confirmation sent in the response was invalid.
Action: See the WS-Security 1.1 specification for the correct @Value of SignatureConfirmation.

Level: 1

Type: ERROR

Impact: Security

WSM-00049: The expected {0} signature is missing in the request messsage.
Cause: No signature (message, or endorsing) was found in the request to confirm.
Action: Resend the request with at least one <Signature>.

Level: 1

Type: WARNING

Impact: Security

WSM-00050: Cannot obtain security token reference.
Cause: The message was not signed or encrypted properly.
Action: Check the <ds:Reference> section of the message.

Level: 1

Type: ERROR

Impact: Other

WSM-00051: The encrypted data or key cannot be obtained.
Cause: The referenced encrypted object could not be found.
Action: Ensure that the reference points to valid <EncryptedKey> element.

Level: 1

Type: ERROR

Impact: Other

WSM-00052: There is an invalid or nonexistent configuration for the Login Module class [{1}] in the Java Platform Security (JPS) context [{0}].
Cause: An invalid or nonexistent configuration for Login Module could have been used.
Action: Change the configuration and retry the operation.

Level: 1

Type: ERROR

Impact: Configuration

WSM-00053: The propagated subject is either null or empty.
Cause: No Subject was found.
Action: Send a valid nonempty Subject.

Level: 1

Type: ERROR

Impact: Security

WSM-00054: The password credentials cannot be obtained from the Credential Store Framework (CSF). Unable to retrive the csfKey "{0}". The csf map "{1}" found in the credential store is being used and the following keys are found in this map <CsfKeyName: UserName>:- {2}
Cause: Failure occurred while doing query for credentials from Credential Store Framework (CSF).
Action: Check CSF configuration.

Level: 1

Type: ERROR

Impact: Configuration

WSM-00055: The keystore located at {0} cannot be loaded due to {1}. Ensure that valid keystore type and password are configured.
Cause: The following keystore-related configuration properties may not be valid:keystore.type, keystore.pass. Also, the keystore could be corrupt or could have been tampered with.
Action: Verify the configuration properties mentioned above and retry the operation. In a rare situation, replace or regenerate the keystore.

Level: 1

Type: ERROR

Impact: Configuration

WSM-00056: The key, {0}, is not retrieved.{4}Ensure that the correct key password is set in the credential store for the above key. The location of the key store being used is "{1}" and its type is "{2}". The following aliases are found in the keystore:- {3}
Cause: Error occurred while obtaining key from store.
Action: Make sure the key exists in the keystore. Check JPS configuration settings for correct key alias, key password and keystore password. Also, check the values of the key keystore-csf-key and its password in the oracle.wsm.security map, through EM or WLST. In a rare situation, this error can also happen if the actual keystore type is ORACLE_WALLET and the keystore type specified in JPS configuration file is PKCS12.

Level: 1

Type: ERROR

Impact: Configuration

WSM-00057: The certificate, {0}, is not retrieved.{4}The location of the key store being used is "{1}" and its type is "{2}". The following aliases are found in the keystore:- {3}
Cause: Failure occurred while retrieving certificate from store.
Action: Verify keystore location configuration property as well as make sure that the requested certificate is present.

Level: 1

Type: ERROR

Impact: Configuration

WSM-00058: The key type {0} is not supported.
Cause: The private key algorithm that was used is unsupported.
Action: Ensure that the private key follows the RSA algorithm.

Level: 1

Type: ERROR

Impact: Configuration

WSM-00059: Signature method algorithms are mismatched. Expected : {0}, Actual : {1}.
Cause: Expected and actual values of signature method algorithms did not match.
Action: Check the policy and WS-Security Policy 1.1 specification for valid values.

Level: 1

Type: ERROR

Impact: Security

WSM-00060: Error validating timestamp.
Cause: Timestamp is expired.
Action: Check the timestamp. Check the allowed clockskew and message expiration time.

Level: 1

Type: ERROR

Impact: Security

WSM-00061: Signature digest verification failure. The system property xml.debug.verify should be enabled for the details about the digest calculations during verification phase (note xml.debug.verify slows down the signature verification for very large messages). Caused by:-{0}
Cause: Digest verification failed possibly due to corrupted digest, or a message that was tampered with.
Action: Recompute the digest and send the message again.

Level: 1

Type: ERROR

Impact: Security

WSM-00062: The path to the certificate used for the signature is invalid.
Cause: The intermediate and root certificates of the signing certificate were not present in the keystore at the verifying end.
Action: Make sure that the entire certificate chain is available in the keystore for verification.

Level: 1

Type: ERROR

Impact: Security

WSM-00063: The version of SAML is incorrect. Expected : {0}, Actual : {1}.
Cause: SAML version in the SAML assertion did not match the expected version.
Action: Check to see that the major version and minor version of the assertion are according to policy.

Level: 1

Type: ERROR

Impact: Security

WSM-00064: SAML subject confirmation mismatch. Expected : {0}, Actual : {1}.
Cause: Subject confirmation method in SAML assertion did not match the policy requirements.
Action: Check to see that the confirmation method for all the SAML assertions is sender-vouches.

Level: 1

Type: ERROR

Impact: Security

WSM-00065: Error sending request over SSL.
Cause: Failure in creating SSL request possibly due to invalid configuration of Credential Store FrameWork (CSF).
Action: Check the JPS configuration for CSF.

Level: 1

Type: ERROR

Impact: Other

WSM-00067: None SOAP message parts can be encrypted.
Cause: The elements to be encrypted in the policy were selected to be either of soap Envelope/Body/Header.
Action: The core soap nodes cannot be encrypted according to WS-Security 1.0 specification.

Level: 1

Type: ERROR

Impact: Security

WSM-00068: The security token is missing.
Cause: Security token was expected but was not found.
Action: Security token is missing. Resend request with valid Security token.

Level: 1

Type: ERROR

Impact: Security

WSM-00069: The security header is missing. Ensure that there is a valid security policy attached at the client side, and the policy is enabled.
Cause: Security header was expected but was not found.
Action: Security header is missing. It could be that client side policy has not been applied. Resend request with appropriate Security header.

Level: 1

Type: ERROR

Impact: Security

WSM-00070: The nonce cannot be validated.
Cause: Failure occurred while performing nonce Validation.
Action: This may be due to a repeated value of nonce. Resend the request with a valid nonce.

Level: 1

Type: ERROR

Impact: Security

WSM-00071: Error validating the wsu:Created attribute.
Cause: Failure occurred while doing Created(Timestamp) validation.
Action: Resend the request with a valid timestamp, and or within the expiration limits.

Level: 1

Type: ERROR

Impact: Security

WSM-00072: An encryption algorithm suite policy compliance failure occurred.
Cause: Failure occurred in encryption algorithms policy compliance check.
Action: Check the encryption algorithm requirements of the policy and resend the message with appropriate value of algorithm suite.

Level: 1

Type: ERROR

Impact: Security

WSM-00073: The mechanism {0} used in the authentication header is not supported.
Cause: The value of mechanism attribute used was not supported.
Action: Change the policy to point to valid value of mechanism(basic), and retry the operation.

Level: 1

Type: ERROR

Impact: Configuration

WSM-00074: The authorization header {0} is not correctly encoded using the Base64 encoding.
Cause: The authorization header was not encoded according to Base64 requirements.
Action: Encode the header with Base64(username:realm:password) format and resend the request.

Level: 1

Type: ERROR

Impact: Security

WSM-00075: The realm property is not configured in the policy.
Cause: The realm property was not configured in the policy.
Action: Configure appropriate value of realm inside the policy.

Level: 1

Type: ERROR

Impact: Configuration

WSM-00076: The user name is missing from the encoded authorization header.
Cause: The Authorization header did not contain a properly encoded username, or username was null.
Action: Encode the header with Base64(username:realm:password) format and resend the request.

Level: 1

Type: NOTIFICATION

Impact: Security

WSM-00077: The password is missing from the encoded authorization header.
Cause: The Authorization header did not contain password encoded properly, or password was null.
Action: Encode the header with Base64(username:realm:password) format and resend the request.

Level: 1

Type: ERROR

Impact: Security

WSM-00078: The configuration of the credentials in the policy is incorrect.
Cause: Credential configuration in the policy was incorrect.
Action: Configure policy with valid Credential Store Framework (CSF) key, or username/password properties.

Level: 1

Type: ERROR

Impact: Configuration

WSM-00079: The <BinarySecurityToken> element is missing.
Cause: <BinarySecurityToken> was not found.
Action: For reference mechanisms that are configured with value direct, send the certificate inside <BinarySecurityToken> element.

Level: 1

Type: ERROR

Impact: Security

WSM-00080: STR Dereferencing Transform not found
Cause: STR Dereferencing Transform was not found.
Action: For reference mechanisms that are configured with value SKI, the Transforms section should contain the STR Dereferencing Transform.

Level: 1

Type: ERROR

Impact: Security

WSM-00081: The X.509 certificate is not signed.
Cause: The X509 token used was not signed according to requirements of certificate authentication scenario.
Action: Sign the X509 token (depending upon the reference mechanism used) for certificate authentication.

Level: 1

Type: ERROR

Impact: Security

WSM-00082: The roles and/or attributes of the user profile cannot be retrieved.
Cause: No information could be obtained regarding the user roles or attributes.
Action: Try resending the request for another user.

Level: 1

Type: ERROR

Impact: Security

WSM-00083: Error computing the digest for this reference.
Cause: Digest computation for the <Reference> failed.
Action: Check log file for possible cause.

Level: 1

Type: ERROR

Impact: Security

WSM-00084: Error computing <SignatureValue> for this signature block.
Cause: Signature value computation for the signature block failed.
Action: Check log file for possible cause.

Level: 1

Type: ERROR

Impact: Security

WSM-00085: The certificates cannot be retrieved from the keystore.
Cause: Failure occurred while trying to retrieve certificate from keystore.
Action: Use a valid alias for the certificate and retry the operation.

Level: 1

Type: ERROR

Impact: Security

WSM-00086: Error initializating nonce cache.
Cause: Failure occurred while initializing iAS Cache.
Action: Check log file for possible cause.

Level: 1

Type: ERROR

Impact: Security

WSM-00087: Either {0} property or the oracle.j2ee.home system property is not set.
Cause: The cache configuration file for iAS cache was not found.
Action: Set the system property oracle.j2ee.home or javacache.config.home system property to the path of the configuration file javacache.xml.

Level: 1

Type: ERROR

Impact: Security

WSM-00088: The ObSSOCookie is missing.
Cause: The OAM security token was not found.
Action: Resend the request by embedding the ObSSOCookie token inside a <BinarySecurityToken> element.

Level: 1

Type: ERROR

Impact: Security

WSM-00089: The attachments security transform is incorrect. Expected : {0}, Actual : {1}.
Cause: The attachment security transform used was incorrect.
Action: Refer to the recipient's policy for information about which SwA Security Transform is to be used.

Level: 1

Type: ERROR

Impact: Security

WSM-00090: The signature for the attachment is non-compliant.
Cause: The attachment signature was not compliant.
Action: Refer to the recipient's policy for information about which SwA Security Transform is to be used.

Level: 1

Type: ERROR

Impact: Security

WSM-00091: The encryption of the attachment is non-compliant.
Cause: The attachment encryption was not compliant.
Action: Refer to the recipient's policy for information about which SwA Security Transform is to be used.

Level: 1

Type: ERROR

Impact: Security

WSM-00092: The <EncryptedKey> element is missing in the request. Ensure that there is a message protection policy attached at the client side.
Cause: No <EncryptedKey> elements were found in the request.
Action: Refer to the WS-Security 1.0 and 1.0 specifications for the semantics.

Level: 1

Type: ERROR

Impact: Security

WSM-00093: The <saml:Assertion> element is missing in the security header. Ensure that there is a SAML token policy attached at the client side. Tokens found in the security header are:- {0}.
Cause: No SAML assertions were found inside the security Header.
Action: Resend the message with at least one SAML assertion in the header.

Level: 1

Type: ERROR

Impact: Security

WSM-00094: The negotiated cipher suite does not meet policy requirements. Expected : {0}, Actual : {1}.
Cause: The negotiated cipher suite did not meet policy requirements.
Action: Check the recipient's policy for the permitted values of the cipher suite.

Level: 1

Type: ERROR

Impact: Security

WSM-00095: There is more than one assertion assigned to the same category {0} in the security policy.
Cause: Two or more assertions assigned to the same category were used.
Action: Ensure that assertions inside a security policy belong to different categories.

Level: 1

Type: ERROR

Impact: Configuration

WSM-00096: The order of the assertions is incorrect.
Cause: Assertion order does not match the requirements of policy.
Action: Use the following order for client side policy : authentication -> msgprotection or authentication -> authorization and following for server side security policy msg-protection -> authentication or msg-protection -> authentication -> authorization.

Level: 1

Type: ERROR

Impact: Configuration

WSM-00097: HTTP basic authentication header is missing.
Cause: HTTP basic authentication header was missing.
Action: Client must provide the HTTP basic authentication header.

Level: 1

Type: NOTIFICATION

Impact: Security

WSM-00098: User realm {0} is either null or is a mismatch with service realm {1}.
Cause: User realm was either null or was a mismatch with service realm.
Action: Make sure user realm sent from client matches with the service realm.

Level: 1

Type: NOTIFICATION

Impact: Security

WSM-00099: Username, password, or both are missing from the HTTP authentication header.
Cause: Username, password, or both were missing from HTTP authentication header.
Action: Make sure the HTTP request header contains the username/password token.

Level: 1

Type: ERROR

Impact: Security

WSM-00100: Found more than one keystore files {0} in application classpath. By default the first keystore is used. Make sure the desired keystore is being used by clearing others from the classpath.
Cause: Found more than one keystore file in application classpath. By default, the first keystore is used.
Action: To ensure the desired keystore is being used, remove other keystores from the classpath, if possible.

Level: 1

Type: WARNING

Impact: Security

WSM-00101: The specified keystore file {0} cannot be found; it either does not exist or its path is not included in the application classpath.
Cause: Keystore file did not exist or its path was either incorrect or not included in the application classpath.
Action: Verify the keystore file does exist and its path is included in the application classpath.

Level: 1

Type: ERROR

Impact: Security

WSM-00102: The specified user/subject does not belong to any role in system ID store.
Cause: The subject/user did not belong to any defined role in system ID store.
Action: Verify and make sure that the specified user belongs to one or more roles.

Level: 1

Type: ERROR

Impact: Security

WSM-00103: The policy is configured incorrectly without specifying roles, or denyAll or permitAll elements.
Cause: The policy was incorrectly configured with no roles and no denyAll/permitAll elements.
Action: Correct the policy by configuring it with a denyAll element, a permitAll element, or at least one role.

Level: 1

Type: ERROR

Impact: Security

WSM-00104: The specified JPS context {0} cannot be found in system-level JPS configuration file.
Cause: The JPS context could not be found in system level JPS configuration.
Action: Verify system level JPS configuration file to ensure that it contains the context.

Level: 1

Type: ERROR

Impact: Security

WSM-00105: Credential Store service instance is missing. Either the Oracle WSM JPS context being used for the keystore does not contain a reference to the Credential Store service instance, or the reference is not valid.
Cause: No Credential Store (CSF) was found at the level where keystore was used.
Action: The error indicates that either the WSM JPS context that is being used for the keystore does not reference the Credential Store service instance, or that the reference is not valid. The Credential Store service instance must be declared at the same level (system or application) as the keystore service instance. Therefore, if an application level keystore is being used, a CSF store must also be declared at the the application level.

Level: 1

Type: ERROR

Impact: Security

WSM-00106: Assertion assigned to a non-security category {0} cannot be added to policy assigned to a security category.
Cause: Assertion belonging to non-security categories could not be added to policies belonging to security category.
Action: Ensure that assertions in security policy also belongs to security category.

Level: 1

Type: ERROR

Impact: Security

WSM-00107: Assertion belonging to {0} category is not valid for generic policy. Only assertion of type security/logging can be added to a generic policy (policy applicable to clients and servers). Check the assertions added to the generic policy.
Cause: Invalid assertions were found in generic policy.
Action: Only assertion of type security/logging can be added to a generic policy (policy applicable to clients and servers). Recheck the assertions added to the generic policy.

Level: 1

Type: ERROR

Impact: Security

WSM-00108: If password type is set to digest, addNonce and addCreated should be true.
Cause: UserNameToken Assertion had Passwordtype as digest but addNonce or addCreated was false.
Action: In case of passwordtype as digest, addNonce and addCreated both should be true. Recheck the assertion.

Level: 1

Type: ERROR

Impact: Security

WSM-00109: Algorithm suite is not supported, only TripleDes is supported for Kerberos assertion.
Cause: Kerberos Assertion had algorithm-suite other than TripleDES.
Action: Only TripleDES algorithm is supported in case of Kerberos, so set algorithm-suite as TripleDes.

Level: 1

Type: ERROR

Impact: Security

WSM-00110: Basic192 and *RSA15 algorithm-suites are not supported for SSL. Change the algorithm suite to one that is supported.
Cause: Basic192 or RSA algorithm-suite was used for SSL.
Action: Use other supported Algorithm-suite for SSL except Basic192 and RSA algorithms.

Level: 1

Type: ERROR

Impact: Security

WSM-00111: Keystore is not properly configured in JPS config.
Cause: Keystore was not properly configured in JPS configuration or through config override properties.
Action: Check the keystore configuration, and try again.

Level: 1

Type: ERROR

Impact: Security

WSM-00112: Missing keystore service instance reference in Oracle WSM JPS context.
Cause: Keystore Service instance reference was not found in WSM JPS context.
Action: Add the keystore service instance reference to WSM JPS context, and try again.

Level: 1

Type: ERROR

Impact: Security

WSM-00113: Unsupported configuration value for Client Credential Configuration location.
Cause: An unsupported configuration value of Client Credential location configuration was provided.
Action: Refer to the documentation for valid values and add the proper configuration value for Client Credential Configuration Location, and try again.

Level: 1

Type: ERROR

Impact: Security

WSM-00114: No matching SSL cipher suite is found for algorithm suite value, specified in the Policy.
Cause: No matching SSL cipher suite was found for algorithm suite value, specified in WS Policy.
Action: Set algorithm suite of Web Service policy to a value that has matching SSL cipher suite.

Level: 1

Type: ERROR

Impact: Security

WSM-00115: JSSE System Property for SSL cipher suite is either not set or does not match algorithm suite value specified in WS Policy.
Cause: JSSE System Property for SSL cipher suite was either not set or did not match algorithm suite value specified in WS Policy.
Action: Set JSSE System Property (https.cipherSuites) to a value that matches algorithm suite as specified in WS Policy.

Level: 1

Type: ERROR

Impact: Security

WSM-00116: Error retrieving SOAP body from SOAP message.
Cause: An error ocurred while retrieving SOAPBody from SOAPMessage. Either the SOAPMessage was not proper or had been tampered with.
Action: Check whether the SOAPMessage is according to the Specifications and try again.

Level: 1

Type: ERROR

Impact: Security

WSM-00117: Error occurred while transforming the security header.
Cause: TransformerException occurred while transforming the WssHeader to String. The SOAPMessage might not have been proper or it did not conform to the specifications.
Action: Check the SOAPMessage and try again.

Level: 1

Type: ERROR

Impact: Security

WSM-00118: OAM token can be inserted only on hosted clients where authenticated subject has been established.
Cause: Insertion of an OAM token tried from a non-hosted client where Authenticated Subject is not established.
Action: Try to add OAM token from a hosted client as only the hosted clients can insert the OAM token extracting it from Authenticated Subject

Level: 1

Type: ERROR

Impact: Security

WSM-00119: Either authorization header or requireTLS must be present.
Cause: The security policy attached did not have either auth Header or requireTLS set to true.
Action: Change the policy to have either auth Header or requireTLS to be true.

Level: 1

Type: ERROR

Impact: Security

WSM-00120: Cannot compute endorsing signature as no message signature is present.
Cause: The security policy did not sign anything from the message, so no signature was there. Endorsing Signature could not be computed as the signature which it was trying to endorse was not present.
Action: Change the policy to Sign at least something in the message.

Level: 1

Type: ERROR

Impact: Security

WSM-00121: Only the attachments are to be signed/encrypted and they are not present.
Cause: Only the attachments were to be signed/encrypted and they were not present.
Action: Retry after putting attachments in the SOAP Message.

Level: 1

Type: ERROR

Impact: Security

WSM-00122: Valid timestamp is not present in the message.
Cause: Timestamp was not present in the message or the timestamp present did not conform to specifications.
Action: Ensure the timestamp is present in the message.

Level: 1

Type: ERROR

Impact: Security

WSM-00123: Timestamp of the message is in future.
Cause: The message had Created timestamp of a time in future so it failed Future message validation.
Action: Ensure freshness of the message and check policy-accessor-config.xml for the configured values of agent.clock.skew.

Level: 1

Type: ERROR

Impact: Security

WSM-00124: Timestamp of the message is in past.
Cause: The message was older than the permissible time limit so it failed Past message validation.
Action: Ensure freshness of the Message and check the policy-accessor-config.xml for the configured values of agent.clock.skew and agent.expire.time.

Level: 1

Type: ERROR

Impact: Security

WSM-00125: Password digest validation failed.
Cause: The password digest in the message was not correct so it failed the digest validation.
Action: Retry after ensuring password digest is proper.

Level: 1

Type: ERROR

Impact: Security

WSM-00126: Subject does not contain JPS user.
Cause: The subject mentioned did not have the JPS User.
Action: Retry after ensuring JPS user in the subject.

Level: 1

Type: ERROR

Impact: Security

WSM-00127: User not in identity store.
Cause: The user mentioned was not present in the identity store.
Action: Retry after ensuring that user is present in the identity Store.

Level: 1

Type: ERROR

Impact: Security

WSM-00128: Keystore instance is null.
Cause: Could not obtain keystore instance. Either the keystore instance type was wrong or the keystore configuration was wrong.
Action: Check JPS configuration settings. Use correct keystore instance type.

Level: 1

Type: ERROR

Impact: Security

WSM-00129: Unsupported SAML token provided : {0}.
Cause: An unsupported SAML token confirmation method was provided.
Action: Provide a supported SAML token confirmation method and retry the operation.

Level: 1

Type: ERROR

Impact: Security

WSM-00130: SAML assertion subject is missing.
Cause: The SAML assertion subject name was not specified.
Action: Provide the SAML assertion subject and retry the operation.

Level: 1

Type: ERROR

Impact: Security

WSM-00131: Unsupported data encryption algorithm: {0}.
Cause: An unsupported data encryption algorithm was provided.
Action: Consult the documentation for the supported encryption algorithms and retry the operation.

Level: 1

Type: ERROR

Impact: Security

WSM-00132: Invalid JPS configuration.
Cause: An invalid JPS configuration was provided.
Action: Make sure that the JPS configuration is valid.

Level: 1

Type: ERROR

Impact: Security

WSM-00134: The signature key, {0}, is not retrieved due to exception {1}.
Cause: Error occurred while obtaining the signature key from store.
Action: Check JPS configuration settings. Make sure that the key password , keystore password, and key alias are valid.

Level: 1

Type: ERROR

Impact: Security

WSM-00135: The encryption key, {0}, is not retrieved due to exception {1}.
Cause: Error occurred while obtaining encryption key from store.
Action: Check JPS configuration settings. Use correct key password, keystore password, and key alias.

Level: 1

Type: ERROR

Impact: Security

WSM-00136: The signature certificate, {0}, is not retrieved due to exception {1}.
Cause: Failure occurred while retrieving the signature certificate from store.
Action: Check JPS configuration settings for keystore location and make sure that the requested certificate is present.

Level: 1

Type: ERROR

Impact: Security

WSM-00137: The encryption certificate, {0}, is not retrieved due to exception {1}.
Cause: Failure occurred while retrieving the encryption certificate from store.
Action: Check JPS configuration settings for keystore location and make sure that the requested certificate is present.

Level: 1

Type: ERROR

Impact: Security

WSM-00138: The path to the certificate is invalid. Validation failed for the certificate {0} Certificates in cert path used for validation are:- {1}
Cause: The intermediate and root certificates of the certificate were not present in the keystore during verification.
Action: Make sure that the entire certificate chain is available in the keystore for verification.

Level: 1

Type: ERROR

Impact: Security

WSM-00139: The scenario category {0} is not supported.
Cause: The scenario category is not supported.
Action: Consult the Oracle documentation for supported categories.

Level: 1

Type: ERROR

Impact: Security

WSM-00140: Invalid execution stage {0} resulting in system internal error.
Cause: System encountered an invalid execution stage.
Action: Retry the operation, If problem persists contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Security

WSM-00141: Error retrieving SOAP header from SOAP message.
Cause: An error occurred while retrieving the header from the SOAP Message. The SOAP message was invalid or was tampered with.
Action: Make sure that the SOAP message is valid according to the specifications and retry the operation.

Level: 1

Type: ERROR

Impact: Security

WSM-00142: Assertion belonging to {0} category is not valid for Component policy
Cause: Assertion belonging to authentication or message protection category was found in Component policy and it is invalid.
Action: Modify the policy to correct the problem and retry the operation.

Level: 1

Type: ERROR

Impact: Security

WSM-00143: Failure creating Java Keystore instance for type {0}.
Cause: Either the keystore type provided is not supported or there is no implementation provider for Java keystore.
Action: Consult the Oracle documentation for supported Keystore types and make sure the implementation provider for Java Keystore is available.

Level: 1

Type: ERROR

Impact: Configuration

WSM-00144: Failure retrieving Keystore aliases.
Cause: Keystore may have not been initialized.
Action: Check the log file for possible causes and retry the operation.

Level: 1

Type: ERROR

Impact: Configuration

WSM-00149: SAML assertion is missing.
Cause: Failed to locate SAML assertion with ID {0}.
Action: Make sure that a valid SAML asssertion exists.

Level: 1

Type: ERROR

Impact: Security

WSM-00150: Processed header list fetched from InterceptorContext is null, agentFunction:{0}, listType:{1}.
Cause: Processed header list fetched from InterceptorContext is null.
Action: Retry the operation. If the problem persists, contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Security

WSM-00153: Error retrieving Weblogic Server subject from JPS subject using SubjectSecurityUtil API
Cause: A failure occurred while converting JPS subject to Weblogic Server subject.
Action: Check log file for possible cause.

Level: 1

Type: ERROR

Impact: Security

WSM-00155: Error retrieving Oracle WSM security policies.
Cause: A failure occurred while retrieving Oracle WSM security policies.
Action: Check log file for possible cause.

Level: 1

Type: ERROR

Impact: Security

WSM-00156: Invalid binary security token.
Cause: Binary security token in the header and the certificate used for endorsing signature did not match.
Action: Make sure a valid binary security token is being passed.

Level: 1

Type: ERROR

Impact: Security

WSM-00157: Recipient key alias not configured and signer certificate was not available because no part of the request was signed.
Cause: Recipient key alias not configured and signer's certificate was not available because no part of request was signed.
Action: Set recipient key alias in service policy or sign part of the request.

Level: 1

Type: ERROR

Impact: Security

WSM-00158: KerberosLoginModule class is not available in the classpath
Cause: The class for the Kerberos login module was not available in the classpath.
Action: Make sure that the KerberosLoginModule class is included in the classpath, and configure the class name properly in policy-config.xml.

Level: 1

Type: ERROR

Impact: Security

WSM-00159: TextCallbackHandler class is not available in the classpath
Cause: The class for the Text callback handler was not available in the classpath.
Action: Make sure that the TextCallbackHandler class is included in the classpath, and configure the class name properly in policy-config.xml.

Level: 1

Type: ERROR

Impact: Security

WSM-00160: The SSL policy must contain a requireTLS element.
Cause: The security policy attached did not have requireTLS set to true.
Action: Change the policy to have requireTLS as true.

Level: 1

Type: ERROR

Impact: Security

WSM-00161: Client encryption public certificate is not configured for Async web service client
Cause: Client encryption public certificate is not configured for async web service client with message protection.
Action: Make sure that client public certificate is configured in client keystore, or provided through client config override for Async web service client that uses message protection

Level: 1

Type: ERROR

Impact: Security

WSM-00162: Invalid recipient cert type: {0} may have been provided through override; It should be either a X509Certificate object or Base64 encoded value in String format.
Cause: Invalid recipient cert type may have been provided through override; It should be either a X509Certificate object or Base64 encoded value in String format.
Action: Verify that only X509Certificate object, or Base64 encoded String value are provided in Policy, descriptor file or through program.

Level: 1

Type: ERROR

Impact: Configuration

WSM-00163: Failure in getting recipient certificate using recipient key alias {0}
Cause: The recipient key alias might not be valid
Action: Check to see if there is such certificate in keystore corresponding to the recipient key alias provided.

Level: 1

Type: ERROR

Impact: Configuration

WSM-00164: Cannot obtain a valid recipient cert for client message sending
Cause: Encountered error while obtaining recipient certificate for sending request.
Action: Must provide valid recipient certificate, or recipient alias for client to send request with message protection.

Level: 1

Type: ERROR

Impact: Configuration

WSM-00165: Creating recipient certificate from base64 encoded string: {0} failed.
Cause: Encountered error while creating recipient certificate from base64 encoded string.
Action: Must provide valid certificate in valid base64 encoded string.

Level: 1

Type: ERROR

Impact: Configuration

WSM-00166: Extract certificate from saved ReplyTo header failed.
Cause: X509Certificate within ReplyTo header element might be invalid.
Action: Ensure that cert. insertion, ReplyTo header serialization/deserializaton to JMS queue are all working properly.

Level: 1

Type: ERROR

Impact: Configuration

WSM-00167: Actual Hostname {0} and Hostname retrieved from Certificate {1} do not match
Cause: HostName verification of certificate retrieved from WSDL failed
Action: Either ensure that the Subject Dn matches the Hostname of the Service or disable the HostName Verification check

Level: 1

Type: ERROR

Impact: Security

WSM-00168: Unable to extract X509Certificate from WSDL Definition Object as WSDL definition Object is unavailable
Cause: WSDL definition required for extraction of X509Certificate not available
Action: Ensure that WSDL Definition Object is available from the MessageContext

Level: 1

Type: ERROR

Impact: Security

WSM-00169: Error decrypting the request message.
Cause: The request message could not be decrypted using the key specified for decryption.
Action: Ensure that the key used for decryption is same as the one used for encryption.

Level: 1

Type: ERROR

Impact: Security

WSM-00170: There are no assertions available under the ExactlyOne policy operator.
Cause: There are no assertions under ExactlyOne policy operator.
Action: Ensure that one or more security assertions are kept under ExactlyOne policy operator.

Level: 1

Type: ERROR

Impact: Security

WSM-00171: A client policy contains an ExactlyOne policy operator.
Cause: A client policy contained an ExactlyOne policy operator.
Action: Remove the ExactlyOne policy operator or switch to a service binding.

Level: 1

Type: ERROR

Impact: Security

WSM-00172: A generic policy contains an ExactlyOne policy operator.
Cause: A generic policy contained an ExactlyOne policy operator.
Action: Remove the ExactlyOne policy operator or switch to a service binding.

Level: 1

Type: ERROR

Impact: Security

WSM-00173: A policy contains more than one ExactlyOne policy operator.
Cause: A policy contained more than one ExactlyOne policy operator.
Action: Remove the additional ExactlyOne policy operators.

Level: 1

Type: ERROR

Impact: Security

WSM-00174: A policy contains a nested ExactlyOne policy operator.
Cause: A policy contained a nested ExactlyOne policy operator.
Action: Remove the nested ExactlyOne policy operators.

Level: 1

Type: ERROR

Impact: Security

WSM-00175: Recipient Certificate for async callback client is not found under the ReplyTo element in async callback client message context
Cause: Recipient cert. for async callback client is not available from message context.
Action: Ensure that original async client has public encryption certificate configured and is inserted into the ReplyTo header or the original async request. Also ensure that the original ReplyTo header along with client encryption certification is preserved and restored to the callback client message context.

Level: 1

Type: ERROR

Impact: Configuration

WSM-00176: The mapped long name(s) for property {0} is null, the property might not be available for client programmatic override. Make sure it is indeed the intension, otherwise, add a mapping to map ConfigOverrideMapping.
Cause: The config override property does not have a corresponding long name mapping
Action: Make sure this is indeed intended, otherwise, add a mapping to the ConfigOverrideMapping.

Level: 1

Type: WARNING

Impact: Configuration

WSM-00177: The CSF key provided by the user is not present in the credential store. So using the default key is being used.
Cause: The CSF key provided by the user is not present in the credential store
Action: Provide a valid key. Till then the default key will be used.

Level: 1

Type: WARNING

Impact: Security

WSM-00178: Public key not found for SAML signature verification.
Cause: Public key not found for SAML signature verification
Action: Ensure that public key is present in Security header which is reqruied For SAML signature verification

Level: 1

Type: WARNING

Impact: Configuration

WSM-00179: SAML assertion issuer name is invalid.
Cause: SAML assertion issuer name is invalid.
Action: Check to see that the overridden SAML trused issuers has SAML assertion issuer name.

Level: 1

Type: ERROR

Impact: Security

WSM-00180: The trust version {0} is not supported for policy advertisement, hence ignored. The default trust version {1} is advertised.
Cause: The trust version specified in the policy is not supported.
Action: Modify the policy with a supported trust version.

Level: 1

Type: WARNING

Impact: Configuration

WSM-00181: A policy issued-token attributes require-internal-reference and require-external-reference both are false, one of them has to be true.
Cause: A policy issued-token attribute require-internal-reference and require-external-reference can not both be false.
Action: At least one of the attribute require-internal-reference and require-external-reference must be set to true

Level: 1

Type: ERROR

Impact: Configuration

WSM-00182: A policy request-security-token-template element attribute token-type has an unsupported value: {0}
Cause: A policy request-security-token-template element contains a token-type that is not supported.
Action: Check documentation for supported token-type

Level: 1

Type: ERROR

Impact: Configuration

WSM-00183: A policy request-security-token-template element attribute algorithm-suite has a value: {0} which does not match to that of msg-security: {1}, change it to match {1}.
Cause: A policy request-security-token-template element contains an algorithm-suite value that does not match to that of msg-security.
Action: Change the algorithm-suite attribute value to match exactly the one in msg-security

Level: 1

Type: ERROR

Impact: Configuration

WSM-00184: An attribute trust-version has an unsupported version: {0}
Cause: A policy contains an unsupported WS-TRUST version.
Action: Check documentation for supported WS-TRUST version

Level: 1

Type: ERROR

Impact: Configuration

WSM-00185: Attribute require-client-entropy and require-server-entropy can not both be set to false, at lease one of them must be set to true.
Cause: A policy can not have both require-client-entropy and require-server-entropy attributes set to false.
Action: At lease set one of them to true

Level: 1

Type: ERROR

Impact: Configuration

WSM-00186: A policy request-security-token-template key-type attribute is expected to be: {0}, but got: {1}
Cause: A policy request-security-token-template key-type attribute value is not set to the expected Bearer.
Action: Set the attribute value to the expected

Level: 1

Type: ERROR

Impact: Configuration

WSM-00187: A policy request-security-token-template key-type attribute is expected to be: {0}, but got: {1}
Cause: A Bearer policy request-security-token-template key-type attribute value is not set to the expected Symmetric or Public.
Action: Set the attribute value to one of the expeted value Symmetric or Public

Level: 1

Type: ERROR

Impact: Configuration

WSM-00188: STS Trust Config policy attribute port-uri has invalid value "{0}", it must be not null, not empty and in the format of http(s)://host:port/sts-service
Cause: STS trust config attribute port-uri is either null, empty or not in the format of "http(s)://host:port/sts-service-name".
Action: Provide valid attribute value which is in the format of "http(s)://host:port/sts-service"

Level: 1

Type: ERROR

Impact: Configuration

WSM-00189: STS Trust Config policy attribute port-endpoint has invalid value "{0}", it must be not empty and in the format of target-namespace#wsdl.endpoint(service-name/port-name)
Cause: STS trust config attribute port-endpoint is either empty or not in the format of "target-namespace#wsdl.endpoint(service-name/port-name)".
Action: Provide valid attribute value which is in the format of "target-namespace#wsdl.endpoint(service-name/port-name)"

Level: 1

Type: ERROR

Impact: Configuration

WSM-00190: STS Trust Config policy attribute policy-reference-uri can not have empty value.
Cause: The value of STS trust config attribute policy-reference-uri is empty or not in the URI format
Action: Specify value for attribute policy-reference-uri

Level: 1

Type: ERROR

Impact: Configuration

WSM-00191: STS Trust Config policy attribute sts-keystore-recipient-alias can not have null or empty value.
Cause: The value of STS trust config attribute sts-keystore-recipient-alias is null or empty
Action: Specify a non null or empty value for attribute sts-keystore-recipient-alias

Level: 1

Type: ERROR

Impact: Configuration

WSM-00192: Kerberos name identifier format is not supported for SAML 1.1 token.
Cause: Kerberos name identifier format is not supported for SAML 1.1 token.
Action: Kerberos name identifier format is only for SAML 2.0 token, use other name identifier formats.

Level: 1

Type: ERROR

Impact: Security

WSM-00193: Security policy contains NULL or empty value for signed-element local name or namespace.
Cause: Security policy contains NULL or empty value for signed-element local name or namespace.
Action: Signed-element local name or namespace must not be null or empty.

Level: 1

Type: ERROR

Impact: Security

WSM-00194: Security policy contains NULL or empty value for signed-part header namespace.
Cause: Security policy contains NULL or empty value for signed-part header namespace.
Action: Signed-part header namespace must not be null or empty.

Level: 1

Type: ERROR

Impact: Security

WSM-00195: Security context for derived key unknown (cannot determine the base symmetric key).
Cause: Security context for derived key unknown (cannot determine the base symmetric key).
Action: DerivedKeyToken should include SecurityReferenceToken (can only be empty in responses where the message context includes the base key).

Level: 1

Type: ERROR

Impact: Security

WSM-00196: Unable to resolve base key referenced in DerivedKeyToken.
Cause: Unable to resolve base key referenced in DerivedKeyToken.
Action: Ensure the SecurityTokenReference in the DerivedKeyToken specifies a valid base key within the security context.

Level: 1

Type: ERROR

Impact: Security

WSM-00197: Unsupported SecurityTokenReference type for DerivedKeyToken.
Cause: Unsupported SecurityTokenReference type for DerivedKeyToken.
Action: Ensure the SecurityTokenReference in the DerivedKeyToken is one of the supported types.

Level: 1

Type: ERROR

Impact: Security

WSM-00198: Unable to resolve EncryptedKey that matches EncryptedKeySHA1 in KeyInfo.
Cause: Unable to resolve EncryptedKey that matches EncryptedKeySHA1 in KeyInfo.
Action: The value of the EncryptedKeySHA1 should match an encrypted key in the security context.

Level: 1

Type: ERROR

Impact: Security

WSM-00199: Unsupported key identifier type "{0}" in security token reference.
Cause: Unsupported key identifier type in security token reference.
Action: Use only of the supported key idetifier types in the security token.

Level: 1

Type: ERROR

Impact: Security

WSM-00200: Exception encountered while checking compliance; returning false.
Cause: Exception encountered while checking compliance; returning false.
Action: Check log for exception details.

Level: 1

Type: ERROR

Impact: Security

WSM-00201: There are no <EncryptedKey> elements in the request.
Cause: There are no <EncryptedKey> elements in the request.
Action: The request should have an <EncryptedKey> element.

Level: 1

Type: ERROR

Impact: Security

WSM-00202: Proof key type is invalid, valid vaues are null, public, symmetric.
Cause: The value of ketype is invalid for SAML Issued Token Policy , valid values are null (no proof key), public, symmetric
Action: Specify valid value for keytype based on the policy

Level: 1

Type: ERROR

Impact: Configuration

WSM-00203: Invalid OPSS Trust Service
Cause: OPSS TrustService is empty or null
Action: Configure Trust Service in OPSS

Level: 1

Type: ERROR

Impact: Configuration

WSM-00204: Invlaid issued token from trust token exchange
Cause: Issued token is null
Action: Check Logs and correct any errors during issuance

Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00205: Proof key type is invalid, valid value is bearer
Cause: The value of ketype is invalid for SAML Bearer Issued Token Policy , valid value is bearer
Action: Specify bearer as the key type for this policy

Level: 1

Type: ERROR

Impact: Configuration

WSM-00206: Requester credentials for authenticating to STS are invalid
Cause: Requester Credentials required for autenticating to STS are missing
Action: Configure sts.auth.user.csf.key or sts.auth.x509.csf.key in issued token policy

Level: 1

Type: ERROR

Impact: Configuration

WSM-00207: Assymetric proof key is invalid
Cause: Assymetric proof key is invalid
Action: Configure sts.auth.x509.csf.key in issued token policy

Level: 1

Type: ERROR

Impact: Configuration

WSM-00208: STS On behalf of user is invalid
Cause: STS On behalf of user is invalid
Action: Configure sts.auth.on.behalf.of.csf.key in issued token policy

Level: 1

Type: ERROR

Impact: Configuration

WSM-00209: Permission{0} required to switch the identity not granted to the resource. {1}
Cause: Permission required to switch the identity not granted
Action: Grant Permission for identity switching to the code source.

Level: 1

Type: ERROR

Impact: Security

WSM-00210: Client is unable to find actual webservice endpoint to set in appliesTo
Cause: Client requires appliesTo and unable to find the actual webservice endpoint URL
Action: Chenck if agent binding ws port ID , service name and port name in log file

Level: 1

Type: ERROR

Impact: Configuration

WSM-00211: Trust token provider tried creating RequestSecurityToken message and it failed because algoirthm use to generate asymmetric key pair was invalid
Cause: Trust token provider tried creating RequestSecurityToken message and it failed because algoirthm use to generate asymmetric key pair was invalid
Action: Check the asymmetric key algorithm

Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00212: Trust token provider tried creating RequestSecurityToken message and it failed because assymetic proofk key was invalid
Cause: Trust token provider tried creating RequestSecurityToken message and it failed because assymetic proofk key was invalid
Action: Check if sts.auth.x509.csf.key is configured correctly in issued token client policy

Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00213: Unable to parse SOAP message sent by STS
Cause: Unable to parse SOAP message sent by STS
Action: Check if message sent by STS is valid

Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00214: Unable to parse RequestSecurityTokenRespnseCollection
Cause: Unable to parse RequestSecurityTokenResponseCollection
Action: Check if RequestSecurityTokenResponseCollection message sent by STS is valid

Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00215: Unable to parse STSTrustConfig
Cause: Unable to parse STSTrustConfig
Action: Check if STSTrustConfig is valid

Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00216: Unable to create SOAP RequestSecurityToken message
Cause: Unable to create SOAP RequestSecurityToken message
Action: Failure in creating SOAP RequestSecurityToken message, check log files

Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00217: STS endpoint URL or WSDL URL (if configured) is invalid
Cause: STS endpoint URL or WSDL URL (if configured) is invalid
Action: Check if STS endpoint URL and WSDL URL (if configured) are valid

Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00218: Security token returned by STS is null
Cause: Security token returned by STS is null
Action: Check if RSTR message sent by STS is valid

Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00219: Proof token returned by STS is null
Cause: Proof token returned by STS is null
Action: Check if RSTR message sent by STS is valid

Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00220: Invalid proof token type, valid values are computedKey and BinarySecret
Cause: Invalid proof token type, valid values are computedKey and BinarySecret
Action: Check the proof token type, valid values are computedKey and BinarySecret

Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00221: Computed key in RSTR message sent by STS is invalid
Cause: Computed key in RSTR message sent by STS is invalid
Action: Check the computed key in RSTR message sent by STS

Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00222: Computed key algorithm in RSTR message sent by STS is invalid}
Cause: Computed key algorithm in RSTR message sent by STS is invalid, valid value is http://docs.oasis-open.org/ws-sx/ws-trust/200512/CK/PSHA1
Action: Check the computed key in RSTR message sent by STS, valid value is http://docs.oasis-open.org/ws-sx/ws-trust/200512/CK/PSHA1

Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00223: Request type is invalid, valid value is issue
Cause: Request type invalid, valid value is issue
Action: Check request type in response sent by STS

Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00224: User credentials of the user on behalf of whom the token is to be issued is missing
Cause: User credentials of the user on behalf of whom the token is to be issued is missing
Action: Check on.behalf.of property in issued token policy. If its set to true then either subject or sts.auth.on.behalf.of.csf-key property needs to be present

Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00225: STS On behalf of user password is invalid
Cause: STS On behalf of user password is invalid
Action: Configure sts.auth.on.behalf.of.csf.key in issued token policy

Level: 1

Type: ERROR

Impact: Configuration

WSM-00226: Security policy contains NULL or empty value for encrypted-element local name or namespace.
Cause: Security policy contains NULL or empty value for encrypted-element local name or namespace.
Action: Encrypted-element local name or namespace must not be null or empty.

Level: 1

Type: ERROR

Impact: Security

WSM-00227: Could not resolve key to use for decryption.
Cause: Could not resolve key to use for decryption.
Action: Ensure request contains all the information necessary to succesfully resolve decryption key.

Level: 1

Type: ERROR

Impact: Security

WSM-00228: Oracle system user is missing in identity store
Cause: Could not find oracle system user .
Action: Check if OracleSystemUser exists in identity store

Level: 1

Type: ERROR

Impact: Configuration

WSM-00229: jndi.lookup.csf.key missing in policy-accessor-config
Cause: Could not find valid jndi.lookup.csf.key in policy-accessor-config.xml .
Action: Check jndi.lookup.csf.key is configured correclty in policy-accessor-config.xml

Level: 1

Type: ERROR

Impact: Configuration

WSM-00230: Cannot find service information from WSDL {0}
Cause: Cannot find service information from WSDL
Action: Check the service information in the WSDL

Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00231: Cannot find client compatible policy for STS {0}, port name {1}
Cause: Cannot find compatible client policy for STS invocation
Action: Check if policy store has compatible client policy

Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00232: Failed to create dynamic STS policy
Cause: Failed to create dynamic STS policy
Action: Check exception stack trace for details

Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00233: STS WSDL URI {0} is invalid
Cause: STS trust config attribute wsdl-uri is not in the format of "http(s)://host:port/sts-service?wsdl".
Action: Provide valid attribute value which is in the format of "http(s)://host:port/sts-service?wsdl

Level: 1

Type: ERROR

Impact: Configuration

WSM-00234: The <saml:Assertion> element of version {0} is missing in the security header.
Cause: Saml assertion with specific version e.g. 1.1, or 2.0 etc. is missing. in the received message
Action: Check exception stack trace for details

Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00235: Failed to initialize dispatcher
Cause: Failed to initialize dispatcher for client to STS communication
Action: Check exception stack trace for details

Level: 1

Type: ERROR

Impact: Requests/Responses

WSM-00237: FKS keystore with stripeName {0}, keystoreName {1} can not be loaded due to {2}.
Cause: The following FKS keystore-related configuration properties may not be valid:keystore.type, keystore.pass, keystore.name. Also, check permissions on the keystore.
Action: Verify the configuration properties mentioned above and retry the operation.

Level: 1

Type: ERROR

Impact: Configuration

WSM-00238: Unable to read FKS keystore. Grant necessary permission to read FKS keystore, stripe name {0} and keystore name {1}
Cause: FKS keystore may have not been initialized or necessary permissions are not granted.
Action: Ensure that necessary permission to read FKS keystore is granted.

Level: 1

Type: ERROR

Impact: Configuration

WSM-00239: FKS trust store can not be loaded, ensure that necessary permissions are granted.
Cause: FKS trust store can not be loaded, probably necessary permissions are not granted.
Action: Ensure that necessary permission to read FKS trust store is granted.

Level: 1

Type: ERROR

Impact: Configuration

WSM-00240: FKS trust store is NULL, ensure that FKS system trust store exist.
Cause: FKS trust store is NULL, may be it doesn't exists or probably necessary permissions are not granted.
Action: Ensure that FKS trust store exists in system stripe and permissions are granted.

Level: 1

Type: ERROR

Impact: Configuration

WSM-00241: Failure retrieving FKS trust store aliases.
Cause: FKS trust store may have not been initialized.
Action: Check the log file for possible causes and retry the operation.

Level: 1

Type: ERROR

Impact: Configuration

WSM-00242: The certificates cannot be retrieved from the trust store.
Cause: Failure occurred while trying to retrieve certificate from trust store.
Action: Use a valid alias for the certificate and retry the operation.

Level: 1

Type: ERROR

Impact: Security

WSM-00243: Unable to read key from FKS keystore. Grant necessary permission to read alias {2} from FKS keystore, stripe name {0} and keystore name {1}
Cause: Unable to read key from FKS keystore. FKS keystore may have not been initialized or necessary permissions are not granted.
Action: Ensure that alias exists in keystore and necessary permission to read key alias is granted.

Level: 1

Type: ERROR

Impact: Configuration

WSM-00244: Unable to read certificate from FKS keystore. Grant necessary permission to read certificate alias {2} from FKS keystore, stripe name {0} and keystore name {1}
Cause: Unable to read certificate from FKS keystore. FKS keystore may have not been initialized or necessary permissions are not granted.
Action: Ensure that alias exists in keystore and necessary permission to read certificate alias is granted.

Level: 1

Type: ERROR

Impact: Configuration

WSM-00245: Failure retrieving FKS key store aliases.
Cause: Unable to list alias from FKS key store.
Action: Check the log file for possible causes and retry the operation.

Level: 1

Type: ERROR

Impact: Configuration

WSM-00246: Failure retrieving IssuedTokenAssertion from advertised policy.
Cause: Possibilly there is a failure in parsing the advertised policy
Action: Check the log file for possible causes and retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-00247: Failed to sign with RSA Key Pair
Cause: Failed to sign with RSA Key Pair
Action: Check exception stack trace for details

Level: 1

Type: ERROR

Impact: Security

WSM-00248: Attesting entity attribute {0} is unsupported.
Cause: Unsupported attesting entity attribute is used
Action: Attesting entity attribute must be DN.

Level: 1

Type: ERROR

Impact: Security

WSM-00249: SAML token DN validation failed for SAML assertion signer DN {0}.
Cause: SAML token DN list validation failed.
Action: Assertion signer DN is not present in trusted DN list, if DN is valid then add it to trusted DNs list.

Level: 1

Type: ERROR

Impact: Security

WSM-00250: Unable to find an implementation class for {0}.
Cause: Unable to find an implementation class for 'javax.el.ExpressionFactory'.
Action: Make sure that the implementation class for 'javax.el.ExpressionFactory' is available in the classpath.

Level: 1

Type: ERROR

Impact: Security

WSM-00251: Failed to create an instance of {0}.
Cause: Failed to create an instance of the javax.el.ExpressionFactory implementation class.
Action: Make sure that the javax.el.ExpressionFactory implementation class can be instantiated.

Level: 1

Type: ERROR

Impact: Security

WSM-00252: Failed to evaluate the constraint expression "{0}" due to the exception: {1}
Cause: Failed to evaluate the constraint expression.
Action: Make sure that the constraint expression is valid. Check exception stack trace for details.

Level: 1

Type: ERROR

Impact: Security

WSM-00253: The constraint expression "{0}" is not valid. The constraint expression should evaluate to the boolean values.
Cause: The constraint expression is not valid.
Action: Make sure that the constraint expression evaluates to the boolean values.

Level: 1

Type: ERROR

Impact: Security

WSM-00254: The current server time is "{0}", incoming message creation time is "{6}", configured agent expiry is {5} seconds, incoming message expiry is {7} seconds, effective message expiry (minimum of agent expiry and incoming message expiry) is {1} seconds, configured clock skew is {2} seconds. The acceptable time range is "{3}" to "{4}". The incoming message is before/after the acceptable time.
Cause: The incoming message is outside the valid range as allowed by clock skew and expiry times.
Action: Adjust times on servers/clients. Check the allowed clockskew and message expiration time and configure them as required.

Level: 1

Type: ERROR

Impact: Security

WSM-00257: Callback class name "{0}" set for SAML certificate validation not found
Cause: Callback class set for SAML certificate validation not found.
Action: Make sure that callback class name is correct and added in classpath.

Level: 1

Type: ERROR

Impact: Security

WSM-00258: Callback class name "{0}" set for SAML certificate validation is invalid.
Cause: Callback class set for SAML certificate validation is not valid.
Action: Make sure that callback class correctly extends required class.

Level: 1

Type: ERROR

Impact: Security

WSM-00259: SAML certificate validation callback failed. {0}.
Cause: Callback class set for SAML certificate validation failed.
Action: Check the error message for details.

Level: 1

Type: ERROR

Impact: Security

WSM-00260: SAML over SSL certificate validation failed because certificate returned from callback and actual certificate differ. Actual certificate DN={0} and callback cert DN={1}
Cause: SAML over SSL certificate validation failed because certificate returned from callback and actual certificate differ.
Action: Make sure that client certificate sent over SSL and certificate returned from callback are same.

Level: 1

Type: ERROR

Impact: Security

WSM-00261: SAML certificate validation callback failed because certificate returned from callback is NULL.
Cause: Callback class set for SAML certificate validation failed because certificate returned from callback is NULL.
Action: Check callback implementation class for the reason of null certificate.

Level: 1

Type: ERROR

Impact: Security

WSM-00262: SAML assertion with confirmation method {0} is missing inside signature.
Cause: SAML assertion is missing inside signature.
Action: Ensure that SAML assertion has required inside signature.

Level: 1

Type: ERROR

Impact: Security

WSM-00263: Failed to create SAML token as 'anonymous' user principal found in Subject.
Cause: Failed to create SAML token as 'anonymous' user principal found in Subject.
Action: Make sure that the subject is created from a valid user.

Level: 1

Type: ERROR

Impact: Security

WSM-00264: The Username token is missing in the security header. Ensure that there is a Username token policy attached on the client side. Tokens found in the security header are :- {0}.
Cause: Username token was expected in the security header but was not found.
Action: Username token is missing. Resend request with valid username token.

Level: 1

Type: ERROR

Impact: Security

WSM-00265: The Kerberos token is missing in the security header.
Cause: Kerberos token was expected in the security header but was not found.
Action: Resend request with valid kerberos token.

Level: 1

Type: ERROR

Impact: Security

WSM-00268: The certificate to be validated is NULL.
Cause: The certficate to be validated is null.
Action: Make sure that the certificate to be validated is not null.

Level: 1

Type: ERROR

Impact: Security

WSM-00269: There is no trusted certificate found in the trust store.
Cause: Trust store does not have any trusted certificate.
Action: Make sure that the required trusted certificates are present in the trust store.

Level: 1

Type: ERROR

Impact: Security

WSM-00270: The issuer "{0}" is not found in the trust store.
Cause: The issuer certificate is not present in the trust store.
Action: Make sure that the issuer certificate is present in the trust store.

Level: 1

Type: ERROR

Impact: Security

WSM-00271: Basic constraints check failed due to the certificate "{0}" is not a CA certificate.
Cause: The certificate is not a CA certificate.
Action: Make sure that the issuer certificate is a CA certificate.

Level: 1

Type: ERROR

Impact: Security

WSM-00272: Basic Constraints check failed for the certificate "{0}", since only an end-entity certificate may follow this certificate in the certification path chain.
Cause: Basic Constraints check failed for the issuer certificate.
Action: Make sure that the issuer certificate is a valid.

Level: 1

Type: ERROR

Impact: Security

WSM-00273: Failed to verify the issuer "{0}".
Cause: The issuer certificate verification failed.
Action: Check error logs for more details.

Level: 1

Type: ERROR

Impact: Security

WSM-00275: The Identity type "{0}" is not suported.
Cause: The Identity type published in the WSDL certificate is not supported.
Action: Make sure that the identity type published in the WSDL certificate is either X509Certificate or supported one.

Level: 1

Type: ERROR

Impact: Security

WSM-00276: Validation failed for the identity published in the WSDL endpoint "{1}". Caused By: {0}
Cause: Validation failed for the Identity published in the WSDL certificate.
Action: Check error logs for more details.

Level: 1

Type: ERROR

Impact: Security

WSM-00277: Endorsing signature is not found in the message. Ensure that a compatible policy is attached at the client side. The security policy "{1}" is attached to the service. Tokens found in the security header are :- {0}.
Cause: Endorsing signature is expected in the message but not found.
Action: Make sure that the endorsing signature is included in the message.

Level: 1

Type: ERROR

Impact: Security

WSM-00278: Failed to decrypt the encrypted key due to {1}. Ensure that the client is properly configured with the server certificate. Client should be using this certificate:- {0}.
Cause: An error occurred while decrypting the encrypted key.
Action: Ensure that the client is properly configured with the server's certificate.

Level: 1

Type: ERROR

Impact: Security

WSM-01501: failure in parsing the policy attachment
Cause: The XML was not well formed, or the XML did not follow the policy attachment schema.
Action: Ensure that the XML is well formed, and the XML follows the policy attachment schema.

Level: 1

Type: ERROR

Impact: Data

WSM-01502: failure in parsing the assertion template
Cause: The XML was not well formed, or the XML did not follow the assertion template schema.
Action: Ensure that the XML is well formed, and the XML follows the assertion template schema.

Level: 1

Type: ERROR

Impact: Data

WSM-01503: failure in parsing the assertion
Cause: The XML was not well formed, or the XML did not follow the assertion schema.
Action: Ensure that the XML is well formed, and the XML follows the assertion schema.

Level: 1

Type: ERROR

Impact: Data

WSM-01504: failure in parsing the property set configuration
Cause: The XML was not well formed, or the XML did not follow the property set Config schema.
Action: Ensure that the XML is well formed, and the XML follows the property set Config schema.

Level: 1

Type: ERROR

Impact: Data

WSM-01505: failure in creating a copy of the policy {0}
Cause: Copying of the policy failed.
Action: Ensure that the policy to be copied is valid. If the problem persists, contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-01506: failure in creating a copy of the assertion template {0}
Cause: Copying of the assertion template failed.
Action: Ensure that the assertion template to be copied is valid. If the problem persists, contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-01507: failure in creating a copy of the assertion {0}
Cause: Copying of the assertion failed.
Action: Ensure that the assertion to be copied is valid. If the problem persists, contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-01508: failure in transforming policy {0} to XML
Cause: The policy could not be serialized to XML.
Action: Ensure that the policy Java object can be serialized to XML format.

Level: 1

Type: ERROR

Impact: Data

WSM-01509: failure in transforming policy set {0} to XML
Cause: The policy set could not be serialized to XML.
Action: Ensure that the policy set Java object can be serialized to XML format.

Level: 1

Type: ERROR

Impact: Data

WSM-01510: failure in transforming policy attachment {0} to XML
Cause: The policy attachment could not be serialized to XML.
Action: Ensure that the policy attachment Java object can be serialized to XML format.

Level: 1

Type: ERROR

Impact: Data

WSM-01511: failure in transforming assertion template {0} to XML
Cause: The assertion template could not be serialized to XML.
Action: Ensure that the assertion template Java object can be serialized to XML format.

Level: 1

Type: ERROR

Impact: Data

WSM-01512: failure in transforming assertion {0} to XML
Cause: The assertion could not be serialized to XML.
Action: Ensure that the assertion Java object can be serialized to XML format.

Level: 1

Type: ERROR

Impact: Data

WSM-01513: failure in transforming configuration {0} to XML
Cause: The configuration could not be serialized to XML.
Action: Ensure that the configuration Java object can be serialized to XML format.

Level: 1

Type: ERROR

Impact: Data

WSM-01514: failure in transforming policy reference {0} to XML
Cause: System could not serialize policy reference to XML.
Action: Ensure passed policy reference Java object doesn't have issues that causes the serialization to XML to fail.

Level: 1

Type: ERROR

Impact: Data

WSM-01515: failure in transforming policy subject {0} to XML
Cause: System could not serialize policy subject to XML.
Action: Ensure passed policy subject Java object doesn't have issues that cause the serialization to XML to fail.

Level: 1

Type: ERROR

Impact: Data

WSM-01524: failure in serialization of WSDL
Cause: WSDL Serialization failed.
Action: Ensure WSDL Extensions are available and configured. Consult diagnostic log for details or contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-01526: WSDL Definition object is null
Cause: WSDL Definition Object is not available
Action: Ensure that a valid WSDL Definition object is sent to OWSM for advertisement of wsdl.

Level: 1

Type: ERROR

Impact: Data

WSM-01600: error in creating or initializing the assertion, key={0}, qname={1}, wspqname={2}, constructorName={3}
Cause: An assertion object could not be created.
Action: Verify that the assertion follows the interface requirements defined in the Oracle documentation.

Level: 1

Type: ERROR

Impact: Programmatic

WSM-01601: failure in loading the resource
Cause: The requested resource could not be loaded.
Action: Ensure that the requested resource is present in the class path.

Level: 1

Type: ERROR

Impact: Configuration

WSM-01602: error in loading class {0}
Cause: The requested class could not be loaded.
Action: Ensure that the requested class is present in the class path.

Level: 1

Type: ERROR

Impact: Programmatic

WSM-01603: failure in parsing the policy
Cause: Parsing of the policy failed.
Action: Ensure that the policy XML follows the policy schema, or a valid policy file exists.

Level: 1

Type: ERROR

Impact: Data

WSM-01604: XML Parser Configuration error
Cause: The XML Parser was not configured properly.
Action: Consult Oracle documentation or Java documentation on how to configure the XML Parser.

Level: 1

Type: ERROR

Impact: Configuration

WSM-01605: XML parser exception
Cause: Parsing of the XML failed.
Action: Ensure that the XML is well formed.

Level: 1

Type: ERROR

Impact: Data

WSM-01606: system I/O error
Cause: The system could not open the Input/Output streams.
Action: Consult the Java documentation.

Level: 1

Type: ERROR

Impact: Files

WSM-01607: XPath expression evaluation error
Cause: Evaluation of the XPATH expression failed.
Action: Ensure that the XPATH expression is valid, and the XML follows the schema.

Level: 1

Type: ERROR

Impact: Data

WSM-01608: The class cannot be found.
Cause: The requested class was not found in the class path.
Action: Ensure that the class name is correct in the configuration files and is in the class path.

Level: 1

Type: ERROR

Impact: Configuration

WSM-01610: cannot initialize standard serializers/deserializers
Cause: The standard serializer and deserializer objects could not be loaded.
Action: Ensure that the product configuration is correct. If the problem persists, contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-01611: The class cannot be loaded because of Java security restrictions.
Cause: The requested classes could not be loaded due to class loading security restrictions.
Action: Contact the site administrator or consult the Java documentation to ensure that the classes have the necessary Java security permissions.

Level: 1

Type: ERROR

Impact: Configuration

WSM-01612: An instance of the requested class cannot be created.
Cause: The system could not create an instance of the requested class.
Action: Consult the Java documentation or contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-01613: The XML parser cannot be configured.
Cause: The XML parser could not be configured.
Action: Consult the Java documentation on how to configure the XML parser.

Level: 1

Type: ERROR

Impact: Configuration

WSM-01614: The assertion XML Java Document cannot be serialized to a String.
Cause: The assertion XML Java Document could not be serialized to a String.
Action: Check the assertion for any errors and retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-01615: The assertion XML String cannot be converted to a Java object.
Cause: The assertion XML String could not converted to a Java Document.
Action: Ensure that the String being converted to XML is a well-formed XML.

Level: 1

Type: ERROR

Impact: Data

WSM-01616: Policy {0} cannot be inserted into the WSDL.
Cause: The WSDL extensions for the policy could not be found or were incorrectly configured.
Action: Ensure that the WSDL extensions for the policy being injected are available and configured. Consult Oracle documentation for more information.

Level: 1

Type: ERROR

Impact: Data

WSM-01617: error in parsing the policies embedded in the WSDL
Cause: The WSDL extensions for the policy could not be found or were incorrectly configured.
Action: Ensure that the WSDL extensions for policy are available and configured. Consult Oracle documentation for more information.

Level: 1

Type: ERROR

Impact: Data

WSM-01618: error in parsing the policy references embedded in the WSDL
Cause: The XML for the policy references in the WSDL could not be parsed.
Action: Ensure that the WSDL extensions for the policy reference are available and configured. Consult Oracle documentation for more information.

Level: 1

Type: ERROR

Impact: Data

WSM-01619: This assertion type is not recognized.
Cause: The assertion type was not recognized.
Action: Consult Oracle documentation for the supported assertion types.

Level: 1

Type: ERROR

Impact: Data

WSM-01620: cannot convert XML Java Document to String
Cause: The XML Java Document being converted was not well formed.
Action: Ensure that the assertions can be serialized to a String.

Level: 1

Type: ERROR

Impact: Data

WSM-01621: Policy intersection algorithm is not defined for assertion type :
Cause: The policy intersection algorithm was not found for the assertion.
Action: Ensure that the intersection algorithm for the assertion used is configured.

Level: 1

Type: ERROR

Impact: Data

WSM-01622: Policy merge algorithm is not defined for assertion type :
Cause: The policy merge algorithm was not found for the assertion.
Action: Ensure that the merge algorithm for the assertion used is configured.

Level: 1

Type: ERROR

Impact: Data

WSM-01623: Policy reference cannot be resolved :
Cause: The policy reference was invalid.
Action: Ensure that the policy reference is valid.

Level: 1

Type: ERROR

Impact: Data

WSM-01624: The policy does not exist in the policy store :
Cause: The policy reference was invalid, or the referenced policy could not be retrieved.
Action: Ensure that the policy reference is valid, and the policy exists in the policy store.

Level: 1

Type: ERROR

Impact: Data

WSM-01625: The Name attribute of the property is missing.
Cause: The Name attribute for a property was missing.
Action: Provide a value for the Name attribute.

Level: 1

Type: ERROR

Impact: Data

WSM-01626: The Type attribute of the property is missing.
Cause: The Type attribute for a property was missing.
Action: Provide a value for the Type attribute.

Level: 1

Type: ERROR

Impact: Data

WSM-01627: The assertion contains too many bindings.
Cause: The assertion contained more than one binding.
Action: Ensure that the assertion contains a single binding.

Level: 1

Type: ERROR

Impact: Data

WSM-01628: The policy normalization algorithm is not defined for this assertion type
Cause: The policy normalization algorithm was not found for the assertion.
Action: Ensure that the normalization algorithm for the assertion used is configured.

Level: 1

Type: ERROR

Impact: Data

WSM-01629: The assertion template contains too many assertions.
Cause: The assertion template contained more than one assertion.
Action: Ensure that assertion template contains only one assertion.

Level: 1

Type: ERROR

Impact: Data

WSM-01630: Element {0} is not a known policy element.
Cause: XML parsing failed; the system encountered unsupported XML elements.
Action: Ensure that the XML follows the schema, and the XML contains only those elements that are supported.

Level: 1

Type: ERROR

Impact: Data

WSM-01631: The assertion {0} contains multiple bindings.
Cause: The assertion contained more than one binding.
Action: Ensure that the assertion contains only one binding.

Level: 1

Type: ERROR

Impact: Data

WSM-01632: The assertion {0} contains multiple policies as child elements.
Cause: The assertion contained more than one policy child element.
Action: Ensure that the assertion contains only one policy child element.

Level: 1

Type: ERROR

Impact: Data

WSM-01633: Assertion type {0} does not match the corresponding Java Object type created.
Cause: The assertion type was incorrectly defined for the assertion.
Action: Ensure that the correct assertion type is set for the assertion.

Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-01635: Passed Java Object {0} does not extend the Assertion class
Cause: The Assertion class did not extend the correct classes.
Action: Consult Oracle Documentation for creating assertion implementations.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-01636: The assertion type {0} is not supported.
Cause: The assertion type does not match any of the predefined assertion types.
Action: Ensure that the assertion type is supported.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-01637: The policy attachment cannot be parsed.
Cause: The policy attachment XML was invalid.
Action: Ensure that policy attachment XML follows the policy attachment XML schema.

Level: 1

Type: ERROR

Impact: Data

WSM-01638: The policy attachment is not valid because the domain is not specified.
Cause: The policy attachment did not contain domain expressions.
Action: Ensure that policy attachment XML follows the policy attachment XML schema.

Level: 1

Type: ERROR

Impact: Data

WSM-01640: The policy reference {0} is not valid.
Cause: The policy reference could not be resolved.
Action: Ensure that the referenced policy exists in the policy store.

Level: 1

Type: ERROR

Impact: Data

WSM-01641: The policy advertisement level is not specified for the policy.
Cause: The policy advertisement level was not specified.
Action: Ensure that a valid value is set for the policy advertisement level.

Level: 1

Type: ERROR

Impact: Configuration

WSM-01642: Policy advertisement is not supported for unsupported WSDL elements.
Cause: Policy advertisement was not supported for the WSDL object.
Action: Consult Oracle documentation for supported WSDL objects.

Level: 1

Type: ERROR

Impact: Data

WSM-01643: What the XML system expects is different from what is encountered.
Cause: Usage of system was invalid or the feature was unsupported.
Action: Consult Documentation on usage and supported features.

Level: 1

Type: ERROR

Impact: Data

WSM-01644: The WSDL object {0} is not supported.
Cause: The WSDL object was not supported.
Action: Consult Oracle documentation for the supported WSDL objects.

Level: 1

Type: ERROR

Impact: Data

WSM-01645: The resource pattern {0} does not match the corresponding WSDL object.
Cause: WSDL Objects did not match.
Action: Ensure that the WSDL Objects match.

Level: 1

Type: ERROR

Impact: Data

WSM-01646: The value for the attachTo attribute of the policy is not valid.
Cause: The attachTo attribute of the policy did not match any of the predefined attachTo values.
Action: Consult Oracle documentation for the valid values for the attachTo attribute.

Level: 1

Type: ERROR

Impact: Data

WSM-01647: There are no policies that match the specified category {0} and resource pattern {1}.
Cause: No policies matched the specified search criteria.
Action: Ensure that the policies that match the search categories exist in the policy store.

Level: 1

Type: ERROR

Impact: Data

WSM-01650: cannot construct policy object
Cause: Construction of the policy Java object failed.
Action: Consult the diagnostic log for details.

Level: 1

Type: ERROR

Impact: Programmatic

WSM-01651: cannot advertise requested policies
Cause: Advertisement of the policies failed.
Action: Consult the diagnostic log for details, or contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Programmatic

WSM-01652: error in parsing the time stamp in the policy set document
Cause: The Timestamp attribute in the XML representation of a policy set document is not a valid number.
Action: Correct or remove the invalid attribute value.

Level: 1

Type: NOTIFICATION

Impact: Data

WSM-01653: The assertion contains more than one Guard element.
Cause: The assertion contained more than one guard.
Action: Ensure that the assertion contains a single guard.

Level: 1

Type: ERROR

Impact: Data

WSM-01654: failure in serialization of security scenario assertion
Cause: The SecurityScenario in OraPolicy could not be serialized or was incorrectly configured.
Action: Ensure that the OraPolicy is correct. Consult Oracle documentation for more information.

Level: 1

Type: ERROR

Impact: Data

WSM-01655: There are no policies that match the specified category {0}.
Cause: No policies matched the specified category.
Action: Ensure that the policies that match the search category exist in the policy store.

Level: 1

Type: ERROR

Impact: Data

WSM-01656: generic Oracle WSM Policy Manager error
Cause: An internal error occurred during the Policy related operation.
Action: Retry the operation. If the problem persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Data

WSM-01657: Oracle WSM Advertisement Engine must be initialized with valid properties. Following properties [{0}] are either empty or null
Cause: WSM Advertisement Engine initialized with invalid parameters.
Action: Ensure that valid parameters are set during WSM Advertisement Engine configuration

Level: 1

Type: ERROR

Impact: Configuration

WSM-01658: X509 Certificate will not be advertised as {0} not found
Cause: Implementation class for advertising X509 Certificate in WSDL is not available
Action: Ensure that implementation class required for advertising X509 Certificate in WSDL is not available. Consult diagnostic log for details or contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Other

WSM-01659: A JAXBContext cannot be created due to underlying exception "{0}".
Cause: One or more expected classes could not be located.
Action: Retry the operation. If the problem persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Data

WSM-01660: A JAXB unmarshaller cannot be created due to underlying exception "{0}".
Cause: An error occurred while creating an unmarshaller.
Action: Retry the operation. If the problem persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Data

WSM-01661: A string cannot be unmarshalled into an object due to underlying exception "{0}".
Cause: The string is not suitable for unmarshalling to the requested type.
Action: Provide a string that is suitable for unmarshalling to the requested type.

Level: 1

Type: ERROR

Impact: Data

WSM-01662: The QName "{0}" does not match the expected QName "{1}" for the unmarshalled object.
Cause: The string is not suitable for unmarshalling to the requested type.
Action: Provide a string that is suitable for unmarshalling to the requested type.

Level: 1

Type: ERROR

Impact: Data

WSM-01663: A null or empty string cannot be unmarshalled into an Intent object.
Cause: An attempt was made to unmarshall an Intent from a null or empty String.
Action: Provide a String that contains a marshalled Intent.

Level: 1

Type: ERROR

Impact: Data

WSM-01664: A null or empty string cannot be unmarshalled into a PolicySet object.
Cause: An attempt was made to unmarshall a PolicySet from a null or empty String.
Action: Provide a String that contains a marshalled PolicySet.

Level: 1

Type: ERROR

Impact: Data

WSM-01665: A JAXB marshaller cannot be created due to underlying exception "{0}".
Cause: An error occurred while creating a marshaller.
Action: Retry the operation. If the problem persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Data

WSM-01666: An object cannot be marshalled to a string due to underlying exception "{0}".
Cause: Marshalling the supplied type of the object is not supported.
Action: Provide an object of a supported type.

Level: 1

Type: ERROR

Impact: Data

WSM-01667: An object cannot be marshalled to a DOM object due to underlying exception "{0}".
Cause: Marshalling the supplied type of the object is not supported.
Action: Provide an object of a supported type.

Level: 1

Type: ERROR

Impact: Data

WSM-01668: A null Intent object cannot be marshalled.
Cause: An attempt was made to marshall a null Intent object.
Action: Provide a non-null Intent object.

Level: 1

Type: ERROR

Impact: Data

WSM-01669: A null PolicySet object cannot be marshalled.
Cause: An attempt was made to marshall a null PolicySet object.
Action: Provide a non-null PolicySet object.

Level: 1

Type: ERROR

Impact: Data

WSM-01670: An object cannot be marshalled into a null DOM object.
Cause: An attempt was made to marshall an object into a null Document object.
Action: Provide a non-null Document object.

Level: 1

Type: ERROR

Impact: Data

WSM-01671: The DOM element cannot be null for policy subject identified by the resource pattern: "{0}".
Cause: The null DOM element was passed.
Action: Pass a valid non-null DOM element.

Level: 1

Type: ERROR

Impact: Compliance

WSM-01672: The policy reference URI: "{1}" for policy subject identified by the resource pattern: "{0}" cannot be empty.
Cause: Empty policy references were found in the DOM element node.
Action: Verify the DOM element node and make sure the policy references specify a valid value and the referenced policies exist in the repository.

Level: 1

Type: ERROR

Impact: Compliance

WSM-01673: Duplicate policy references: "{1}" are found for policy subject identified by resource pattern "{0}".
Cause: Duplicate policy references were found in the same DOM element node.
Action: Remove the duplicate policy references from the DOM element node.

Level: 1

Type: ERROR

Impact: Compliance

WSM-01674: The DOM element: "{1}" for policy subject identified by resource pattern "{0}" is unsupported element.
Cause: Policies cannot be retrieved for unsupported DOM element node.
Action: Verify that a supported DOM element node is provided for retrieving the policy.

Level: 1

Type: WARNING

Impact: Compliance

WSM-01675: The policy references cannot be null.
Cause: A null policy reference was passed.
Action: Pass the valid non-null policy reference object.

Level: 1

Type: ERROR

Impact: Compliance

WSM-01676: The resource pattern cannot be null.
Cause: A null resource pattern was passed.
Action: Pass a valid non-null resource pattern.

Level: 1

Type: ERROR

Impact: Compliance

WSM-01677: The domain expression cannot be null.
Cause: A null domain expression was passed.
Action: Pass a valid non-null domain expression.

Level: 1

Type: ERROR

Impact: Compliance

WSM-01678: Element {0} is not a valid child element for Policy object.
Cause: Invalid child element found for Policy object.
Action: Check the policy string being parsed and make sure only valid child elements are present for the Policy.

Level: 1

Type: ERROR

Impact: Data

WSM-01679: A DOM node cannot be unmarshalled into an object due to underlying exception "{0}".
Cause: The string is not suitable for unmarshalling to the requested type.
Action: Provide a string that is suitable for unmarshalling to the requested type.

Level: 1

Type: ERROR

Impact: Data

WSM-01680: A null node cannot be unmarshalled into a RepositoryInfo object.
Cause: An attempt was made to unmarshall a RepositoryInfo from a null node.
Action: Provide a node that contains a marshalled RepositoryInfo.

Level: 1

Type: ERROR

Impact: Data

WSM-01681: A null or empty string cannot be unmarshalled into a RepositoryInfo object.
Cause: An attempt was made to unmarshall a RepositoryInfo from a null or empty String.
Action: Provide a String that contains a marshalled RepositoryInfo.

Level: 1

Type: ERROR

Impact: Data

WSM-01682: A null RepositoryInfo object cannot be marshalled.
Cause: An attempt was made to marshall a null RepositoryInfo object.
Action: Provide a non-null RepositoryInfo object.

Level: 1

Type: ERROR

Impact: Data

WSM-01683: The passed String "{0}" could not be parsed using UTF encoding.
Cause: Underlying JVM does not support UTF-8 encoding.
Action: Check the JVM configuration to make sure it supports UTF-8 encoding format.

Level: 1

Type: ERROR

Impact: Data

WSM-01684: A null or empty string cannot be unmarshalled into a Policy object.
Cause: An attempt was made to unmarshall a Policy from a null or empty String.
Action: Provide a String that contains a marshalled Policy.

Level: 1

Type: ERROR

Impact: Data

WSM-01685: Issuer Uri is not available. Either sts_trust_config_service_policy is not attached to service or the Issuer Uri is missing from the policy. Ignore this warning if sts_trust_config_client_policy is attached to client.
Cause: Issuer Uri is not available. Either sts_trust_config_service_policy is not attached to service or the Issuer Uri is missing from the policy. Ignore this warning if sts_trust_config_client_policy is attached to client.
Action: Attach sts_trust_config_service_policy if not attached yet, or specify issuer uri value in the policy if not specified. Ignore if using sts_trust_config_client_policy.

Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-01686: Advertisement failed due to an unexpected assertion type: {0}.
Cause: The assertion type is not recognized.
Action: Internal error. Provide

Level: 1

Type: ERROR

Impact: Configuration

WSM-01687: The constant property "{0}" cannot be overriden.
Cause: There is an attempt to override a property value which is defined as a constant in the policy.
Action: Ensure that there is no attempt to override a constant property.

Level: 1

Type: WARNING

Impact: Configuration

WSM-01688: X509 Certificate will not be advertised due to underlying exception "{0}".
Cause: Either the keystore was not available or the keystore configuration was incorrect.
Action: Ensure the keystore exists and that the keystore password and aliases are correct.

Level: 1

Type: WARNING

Impact: Configuration

WSM-01689: Advertisement failed due to an incorrect ws-policy/ws-securitypolicy specification version {0}/{1}.
Cause: Invalid ws-policy/ws-securitypolicy specification version used to advertise policy.
Action: Ensure the ws-policy/ws-securitypolicy specification versions are correct.

Level: 1

Type: WARNING

Impact: Configuration

WSM-01690: Assertion {0} located by QName {1} is not an instanceof type {2}.
Cause: An internal error, probably policy was not deserialized into the correct assertion instance.
Action: Consult diagnostic log for details or contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-01691: Cannot construct policy object for policy "{0}" due to underlying exception "{1}".
Cause: Construction of the policy Java object failed for the given policy name.
Action: Consult the diagnostic log for details.

Level: 1

Type: ERROR

Impact: Programmatic

WSM-01692: Advertisement failed due to multiple ws-policy specification version specified.
Cause: Multiple ws-policy specification version used to advertise policy.
Action: Remove the duplicate ws-policy specification versions and try again.

Level: 1

Type: WARNING

Impact: Configuration

WSM-01693: Advertisement failed due to multiple wssecurity-policy specification version specified.
Cause: Multiple ws-securitypolicy specification version used to advertise policy.
Action: Remove the duplicate ws-securitypolicy specification versions and try again.

Level: 1

Type: WARNING

Impact: Configuration

WSM-01751: The name of an assertion property is empty.
Cause: The name of an assertion property was empty.
Action: Make sure that you specify a name for all assertion properties.

Level: 1

Type: ERROR

Impact: Data

WSM-01752: The data type of the value does not match the data type of property {0}. The expected data type is String.
Cause: The datatype of the property value entered was not of type String.
Action: Make sure that the data type for the property value is of type String.

Level: 1

Type: ERROR

Impact: Data

WSM-01753: The data type of the value does not match the data type of property {0}. The expected data type is Boolean.
Cause: The data type of the property value entered was not of type Boolean.
Action: Make sure that the data type for the property value is of type Boolean.

Level: 1

Type: ERROR

Impact: Data

WSM-01754: The data type of the value does not match the data type of property {0}. The expected data type is Integer.
Cause: The data type of the property value entered was not of type Integer.
Action: Make sure that the data type for the property value is of type Integer.

Level: 1

Type: ERROR

Impact: Data

WSM-01755: An empty value is specified for property {0}.
Cause: An empty value was specified for a property that has a data type of type Password.
Action: Specify a value for all properties that have a data type of type Password.

Level: 1

Type: ERROR

Impact: Data

WSM-01756: The "Property Set Name" field is empty.
Cause: The Property Set Name field in one of the assertions was empty.
Action: Make sure that you specify a name for all assertion property sets.

Level: 1

Type: ERROR

Impact: Data

WSM-01757: The name attribute for the "Config" element is empty.
Cause: The name for the Config element was empty.
Action: Make sure that a name is specified for the Config element.

Level: 1

Type: ERROR

Impact: Data

WSM-01758: The assertion name is empty.
Cause: The assertion name was empty.
Action: Make sure that the assertion name is specified.

Level: 1

Type: ERROR

Impact: Data

WSM-01759: The policy ID is empty.
Cause: The policy ID was empty.
Action: Make sure that the policy ID is specified.

Level: 1

Type: ERROR

Impact: Data

WSM-01760: The policy name is empty.
Cause: The policy name was empty.
Action: Make sure that the policy name is specified.

Level: 1

Type: ERROR

Impact: Data

WSM-01761: Specifying a policy ID for a child policy is not permitted : {0}.
Cause: Policy ID must not be specified for child policies.
Action: Remove the policy ID of the child policy.

Level: 1

Type: NOTIFICATION

Impact: Data

WSM-01762: Specifying a policy name for a child policy is not permitted : {0}.
Cause: Policy name must not be specified for child policies.
Action: Remove the policy name of the child policy.

Level: 1

Type: NOTIFICATION

Impact: Data

WSM-01763: The value specified for the policy attachTo attribute {0}, does not match any of the supported values.
Cause: The value specified for the policy attachTo attribute did not match any of the supported values.
Action: Specify a valid value for the attachTo attribute. Consult the Oracle documentation for the supported values.

Level: 1

Type: ERROR

Impact: Data

WSM-01764: The value specified for the policy category {0} does not match any of the supported values.
Cause: The value specified for policy category attribute did not match any of the supported values.
Action: Specify a valid value for the category attribute. Consult the Oracle documentation for the supported values.

Level: 1

Type: ERROR

Impact: Data

WSM-01765: The data type of the value specified for property {0} is not supported.
Cause: The data type specified for the property did not match any of the supported data types.
Action: Specify a valid data type for the property. Consult the Oracle documentation for the supported data types.

Level: 1

Type: ERROR

Impact: Data

WSM-01766: The assertion template ID cannot be empty.
Cause: The assertion template ID was empty.
Action: Specify a value for assertion template ID.

Level: 1

Type: ERROR

Impact: Data

WSM-01767: The assertion template name cannot be empty.
Cause: The assertion template name was empty.
Action: Specify a value for the assertion template name.

Level: 1

Type: ERROR

Impact: Data

WSM-01768: The value specified for the assertion template attachTo attribute {0} does not match any of the supported values.
Cause: The value specified for the assertion template attachTo attribute did not match any of the supported values.
Action: Specify a valid value for the attachTo attribute. Consult the Oracle documentation for the supported values.

Level: 1

Type: ERROR

Impact: Data

WSM-01769: The value specified for the assertion template category {0} does not match any of the supported values.
Cause: The value specified for the assertion template category attribute did not match any of the supported values.
Action: Specify a valid value for the category attribute. Consult the Oracle documentation for the supported values.

Level: 1

Type: ERROR

Impact: Data

WSM-01770: A value or default value is not specified for property {0}.
Cause: No value or default value was specified for the property.
Action: Specify a value or a default value for the property.

Level: 1

Type: ERROR

Impact: Data

WSM-01771: Attaching multiple reliable messaging policies is not supported. Only one reliable messaging policy can be attached to a policy subject
Cause: More than one reliable messaging policy was attached to a policy subject.
Action: Make sure that only one reliable messaging policy is attached to a policy subject.

Level: 1

Type: ERROR

Impact: Data

WSM-01772: Attaching multiple Message Transmission Optimization Mechanism (MTOM) policies is not supported. Only one MTOM policy can be attached to a policy subject.
Cause: More than one MTOM policy was attached to a policy subject.
Action: Make sure that only one reliable MTOM is attached to a policy subject.

Level: 1

Type: ERROR

Impact: Data

WSM-01773: Attaching multiple WS-Addressing policies is not supported. Only one WS-Addressing policy can be attached to a policy subject.
Cause: The user attached more than one WS-Addressing policy.
Action: Make sure that only one reliable WS-Addressing is attached to a policy subject.

Level: 1

Type: ERROR

Impact: Data

WSM-01774: The policy "{0}" cannot be attached to policy subject "{1}" having unsupported subject type "{2}".
Cause: A policy was attached to an unsupported policy subject.
Action: Make sure that the policy subject supports policy attachment. Consult the Oracle documentation for the supported values.

Level: 1

Type: ERROR

Impact: Data

WSM-01775: The policy "{0}" cannot be attached to policy subject "{1}" having subject type "{2}" since it may only be used with "{3}".
Cause: An incompatible policy was attached to the policy subject.
Action: Make sure that the attached policy is compatible with the policy subject.

Level: 1

Type: ERROR

Impact: Data

WSM-01776: The policy reference "{0}" is invalid.
Cause: The policy reference was invalid because the policy did not exist.
Action: Make sure that the referenced policy exists in the policy store.

Level: 1

Type: ERROR

Impact: Data

WSM-01777: Attaching multiple authorization security policies is not supported. Only one authorization security policy can be attached to a policy subject.
Cause: More than one authorization security policy was attached to a policy subject.
Action: Make sure that only one authorization security policy is attached to a policy subject.

Level: 1

Type: ERROR

Impact: Data

WSM-01778: Attaching multiple authentication security policies is not supported. Only one authentication security policy can be attached to a policy subject.
Cause: More than one authentication security policy was attached to a policy subject.
Action: Make sure that only one authentication security policy is attached to a policy subject.

Level: 1

Type: ERROR

Impact: Data

WSM-01779: Attaching multiple message protection security policies is not supported. Only one message protection security policy can be attached to a policy subject.
Cause: More than one message protection security policy was attached to a policy subject.
Action: Make sure that only one message protection security policy is attached to a policy subject.

Level: 1

Type: ERROR

Impact: Data

WSM-01780: The policy reference category and the policy category do not match.
Cause: There was a mismatch between the policy reference category and the policy category.
Action: Ensure that the policy reference category matches the policy category.

Level: 1

Type: ERROR

Impact: Data

WSM-01781: Validation failure due to generic error.
Cause: A generic internal error occurred.
Action: Consult the diagnostic logs for details.

Level: 1

Type: ERROR

Impact: Data

WSM-01782: Policy contains no assertions. A policy must contain at least one assertion.
Cause: The policy did not contain any assertions.
Action: Make sure that the policy contains at least one assertion.

Level: 1

Type: ERROR

Impact: Data

WSM-01783: Guard does not contain any of the three elements of resource-match, action-match and constraint-match.
Cause: Guard does not contain any of the three elments of resource-match, action-match and constraint-match.
Action: Make sure that at least one of three elements of resource-match, action-match and constraint-match is specified with its corresponding value in the Guard element.

Level: 1

Type: ERROR

Impact: Data

WSM-01784: Validation not supported for Custom Documents. Only a Policy or PolicySet can be validated.
Cause: Validation is not supported for Custom Documents.
Action: Ensure that the document is either a Policy or a PolicySet.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-01785: Signing or encryption of the soap fault is not supported.
Cause: The soap fault is to be signed or encrypted.
Action: Make sure that the soap fault is not to be signed or encrypted.

Level: 1

Type: ERROR

Impact: Data

WSM-01801: The type of resources expression is empty or missing.
Cause: The value specified for the appliesTo attribute was empty.
Action: Specify a valid non-empty value for the appliesTo attribute.

Level: 1

Type: ERROR

Impact: Data

WSM-01802: The type of resources expression "{0}" is not supported.
Cause: The value specified for the appliesTo attribute was invalid.
Action: Specify a valid value for the appliesTo attribute.

Level: 1

Type: ERROR

Impact: Data

WSM-01811: The attachment expression is empty or missing. A non-empty expression with a function is expected.
Cause: The value specified for the attachTo attribute was empty.
Action: Specify a valid, non-empty value for the attachTo attribute.

Level: 1

Type: ERROR

Impact: Data

WSM-01812: The function "{2}" at index {1} in attachment expression "{0}" is empty. A function requires a non-empty value.
Cause: The argument for a function was missing or empty.
Action: Specify a valid, non-empty value for the function argument.

Level: 1

Type: ERROR

Impact: Data

WSM-01813: The function "{2}" at index {1} in attachment expression "{0}" duplicates a previous function. A function may only appear once in an expression.
Cause: A function appeared more than once in an attachment expression.
Action: Remove the duplicated function from the expression.

Level: 1

Type: ERROR

Impact: Data

WSM-01814: The function "{2}" is not expected at index {1} in attachment expression "{0}". An operator is expected at this point.
Cause: A function was found in an attachment expression where an operator was expected.
Action: Specify the "and" operator between each function.

Level: 1

Type: ERROR

Impact: Data

WSM-01815: A function is expected at index {1} in attachment expression "{0}".
Cause: The attachment expression ended with an operator.
Action: Remove the dangling operator or add the missing function.

Level: 1

Type: ERROR

Impact: Data

WSM-01816: The operator "{2}" at index {1} in attachment expression "{0}" is not supported. "and" is the only supported operator.
Cause: An unrecognized operator was found in an attachment expression.
Action: Specify the "and" operator between each function.

Level: 1

Type: ERROR

Impact: Data

WSM-01817: The text "{2}" at index {1} in attachment expression "{0}" is not expected. A function is expected at this point.
Cause: An unrecognized block of text was found in an attachment expression where a function was expected.
Action: Specify a valid function in the expression.

Level: 1

Type: ERROR

Impact: Data

WSM-01818: The text "{2}" at index {1} in attachment expression "{0}" is unrecognized. The operator "and" is expected at this point.
Cause: An unrecognized block of text was found in an attachment expression where an operator was expected.
Action: Specify the "and" operator between each function.

Level: 1

Type: ERROR

Impact: Data

WSM-01821: The function "{0}" in attachment expression "{1}" is incompatible with "{2}" type of resources.
Cause: A function was found in an attachment expression that is not usable with the type of resource.
Action: Specify a function that is compatible with the associated type of resource.

Level: 1

Type: ERROR

Impact: Data

WSM-01822: The function "{0}" in attachment expression "{1}" is not supported for attachment.
Cause: A function was found in an attachment expression that is not usable for attachment.
Action: Specify a function that is compatible with the associated type of resource.

Level: 1

Type: ERROR

Impact: Data

WSM-02000: Cannot retrieve assertion template {0}.
Cause: A failure occurred while retrieving the assertion template from the data store.
Action: Retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-02001: Cannot serialize XML to policy attachment.
Cause: The policy attachment XML was not well formed, or the XML did not follow the policy attachment schema.
Action: Ensure that the XML is well formed, and the XML follows the policy attachment schema.

Level: 1

Type: ERROR

Impact: Data

WSM-02002: Cannot retrieve policies.
Cause: A failure occurred while retrieving policies from the data store.
Action: Retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-02003: Cannot retrieve policy references for resource pattern {0}.
Cause: A failure occurred while retrieving policy references from the data store.
Action: Retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-02004: Cannot search policies for condition {0}.
Cause: A failure occurred while searching for policies in the data store.
Action: Retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-02005: Cannot perform policy compatibility check for policies {0}.
Cause: An internal error was encountered while performing the policy compatibility check.
Action: Contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02006: Cannot add policies {0} to data store.
Cause: A failure occurred while adding policies to the data store.
Action: Retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-02007: Cannot delete assertion templates {0}.
Cause: A failure occurred while deleting assertion templates from the data store.
Action: Retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-02008: Cannot delete policies {0}.
Cause: A failure occurred while deleting policies from the data store.
Action: Retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-02009: Cannot delete all assertion templates from the data store.
Cause: A failure occurred while deleting all assertion templates from the data store.
Action: Retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-02010: Unable to delete all policies from the data store.
Cause: A failure occurred while deleting all policies from the data store.
Action: Retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-02011: Cannot delete assertion template {0}.
Cause: A failure occurred while deleting the specified assertion template from the data store.
Action: Retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-02012: Cannot delete policy {0}.
Cause: A failure occurred while deleting the specified policy from the data store.
Action: Retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-02013: Cannot retrieve policy configuration {0}.
Cause: A failure occurred while retrieving the policy configuration.
Action: Check the policy configuration, and retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-02014: The value for the attachTo attribute {0} is not valid.
Cause: The value for the attachTo attribute is not valid.
Action: Consult Oracle documentation for the valid values for the attachTo attribute.

Level: 1

Type: ERROR

Impact: Data

WSM-02015: Cannot retrieve object(s) due to Java RuntimeException.
Cause: The unexpected RuntimeException was encountered while trying to access data store.
Action: Check the log file for possible causes, and retry the operation.

Level: 1

Type: WARNING

Impact: Data

WSM-02016: Cannot retrieve timestamp for the last data store update.
Cause: A problem occurred while accessing the repository.
Action: Examine the logs for the cause of the failure.

Level: 1

Type: WARNING

Impact: Data

WSM-02017: Cannot retrieve the document from the repository.
Cause: The document was not found in the repository.
Action: Verify that the document exist in the reository..

Level: 1

Type: WARNING

Impact: Data

WSM-02044: Cannot save assertion template {0} to data store.
Cause: Another process was trying to update the same assertion template.
Action: Ensure that no other process is trying to update the same assertion template object and retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-02045: Cannot delete policy version from data store.
Cause: Failure occurred while deleting policy versions from the data store.
Action: Retry the operation.

Level: 1

Type: ERROR

Impact: Configuration

WSM-02046: Cannot delete assertion template versions from data store.
Cause: Failure occurred while deleting assertion template versions from the data store.
Action: Retry the operation.

Level: 1

Type: ERROR

Impact: Configuration

WSM-02047: Unable to create multiple policies.
Cause: Failure occurred while creating multiple policies
Action: Retry the operation.

Level: 1

Type: ERROR

Impact: Configuration

WSM-02048: Unable to update multiple policies.
Cause: Failure occurred while updating multiple policies.
Action: Retry the operation.

Level: 1

Type: ERROR

Impact: Configuration

WSM-02049: Unable to update the assertion template.
Cause: Failure occurred while updating an assertion template.
Action: Retry the operation.

Level: 1

Type: ERROR

Impact: Configuration

WSM-02050: Unable to set the older version of a policy as the latest version.
Cause: Failure occurred while setting an older version of a policy as the latest version.
Action: Retry the operation.

Level: 1

Type: ERROR

Impact: Configuration

WSM-02051: Unable to add resources to policy attachment.
Cause: Failure occurred while trying to add resources to a policy attachment.
Action: Retry the operation.

Level: 1

Type: ERROR

Impact: Configuration

WSM-02052: Unable to remove resources from policy attachment.
Cause: Failure occurred while trying to remove resources from policy attachment.
Action: Retry the operation.

Level: 1

Type: ERROR

Impact: Configuration

WSM-02053: Unable to set the older version of a policy as the latest version.
Cause: Failure occurred while setting an older version of a policy as the latest version.
Action: Retry the operation.

Level: 1

Type: ERROR

Impact: Configuration

WSM-02054: Failure in looking up EJB component {0}.
Cause: Failure occurred in looking up requested component on the application server.
Action: Make sure that the right configuration is passed for the EJB lookup and retry the operation.

Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-02055: Failure calculating smart digest for policy {0}
Cause: Failure occurred in calculating smart digest when updating or creating policy.
Action: You can ignore this message or you can retry the operation. Increase the log levels for more details as to the underlying cause for the smart digest calculation failure.

Level: 1

Type: WARNING

Impact: Data

WSM-02056: Unable to locate the RMI port for communication
Cause: Failure occurred when looking up RMI port for the application server.
Action: Confirm that the RMI port settings are correct in the application server configuration and retry the operation.

Level: 1

Type: WARNING

Impact: Data

WSM-02057: Mismatch in EJB lookup. Expected object type: {0}, Actual object type: {1}.
Cause: Mismatch in expected EJB object type and actual object type.
Action: Confirm that the Policy Manager EJB is configured correctly, and its version is compatible with the client.

Level: 1

Type: WARNING

Impact: Data

WSM-02058: Failure occurred in Policy Manager while seeding policies in data store.
Cause: Failure occurred in Policy Manager while seeding policies in data store.
Action: Make sure the correct configuration is passed to Policy Manager for seeding policies.

Level: 1

Type: ERROR

Impact: Data

WSM-02059: Version-related operations are not supported for the configured datastore.
Cause: Version-related operations are not supported for the configured datastore.
Action: Make sure the datastore used is a database and not file-system based.

Level: 1

Type: ERROR

Impact: Data

WSM-02060: EJB lookup failed due to invalid lookup configuration
Cause: Unable to perform EJB lookup.
Action: Make sure that valid JNDI name and JNDI properties are supplied for EJB lookups.

Level: 1

Type: ERROR

Impact: Data

WSM-02061: Failed to close Initial Context created for EJB lookups
Cause: Unable to close the Java Initial Context.
Action: Confirm that no other component is using the context and there are no memory leaks.

Level: 1

Type: ERROR

Impact: Data

WSM-02062: Unable to retrieve credentials for the specified csf-key {0}
Cause: Credential configuration in the policy accessor configuration file was incorrect.
Action: Configure policy with valid CSF key.

Level: 1

Type: ERROR

Impact: Configuration

WSM-02063: The password credentials cannot be obtained from the Credential Store.
Cause: Failure occurred while querying for credentials from CSF.
Action: Check CSF configuration.

Level: 1

Type: ERROR

Impact: Configuration

WSM-02064: The Java Object Name {0} being created is invalid.
Cause: An error occurred while creating the specifed JMX ObjectName.
Action: Check the MBean ObjectName being instantiated and retry the operation.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02065: The MBean being registered is not a JMX compliant MBean
Cause: Failed to register MBean.
Action: Retry the operation. If the problem persists, contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02066: Failed to get server context
Cause: Failed to get server initial context.
Action: Retry the operation. If the problem persists, contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02067: Cannot register MBean {0}, an MBean with same name already exists on the server
Cause: The MBean being registered already exists on the server.
Action: Check the name of the MBean being registered and retry the operation.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02068: Failed to register MBean {0}
Cause: Failed to register MBean.
Action: Retry the operation. If the problem persists, contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02069: Failed to deregister MBean {0}
Cause: Failed to deregister MBean.
Action: No action needs to be taken at this time. However, if the server exhibits any erraneous behavior, try restarting the server.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02070: Failed to load updates.xml file
Cause: Failed to load updates.xml file.
Action: Make sure that the wsm-seed-policies.jar exists and it corresponds to the latest version and retry the operation.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02071: No entries found in the wsm-seed-policies.jar file
Cause: The wsm-seed-policies.jar file does not contain any entries.
Action: Make sure that the wsm-seed-policies.jar file is not corrupted and retry the operation.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02072: Failed to load wsm-seed-policies.jar file
Cause: The wsm-seed-policies.jar file could not be loaded.
Action: Make sure that the wsm-seed-policies.jar file exists in the application classpath and retry the operation.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02073: Unable to connect to the WSM datastore
Cause: Unable to connect to the WSM datastore.
Action: Make sure the datastore settings are correctly set in the wsm-pm application and retry the operation.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02074: Invalid arguments passed to find the difference in shipped documents between versions
Cause: The arguments supplied to find difference between repository versions are invalid.
Action: Make sure that the arguments passed comply with the Javadoc requirements and retry the operation.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02075: Cannot unregister MBean {0}. since it does not exist on the server
Cause: The MBean being unregistered does not exists on the sever.
Action: Check the name of the MBean being unregistered and retry the operation.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02076: Unable to get an instance of PortableMBeanFactory.
Cause: Could not obtain an instance of PortableMBeanFactory.
Action: Check the configuration and try again.

Level: 1

Type: ERROR

Impact: Configuration

WSM-02077: Unable to get a handle to MBeanServer.
Cause: Could not obtain an instance to MBeanServer
Action: Check the configuration and try again.

Level: 1

Type: ERROR

Impact: Configuration

WSM-02078: Unable to construct MBean ObjectName due to null object name string.
Cause: MBean object name is invalid.
Action: Make sure that the supplied object name is not null and retry the lookup.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02079: Failed to connect to Policy Manager instance due to error "{0}".
Cause: Connection to Policy Manager failed.
Action: Make sure that the WSM Policy Manager is up and running and retry the operation.

Level: 1

Type: TRACE

Impact: Data

WSM-02080: Failure to get executor due to underlying error "{0}".
Cause: Failed to get the correct executor to perform requested action.
Action: Check the system security configuration and retry the operation.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02081: Failed to login to perform requested action.
Cause: Failed to login to perform requested action.
Action: Check the system security configuration and retry the operation.

Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-02082: Unsupported callback handler.
Cause: Unsupported callback handler.
Action: Check the system security configuration and retry the operation.

Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-02083: Invalid security configuration entry name.
Cause: Invalid security configuration entry name.
Action: Check the system security configuration and retry the operation.

Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-02100: Error parsing the resource from String {0}.
Cause: An XML parsing failure occurred while creating the document from the passed String.
Action: Verify that the passed String is a well-formed XML and follows the XML schema for its object type.

Level: 1

Type: ERROR

Impact: Data

WSM-02101: Generic Oracle WSM Policy Manager error.
Cause: An internal error occurred during the Policy Manager operation.
Action: Retry the operation. If the problem persists, contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02102: The policy name is missing.
Cause: The policy name was missing.
Action: Make sure that the supplied policy has a valid name, and retry the operation.

Level: 1

Type: ERROR

Impact: Programmatic

WSM-02103: The assertion template name is missing.
Cause: The assertion template name was missing.
Action: Make sure that the supplied assertion template has a valid name, and retry the operation.

Level: 1

Type: ERROR

Impact: Programmatic

WSM-02104: The assertion template from file {0} cannot be parsed.
Cause: A failure occurred while parsing the assertion template from the file.
Action: Check for any syntax errors in the file specified, and retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-02105: The policy search query is not valid.
Cause: An invalid policy search condition was specified.
Action: Check the search query and retry the operation.

Level: 1

Type: ERROR

Impact: Programmatic

WSM-02106: Cannot retrieve policy {0}.
Cause: A failure occurred while retrieving the policy.
Action: Retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-02107: Cannot update policy {0}.
Cause: A failure occurred while updating the policy.
Action: Retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-02108: Cannot retrieve version {0} of policy {1}.
Cause: A failure occurred while retrieving the requested version of the policy.
Action: Check the version and policy details and retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-02109: Cannot retrieve version {0} of assertion template {1}.
Cause: A failure occurred while retrieving the requested version of the specified assertion template.
Action: Check the version and assertion template details, and retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-02111: The configuration name is missing.
Cause: The policy configuration name was missing.
Action: Provide a valid name for the policy configuration, and retry the operation.

Level: 1

Type: ERROR

Impact: Programmatic

WSM-02112: The policy attachment name is missing.
Cause: The policy attachment name was missing.
Action: Provide a valid policy attachment name, and retry the operation

Level: 1

Type: ERROR

Impact: Programmatic

WSM-02113: Error in creating the policy attachment {0}.
Cause: A failure occurred while creating the policy attachment.
Action: Check the specified values and retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-02114: Error in deleting the policy attachment {0}.
Cause: A failure occurred while deleting the policy attachment.
Action: Check the specified values and retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-02115: Error in updating the policy attachment {0}.
Cause: A failure occurred while updating the policy attachment.
Action: Check the specified values and retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-02116: The resource pattern used in the search is empty or contains wildcard characters like %.
Cause: The resource pattern specified in the search was empty or contained wildcard characters such as %.
Action: Correct the search criteria and retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-02117: Cannot delete all policy attachments from the data store.
Cause: A failure occurred when deleting multiple policy attachments from the data store.
Action: Retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-02118: The query service cannot be created.
Cause: A failure occurred while creating the query service.
Action: Check the Policy Manager configuration and retry the operation.

Level: 1

Type: ERROR

Impact: Configuration

WSM-02119: The update service cannot be created.
Cause: A failure occurred while creating the update service.
Action: Check the Policy Manager configuration and retry the operation.

Level: 1

Type: ERROR

Impact: Configuration

WSM-02120: Unable to connect to the Oracle WSM Policy Manager due to the following error "{0}".
Cause: A connection to the Oracle WSM Policy Manager could not be established.
Action: Check the server and Oracle WSM Policy Manager configuration. Confirm it is in active running state, then retry the operation.

Level: 1

Type: ERROR

Impact: Configuration

WSM-02121: Internal system error, cannot look up credential.
Cause: A failure occurred while looking up credentials due to an internal system configuration error.
Action: Contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-02122: The protocol is invalid.
Cause: The protocol was invalid.
Action: Check Oracle documentation for the supported protocols.

Level: 1

Type: ERROR

Impact: Configuration

WSM-02123: Cannot access policy-accessor-config.xml file.
Cause: A failure occurred while reading the policy-accessor-config.xml file.
Action: Ensure that the file exists.

Level: 1

Type: ERROR

Impact: Configuration

WSM-02124: Cannot create policy access service.
Cause: The user connecting to the policy access service did not have sufficient privileges.
Action: Confirm that the user has rights to connect to the policy access service, and retry the operation.

Level: 1

Type: ERROR

Impact: Configuration

WSM-02125: Cannot perform policy compatibility check.
Cause: A failure occurred while performing a policy compatibility check.
Action: Contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-02126: Cannot add policy {0} to data store.
Cause: A failure occurred while adding the policy to the data store.
Action: Retry the operation.

Level: 1

Type: ERROR

Impact: Configuration

WSM-02127: Cannot add assertion template {0} to data store.
Cause: A failure occurred while adding the assertion template to the data store.
Action: Retry the operation.

Level: 1

Type: ERROR

Impact: Configuration

WSM-02128: Cannot read WSDL.
Cause: A failure occurred while parsing the WSDL.
Action: Confirm that the supplied WSDL follows the WSDL XML schema.

Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-02129: Cannot create policy service.
Cause: The user connecting to the policy service did not have sufficient privileges.
Action: Confirm that the user has privileges to connect to the policy service, and retry the operation.

Level: 1

Type: ERROR

Impact: Configuration

WSM-02130: Cannot retrieve policy attachment from data store.
Cause: A failure occurred while retrieving the policy attachment from the data store.
Action: Retry the operation.

Level: 1

Type: WARNING

Impact: Data

WSM-02131: Standard WSDL is provided, but ORAWSDL is required.
Cause: The WSDL did not have the expected Oracle extensions.
Action: Retry the operation with WSDL with Oracle Extensions.

Level: 1

Type: WARNING

Impact: Data

WSM-02132: Cannot find service {0} in WSDL.
Cause: The service was not found in the WSDL.
Action: Retry the operation with the correct parameters.

Level: 1

Type: WARNING

Impact: Data

WSM-02133: Cannot find policies in WSDL.
Cause: No policies were found in the WSDL.
Action: Confirm that the supplied WSDL contains the correct policies.

Level: 1

Type: WARNING

Impact: Data

WSM-02134: Cannot access Policy Manager EJB.
Cause: The user connecting to the Policy Manager EJB did not have sufficient privileges.
Action: Confirm that the user has privileges to connect to the Policy Manager EJB, and retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-02135: Insufficient privileges for accessing the Policy Manager interface.
Cause: Caller's privileges for accessing the Policy Manager EJB were insufficient.
Action: Examine underlying errors for root cause.

Level: 1

Type: ERROR

Impact: Data

WSM-02136: Bulk update operations are not supported for file-based data stores.
Cause: The bulk update operation failed because the data store does not support transactions.
Action: Use a repository that supports transactions, for example, a database repository.

Level: 1

Type: ERROR

Impact: Data

WSM-02138: Cannot save policy attachment {0} to data store.
Cause: A concurrent update failure occurred while saving the policy attachment in the data store.
Action: Make sure no other process is trying to update the same policy attachment object and retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-02139: Cannot save policy {0} to data store.
Cause: A concurrent update failure occurred while saving the policy in the data store.
Action: Make sure no other process is trying to update the same policy object and retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-02201: A comparator is required for a search criterion.
Cause: A search comparator was not provided.
Action: Supply a comparator.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02202: The comparator "{0}" is not supported for a numeric attribute search criterion.
Cause: The search comparator is not supported for numeric comparisons.
Action: Supply a comparator that supports numeric comparisons.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02203: The comparator "{0}" is not supported for a text attribute search criterion.
Cause: The search comparator is not supported for numeric comparisons.
Action: Supply a comparator that supports numeric comparisons.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02204: The comparator "UNKNOWN" is not supported for an attribute search criterion.
Cause: The search comparator UNKNOWN is not supported for attribute comparisons.
Action: Supply a comparator that supports attribute comparisons.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02205: The search criterion "{0}" cannot be parsed.
Cause: The search criterion was corrupt or used an unrecognized schema.
Action: Supply a supported search criterion.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02206: The document name "{0}" is not valid for a search criterion.
Cause: The document name contained illegal characters, such as a slash character.
Action: Supply a legal document name.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02207: A document type is required for a search criterion.
Cause: The document type was null, whitespace, or empty.
Action: Supply a non-empty document type.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02208: A document URI ends with a path separator.
Cause: The document URI ends with a path separator.
Action: Supply a document URI that does not appear to be a path.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02209: A document URI is required for a search criterion.
Cause: The document URI was empty.
Action: Supply a non-empty document URI.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02210: An element search criterion cannot be created with the child search expression "{0}" because it contains a non-attribute criterion.
Cause: The search expression contained one or more attribute criteria.
Action: Supply an expression containing only attribute criteria.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02211: A number is required for a search criterion.
Cause: A number was not provided.
Action: Supply a valid number.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02212: The search expression "{0}" contains invalid operator "{1}".
Cause: The search expression contained an invalid operator.
Action: Supply an expression with a valid operator.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02213: A search operator is required for a search expression.
Cause: A search operator was not provided.
Action: Supply a valid operator.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02214: The operator "UNKNOWN" is not supported for a search expression.
Cause: The search operator UNKNOWN is not supported for expressions.
Action: Supply a valid operator.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02215: A QName is required for a search criterion.
Cause: A search QName was not provided.
Action: Supply a valid Name.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02216: The search expression "{0}" contains a close parenthesis at index {1} without a matching open parenthesis.
Cause: The search expression contained an unbalanced parenthesis.
Action: Supply an expression with matching open and close parenthesis.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02217: The search expression "{0}" contains an open parenthesis without a matching close parenthesis.
Cause: The search expression contained an unclosed parenthesis.
Action: Supply an expression with matching open and close parenthesis.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02218: The comparator "{0}" is not supported for text content search criterion.
Cause: The search comparator is not supported for text comparisons.
Action: Supply a comparator that supports text comparisons.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02251: Subject metadata is required to build a PolicySet.
Cause: Subject metadata was not provided for building a PolicySet.
Action: Supply valid subject metadata.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02252: A repository accessor is required to build a PolicySet.
Cause: A repository accessor was not provided for building a PolicySet.
Action: Supply suitable repository accessor instance.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02253: The resource pattern for the subject "{0}" is invalid. External attachments and policy usage tracking is disabled.
Cause: An invalid resource pattern was provided with the metadata for a policy subject.
Action: Contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02261: A map of terms is required when creating a ResourcePattern.
Cause: A null map of terms was provided to the ResourcePattern constructor.
Action: Supply a valid map of terms when creating a resource pattern.

Level: 1

Type: ERROR

Impact: Programmatic

WSM-02262: A "{0}" term is required when creating a ResourcePattern.
Cause: The required term was not provided to the ResourcePattern constructor.
Action: Supply a valid map of terms when creating a resource pattern.

Level: 1

Type: ERROR

Impact: Data

WSM-02263: A map of terms is required when creating a ResourcePattern.
Cause: A null String was provided to the ResourcePattern constructor.
Action: Supply a valid resource pattern String.

Level: 1

Type: ERROR

Impact: Programmatic

WSM-02264: "{0}" is not a recognized resource pattern.
Cause: The supplied String did not match one of the known resource pattern formats.
Action: Supply a valid resource pattern String.

Level: 1

Type: ERROR

Impact: Data

WSM-02301: Failed to get document from URL "{0}" due to underlying error "{1}"
Cause: URL resource was not loaded.
Action: Check that the passed URL is valid and retry the operation.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02302: Failed to access document repository due to underlying error "{0}"
Cause: The Document Repository could not be accessed.
Action: Check the configuration for accessing Document Repository and retry the operation.

Level: 32

Type: INCIDENT_ERROR

Impact: Requests/Responses

WSM-02303: The passed search expression "{0}" could not be parsed due to underlying error "{1}"
Cause: Failure in parsing the passed search expression.
Action: Check that the passed search expression is valid and retry the operation.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02304: The passed expressionMap "{0}" contains search expression which cannot be parsed due to underlying error "{1}".
Cause: Failure in parsing the search expression contained in the passed expressionMap.
Action: Check that the passed expressionMap contains valid search expression and retry the operation.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02310: Failed to retrieve requested documents due to underlying error "{0}". The operation will be retried.
Cause: Failure in retrieving the requested documents.
Action: No corrective action needed as this time, the operation will be retried.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02311: Failed to retrieve requested documents due to underlying error "{0}".
Cause: Failure in retrieving the requested documents.
Action: Check that the document repository is reachable and is correctly configured.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02312: Failed to store resource usage information to underlying error "{0}". The operation will be retried.
Cause: Failure in persisting usage information.
Action: No corrective action needed as this time, the operation will be retried..

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02313: Failed to store resource usage information to underlying error "{0}".
Cause: Failure in persisting usage information.
Action: Check that the document repository is reachable and is correctly configured.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02351: A invalid bean class "{0}" is provided.
Cause: A invalid bean class was provided to the bean factory to create a bean instance.
Action: Provide a valid bean class.

Level: 1

Type: ERROR

Impact: Data

WSM-02352: A invalid bean type "{0}" is provided.
Cause: A invalid bean type was provided to the bean factory to create a bean instance.
Action: Provide a valid bean type.

Level: 1

Type: ERROR

Impact: Data

WSM-02353: Unable to get the Action Executor.
Cause: A failure occurred while getting Action Executor.
Action: Check that valid subject is passed to get the Action Executor

Level: 1

Type: ERROR

Impact: Configuration

WSM-02354: Unexpected exception "{0}" caught when privileged method is called.
Cause: Unexpected exception caught on calling a privileged code.
Action: Check the underlying signature of method called in privileged code

Level: 1

Type: ERROR

Impact: Configuration

WSM-02355: A subject passed to BeanFactory is null.
Cause: The subject passed to the bean factory is null.
Action: Ensure that the subject is not null.

Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-02356: Cannot cast to "{0}" object.
Cause: Unable to cast the object. It may be using older implementation.
Action: Verify that the older implementation is not being used.

Level: 1

Type: ERROR

Impact: Configuration

WSM-02359: Lookup attempted for unsupported Server.
Cause: A lookup is attempted for unsupported Server.
Action: Check the system configurations to ensure correct server is running.

Level: 1

Type: ERROR

Impact: Configuration

WSM-02360: The path to the jar file "{0}" is either invalid or the jar file is corrupt.
Cause: The path provided to the jar file is either incorrect or the jar file is corrupt
Action: Provide the path to a valid jar file.

Level: 1

Type: ERROR

Impact: Configuration

WSM-02401: Failed to store policy usage information to the repository because document criterion "{1}" is not a valid document name for the repository due to underlying error "{0}".
Cause: The document criterion contains invalid document name for the repository.
Action: Choose a valid document name and try again.

Level: 1

Type: ERROR

Impact: Data

WSM-02402: Expression "{0}" does not identify specific documents.
Cause: An invalid search expression was specified.
Action: Check the search expression and retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-02403: Failed to store policy usage information to the repository because the expressionMap "{0}" has document criterion with invalid document name for the repository resulting in underlying error "{1}".
Cause: The search expression within the map has document criterion having invalid document name for the repository.
Action: Choose a valid document name and try again.

Level: 1

Type: ERROR

Impact: Data

WSM-02451: Document cannot be deleted from repository due to underlying error "{0}".
Cause: Failure in deleting requested document.
Action: Check that the document exists in the repository

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02452: Document criterion "{0}" is invalid for the requested operation due to underlying error "{0}".
Cause: Document criteria is invalid for the requested operation.
Action: Check that the document criterion is valid for the repository.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02453: Failed to delete the document with version "{1}" and criterion "{0}" due to underlying error "{2}".
Cause: Failure in deleting the specified version of the document.
Action: Check that the document with the specified version exists in repository.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02454: The search expression "{0}" does not identify a unique document.
Cause: The search expression do not identify unique document.
Action: Supply an expression which identifies unique document.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02455: Document version cannot be promoted to tip due to underlying error "{0}".
Cause: Failure in promoting the requested document.
Action: Check that the document exists in the repository.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02456: A retrieval flag cannot be parsed into a number due to underlying error "{0}".
Cause: Failure in parsing flags for document retrieval operation.
Action: Check that the value specified for the flags are valid.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02457: Document retrieval failed due to underlying error "{0}".
Cause: Failure in retrieving documents due to invalid document criteria.
Action: Check that the value specified for the document criteria are valid.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02458: Document "{0}" cannot be overwritten as it does not exist in the repository.
Cause: Failure in write operation using WRITE_EXISTING mode since document do not exist in repository.
Action: Define a new search criterion.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02459: Document "{0}" cannot be created as already exists in the repository.
Cause: Failure in write operation using WRITE_NEW mode since document exists in repository.
Action: Define a new search criterion.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02460: Unable to write invalid document due to underlying error "{0}".
Cause: URI for the document is invalid for the write operation.
Action: Check that the document URI is valid for the repository

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02461: A document without a naming attribute cannot be written.
Cause: Document name is not specified at time of document creation.
Action: Please specify a valid document name for the document creation.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02462: The session state is invalid due to underlying error "{0}".
Cause: Session state is invalid for the given operation.
Action: Retry the operation.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02463: A document transformer cannot be created due to underlying error "{0}".
Cause: The DOM Parser was not configured properly.
Action: Consult Java documentation.

Level: 1

Type: ERROR

Impact: Other

WSM-02464: A DOM document cannot be marshalled into XML due to underlying transformation error "{0}".
Cause: Parsing of the document failed.
Action: Ensure that the document is in well-formed XML format.

Level: 1

Type: ERROR

Impact: Other

WSM-02465: A DOM document builder cannot be created due to underlying error "{0}".
Cause: The XML Parser was not configured properly.
Action: Consult Java documentation.

Level: 1

Type: ERROR

Impact: Configuration

WSM-02466: An XML document cannot be unmarshalled into DOM due to underlying parsing error "{0}".
Cause: Parsing of the XML failed.
Action: Ensure that the XML is well formed.

Level: 1

Type: ERROR

Impact: Data

WSM-02467: An XML document cannot be unmarshalled into DOM due to underlying I/O error "{0}".
Cause: The system could not open the Input/Output streams.
Action: Consult the Java documentation.

Level: 1

Type: ERROR

Impact: Files

WSM-02468: The document specified in search expresion "{0}" resulted in underlying error "{1}".
Cause: The document name specified for the repository is invalid.
Action: Please specify a valid document name.

Level: 1

Type: ERROR

Impact: Files

WSM-02469: Unable to retrieve document due to underlying error "{0}".
Cause: URI for the document is invalid for the retrieve operation.
Action: Check that the document URI is valid for the repository

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02470: Unable to write document due to invalid Write Mode "{0}".
Cause: Invalid Write Mode specified to write a document.
Action: Check that a valid Write Mode is specified to write a document.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02471: The exception "{0}" is caused because invalid document uri is being used.
Cause: URI for any document is invalid.
Action: Check that all the document URI used are valid for the repository

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02551: Unable to retrieve document due to underlying error "{0}".
Cause: URI for the jar is invalid for the retrieve operation.
Action: Check that the jar URI is valid.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02552: Unable to load seed policies jar file
Cause: Inability to load seed policies jar either automatically or by a provided path
Action: Check that the path to the jar file is correct

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-02553: Unable to load updates.xml from the seed policy jar
Cause: There is some problem while loading updates.xml from the seed policies jar
Action: Make sure a valid seed policies jar is provided containing a valid updates.xml file

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-03001: Oracle WSM Monitor internal error {0}
Cause: An unexpected error occurred while monitoring Oracle WSM Agent.
Action: Retry the operation. If the problem persists, contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-03002: Failure initializing Oracle WSM Monitor, {0} is null.
Cause: Creation of one or more DMS Event sensors failed while initializing Oracle WSM Monitor.
Action: Retry the operation. If the problem persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Configuration

WSM-03003: The topology node value {0} is not valid.
Cause: The topology node value passed from the security interceptor to Oracle WSM Agent was invalid.
Action: Retry the operation. If the problem persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Configuration

WSM-03004: The parameter {0} is not valid.
Cause: The parameter was either null or invalid.
Action: Retry the operation. If the problem persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Configuration

WSM-04501: generic error in accessing the data store
Cause: An internal error occurred while accessing the MDS data store.
Action: Retry the operation. If the problem persists, contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-04502: The name of the resource is empty.
Cause: The name of the resource to be updated or retrieved was empty.
Action: Assign a name to the resource being processed.

Level: 1

Type: ERROR

Impact: Programmatic

WSM-04503: resource {0} does not exist in the data store
Cause: The requested resource was not found in the data store.
Action: Check the search criteria and try again.

Level: 1

Type: ERROR

Impact: Data

WSM-04504: resource {0} cannot be updated
Cause: The resource could not be updated.
Action: Retry the operation. If the problem persists, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Data

WSM-04505: resource {0} cannot be created
Cause: The specified name has already been assigned to another resource.
Action: Specify a unique name, and retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-04506: cannot create resource {0}
Cause: The resource could not be saved to the data store.
Action: Retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-04507: cannot delete resource {0}
Cause: The resource could not be deleted from the data store.
Action: Retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-04508: cannot update resource {0}
Cause: The resource could not be updated to the data store.
Action: Retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-04509: cannot initialize the connection to the data store
Cause: Connecting to the data store failed.
Action: Check the data store credentials, and retry the operation. Ensure that WSM-PM is installed, deployed correctly and running at http://<host:port>/wsm-pm/ and by clicking the Validator link. Also, ensure that the database to which WSM-PM connects is up and the mds-owsm data source is configured properly and targeted to the right server.

Level: 1

Type: ERROR

Impact: Data

WSM-04510: The version {0} for resource {1} cannot be found.
Cause: The requested version for the specified resource was not found.
Action: Check the search criteria, and retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-04511: cannot perform simultaneous deletes
Cause: Deleting multiple resources simultaneously from the data store failed.
Action: Check supplied data, and retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-04512: internal data store error
Cause: A generic data store exception occurred.
Action: Check the data store credentials that were provided and retry the operation. If the problem persists, contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-04513: cannot commit changes to the repository
Cause: A failure occurred while finalizing changes to the data store.
Action: Retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-04514: The version {0} for resource {1} cannot be deleted.
Cause: Deleting the specified version(s) of the resource failed.
Action: Check the supplied values, and retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-04515: Auditing is disabled for MDS operations.
Cause: An internal error occurred; failed to initialize the auditor.
Action: Retry the operation. If the problem persists, contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-04516: The version of the passed resource is invalid.
Cause: The requested version of the resource was invalid.
Action: The version number must be a positive integer.

Level: 1

Type: ERROR

Impact: Programmatic

WSM-04517: cannot update resource {0}
Cause: The resource to be updated was concurrently being updated by another process.
Action: Make sure no other process is attempting to change the resource being updated, and retry the operation.

Level: 1

Type: ERROR

Impact: Programmatic

WSM-04518: document name is invalid
Cause: The document name was invalid.
Action: Specify a name for the document that follows the document naming conventions. Refer to Oracle documentation for the naming rules.

Level: 1

Type: ERROR

Impact: Programmatic

WSM-04519: Unable to create document.
Cause: The repository permissions were read-only. Creation of a new document requires write permissions.
Action: Reconfigure the repository to have write permissions.

Level: 1

Type: ERROR

Impact: Programmatic

WSM-04520: The repository timestamp is invalid.
Cause: The repository timestamp was invalid or missing.
Action: Retry the operation. If the problem persists, consult the diagnostic logs.

Level: 1

Type: NOTIFICATION

Impact: Programmatic

WSM-04521: Resource to be deleted does not exist in datastore.
Cause: The resource could not be deleted since it does not exist in the data store.
Action: You don't need to take any action, the resource is not present in the datastore.

Level: 1

Type: ERROR

Impact: Data

WSM-04601: A JDBC URL is required to connect to a database-based MDS repository.
Cause: A null or empty JDBC URL was provided when attempting to create an MDS instance for a database-based repository.
Action: Provide a valid JDBC URL and try again.

Level: 1

Type: ERROR

Impact: Programmatic

WSM-04602: A password is required to connect to a database-based MDS repository.
Cause: A null or empty password was provided when attempting to create an MDS instance for a database-based repository.
Action: Provide a valid password and try again.

Level: 1

Type: ERROR

Impact: Programmatic

WSM-04603: A username is required to connect to a database-based MDS repository.
Cause: A null or empty username was provided when attempting to create an MDS instance for a database-based repository.
Action: Provide a valid username and try again.

Level: 1

Type: ERROR

Impact: Programmatic

WSM-04606: One or more directories are required to connect to a file-based MDS repository.
Cause: A path was not provided when attempting to create an MDS instance for a file-based repository.
Action: Provide a valid directory and try again.

Level: 1

Type: ERROR

Impact: Programmatic

WSM-04611: An MDS session cannot be created due to underlying error "{0}".
Cause: MDS encountered an unexpected condition.
Action: Follow the recommendations for the underlying exception.

Level: 1

Type: ERROR

Impact: Data

WSM-04641: The operation "{0}" for document "{1}" cannot be performed on a closed session.
Cause: A operation was requested on a session that has already been closed.
Action: Create a new repository session and perform the operation again.

Level: 1

Type: NOTIFICATION

Impact: Programmatic

WSM-04642: The operation "{0}" for document "{1}" cannot be performed on a read-only session.
Cause: See error message.
Action: Create a new session on a writable repository and try again.

Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-04643: The operation "{0}" cannot be performed on virtual document "{1}".
Cause: A write operation was requested on a virtual document.
Action: Choose a different document name and try again.

Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-04651: The search criterion "{0}" does not identify a specific document to be created.
Cause: The supplied criterion does not have the correct type.
Action: Supply a NAME search criterion.

Level: 1

Type: ERROR

Impact: Programmatic

WSM-04652: The document "{0}" already exists in the repository.
Cause: The document already exists in the repository.
Action: Choose a different name for the document to create or perform an update instead.

Level: 1

Type: ERROR

Impact: Data

WSM-04653: The document "{0}" cannot be created in a read-only repository.
Cause: The repository is read-only.
Action: Reconfigure the repository to support writes and try again.

Level: 1

Type: ERROR

Impact: Configuration

WSM-04654: The name "{0}" is invalid for creating a document due to underlying reason "{2}".
Cause: The document name is invalid for the repository.
Action: Choose a valid name and try again.

Level: 1

Type: ERROR

Impact: Data

WSM-04655: Repository information cannot be marshalled due to underlying parser error "{2}"
Cause: The system does not support the required DOM document builder configuration.
Action: Correct underlying error or contact Oracle Support Services for assistance.

Level: 32

Type: INCIDENT_ERROR

Impact: Other

WSM-04656: Repository information cannot be marshalled due to underlying marshalling error "{2}"
Cause: The repository information object could not be marshalled into a DOM document.
Action: Correct underlying error or contact Oracle Support Services for assistance.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-04657: The document "{0}" cannot be created in a session spanning multiple stores due to underlying error "{2}".
Cause: The document to be created belongs in a store that is different from other write operations in the session.
Action: Create the document in a different session.

Level: 1

Type: ERROR

Impact: Configuration

WSM-04661: The document "{0}" cannot be deleted in a read-only repository.
Cause: The repository is read-only.
Action: Reconfigure the repository to support writes and try again.

Level: 1

Type: ERROR

Impact: Data

WSM-04662: The name "{0}" is invalid for deleting a document due to underlying reason "{2}".
Cause: The document name is invalid for the repository.
Action: Choose a valid name and try again.

Level: 1

Type: ERROR

Impact: Data

WSM-04663: The document "{0}" cannot be deleted in a session spanning multiple stores due to underlying error "{2}".
Cause: The document to be created belongs in a store that is different from other write operations in the session.
Action: Delete the document in a different session.

Level: 1

Type: ERROR

Impact: Data

WSM-04664: Version {1} to {3} of document "{0}" cannot be deleted.
Cause: The repository does not support deletion of individual versions of a document.
Action: Ignore the document version or delete the entire document.

Level: 1

Type: ERROR

Impact: Data

WSM-04671: A concurrent write prevented the document "{0}" from being written due to underlying error "{2}".
Cause: A document in this session was modified by another session.
Action: Retry the operation.

Level: 1

Type: ERROR

Impact: Data

WSM-04672: The document "{0}" cannot be written to repository due to underlying error "{2}".
Cause: An I/O error occurred while writing to repository.
Action: Correct the underlying problem and retry.

Level: 1

Type: ERROR

Impact: Data

WSM-04673: The session cannot be commited due to underlying error "{2}".
Cause: The resource could not be deleted since it does not exist in the data store.
Action: You don't need to take any action, the resource is not present in the datastore.

Level: 1

Type: ERROR

Impact: Data

WSM-04674: The document "{0}" cannot be validated due to underlying error "{2}".
Cause: Validation failed for a metadata object written in the session.
Action: Correct the underlying problem and retry.

Level: 1

Type: ERROR

Impact: Data

WSM-04681: The document "{0}" to be modified was not found in the repository due to underlying error "{2}".
Cause: The document was not found in the repository.
Action: Create the document instead of modifying it.

Level: 1

Type: ERROR

Impact: Data

WSM-04682: The document "{0}" cannot be modified in a session spanning multiple stores due to underlying error "{2}".
Cause: The document to be modified belongs in a store that is different from other write operations in the session.
Action: Modify the document in a different session.

Level: 1

Type: ERROR

Impact: Data

WSM-04691: The document "{0}" cannot be found in repository due to underlying error "{2}".
Cause: The document was not found in the repository.
Action: Create the document and try again.

Level: 1

Type: NOTIFICATION

Impact: Data

WSM-04692: The name "{0}" is invalid for retrieving a document due to the error "{2}".
Cause: The document name is invalid for the repository.
Action: Choose a valid name and try again.

Level: 1

Type: ERROR

Impact: Data

WSM-04693: Version information is not available for document "{0}".
Cause: The repository does not support versioning.
Action: Configure the repository to support versioning.

Level: 1

Type: ERROR

Impact: Data

WSM-04694: An invalid directory was provided to connect to a file-base MDS repository.
Cause: An invalid directory was provided when attempting to create an MDS instance for a file-based repository.
Action: Provide a valid directory and try again.

Level: 1

Type: ERROR

Impact: Programmatic

WSM-04695: The retrieved version of document "{0}" is no longer available.
Cause: A new version of the document was created after it was initially retrieved.
Action: Retry the operation to get the latest version of the document.

Level: 1

Type: ERROR

Impact: Data

WSM-04696: The operation "{0}" cannot be performed on a closed session.
Cause: A operation was requested on a session that has already been closed.
Action: Create a new repository session and perform the operation again.

Level: 1

Type: NOTIFICATION

Impact: Programmatic

WSM-04697: The operation "{0}" cannot be performed on a read-only session.
Cause: See error message.
Action: Create a new session on a writable repository and try again.

Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-04698: Versions {1} to {3} of document "{0}" are not deletable due to underlying error "{2}".
Cause: An I/O error occurred while trying to delete versions of a document from repository.
Action: Correct the underlying problem and retry.

Level: 1

Type: ERROR

Impact: Data

WSM-04699: A write lock is not available to delete versions {1} to {3} of document "{0}" due to underlying error "{2}".
Cause: A write lock could not be obtained to delete versions of a document.
Action: Retry the operation.

Level: 1

Type: WARNING

Impact: Data

WSM-06001: Error obtaining Policy Set.
Cause: Failed to get PolicySet.
Action: Check log file for possible causes.

Level: 1

Type: ERROR

Impact: Configuration

WSM-06017: Error converting to the canonical path for the File Policy Resolver.
Cause: An invalid canonical path was passed for the File Policy Resolver.
Action: Verify the canonical path passed for the File Policy Resolver and retry the operation.

Level: 1

Type: ERROR

Impact: Files

WSM-06036: The class cannot be instantiated.
Cause: The system could not instantiate a class.
Action: Consult the Java documentation or Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-06101: The policy set cannot be created for null Service Component Architecture (SCA) node.
Cause: The PolicySet could not be generated for the null Service Component Architecture (SCA) node.
Action: Pass a valid SCA node object.

Level: 1

Type: ERROR

Impact: Compliance

WSM-06102: The policy referenced by URI "{0}" could not be retrieved.
Cause: Cannot connect to the policy manager due to credential issue.
Action: Verify that credentials are correctly specified, if not using the default principal, and that the principal is authorized to access the policy manager application.

Level: 1

Type: ERROR

Impact: Compliance

WSM-06103: No configuration has been specified for the Policy Accessor.
Cause: The Policy Accessor object could not be initialized because it is not correctly configured.
Action: Call the init method to initialize the Policy Accessor object before invoking this method.

Level: 1

Type: ERROR

Impact: Configuration

WSM-06104: The protocol specified for Policy Accessor is not supported.
Cause: A policy access protocol was specified that was invalid for this environment.
Action: Change protocol to one that is supported by the environment. For J2EE environments, the supported protocols are "local" and "remote"; for J2SE environments, the supported protocols are "classpath", "local", and "remote".

Level: 1

Type: ERROR

Impact: Compliance

WSM-06105: The duplicate policy references are found in the same Service Component Architecture (SCA) binding node.
Cause: The same policy has been attached multiple times and so duplicate policy references were found in the same Service Component Architecture (SCA) binding node.
Action: Remove the duplicate policy references from the SCA binding node by attaching each policy only once.

Level: 1

Type: ERROR

Impact: Compliance

WSM-06106: The policy reference URI cannot be empty.
Cause: Empty policy references were found in the Service Component Architecture (SCA) node.
Action: Verify the Service Component Architecture (SCA) node and make sure the policy references specify a valid value and the referenced policies exist in the repository.

Level: 1

Type: ERROR

Impact: Compliance

WSM-06107: The node that is expected is <binding.ws> or <component>. The node {0} passed is not a supported node.
Cause: An unsupported Service Component Architecture (SCA) node was found.
Action: Specify a supported SCA node. Consult Oracle documentation for further details

Level: 1

Type: ERROR

Impact: Compliance

WSM-06108: Error initializing the Oracle WSM Policy Resolver because incorrect configuration is passed
Cause: The Policy Resolver did not get created. This could be due to the wrong configuration being passed.
Action: Verify the configuration passed for creating the Policy Resolver. Verify that the correct Policy Accessor protocol is passed.

Level: 1

Type: ERROR

Impact: Configuration

WSM-06109: Cannot retrieve policies.
Cause: The policies were not retrieved. This may be due to incorrect policy references in the Service Component Architecture (SCA) node.
Action: Verify that the policy references are referring to policies that exist in the repository. Also, ensure that the data store is seeded with policies.

Level: 1

Type: ERROR

Impact: Data

WSM-06110: The MetaData Store (MDS) home cannot be null.
Cause: The Policy Repository was not valid because MDS Home is set to null.
Action: Check the mds.home.module property for the correct value for MDS Home.

Level: 1

Type: ERROR

Impact: Configuration

WSM-06111: The policy name cannot be null.
Cause: The policy name passed was null or empty.
Action: Verify that the policy name is not an empty string, and verify that a null policy name is not being passed.

Level: 1

Type: ERROR

Impact: Compliance

WSM-06112: Policies are not supported for a node of type:{0}.
Cause: Policies cannot be retrieved for unsupported Service Component Architecture (SCA) nodes.
Action: Verify that a supported SCA node is provided for retrieving the policy.

Level: 1

Type: WARNING

Impact: Compliance

WSM-06113: The configuration name cannot be null or empty.
Cause: The configuration file was either empty or did not exist.
Action: Verify that the configuration file exists and contains policy references to retrieve policies from the Policy Repository.

Level: 1

Type: ERROR

Impact: Configuration

WSM-06114: The home directory for the File Policy Resolver cannot be null.
Cause: The home directory for File Policy Resolver was null.
Action: Verify that a valid home directory is passed for the File Policy Resolver.

Level: 1

Type: ERROR

Impact: Files

WSM-06115: The path for the File Policy Resolver does not exist.
Cause: The path for File Policy Resolver did not exist.
Action: Ensure that a valid path is passed for File Policy Resolver.

Level: 1

Type: ERROR

Impact: Files

WSM-06116: The path for the File Policy Resolver is not a directory.
Cause: An invalid directory name was passed for the File Policy Resolver.
Action: Verify that a valid directory name is passed for the File Policy Resolver.

Level: 1

Type: ERROR

Impact: Files

WSM-06118: The resource name for the File Policy Resolver cannot be null.
Cause: The resource name for the File Policy Resolver is null.
Action: Verify that a valid resource name is passed for the File Policy Resolver.

Level: 1

Type: ERROR

Impact: Files

WSM-06119: The file {0} for the File Policy Resolver does not exist under {1}.
Cause: The file did not exist.
Action: Verify that the file exists at the specified location.

Level: 1

Type: ERROR

Impact: Files

WSM-06120: The resource name for the File Policy Resolver cannot be null.
Cause: The resource name for the File Policy Resolver was null.
Action: Ensure that a non-null resource name is passed for the File Policy Resolver.

Level: 1

Type: ERROR

Impact: Files

WSM-06121: No policy is found for the policy reference: {0}.
Cause: No policy was found for the specified policy reference.
Action: Verify that the policy exists in the repository for the given policy reference, and that the correct policy reference is passed.

Level: 1

Type: ERROR

Impact: Data

WSM-06122: Error retrieving policies.
Cause: An unexpected error occurred while retrieving the policies from the Policy Manager.
Action: Retry the operation. If the problem persists, contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Data

WSM-06123: Error initializing internally the File Policy Resolver: {0} {1}
Cause: An unexpected error occurred while initializing the File Policy Resolver.
Action: Retry the operation. If the problem persists, contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Security

WSM-06124: Error initializing the Oracle WSM Policy Manager Policy Resolver : {0} {1}.
Cause: An unexpected error occurred while initializing the Policy Manager Policy Resolver. The Policy Manager Policy Resolver was not able to find the property named mds.config
Action: Verify that the property mds.config exists and is referencing a valid property file.

Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-06125: Error in the XPath expression {0}.
Cause: The XPath Expression for the policy reference for the given Service Component Architecture (SCA) node was invalid.
Action: Verify the XPath for the policy reference within the SCA node.

Level: 1

Type: ERROR

Impact: Compliance

WSM-06128: Error accessing the PolicySet : {0} : {1}.
Cause: An unexpected error occurred while accessing the PolicySet.
Action: Retry the operation. If the problem persists, contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-06129: Error parsing the PolicySet : {0} : {1}.
Cause: An unexpected error occurred while parsing the PolicySet.
Action: Retry the operation. If the problem persists, contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-06130: Error creating the policy parser.
Cause: The Policy Parser did not get created.
Action: Check the configuration for the Policy Parser.

Level: 1

Type: ERROR

Impact: Configuration

WSM-06132: Error creating a connection to Oracle WSM Policy Manager.
Cause: A failure occurred while connecting to the Policy Manager.
Action: Ensure that the Policy Manager is up and running. Ensure that WSM-PM is installed, deployed correctly and running at http://<host:port>/wsm-pm/ and by clicking the Validator link. Also, ensure that the database to which WSM-PM connects is up and the mds-owsm data source is configured properly and targeted to the right server.

Level: 1

Type: ERROR

Impact: Configuration

WSM-06133: Error connecting to Oracle WSM Policy Manager.
Cause: A failure occurred while connecting to Policy Manager J2EE Application.
Action: Before connecting to a Policy Manager, ensure that the Policy Manager is up and running.

Level: 1

Type: ERROR

Impact: Configuration

WSM-06134: The class cannot be found.
Cause: The class could not be found in the classpath.
Action: Verify that the class name is correct in the configuration files and ensure that the class is specified in the classpath variable.

Level: 1

Type: ERROR

Impact: Configuration

WSM-06135: The class cannot be loaded due to Java 2 security restrictions.
Cause: Some classes were not loaded due to class loading security restrictions.
Action: Contact the site administrator or Java documentation to ensure that the classes have the necessary Java2 security permissions.

Level: 1

Type: ERROR

Impact: Configuration

WSM-06137: The "mds" policy access protocol is deprecated - use "local" instead.
Cause: A deprecated Policy Accessor Protocol was specified.
Action: Update the configuration to use the standard protocol name.

Level: 1

Type: WARNING

Impact: Configuration

WSM-06138: The "owsm" policy access protocol is deprecated - use "remote" instead.
Cause: A deprecated Policy Accessor protocol was specified.
Action: Update the configuration to use the standard protocol name.

Level: 1

Type: WARNING

Impact: Configuration

WSM-06139: Error closing a stream
Cause: Failure occurred in closing the stream while parsing the configuration file or the policy in the FILE protocol.
Action: Verify that the correct configuration file or policy name is provided.

Level: 1

Type: WARNING

Impact: Configuration

WSM-06140: Failure finding policy {0} in the classpath roots path {1}.
Cause: The configured roots are invalid.
Action: Correct the classpath roots to point to the correct locations.

Level: 1

Type: WARNING

Impact: Configuration

WSM-06141: Error initializing Policy Resolver.
Cause: The Policy Resolver was not initialized.
Action: Invoke the init method to initialize the Policy Resolver before executing this method.

Level: 1

Type: ERROR

Impact: Configuration

WSM-06142: Unable to retrieve policy store timestamp.
Cause: The Policy Resolver could not connect to Policy Manager to retrieve the policy store timestamp.
Action: Check the MDS configuration file.

Level: 1

Type: WARNING

Impact: Configuration

WSM-06143: The validation check in the policy "{0}" failed.
Cause: An error occurred while validating the policy.
Action: Ensure that the policy is valid.

Level: 1

Type: ERROR

Impact: Configuration

WSM-06144: Null policy subject value is not allowed from JEE application.
Cause: The null policy subject value was passed from JEE application.
Action: Ensure that a valid policy subject is passed from the JEE application.

Level: 1

Type: ERROR

Impact: Compliance

WSM-06145: Internal system error, cannot look up credential
Cause: Failure occurred while looking up credentials.
Action: Internal system configuration error. Contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-06146: Error deleting the attachment entries.
Cause: Failure occurred while deleting the attachment entries.
Action: Ensure that a valid list of policy subjects for deactivated lifecycle type is passed

Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-06147: There is mismatch in Policy reference category "{0}" and Policy category "{1}". Policy reference category should match with Policy category.
Cause: Mismatch in expected policy category and fetched policy category.
Action: Confirm that the Policy Reference category is correct and that it matches the Policy category.

Level: 1

Type: WARNING

Impact: Data

WSM-06148: Unable to apply property overrides to Policy
Cause: Unable to apply property overrides to Policy.
Action: Make sure the policy model conforms to the Oracle Web service policy model.

Level: 1

Type: WARNING

Impact: Data

WSM-06149: The policy reference URI is not valid : {0}
Cause: The Policy Reference URI provided was not valid.
Action: Verify that the Policy Reference URI is correct.

Level: 1

Type: ERROR

Impact: Compliance

WSM-06150: Invalid category : {0} for policy : {1}. Only policies assigned to the security category are supported.
Cause: The Policy category provided was not valid.
Action: Verify that the Policy category is correct.

Level: 1

Type: ERROR

Impact: Compliance

WSM-06152: The Policy Cache is not available.
Cause: The Policy Cache is not available.
Action: You may need to restart the server.

Level: 1

Type: ERROR

Impact: Compliance

WSM-06153: Could not access the Policy Cache.
Cause: Cannot access the Policy Cache.
Action: You may need to restart the server.

Level: 1

Type: ERROR

Impact: Compliance

WSM-06154: Could not initialize Policy Java Object Cache.
Cause: Cannot initialize the Policy Cache.
Action: You may need to restart the server.

Level: 1

Type: ERROR

Impact: Compliance

WSM-06155: Could not re-create Policy Java Object Cache.
Cause: Could not re-create the Policy Cache.
Action: You may need to restart the server.

Level: 1

Type: ERROR

Impact: Compliance

WSM-06156: The policy referenced by URI "{0}" could not be retrieved since the URI is invalid.
Cause: The policy URI is missing, empty or contains invalid characters.
Action: Provide a valid URI for a policy in the repository or remove the reference.

Level: 1

Type: ERROR

Impact: Compliance

WSM-06157: The policy referenced by URI "{0}" could not be retrieved due to incorrect repository configuration.
Cause: The repository database is not configured correctly or not running.
Action: Verify that the repository database is configured correctly according to the user documentation and is running.

Level: 1

Type: ERROR

Impact: Compliance

WSM-06158: The policy referenced by URI "{0}" does not exist in the repository.
Cause: The referenced policy does not exist in the repository.
Action: Provide the URI for a policy in the repository or load the desired policy into the repository.

Level: 1

Type: ERROR

Impact: Data

WSM-06159: The policy referenced by URI "{0}" could not be retrieved due to invalid credential being used to connect to the Policy Manager.
Cause: Cannot connect to the policy manager due to credential issue.
Action: Verify that credentials are correctly specified, if not using the default principal, and that the principal is authorized to access the policy manager application.

Level: 1

Type: ERROR

Impact: Compliance

WSM-06160: The policy referenced by URI "{0}" could not be retrieved since Policy Manager is either not deployed or not in ACTIVE state.
Cause: The policy manager application has not been deployed or is not running.
Action: Verify that the policy manager application is deployed and configured correctly and in an active state.

Level: 1

Type: ERROR

Impact: Compliance

WSM-06161: The policy referenced by URI "{0}" could not be retrieved since Policy Manager is not deployed.
Cause: The policy manager application has not been deployed.
Action: Verify that the policy manager application is deployed.

Level: 1

Type: ERROR

Impact: Compliance

WSM-06162: The policy referenced by URI "{0}" could not be retrieved as connection to Policy Manager cannot be established at "{1}" due to invalid configuration or inactive state.
Cause: The policy manager application is not running or is not configured correctly.
Action: Verify that the policy manager application is configured correctly and is in an active state. Provide correct configuration for URL of policy manager, setting its listen address if using auto-discovery, and ensure that any required SSL certificate is valid.

Level: 1

Type: ERROR

Impact: Compliance

WSM-06201: The {0} repository accessor class cannot be accessed due to underlying error "{1}".
Cause: The nullary constructor for the specified accessor is not accessible to the configuration framework.
Action: Specify a valid accessor.

Level: 1

Type: ERROR

Impact: Configuration

WSM-06202: The {0} repository accessor class cannot be initialized due to underlying error "{1}".
Cause: A exception was encountered during evaluation of a static initializer for the specified accessor class.
Action: Specify a valid accessor.

Level: 1

Type: ERROR

Impact: Configuration

WSM-06203: The {0} repository accessor class cannot be used as a repository accessor because it does not implement the {1} interface.
Cause: The specified accessor does not implement the IRepositoryAccessor interface.
Action: Specify a valid accessor.

Level: 1

Type: ERROR

Impact: Configuration

WSM-06204: The {0} repository accessor class cannot be linked due to underlying error "{1}".
Cause: The specified accessor depends on a class whose signature has changed since the accessor was compiled.
Action: Update the accessor class or revert to an older version of the dependent class.

Level: 1

Type: ERROR

Impact: Configuration

WSM-06205: The repository accessor "{0}" cannot be found due to underlying error "{1}".
Cause: The specified accessor was not found.
Action: Specify a valid accessor.

Level: 1

Type: ERROR

Impact: Configuration

WSM-06206: The {0} repository accessor class cannot be instantiated due to underlying error "{1}".
Cause: The specified accessor is an abstract class, an interface, an array class, a primitive type, or void, or the class does not have a nullary constructor.
Action: Specify a valid accessor.

Level: 1

Type: ERROR

Impact: Configuration

WSM-06207: A task scheduler was not available for configuring the {0} repository accessor for context "{1}".
Cause: A task scheduler was not supplied to the configuration framework.
Action: Provide a task scheduler to the configuration framework.

Level: 1

Type: WARNING

Impact: Configuration

WSM-06208: Access to the {0} repository accessor class is denied due to underlying error "{1}".
Cause: The configuration framework does not have permission to instantiate the specified accessor.
Action: Ensure the necessary permissions are granted to the WSM code base.

Level: 1

Type: ERROR

Impact: Configuration

WSM-06209: An action executor cannot be created for user "{0}" due to underlying error "{1}".
Cause: The configuration framework did not have permission to get an action executor.
Action: Ensure the necessary permissions are granted to the WSM code base.

Level: 1

Type: ERROR

Impact: Configuration

WSM-06210: An instance of the {2} bean for the local repository at path "{3}" was not available for configuring the {0} repository accessor for context "{1}".
Cause: A bean instance could not be obtained by the configuration framework.
Action: Correct underlying problem and wait for coniguration refresh.

Level: 1

Type: WARNING

Impact: Configuration

WSM-06211: An instance of the {2} bean for the local repository at path "{3}" was provided for configuring the {0} repository accessor for context "{1}".
Cause: A bean instance was obtained by the configuration framework.
Action: None.

Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-06212: An instance of the {2} bean for a remote repository was not available for configuring the {0} repository accessor for context "{1}".
Cause: A bean instance could not be obtained by the configuration framework.
Action: Correct underlying problem and wait for coniguration refresh.

Level: 1

Type: WARNING

Impact: Configuration

WSM-06213: An instance of the {2} bean for a remote repository was provided for configuring the {0} repository accessor for context "{1}".
Cause: A bean instance was obtained by the configuration framework.
Action: None.

Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-06214: A task scheduler was provided for configuring the {0} repository accessor for context "{1}".
Cause: A task scheduler was supplied to the configuration framework.
Action: None.

Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-06215: An instance of the {1} bean for the local repository at path "{2}" was not available for configuring the {0} repository accessor for the default context.
Cause: A bean instance could not be obtained by the configuration framework.
Action: Correct underlying problem and wait for coniguration refresh.

Level: 1

Type: WARNING

Impact: Configuration

WSM-06216: An instance of the {1} bean for the local repository at path "{2}" was provided for configuring the {0} repository accessor for the default context.
Cause: A bean instance was obtained by the configuration framework.
Action: None.

Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-06217: An instance of the {1} bean for a remote repository was not available for configuring the {0} repository accessor for the default context.
Cause: A bean instance could not be obtained by the configuration framework.
Action: Correct underlying problem and wait for coniguration refresh.

Level: 1

Type: WARNING

Impact: Configuration

WSM-06218: An instance of the {1} bean for a remote repository was provided for configuring the {0} repository accessor for the default context.
Cause: A bean instance was obtained by the configuration framework.
Action: None.

Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-06219: A task scheduler was not available for configuring the {0} repository accessor for the default context.
Cause: A task scheduler was not supplied to the configuration framework.
Action: Provide a task scheduler to the configuration framework.

Level: 1

Type: WARNING

Impact: Configuration

WSM-06220: A task scheduler was provided for configuring the {0} repository accessor for the default context.
Cause: A task scheduler was supplied to the configuration framework.
Action: None.

Level: 1

Type: NOTIFICATION

Impact: Configuration

WSM-06221: The password credentials cannot be obtained from the Credential Store.
Cause: Failure occurred while querying for credentials from CSF.
Action: Check CSF configuration.

Level: 1

Type: ERROR

Impact: Configuration

WSM-06222: The credentials passed to the credentials store are expired.
Cause: The Credentials have expired.
Action: Ensure valid credentials are passed

Level: 1

Type: ERROR

Impact: Configuration

WSM-06223: The access to the store or credentials is denied.
Cause: The requested access Credentials or Store is denied.
Action: Ensure Store is properly initialized and valid credentials are passed

Level: 1

Type: ERROR

Impact: Configuration

WSM-06224: Unexpected exception "{0}" caught when privileged method is called.
Cause: Unexpected exception caught on calling a privileged code.
Action: Check the underlying signature of method called in privileged code

Level: 1

Type: ERROR

Impact: Configuration

WSM-06225: Unable to retrieve credentials for the specified CSF key {0}.
Cause: Credential configuration in the policy accessor configuration file was incorrect.
Action: Configure policy with valid CSF key.

Level: 1

Type: ERROR

Impact: Configuration

WSM-06301: Subject Metadata is required when registering a listener.
Cause: A null value was provided for the subject metadata.
Action: Provide a valid metadata.

Level: 1

Type: ERROR

Impact: Programmatic

WSM-06302: A listener is required for asynchronous notification.
Cause: A null value was provided for asynchronous listener registration.
Action: Provide a valid listener.

Level: 1

Type: ERROR

Impact: Programmatic

WSM-06303: The method "{0}" was not called with required permission "{1}"
Cause: The method was not called with required permission
Action: Ensure necessary permissions are granted to the caller before calling the required methods.

Level: 1

Type: ERROR

Impact: Security

WSM-07501: Failure in Oracle WSM Agent processRequest, category={0}, function={1}, application={2}, composite={3}, modelObj={4}, policy={5}, policyVersion={6}, assertionName={7}.
Cause: Processing request failed in the security interceptor while enforcing policy.
Action: Check the log file for possible causes.

Level: 1

Type: ERROR

Impact: Configuration

WSM-07502: Failure in Oracle WSM Agent processResponse, category= {0}, function={1}, application={2}, composite={3}, modelObj={4}, policy={5}, policyVersion={6}, assertionName={7}.
Cause: Processing response failed in the security interceptor while enforcing policy.
Action: Check the log file for possible causes.

Level: 1

Type: ERROR

Impact: Configuration

WSM-07503: Failure in Oracle WSM Agent processFault, category= {0}, function={1}, application={2}, composite={3}, modelObj={4}, policy={5}, policyVersion={6}, assertionName={7}.
Cause: Processing fault failed in the security interceptor while enforcing policy.
Action: Check the log file for possible causes.

Level: 1

Type: ERROR

Impact: Configuration

WSM-07504: Failure in Oracle WSM Agent processEvent, category= {0}, function={1}, application={2}, composite={3}, modelObj={4}.
Cause: Processing Fabric Lifecycle event failed in security interceptor.
Action: Check the log file for possible causes

Level: 1

Type: ERROR

Impact: Configuration

WSM-07505: Failure in Oracle WSM Agent initialization, category= {0}, function={1}.
Cause: Agent initialization failed in the security interceptor.
Action: Check the log file for possible causes.

Level: 1

Type: ERROR

Impact: Configuration

WSM-07506: Failure in Oracle WSM Agent processFinish, category= {0}, function={1}, application={2}, composite={3}, modelObj={4}.
Cause: Agent finish failed in the security interceptor.
Action: Check the log file for possible causes.

Level: 1

Type: ERROR

Impact: Configuration

WSM-07507: Failure in Oracle WSM Agent, category= {0}, function={1}, stage={2} due to RuntimeException.
Cause: An unexpected RuntimeException was encountered while trying to access security interceptor.
Action: Check the log file for possible causes and retry the operation.

Level: 1

Type: WARNING

Impact: Data

WSM-07508: Oracle WSM Agent must be initialized before policy enforcement
Cause: Agent not initialized
Action: Initialize the Agent with required parameters

Level: 1

Type: ERROR

Impact: Configuration

WSM-07509: Oracle WSM Agent must be initialized with valid properties. Following parameters [{0}] are either Empty or null
Cause: Agent not initialized with valid parameters.
Action: Initialize the Agent with required parameters

Level: 1

Type: ERROR

Impact: Configuration

WSM-07600: Error while copying the message.
Cause: An unexpected error occurred while cloning SOAP or normalized message context.
Action: Retry the operation. If the problem persists, contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Security

WSM-07601: Failure initializing the WSPolicyExecutor class {0}.
Cause: An unexpected error occurred while initializing the policy engine.
Action: Retry the operation. If the problem persists, contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-07602: Failure in WS-Policy Execution due to exception.
Cause: Due to an unexpected error, policy execution failed at runtime.
Action: Check the log file for possible causes.

Level: 1

Type: ERROR

Impact: Security

WSM-07603: Failure in log assertion execution caused by exception.
Cause: File I/O problem or SOAP message access problem occurred.
Action: Verify file access permission and the SOAP message.

Level: 1

Type: ERROR

Impact: Files

WSM-07604: Internal error during policy enforcement.
Cause: An unexpected error occurred while enforcing the policy.
Action: Retry the operation. If the problem persists, contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Security

WSM-07605: The binding.ws port ID {0} is invalid.
Cause: An unexpected error occurred in the Oracle WSM processEvent API.
Action: Retry the operation. If the problem persists, contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-07606: Policy {0} execution failure.
Cause: Due to an unexpected error, policy execution failed at runtime.
Action: Check the log file for possible causes.

Level: 1

Type: ERROR

Impact: Security

WSM-07607: Failure in execution of assertion {0} executor class {1}.
Cause: The policy engine failed to execute an assertion.
Action: Check the log file for possible causes.

Level: 1

Type: ERROR

Impact: Security

WSM-07608: The assertion type is not valid.
Cause: Policy execution failed due to an invalid assertion.
Action: Check the assertion type.

Level: 1

Type: ERROR

Impact: Security

WSM-07609: Policy with attachto value of {0} cannot be applied to subject of type {1}.
Cause: The attached policy was incompatible with the subject.
Action: Verify that the subject type and the policy's Attachto value are compatible.

Level: 1

Type: ERROR

Impact: Security

WSM-07610: Internal error in policy status audit. One or more of the argument passed is null, result:{0}, agentFunction:{1}, policy:{2}, msgCtx:{3}
Cause: An internal error occurred; the enforcement auditor encountered one or more null arguments.
Action: Retry the operation. If the problem persists, contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-07611: Failure initializing of enforcement auditor: category={0}, function= {1}, topologyNode={2}.
Cause: An internal error occurred; the enforcement auditor initialization failed.
Action: Retry the operation. If the problem persists, contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-07612: Failure shutting down enforcement auditor.
Cause: An internal error occurred; the enforcement auditor shutdown failed.
Action: Retry the operation. If the problem persists, contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-07613: Failure enforcing auditing policy.
Cause: An internal error occurred while auditing security or management policy enforcement.
Action: Retry the operation. If the problem persists, contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-07614: Failure in Agent initialization due to invalid topology node path. Topology node path cannot be null or empty for non-JSE client. category={0}, function={1}, topologyNode={2}, isRunningInJEE={3}
Cause: Oracle WSM Agent initialization failed due to problem creating and initializing DMS instrumentation. An invalid, null, or empty topology node path was encountered for non-JSE client.
Action: Retry the operation. If the problem persists, contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Configuration

WSM-07616: Resource name not retrievable from MessageContext. Guard evaluation requires resource name to be present in MessageContext
Cause: Resource name not retrievable from MessageContext. Guard evaluation requires resource name to be present in MessageContext
Action: Retry the operation. If the problem persists, contact Oracle Support Services.

Level: 32

Type: INCIDENT_ERROR

Impact: Security

WSM-07617: Policy: {0} contains unsupported assertions.
Cause: Policy contains unsupported assertions. Assertions of type http-security are not supported for WLS JAXWS web services.
Action: Check the assertion type.

Level: 1

Type: ERROR

Impact: Security

WSM-07618: Failed to execute the assertion "{0}" in the conditional policy. {1}
Cause: Failed to execute the assertion
Action: Check exception stack trace for details

Level: 1

Type: ERROR

Impact: Security

WSM-07619: Failed to retrieve the Welogic Server subject.
Cause: An error occurred while retrieving Weblogic Server subject.
Action: Check log file for possible cause.

Level: 1

Type: ERROR

Impact: Security

WSM-09001: The audit event definitions cannot be found.
Cause: Component audit event definitions were missing.
Action: Check the installation for any missing or corrupted JAR files.

Level: 1

Type: ERROR

Impact: Configuration

WSM-09002: The audit event definitions file cannot be opened.
Cause: Component audit event definitions could not be opened.
Action: Check the installation for any corrupted JAR files, or free up system resources.

Level: 1

Type: ERROR

Impact: Configuration

WSM-09003: The audit event definitions file cannot be read.
Cause: Component's audit event definitions were not readable.
Action: Check the installation for any corrupted JAR files.

Level: 1

Type: ERROR

Impact: Configuration

WSM-09004: Component auditing cannot be initialized.
Cause: The audit framework encountered an error.
Action: Check the logs for the possible causes.

Level: 1

Type: WARNING

Impact: Logging

WSM-09005: It is not possible to verify that the event is enabled.
Cause: The audit framework encountered an error.
Action: Check the logs for the possible causes.

Level: 1

Type: ERROR

Impact: Logging

WSM-09007: The event cannot be audited.
Cause: The audit framework encountered an error.
Action: Check the logs for the possible causes.

Level: 1

Type: ERROR

Impact: Logging

WSM-09008: A URL cannot be created for {0}.
Cause: XML utility encountered an error.
Action: Check the logs for the possible causes.

Level: 1

Type: ERROR

Impact: Logging

WSM-09009: Failure parsing the XML file
Cause: XML utility encountered an error.
Action: Check the logs for the possible causes.

Level: 1

Type: ERROR

Impact: Logging

WSM-09010: Error opening and/or closing the stream
Cause: XML utility encountered an error.
Action: Check the logs for the possible causes.

Level: 1

Type: ERROR

Impact: Logging

WSM-09011: Error writing the XML file
Cause: XML utility encountered an error.
Action: Check the logs for the possible causes.

Level: 1

Type: ERROR

Impact: Logging

WSM-09012: Key, {0}, is not found in the resource bundle {1}.
Cause: No key was found in the provided resource bundle.
Action: Add the key to the resource bundle and retry the operation.

Level: 1

Type: ERROR

Impact: Configuration

WSM-09013: Failure shutting down auditing.
Cause: An exception was caught when attempting to shut down the audit framework.
Action: Examine the stack trace for any underlying errors.

Level: 1

Type: WARNING

Impact: Logging

WSM-09014: Streaming SOAP message attachment is not being logged.
Cause: SOAP message attachment was not logged because it was a streaming attachment.
Action: Check the logs for the possible causes.

Level: 1

Type: WARNING

Impact: Logging

WSM-09015: Interrupted while checking out object from pool.
Cause: Received interrupt while checking out from pool.
Action: Check the logs for the possible causes.

Level: 1

Type: ERROR

Impact: Other

WSM-09016: Failure creating transformer using factory {0}.
Cause: Transformer factory failed to create new transformer instance.
Action: Check the logs for the possible causes.

Level: 1

Type: ERROR

Impact: Other

WSM-09017: Failure checking out a transformer instance.
Cause: Failure checking out a transformer instance.
Action: Check the logs for the possible causes.

Level: 1

Type: ERROR

Impact: Other

WSM-09018: A ScheduledExecutorService is required when creating a scheduler wrapper.
Cause: A ScheduledExecutorService was not provided when constructing a wrapper.
Action: Provide a valid ScheduledExecutorService instance.

Level: 1

Type: ERROR

Impact: Other

WSM-09019: An executor requires a task for scheduling.
Cause: A task was not provided when scheduling a task.
Action: Provide a valid task.

Level: 1

Type: ERROR

Impact: Other

WSM-09020: An executor rejected a task due to error "{0}".
Cause: The ScheduledExecutorService refused to schedule a task.
Action: Check the logs for the possible causes.

Level: 1

Type: ERROR

Impact: Other

WSM-09021: A TimerManager is required when creating a scheduler wrapper.
Cause: A TimerManager was not provided when constructing a wrapper.
Action: Provide a valid TimerManager instance.

Level: 1

Type: ERROR

Impact: Other

WSM-09022: A timer cannot schedule a task due to illegal argument error "{0}".
Cause: The scheduling parameters were negative.
Action: Provide non-negative values.

Level: 1

Type: ERROR

Impact: Other

WSM-09023: A timer cannot schedule a task due to illegal state error "{0}".
Cause: A task could not be scheduled because the underlying TimerManager was stopped.
Action: Schedule the task using a running TimerManager.

Level: 1

Type: ERROR

Impact: Other

WSM-09024: Failure parsing the XML URL when: {0}, from: {1}
Cause: XML utility parseXMLDocument from URL encountered an error.
Action: Check the logs for the possible causes.

Level: 1

Type: ERROR

Impact: Logging