Troubleshooting Groove Server 2010 Relay
Applies to: Groove Server 2010
Topic Last Modified: 2011-08-05
This section lists problems that may occur while Groove Server Relay is running at your site, and suggests ways to resolve them.
You can start diagnosing server problems by opening the Windows Event Viewer and checking for Relay server application errors. You can also check the Groove Server Manager Server Log for problems involving contact with registered Groove Server Relay computers. For information about how to use Windows Event Viewer, see Windows Event Viewer for Windows Server (https://go.microsoft.com/fwlink/p/?LinkId=177514).
For the latest information about addressing specific Groove Server Relay problems, visit Microsoft Help and Support (https://go.microsoft.com/fwlink/p/?LinkID=183328).
Note
To avoid problems, refer to the following Windows tools:
-
Use the Windows Administrative Tools to check the disk usage of any drive that is reported to be low to verify this condition.
-
Use the Windows Task Manager to check the memory and processor usage for abnormally high or low usage values. Check the services panel to verify that the Groove Server Relay service is running. A computer that has over 1,000 connections should be using no more than 50 percent of both processors, without increasing memory use.
For information about how to troubleshoot Groove Server Manager, see Troubleshooting Groove Server 2010 Manager.
This section lists problems that may occur while Groove Server Relay is running at your site, and suggests ways to resolve them.
Problem | Solution |
---|---|
An administrator cannot access the Groove Server Relay administrative Web pages. |
Access to the Groove Server Relay administrative Web pages requires membership in the authorized Admin User/Group defined on the Admin Interface page of the Groove Relay control panel item. The recommended approach to setting up access to relay server administrative Web pages is to do the following:
|
A certificate error appears when you try to access the SSL-protected Groove Server Relay administrative Web pages. |
The SSL certificate for Groove Server Relay is self-signed. Therefore, you can ignore this error and click Continue to this Website. The certificate error results because the self-signed certificate is not trusted. You can resolve this by installing the self-signed certificate as a trusted root Certificate Authority on the computer being used to access the Web pages. |
Managed SharePoint Workspace users cannot authenticate to the Groove Server Relay. Errors appear in the Groove Server Relay event log. |
The cause of this problem could be an incorrectly generated Serverid.xml file, which may not have been successfully imported to the Groove Server Manager. Try removing the Relay server listing from the Groove Server Manager, and then re-assigning it. If that does not resolve this problem, try regenerating the Serverid.xml file and re-importing it to the Groove Server Manager. You will need to restart both Groove Server Manager and Groove Server Relay after regenerating and importing the Serverid.xml file. For information about exchanging authentication keys between the two servers and assigning Groove Server Relay servers to SharePoint Workspace users, see Registering Relay servers with Groove Server Manager. |
Groove Server Relay does not sustain HTTP connections. |
Ensure that no other service or program is active or installed that requires use of ports 80, 443, or 2492. |
Groove Server Relay performance on a Windows Server 2008 computer is slow. |
Try the following approaches:
|
See Also
Concepts
Operations for Groove Server 2010 Relay
Troubleshooting Groove Server 2010 Manager