Delen via

  • Artikel

Troubleshooting Groove Server 2010 Manager

 

Applies to: Groove Server 2010

Topic Last Modified: 2011-08-05

This section lists problems that may occur while Groove Server Manager is running at your site and suggests ways to resolve them.

For help about how to address specific Groove Server Manager problems, visit Microsoft Help and Support at https://support.microsoft.com.

For information about how to troubleshoot Groove Server Relay, see Troubleshooting Groove Server 2010 Relay.

Microsoft SharePoint Workspace, see Troubleshoot SharePoint Workspace 2010.

Problem Solution

Groove clients cannot connect to the Groove Server Manager.

You may have set up authentication for the whole Groove Server Manager Web site. This prevents clients from contacting the server. If this is the case, reconfigure authentication to protect the Groove Server Manager administrative interface in the Admin directory of IIS but configure Anonymous authentication for the client directory to allow for Internet connections from SharePoint Workspace clients. For information about Groove Server Manager directories, see Groove Server Manager directory reference.

The Groove Server Manager reporting time stamp shows a different time than the local administrative computer.

Your Groove Server Manager may be located in a different time zone from your logon time zone. The Groove Server Manager records and displays times based on the server time zone. For example, if you are using a Groove Server Manager installation based in the United States, and you log on from a location in Europe, the reported times on the server will differ from your local time.

The Groove Server Manager log reports that the SQL Server has reached capacity so that no more space is available for the Groove Server Manager database and transaction log. Groove Server Manager may stop operating.

See SQL Administration (https://go.microsoft.com/fwlink/p/?LinkId=168440) for information about how to manage disk space on the SQL Server.

SharePoint Workspace automatic account configuration fails.

Auto-account configuration often fails because of an untrusted Secure Socket Layer (SSL) certificate. A valid and trusted for the certificate requires the following conditions to be met: the fully qualified domain name of the Manager server must exactly match the certificate name, certificate use must be within the valid dates, and the certificate path must be trusted. Ensure that the SSL certificate is valid and trusted by SharePoint Workspace clients.

Auto-account configuration often fails because of a naming disparity. Ensure that the name that is used in the Groove Server Manager Group Policy object matches the fully qualified name of the SSL certificate that is used to help secure the Groove Server Manager Web site. See Automate SharePoint Workspace account configuration/restoration for more information about how to enable Auto-Configuration via Group Policy object and the groove.ADM file.

Download of the Groove Server Manager public key to Groove Server Relay, for Relay registration, fails.

You may have tried to download a Manager public key (.reg file) to the Relay server by running the public key file from a 32-bit Internet Explorer on the Relay server. This can cause the Manager key to be imported into the wrong location in the registry (under HKLM\Software\Wow6432Node\). To avoid this condition, save the Manager public key file, copy it to the Relay server, and then run the .reg file from the Relay server to update the Relay registry. Do not try to run the Manager public key from a browser on the Relay server.

If you want to check the 64-bit version, click About Internet Explorer from the browser Help menu. The text, 64-bit Edition will appear after the version if you running a 64-bit browser. You can select the 64-bit edition by clicking Start->Programs->Internet Explorer 64-bit.

For more information about how to register Groove Server Relay with Groove Server Manager, see Registering Relay servers with Groove Server Manager.

Searching for management domain members and other user administration tasks results in errors.

This condition is most likely due to a language limitation of the Groove Server Manager back-end SQL server. U.S. English is the only language supported by the underlying operating system of SQL Server.