Issue:
You send a web services call to a known, existing method, but do not include one of the required arguments for that method. The response returned from the server includes the error message No such operation with the name of the method. An example screenshot is provided below, though this can occur with any method name.
<Please see attached file for image>

Environment:
This error occurs solely in web services calls.
Cause:
If a required argument is left blank or otherwise not included, the call is sent with one fewer argument than it normally requires. Apache AXIS then attempts to find a method that accepts the provided number of arguments, fails to find one, and yields the No such operation error message.
As an example, if you call the getHandleForUserid method, but do not provide a SID value in the call, as in the screenshot below...
<Please see attached file for image>

...the response from the server will say that there is No such operation 'getHandleForUserid', as above. While this error seems somewhat misleading, as getHandleForUserid is a valid method, getHandleForUserid requires two arguments: <sid> and <userID>. If only one of these arguments is provided, Apache AXIS attempts to find a version of getHandleForUserID that accepts a single argument. When it cannot find one, the "No such operation" error is given.
Resolution:
Ensure that all required arguments are provided to the method.
Additional Information:
Details on the supported Web Services methods, and their required arguments can be found on the CA Service Management wiki.