Using Groove Web Services Registry Keys
It is possible for Groove to be shut down and then restarted while your SOAP client is executing. In this case, Groove assigns new values to the LocalRequestKey and LocalResponseKey keys. If it does not obtain the same port, it assigns new values to the GrooveHTTPPort and GrooveLocalHTTPPort keys as well. Consequently, your application should read these registry keys before calling each operation, and should not read them once and then re-use the values for multiple operations.
On Groove systems, the request and response keys are stored in the HKEY_CURRENT_USER registry key because it is only accessible to processes that are running under the same account, or under an account with system admin privileges. By providing the LocalRequestKey, your application demonstrates that it is running on the same Windows account as Groove, or on a trusted account with admin privileges.