2.7 Error Handling
The RMS protocols are SOAP-based protocols that use HTTP 1.1 for transport. The protocols allow a server to notify a client of application-level faults by generating SOAP faults as specified in [SOAP1.1] section 4.4. In the SOAP fault, the faultcode element contains the type of exception that is being thrown. The faultstring element contains the text of the exception that is being thrown. For more information about the SOAP faults from the RMS server, see [MS-RMPR] section 3.1.4.5 and [MS-RMPRS] section 2.2.9.1.
Some common areas of failure are:
The certificate or license format or arguments are invalid.
The certificate or license has expired.
Access is unauthorized.
The email address is invalid or formatted incorrectly.
The machine certificate (SPC) is not valid.
A certificate or license has been tampered with (signature validation failed).
The VersionData element contains an invalid or unsupported version number.
The user does not have rights in the publishing license (PL).
The certificate or license did not come from a trusted issuer.
The RMS protocols cannot function if there are failures on the services that they depend on, such as network connectivity, availability of DNS, or availability of a directory service.
Note The Binary Group Expansion interface uses the HTTP transport ([RFC1945] and [RFC2616]) and does not generate SOAP faults.