Handling SOAP Exceptions
If a Groove Web Services operation fails, it generates a SOAP exception and has no effect. Operations can generate SOAP exceptions for many reasons including errors in the operation parameters or lack of Groove permissions to perform the specified operation.
In general, you should provide exceptions when handling code, since any Groove Web Services request can fail even if there are no coding errors.
Operations can fail because:
The user has exited from Groove,
The workspace or item being accessed has been deleted
Groove was busy and the SOAP request timed out.
In order for your application to continue to execute, it must handle these exceptions.
For a specific error condition, the contents of the text explanation and other elements of the SOAP exception might be dependent on internal implementation details and might consequently change in a future release.
Your program logic should not depend on detecting specific values in a SOAP exception, unless the contents of the SOAP exception are explicitly documented in the Groove Web Services Programmer's Guide or the Groove Web Services API Reference.
In most cases, the text explanations in SOAP exceptions are not localized and are not intended for end users.