Explanation: OSGI Bundle has started
User response: None
Explanation: The AUID Descriptor File could not be parsed
User response: Please ensure the AUID Descriptor File is correct
Explanation: The XCAP-CAPS file could not be parsed either because the XML file is not well formed or the schemas have a loading order dependency.
User response: Please ensure the XCAP-CAPS file is correct or the /WEB-INF/schema/schema_order.properties lists the correct schema loading order.
Explanation: An error was encountered loading the helper functions
User response: Please ensure the AUID Descriptor File is correct
Explanation: An error was encountered loading the XCAP Filters
User response: Please ensure the AUID Descriptor File is correct and the XCAP Filter classes defined in it exist
Explanation: An error was encountered initializing XML Schema Files
User response: Please ensure your schemas are valid and if necessary, insure the ordering is correct in schema_order.properties
Explanation: The XCAP-CAPS file could not be found
User response: Please ensure the XCAP-CAPS file exists in your web module
Explanation: The AUID Descriptor File could not be found
User response: Please ensure the AUID Descriptor File exists in your web module
Explanation: The base Error XML Document could not be parsed
User response: Please contact IBM Support
Explanation: PUT failed while interacting with the database
User response: Please ensure your database settings are correct
Explanation: DELETE failed while interacting with the database
User response: Please ensure your database settings are correct
Explanation: GET failed while interacting with the database
User response: Please ensure your database settings are correct
Explanation: The content-type header is either missing or invalid.
User response: Please ensure that the content-type header is correctly specified.
Explanation: The root element does not comply with namespace of the application usage.
User response: Please ensure that the parent element namespace within the document is correctly specified.
Explanation: The XCAP PUT or POST request requires XML content.
User response: Please ensure that XML content is sent in the XCAP request.
Explanation: Datasource or the Resource Provider Enviroment configuration is not valid.
User response: Please ensure the datasource and Resource Provider Environment is valid for your AUID.
Explanation: The list contains more entries than the maximum allowed.
User response: Please ensure the list does not contain more entries than are specified in the listMaximumMembers property.
Explanation: The list contains fewer entries than the minimum allowed.
User response: Please ensure the list does not contain fewer entries than are specified in the listMinimumMembers property.
Explanation: No AUID properties file exists in the WAR file for this AUID.
User response: None if no Resource Environment Provider is required for this AUID. If a Resource Environment Provider should be created, then ensure the properities file is in the WAR file with the path /WEB-INF/auids/<AUID>.properties.
Explanation: No AUID properties file exists in the WAR file for this AUID.
User response: None if no Resource Environment Provider is required for this AUID. If a Resource Environment Provider should be created, then ensure the properities file is in the WAR file with the path /WEB-INF/auids/<AUID>.properties.
Explanation: Datasource or the Resource Provider Enviroment configuration is not valid.
User response: Please ensure the datasource and Resource Provider Environment is valid for your AUID.
Explanation: Datasource or the Resource Provider Enviroment configuration may not be valid.
User response: Please ensure the datasource and Resource Provider Environment is valid for your AUID.
Explanation: Datasource or the Resource Provider Enviroment configuration is not valid.
User response: Please ensure the datasource and Resource Provider Environment is valid for your AUID.
Explanation: XQuery failed while interacting with the database
User response: Please ensure your database settings are correct
Explanation: AUID descriptor file is incorrect or the helper function is not available on the application server's classpath
User response: Please ensure the AUID Descriptor File is correct and the helper function is in the application server's classpath
Explanation: The xcapRoot property is required for successful operation of XCAP and SIP for the XDMS.
User response: Please ensure that the xcapRoot is defined for the ibm-xdms Resource Environment Provider.
Explanation: A subscription was not removed because it may have been previously removed.
User response: No user action required.
Explanation: All rls-services document must have unique service URIs.
User response: Remove the redundant rls-services document service URI to ensure uniqueness.
Explanation: An error occurred while refreshing the configuration settings for an REP.
User response: Ensure super admin user is setup correctly in global REP, also examine log file for more information.
Explanation: Failed retrieving configuration settings for Resource Environment Provider
User response: Ensure the Resource Environment Provider exists and as Custom Properties defined. Ensure nodes have been synchronized with latest configuration.
Explanation: An error occurred while trying to log into WebSphere.
User response: Ensure the super admin username and password are set correctly in the ibm-xdms Resource Environment Provider. Ensure nodes have been synchronized with latest configuration.
Explanation: An error occurred while encoding or decoding a Resource Environment Provider's custom property.
User response: Ensure the super admin username and password are set correctly in the ibm-xdms Resource Environment Provider. Ensure nodes have been synchronized with latest configuration.
Explanation: The IETF simple-xcap specification does not allow XCAP modifications of element namespaces.
User response: Do not delete or modify existing namespaces specified with a Node Selector
Explanation: The IETF simple-xcap specification does not allow a namespace referenced as an element attribute.
User response: Do not reference a namespace as an attribute with a Node Selector
Explanation: Usage record datasource or the Resource Provider Enviroment configuration is not valid.
User response: Please ensure the usage record datasource and Resource Provider Environment is valid for your AUID.
Explanation: The XDMS was unable to retreive a UserTransaction object from the Application Server
User response: Please contact IBM Support
Explanation: The XDMS was unable to commit the UserTransaction object from the Application Server
User response: Please contact IBM Support
Explanation: The XDMS was unable to begin the UserTransaction object from the Application Server
User response: Please contact IBM Support
Explanation: The XDMS was unable to rollback the UserTransaction object from the Application Server
User response: Please contact IBM Support
Explanation: The HTTP PUT method was called on the global index document. This operation is restricted.
User response: Do not attempt to PUT a global index document
Explanation: An attempt was made to change the name attribute of a list element.
User response: Do not change the name attribute
Explanation: Constraint validation failed because the request would have resulted in a list element which does not contain the required attribute name
User response: Always include the name attribute in a list element
Explanation: The request failed because the name attribute of a top-level does not conform to the OMNA URI List Usage Name Registry
User response: See the registry specification to create a valid name
Explanation: The resource-list element must contain an absolute HTTP URI
User response: Change the resource-list element to contain an absolute HTTP URI
Explanation: The resource-list element must contain a valid URI
User response: Change the resource-list element to contain a valid URI
Explanation: The resource-list element URI must have the AUID resource-lists
User response: Change the resource-list element to have an AUID of resource-lists
Explanation: The resource-list element must contains an XUI which matches the RLS services document
User response: Change the resource-list element to have an XUI to match the RLS services document
Explanation: The entry element must have the uri attribute
User response: Add a uri attribute to the entry element
Explanation: The entry-ref element must have a ref attribute
User response: Add a ref attribute to the entry-ref element
Explanation: The entry-ref element's ref attribute must be a relative path
User response: Change the entry-ref element's ref attribute to be a relative path
Explanation: The external element's anchor attribute must be an absolute HTTP URI
User response: Change the external element's anchor attribute to be an absolute HTTP URI
Explanation: The HTTP DELETE method was called on the global index document. This operation is restricted.
User response: Do not attempt to DELETE a global index document
Explanation: enableExternalElementValidation is enabled, therefore the client must not have <external> elements which cause circular references
User response: Client should remove any circular references and retry their request
Explanation: An <external> element in the document or a referenced document contains an invalid XCAP URI
User response: The client should insure all <external> elements contain valid XCAP URIs
Explanation: The node selector must be qualified by an attribute when performing a HTTP GET on the global index
User response: Retry the request using a node selector qualified by an attribute
Explanation: Either the global-index-nodeselector is not configured for this AUID, or the client sent a node selector which does not match the global-index-nodeselector pattern
User response: Insure the global-index-nodeselector element is configured in the AUID XML file or the client is sending a node selector which corresponds to the global-index-nodeselector pattern
Explanation: The specified element was found after the appusages element in an OMA resource-list index document
User response: Rearrange the document so that the appusages element comes after other list, entry, entry-ref, and external elements at the same level
Explanation: More than one appusages element was found in a list. Each list should only have one appusages element
User response: Retry the request with only one appusages element
Explanation: The anchor attribute is mandatory for the external element in a resource list document
User response: Retry the request with an anchor attribute in the external element
Explanation: The entry-ref element's ref attribute must be a relative URI which resolves to an <entry> element with a resource-lists document
User response: Correct the entry-ref element's ref attribute to resolve to an <entry> element with a resource-lists document
Explanation: Failed to publish a JMS message about a change to a document
User response: Please ensure you Service Integration Bus was properly created and that your JMS messaging engine is running
Explanation: The HTTP GET method was called on the global index document. This operation is restricted.
User response: Do not attempt to GET a global index document without a node selector
Explanation: The domain attribute must be a valid domain name
User response: Correct the domain attribute to be a valid domain name
Explanation: A resource-list element in a global RLS services document must exist underneath any user's home directory in the resource-lists application usage
User response: Change the resource-list element to have an XUI
Explanation: A resource-list element must have an XCAP root which is the same as the XCAP root of the RLS services document
User response: Change the resource-list element to have an XCAP root which matches the XCAP root for the RLS services document
Explanation: The anchor attribute of the external element must contain a valid URI
User response: Change the anchor attribute of the external element to contain a valid URI
Explanation: The anchor attribute of the external element URI must have the AUID resource-lists
User response: Change the anchor attribute of the external element to have an AUID of resource-lists
Explanation: The anchor attribute of the external element must resolve to a list element
User response: Change the anchor attribute of the external element to resolve to a list element
Explanation: The resource-list element must resolve to a list element
User response: Change the resouce-list element to resolve to a list element
Explanation: The anchor attribute of the external element must be a URI which resolves to a <list> element with a resource-lists document
User response: Correct the anchor attribute of the external element to resolve to a <list> element with a resource-lists document
Explanation: The <conditions> element does not support <sphere>, <validity>, or <other-identity> elements.
User response: Please remove the unsupported <sphere>, <validity>, or <other-identity> elements.
Explanation: The <rule> element must contain an id attribute of read, write, delete, or admin.
User response: Please specify only read, write, delete, or admin for the <rule> element id attribute.
Explanation: The <conditions> element must not contain more than one of each <external-list>, <anonymous-request>, or <identity> element.
User response: Please specify no more than one of each <external-list>, <anonymous-request>, or <identity> element for a <conditions> element.
Explanation: The SIP Servlet is terminating.
User response: To restart the servlet, access the IBM Administrative Console and restart the XDMS application.
Explanation: The HTTP Servlet is terminating.
User response: To restart the servlet, access the IBM Administrative Console and restart the XDMS application.
Explanation: The uri attribute of a service element failed a constraint provided by a custom UriHelper.validate() method.
User response: Specify a value for the uri attribute of the service element which will pass the custom validate method.
Explanation: The uri attribute of a service element failed to parse into a URI object. The uri attribute is malformed.
User response: Correct the value of the uri attribute of the service element to contain a well formed URI.
Explanation: The Node Selector selected another portion of the document after performing the delete, this is in violation of the XCAP specification
User response: The client should adjust its Node Selector accordingly, and retry the request
Explanation: The Node Selector selected another portion of the document after performing the PUT, this is in violation of the XCAP specification
User response: The client should adjust its Node Selector accordingly, and retry the request
Explanation: When trying to parse the alarmInterval REP, an exception occurred.
User response: Please check the REP and ensure it is a valid integer.
Explanation: The <conditions> element must not contain more than one of each <identity>, <external-list>, <other-identity>, or <anonymous-request> element.
User response: Please specify no more than one of each <identity>, <external-list>, <other-identity>, or <anonymous-request> element for a <conditions> element.
Explanation: The XQuery request the client sent violates the Application Usage
User response: The client should ensure their search request adheres to the application usage, or not send one if the application usage does not support search.
Explanation: The URL for the external authorization list or entry is either malformed or the SharedList XDMS is unavailable.
User response: Verify the accuracy of the URL and the availability of the SharedList XDMS. Until resolved authorization is denied for users defined in the list or entry.
Explanation: The request AUID is protected by authorization policies that make use of the directory.xml.
User response: Please choose another document name besides directory.xml. The document name directory is acceptable without the .xml file extension.
Explanation: A portion of the node selector used for Global Index is invalid.
User response: Ensure the node selector template defined in the global-index-nodeselector element of your AUID descriptor file is correct
Explanation: XDMS tried to get configuration data from WebSphere, but the configuration object was not found.
User response: Ensure the super admin username and password are set correctly in the ibm-xdms Resource Environment Provider. Ensure nodes have been synchronized with latest configuration.
Explanation: The entry included in the SIP SUBSCRIBE does not match the Node Level Constraints defined in the AUID descriptor file
User response: Check your subscription against the Node Level Constraints in the AUID Descriptor file
Explanation: The entry included in the SIP SUBSCRIBE contains an AUID that does not exist
User response: Check the AUID defined for this entry
Explanation: The user that issued this SUBSCRIBE request does not have access to subscribe to this entry
User response: Check the authorization policy documents to make sure the user has read access for this entry
Explanation: The service element could not be found via the global index
User response: Check entry or wait until service element is present again to subscribe
Explanation: The entry included in the SIP SUBSCRIBE does not match the Global Index Constraint defined in the AUID descriptor file
User response: Check your subscription against the Global Index Constraint in the AUID Descriptor file
Explanation: The entry included in the SIP SUBSCRIBE contains an xcap-root that does not match the xcap-root specified in the REP
User response: Check the xcap-root of the entry and the xcap-root specified in the REP
Explanation: The entry included in the SIP SUBSCRIBE is not a valid URI
User response: Change the entry to a valid URI
Explanation: The common-usages element must have the id attribute
User response: Add a id attribute to the common-usages element
Explanation: Each entry element must contain only one uriusages element
User response: Remove multiple uriusages elements from the entry
Explanation: entry-ref elements are not allowed in group-usage-list documents
User response: Remove the entry-ref elements
Explanation: external elements are not allowed in group-usage-list documents
User response: Remove the external elements
Explanation: There cannot be multiple <rule> elements with the same id attribute
User response: Please do not specify multiple <rule> elements with the same id attribute.
Explanation: There <rule> element had an id that did not match the <nodeLevelConstraints>
User response: Form the id attribute of the <rule> element to match the <nodeLevelConstraints> for the AUID of the document rule is reffering to.
Explanation: The one element id attribute must contain a SIP URI or a TEL URI
User response: Change the id attribute of the one element to a SIP URI or a TEL URI
Explanation: The except element id attribute must contain a SIP URI or a TEL URI
User response: Change the id attribute of the except element to a SIP URI or a TEL URI
Explanation: An external element contains an anchor that is malformed
User response: Use a valid document URI for the external element
Explanation: The AUID value of the Document or Node URI propsed in an <external-list> should be resource-lists
User response: Change the extenal-list element to point to a resource-list document
Explanation: XUI value of the Document or Node URI propsed in an <external-list> element does not match the XUI of the User Access Policy Document URI
User response: Change the XUI so that it matches
Explanation: The value of the 'uri' attribute of the <user-profile> element must be the same as the XUI value of the Document URI for the User Profile document
User response: Change the value of the uri attribute to the XUI of the Document URI for the User Profile document
Explanation: The document must be named 'user-profile'
User response: Name the document 'user-profile'
Explanation: The document must be named 'lockedprofile'
User response: Name the document 'lockedprofile'
Explanation: Cannot have more than one list-service element defined
User response: Remove multiple list-service elements
Explanation: A uri attribute does not match constraints
User response: Update URI to match constraints
Explanation: URI already exists
User response: Form unique URI
Explanation: Cannot have more than one max-participant-count element defined
User response: Remove multiple max-participant-count elements
Explanation: Maximum number of participants exceeded or is invalid
User response: Modify max-participant-count
Explanation: The uri of the entry element matches an existing entry element of the list
User response: Retry with unique uri
Explanation: The list element may not contain an entry-ref element
User response: Remove entry-ref element
Explanation: The <conditions> element may not contain more than one child element of <external-list>, <anonymous-request>, <other-identity> or <is-list-member>
User response: Remove multiple child elements of the <condtitions> element
Explanation: Automatic group advertisement not supported
User response: Automatic group advertisement not supported
Explanation: The identity in the request does not have access to perform the operation
User response: The identity in the request does not have access to perform the operation
Explanation: The document must be named 'access-rules'
User response: Name the document 'access-rules'
Explanation: A uri attribute does not match constraints
User response: Update URI to match constraints
Explanation: Failed to write Usage Record
User response: Please ensure the Usage Record DB is up and running
Explanation: User is doing a PUT with XML content greater than 4000 characters on an Oracle DB. This causes the Temp Tablespace to grow
User response: Disallow PUTs with XML content greater than 4000 characters or monitor the temp tablespace on the Oracle DB