3.1.4.1 Error Handling

The WSUSAR protocol allows a server to notify a client of an application-level fault by generating a SOAP fault as specified in [SOAP1.1] section 4.4. The format for the fault is as shown below, where the XML MUST implement the specified format in the fault's <detail> element.

 <Exception
   Assembly="[string]"
   Type="[exception type]"
   Message="[string]" />
            

Assembly: Represents the fully qualified name of the binary file in which the type of the exception is implemented.

Message: Contains an informational message that explains the error that occurred.

Type: Identifies the exact type of the exception that occurred. This specification defines the following exception types.

Type	Description
Microsoft.UpdateServices.Administration.WsusObjectNotFoundException	This exception message MUST be sent by the server implementation if a WSDL operation performs a query for a certain object, but that object cannot be found in the update server.
Microsoft.UpdateServices.Administration.WsusObjectAlreadyExistsException	This exception message MUST be sent by the server implementation if a WSDL operation performs a query for a certain object, but that object already exists in the update server.
System.ArgumentNullException	This exception message MUST be sent by the server implementation if a required parameter in a request message of a WSDL operation is missing.
Microsoft.UpdateServices.Internal.WsusServiceException	This exception message MUST be sent by the server implementation if a WSDL operation attempts to start or stop the WSUS service, but the attempt fails.
System.ArgumentOutOfRangeException	This exception message MUST be sent by the server implementation when a parameter in a message of a WSDL operation does not fit within the specified range.

Note Unless otherwise noted, the protocol server implementation MUST send a System.ArgumentNullException SOAP fault whenever a parameter is missing that MUST be present.