Groove Server Relay errors and events

 

Applies to: Groove Server 2010

Topic Last Modified: 2011-09-10

This article provides reference information about Groove Server Relay event log codes and messages. Groove Server Relay assigns a unique number to each event message that appears in the Windows Event Log. Microsoft Operations Manager (MOM) and other tools that scan the Windows Event Log to automate server monitoring tasks (such as the Windows tool eventtriggers.exe) can reference these numbers.

Different categories of Relay server events fall into specific numeric ranges, as summarized in the following table:

Event Message Code Range	Event Category
0 - 99	Reserved
100 - 2999	General Relay server
3000 - 3999	Database
4000 - 4999	Network
5000 - 5999	Security
6000 - 6999	Operating System (OS)-level services
7000 - 7999	Administrative
8000 - 8999	Resource monitor
10,000-10,999	General debug/trace

The following tables list the most frequently occurring Relay server events together with their unique identifiers. Note that the events listed here are for the current version of Groove Server Relay; new events may be added in future versions. Also be aware that events that are not prefaced by ERROR or WARNING are usually informational messages.

For details about a specific event occurrence, contact Microsoft Help and Support (https://go.microsoft.com/fwlink/p/?LinkID=183328).

In this article:

• General Relay server events (100-299)

• Database events (3000-3999)

• Network events (4000-4999)

• Security events (5000-5999)

• Operating system events (6000-6999)

• Administrative events (7000-7999)

• Resource Monitor events (8000-8999)

General Relay server events (100-299)

Event MessageId code	General Relay server event message	Explanation
100	The Groove Relay service was installed.	Groove Server Relay was installed and the Groove Relay service has started. No action is needed.
101	The Groove Relay service was removed.	The Groove Relay service was removed. No action is needed.
102	ERROR: The Groove Relay service could not be removed.	The Groove Relay service could not be removed. Contact Microsoft Support for help.
104	ERROR: The initialization process failed. Check the Windows EventLog for more information.	Groove Server Relay could not be initialized. Possibly, Groove Server Relay is already running. Check whether the Groove Relay process is already running by opening the Windows Task Manager and noting whether Relay.exe appears on the Processes tab). If the Groove Relay process is not running and cannot be initialized, contact Microsoft Support for help.
105	The Groove Relay service was started.	The Groove Relay service has started. No action is needed.
108	The Groove Relay service was stopped.	The Groove Relay service has stopped. Look for earlier Event Log warnings or errors that caused this condition, such as low disk space. When condition is corrected, use the Windows Administrative Tools to re-enable the service.
116	Starting Relay server.	The Groove Relay service is starting. No action is required.
117	Relay server shutting down...	The Groove Relay service is shutting down.
118	ERROR: Service (Relay server) not installed: failed to install default service parameters.	Contact Microsoft Support for help.
123	ERROR: RQPurge thread stalled.	Purging of the RQS directory transaction logs has stalled. If this problem persists, contact Microsoft Support for help.
124	WARNING: RQPurge thread stalled.	Purging of the RQS directory transaction logs has stalled. Contact Microsoft Support for help.
131	ERROR: Network Thread stalled for __ timeout periods.	Relay operations stalled for a specified period. Thread stalling does not necessarily indicate a problem and frequently the condition resolves itself. If this condition persists, contact Microsoft Support for help.
132	WARNING: Network Thread stalled for __ timeout periods.	Relay operations stalled for a specified period. Thread stalling does not necessarily indicate a problem and frequently the condition resolves itself. If the condition persists or a subsequent error results, contact Microsoft Support for help.
133	ERROR: TimerQueue Thread stalled for __ timeout periods.	The Relay server operations stalled for a specified period, possibly indicating a performance problem. Check whether the Relay server is overloaded, as follows: Check CPU usage, memory, and disk I/O, by using the Windows Performance monitoring tools. Check network connections, by using the Relay Statistics page of the Administrative Web interface. Decrease the load if necessary and possible. If the problem persists, contact Microsoft Support for help.
134	WARNING: TimerQueue Thread stalled for __ timeout periods.	This condition may resolve itself. Check whether the Relay server is overloaded, as described in 133. If the condition persists or a subsequent error results, contact Microsoft Support for help.
135	ERROR: FFQ Worker Thread stalled for __ timeout periods.	Relay server operations stalled for specified period. Check whether the Relay server is overloaded, as described in 133. If the condition persists, contact Microsoft Support for help.
136	WARNING: FFQ Worker Thread stalled for __ timeout periods.	This condition may resolve itself. Check whether the Relay server is overloaded, as described in 133. If the condition persists, contact Microsoft Support for help.
137	ERROR: FFQ IOHelper Thread stalled for Relay server timeout periods.	Relay operations stalled for specified period. Contact Microsoft Support for help.
138	WARNING: FFQ IOHelper Thread stalled for __ timeout periods.	This condition may resolve itself. If a subsequent error results, contact Microsoft Support for help.
139	ERROR: Work List Thread stalled for Relay server timeout periods.	Relay operations stalled for a specified period. Check whether the Relay server is overloaded, as described in 133. If the condition persists, contact Microsoft Support for help.
140	WARNING: Work List Thread.	This condition may resolve itself. Check whether the Relay server is overloaded, as described in event 133. If the condition persists, contact Microsoft Support for help.
147	ERROR: Fatal Configuration Error: The Groove Relay Server cannot communicate with Groove clients because __. The Groove Relay Server is shutting down.	The current firewall configuration rules block all Groove Server Relay network traffic. No communication is possible. Review the firewall configuration for inbound/outbound rules and make appropriate changes to allow Groove Server Relay traffic. By default the Relay accepts inbound traffic on ports 2492, 80 and 443, and accepts Outbound traffic on port 2492.
158	Error: GMS __ certificate registry key was not found, but it was found under the WOW6432Node key. Please refer to the Groove Relay Admin Guide for how to properly configure the Groove Manager certificate registry key.	A 32-bit browser was used on a 64-bit OS to import the SSL certificate for the Relay server-to-Manager server interface. See Changing SSL and administrative access settings for Groove Server Relay for information about how to import SSL certificates for the Relay server.

Database events (3000-3999)

Event MessageId code	Database event message	Explanation
3003	ERROR: RQS initialization failed, another process is using the RQS subsystem, RQSPathHome __.	Usually occurs when the Relay server is started two times or when some other application is accessing the Relay database directories. Confirm whether only one Groove Relay process is running (check the Windows Task Manager). If multiple relay processes are running, stop one of them. If the error persists when only one relay process is running, contact Microsoft Support for help. See Starting and stopping Groove Server Relay for information about how to stop a Relay server process.
3004	ERROR: Open database environment failed, invalid path specified __.	If this error occurs after installing and starting the Relay server, you may have specified an invalid database path after you modified a path in the Windows registry (to move a relay database, for example). Uninstall, and then re-install Relay server and verify the path information. If this error persists, contact Microsoft Support for help.
3008	ERROR: Open database environment failed, unable to set data directory to __, error __.	See event 3004.
3009	ERROR: Open database environment failed, unable to set log directory to __, error __.	See event 3004.
3015	ERROR: RQS initialization failed, unsupported database version, RQSPathHome __.	RQS data (of client identity, device, and account information) could not be created at startup, possibly after an upgrade attempt. Contact Microsoft Support for help.
3016	ERROR: RQS initialization failed - RQSPathHome __, RQSPathDatabases __, RQSPathLogfiles __, HResult__.	RQS data (of client identity, device, and account information) could not be created at startup. Contact Microsoft Support for help.
3033	ERROR: Could not create pre-allocated extent directory \<directory>\__.	FFQ directory (of client data) could not be created, possibly because of insufficient disk space. Check disk I/O and available disk space by using the Windows Event Viewer and Performance monitoring tools. If the problem persists, contact Microsoft Support for help.
3036	ERROR: FFQ running on \__\Directory __ is compressed. Not supported.	FFQ directory in specified path is compressed which could cause poor relay performance and too much memory usage. Uncompress the directory (or related volume), then restart the Relay server service.

Network events (4000-4999)

Event MessageId code	Network event message	Explanation
4002	WARNING: Invalid IP address __ specified to bind call; defaulting to INADDR_ANY.	An administrator entered an incorrect bind address for the Relay server. Correct this error by updating the registry value HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\Relay server\Parameters and restart the Relay server.
4010	WARNING: The __ Service Listener failed __, suspending __ listener thread for __ seconds, before retrying listener operation	A listen service failed to bind to its associated network port. This error may be transient so the Relay server retries the bind operation a few times. If the retry operation fails, error 4051 is logged.
4050	ERROR: Both IPv4 and IPv6 stack are disabled. All inbound and outbound connections to server would fail.	No network communication is possible. Enable Internet Protocol version 6 (IPv6) or Internet Protocol version 4 (IPv4) before trying to start the Relay server. For information about how to enable or disable these protocols, see the article, How to disable certain Internet Protocol version 6 (IPv6) components (https://go.microsoft.com/fwlink/p/?LinkId=184623).
4051	ERROR: The __ Listener cannot start. Port __ is inuse by another service or application. Disable the other service or application before restarting.	The specified listener could not bind to the specified port. This error typically occurs when another application is using one of the Relay server default ports (2492, 443, or 80). Stop the other application to free the port so that the Relay can bind to it. This is a common error if Internet Information Services (IIS) is running when the Relay server attempts to start.

Security events (5000-5999)

Event MessageId code	Security event message	Explanation
5003	WARNING: Unable to examine ACL on registry key __. The service may be running with exposed security information.	Unable to find system access control list (SACL) associated with Groove client registry key, which may indicate that the relay service is running insecurely with exposed data. Contact Microsoft Support for help.
5012	ERROR: Security - PreauthRequired and no User ID found in users database, user __, account __.	The Relay server could not locate the Groove Server Manager member information for a client that is trying to contact the Relay server. Use Groove Server Manager to check whether the user is properly assigned to this Relay server.
5013	ERROR: PreauthRequired and error __ returned from UserOpen, User __, account __.	The Relay server found the Groove_Server_Manager_current_NoVer member information for a client that is trying to contact the Relay server, but the file was unreadable. Contact Microsoft Support for help.
5014	ERROR: Security - Failed to parse user on new device message during attach sequence for user __; parser returned __.	The Relay server could not find the user associated with a device-targeted message. Use Groove Server Manager to confirm that the user is properly provisioned to this Relay server, so that the user device can successfully dequeue messages.
5015	WARNING: User locked out Relay server.	The Groove Server Manager user cannot access the Relay server because a Groove Server Manager setting locked this Relay server from user’s domain. To re-instate the Relay server in the Manager server domain, contact the domain administrator to reset the option.
5016	WARNING: PreauthRequired and User ID locked out __, account __.	The Groove Server Manager user cannot access the Relay server because a Groove Server Manager setting locked this relay server from user’s domain. To re-instate the Relay server in the Manager server domain, contact the domain administrator to reset the option.
5019	ERROR: No passphrase entered; unable to start the service.	An administrator password is required to start the relay service and the relay configuration option for Unattended startup is disabled, but a password was not supplied. Enter a valid password. If the password is unknown, you cannot start the Relay server. To recover, if the password is forgotten and cannot be recovered, you must deprovision users from the server, reconfigure it with a new relay name and password, re-register it with Groove Server Manager, and re-provision SharePoint Workspace clients.
5020	ERROR: Unable to display passphrase prompt dialog.	An administrator password is required to start the Groove Relay service but the password prompt cannot be displayed. This may indicate a system error. Contact Microsoft Support for help.
5021	ERROR: No private key found in key file __.	The file that contains the Relay server private key (<privkey>.dat) is missing or damaged. If you backed up the private key file (by using the Backup Private Key File button on the Server tab of the Groove Relay control panel item), restore this file. If you did not back up this file and the password is lost or forgotten, to recover, use Groove Server Manager to assign SharePoint Workspace users to another Relay server. Then, use the Groove Relay Control Panel item to re-configure the Relay server with a new name and password, re-register the Relay server with Groove Server Manager, and re-provision Groove clients. For information about how to assign managed SharePoint Workspace users to Relay servers and how to register Relay servers with a Manager server, see articles on these topics in Operations for Groove Server 2010 Manager. For information about how to configure the Relay server, see Changing Server settings for Groove Server Relay.
5022	ERROR: Private key not found __; unable to start the service.	See error 5021.
5023	ERROR: Could not extract public key from private key; unable to start the service.	See error 5021.
5013	ERROR: Security: PreauthRequired and error __ returned from UserOpen, user __, account __.	The Relay server found the user record for pre-authentication but the record was unreadable. Contact Microsoft Support for help.
5024	ERROR: Could not calculate certificate fingerprint from public key values; unable to start the service.	See error 5021.
5025	ERROR: Private key found is invalid; unable to start the service.	See error 5021.
5028	WARNING: World access allowed on registry key __. The service may be running with exposed security information.	The Relay server did not apply the necessary access control lists (ACLs) to the Relay server registry key during installation. Retry the installation. If the problem persists, contact Microsoft Support for help.
5029	WARNING: World access removed from registry key __, in order to avoid exposure of security information.	The Relay server did not apply the necessary access control lists (ACLs) to the Relay server registry key during installation, but the Relay server repaired this condition.
5030	ERROR: No private key; unable to start the service.	See error 5021.
5034	WARNING: Mac check failed on connect; msgId: __ device: __	The message authentication information that is sent by the SharePoint Workspace client does not match the authentication information originally stored on the Relay server from the client’s initial Relay server contact. Open the Relay server administrative Web interface, select the Devices view, and specify the name of the device that generated the error. When the statistics page appears for the device, click the Clear Security Keys button to clear the existing key information about the client, and then restart the client and log on to the SharePoint Workspace application. If this does not resolve this problem, contact Microsoft Support.
5035	WARNING: Mac check failed on attach; msgId: __ user: ___ relay: ___ device: __	See warning 5034.
5036	WARNING: Mac check failed on UserOnNewDevice; msgId: msgId: __ user: ___ relay: ___ device: __ timestamp __	See warning 5034.
5037	WARNING: Mac check failed on IdentityReg; msgId: __ user: ___ relay: ___ device: <Relay server> timestamp __	See warning 5034.
5038	WARNING: DeviceUserRegistration: User layer message verification failed for peer __ user (grooveAccount: __) on device (dpp:__)	The Relay server has not successfully transmitted the managed SharePoint Workspace identity information from the Groove Server Manager. If the problem persists, contact Microsoft Support.
5102	ERROR: ACL error on Registry Key [__] (__)	The Relay server failed to perform a Registry operation because of incorrect Registry access control settings. Review access control settings on the specified Registry key/Value and edit access controls as necessary.
5103	ERROR: ACL error on Directory [__] (__)	The Relay server failed to access a directory because of incorrect access control settings. Review access control settings on the specified directory and change access controls as necessary.
5104	ERROR: ACL error on File [__] (_)	The Groove Relay failed to gain read/write access a file because of incorrect access control settings. Review the access control settings on the specified file and change access controls as necessary.
5107	Secure RunTime Environment Relay Initialization…	This informational event logs the security settings currently in use by the Groove Relay. The displayed security information includes account, access controls, and permissions details.

Operating system events (6000-6999)

Event MessageId code	OS Event message	Explanation
6011	ERROR: Failure attempting to allocate memory of size __ bytes.	A Relay server memory allocation has failed, possibly indicating a performance problem. First, restart the Relay server. If the problem persists, check whether the Relay server is overloaded, as follows: Check CPU usage, memory, and disk I/O by using the Windows Performance monitoring tools. Check network connections by using the Relay Statistics page of the Administrative Web interface. Decrease the load if necessary and possible. If the problem persists, contact Microsoft Support for help.
6012	ERROR: Permanent Failure attempting to allocate memory of size __ bytes.	A Relay server memory allocation has failed (possibly because of insufficient memory). Restart the Relay server. If the problem persists, contact Microsoft Support for help.
6015	ERROR: Incorrect device scheme (should be __).	A SharePoint Workspace client device has tried to connect to the Relay server with an incorrectly formatted device URL. Contact Microsoft Support for help.
6018	ERROR: \Port\ setting out of range (must be between 1 and 65535): (0)
6019	WARNING: Registry Key - BandwidthDataPollInterval is out of its allowed range. Set to its default __.	A registry value related to bandwidth monitoring is invalid. Format the value correctly, as described in Configuring Groove Server Relay bandwidth usage statistics.
6020	WARNING: Registry Key - BandwidthDataSampleSize is out of its allowed range. Set to its default __.	A registry value related to bandwidth monitoring is invalid. Contact Microsoft Support for more information.
6027	Second Chance Exception: Handler - Done.	A severe relay error has occurred. If this problem persists, contact Microsoft Support for help.
6032	Last chance Exception: Handler - Done.	A severe relay error has occurred. If this problem persists, contact Microsoft Support for help.
6039	RELAY PROCESS ABORTING.	A severe relay error may have occurred. The relay has shut down (and will restart if running as a service). Contact Microsoft Support for help.
6666	FATAL ERROR: System callstack dump event.	A severe relay error has occurred that will cause service interruption. If this problem persists, errors 6027, 6032, and 6039 will follow.
6068	WARNING: Data Path__ is not a valid directory, data will be stored in the install directory __.	The data files path, specified during Relay server installation or upgrade, is not valid. The default directory will be used instead. If this warning appears after an upgrade, pre-existing data may be inaccessible. If this warning appears at another time, it may indicate a failed volume. If the problem persists, contact Microsoft Support for help.
6069	WARNING: Diagnostic Path __ is not a valid directory, Diagnostic data will be stored in the install directory __.	The diagnostic files path set during Relay server installation, is not a valid path. The default Diagnostic directory will be used instead.
6070	WARNING: DumpFile Path __ is not a valid directory, Diagnostic data will be stored in the install directory __.	The diagnostic files path used for the DumpFile (specified during Groove Server Relay configuration) is not a valid path. The default Diagnostic directory will be used instead. Correct registry keys are as follows: Data Directory RQSPathDatabases RQSPathLogFiles Diagnostics Directory
6072	ERROR: Low memory condition.	Check the Relay server memory allocations and reconfigure. Restart the Relay server. If the problem persists, check whether the Relay server is overloaded, as follows: Check CPU usage and disk I/O by using the Windows Performance monitoring tools. Check network connections by using the Relay Statistics page of the Administrative Web interface. Decrease the load if necessary and possible. If the problem persists, contact Microsoft Support for help.
6100	Error - STD Exception [__] (__)	An unhandled exception occurred. This is an internal error which causes the Groove Relay to abnormally terminate. Contact Microsoft Support for help.
6101	Error - SafeInt SafeIntArithmeticOverflow Exception [__]	An unhandled exception occurred. This is an internal error which causes the Groove Relay to abnormally terminate. Contact Microsoft Support for help.
6102	Error - SafeInt SafeIntDivideByZero Exception [__]	An unhandled exception occurred. This is an internal error which causes the Groove Relay to abnormally terminate. Contact Microsoft Support for help.
6103	Error - SafeInt Unknown Exception [__] (__)	An unhandled exception occurred. This is an internal error which causes the Groove Relay to abnormally terminate. Contact Microsoft Support for help.
6104	Error - GCException (Internal Error condition) [__] Result:(__) Reason:(__)	An unhandled exception occurred. This is an internal error which causes the Groove Relay to abnormally terminate. Contact Microsoft Support for help.

Administrative events (7000-7999)

Event MessageId code	Administrative event message	Explanation
7002	Entering quiescent to __, no connections are being accepted.	Relay server is receiving Groove Server Manager SOAP transmissions (a temporary condition), and is not accepting SharePoint Workspace client connections. No action necessary.
7003	Setting quiescent to __.	Relay server is not receiving Groove Server Manager SOAP transmissions, and client connections are accepted. No action necessary.
7007	Purge/Compress already running.	A periodic purge of Relay server queues was already underway when the Relay server received an administrator-initiated Purge message. No action is needed.
7008	DbBackup already running.	A backup of Relay databases was already underway when the Relay server received an FFQBackup request (from the command line). No action is needed.
7009	QueueReport already running.	Relay server queue report was already being generated when Relay server received request for relay queue report from relay administrative Web pages. No action is needed.
7014	Starting Queue Information Report...	Relay server queue report being generated. No action is needed.
7015	Queue Information completed after __ minute(s). Reported__ queues , __ recovered, __ failed to open.	Queue recovery information which includes the total number queues examined for recovery, the total number of queues recovered and the number of minutes required to recovery all queues, during which time the Relay server was not processing network connection requests.
7016	Purge completed after __ minute(s). Reviewed __ queues. Purged __ messages, __ bytes. Compressed __ bytes.	Relay server queues reviewed, compressed, and purged in specified number of minutes. No action is needed. Relay purge has finished.
7017	Purge canceled after reviewing __ queues. Purged __ messages, __ bytes. Compressed Relay server bytes.	Purge canceled after specified number of queues were reviewed (because of request from administrative Web pages). No action is needed.
7018	DB MetaData Save completed after __ minute(s), wrote __ Accounts, __ Devices, __ Identities and __ User records.	Relay server metadata for specified account, device, and identity information saved in specified number of minutes. No action is needed.
7019	Starting Purge...	Relay server queue purge starting. No action is needed.
7020	Running DB meta data save on thread __.	Relay server metadata (account, device, and identity information) being saved. No action is needed.
7025	FFQ Startup Recovery Begins, client listener sockets not yet opened	Relay database queues are being recovered. The Relay server will not accept incoming connection requests until recovery is complete. Database recovery is required when a database queue is closed without the data first being committed. This typically occurs after the Relay process stops abnormally.
7026	FFQ Startup Recovery Complete, client listener sockets now being opened...	Relay database queues recovery is complete. The Relay server will not accept incoming connection requests until recovery is complete.
7028	WARNING: Handling large SOAP transaction, Admin page request handling may be delayed	The Relay server has started processing a Groove Server Manager SOAP request which may require a long run-time.
7029	Large SOAP transaction complete, resume normal Admin page request handling	The processing of a Groove Server Manager SOAP request (often a lengthy process) has finished.

Resource Monitor events (8000-8999)

Event MessageId code	Resource Monitor event message	Explanation
8000	ERROR: Resource Monitor: Error - Resource Exhaustion, Relay Service shutting down. Upon restart, incoming connections will be rejected until low resource problem Is resolved.	One or more Relay server resources has reached its maximum limit, resulting in server shutdown. Typically, a restart follows. Previous errors usually identify the expired resource.
8001	ERROR: Resource Exhaustion, Relay Service restarting.	One or more Relay server resources has reached its maximum limit, resulting in server restart after shutdown.
8004	ERROR: Resource Monitor: Error - Free disk space limit of __ GB reached on __. Incoming connections will be rejected until low resource problem is resolved.	Free space limit exceeded on specified disk. The Relay server shuts down automatically. Purge the relay queues, as described in Managing Groove Server Relay databases, and, if the Relay server diagnostics directory is located on a separate volume, purge that directory. If the condition persists, clear the disk of unnecessary (non-relay) data or replace the disk with a larger volume, and restart the server.
8005	WARNING: Approaching free disk space limit of __ percent on __, current free disk space equals __.__ percent.	Limited free space remaining on specified disk. Purge the relay queues (from the administrative Web pages). If the condition persists, clear the disk of unnecessary (non-relay) data or replace the disk with a larger volume, and restart the server. This warning precedes the 8004 error condition.
8006	ERROR: Free disk space limit of __ percent reached on __.	Free space limit exceeded on specified disk. If the Relay server does not shut down automatically, shut down and restart it. Purge the relay queues, as described in Managing Groove Server Relay databases and, if the Relay server diagnostics directory is located on a separate volume, purge that directory. If the condition persists, clear the disk of unnecessary (non-relay) data or replace the disk with a larger volume, and restart the server.
8007	WARNING: Approaching free disk space limit of __ percent on __, current free disk space equals __.__ percent.	Limited free space remaining on specified disk. Purge the relay queues (from the administrative Web pages). If the condition persists, clear the disk of unnecessary (non-relay) data or replace the disk with a larger volume, and restart server. This warning precedes the 8006 error condition.
8008	WARNING: Approaching SSTP connection limit of __, __.__ percent remaining before limit is reached.	Approaching maximum number of SSTP connections that Relay server can support. You may want to increase relay capacity or add more Relay servers.
8009	WARNING: Approaching HTTP connection limit of __, __..__ percent remaining before limit is reached.	Approaching maximum number of HTTP connections that Relay server can support. HTTP communications may be denied until condition clears. You may want to increase relay capacity or add more Relay servers.
8016	INFO: Free disk space limit of __ percent on __ has been restored, current free disk space equals __.__ GB.	Free disk space (of the specified amount) has been restored. No action is needed. This message appears after recovery from error 8004 or warning 8005
8017	INFO: Free disk space limit of __ percent on [Relay server] has been restored, current free disk space equals __. __ percent.	Free disk space (of the specified percentage) has been restored. No action is needed. This message appears after recovery from error 8006 or warning 8007.
8024	ERROR: SSTP connection limit of __, has been reached. Clients will attempt to connect to Relay using HTTP connections which consume more resources than SSTP connections.	Maximum number of SSTP connections has been reached, resulting in SSTP failover to HTTP; Groove clients will attempt to connect to relay using HTTP connections, which consume more resources than SSTP connections. You may want to increase relay capacity or add more Relay servers.
8025	ERROR: HTTP connection limit of __, has been reached.	Maximum number of HTTP connections has been reached. HTTP communications will be denied until condition clears. You may want to increase relay capacity or add more Relay servers.
8028	Resource Monitor: MemoryLoadGreenFlowControl Set MemLoad[75] (LWM[70] HWM[75]) Current Enqueue Bytes : Local[0] Transit[11563767] Resource Monitor: MemoryLoadYellowFlowControl Set MemLoad[85] (LWM[80] HWM[85]) Current Enqueue Bytes : Local[0] Transit[10141491] Resource Monitor: MemoryLoadRedFlowControl Set MemLoad[92] (LWM[88] HWM[92]) Current Enqueue Bytes : Local[0] Transit[10076734]	Relay Server memory load has reached a threshold that requires a level of flow control, based on per-session bandwidth usage. The system applies flow control automatically and dynamically, based upon instantaneously measured memory load. Incoming client-originated messages contribute to memory-load until they are successfully written to the local disk, or transmission to a remote Relay server has been acknowledged. Flow control events are generated for Relay servers that have over 8 gigabytes of memory, as part of the Groove Server 2010 Relay memory-based flow control service. Event messages indicate that a memory usage limit has been reached which starts a level or zone of flow control (indicated by color), as follows: Green - Memory load has reached 75% and a flow control zone has been set for a memory usage range of 70% to 75%. %. Flow control is applied only to sessions with large memory requirements. This level of flow control persists until memory load drops below the range or until memory usage reaches the level for the next zone. Yellow - Memory load has reached 85% and a flow control zone has been set for a memory usage range of 80% to 85%. Aggressive flow control is applied to sessions with large memory requirements, while less aggressive flow control is applied to sessions that present a smaller load. This flow control level persists until memory load drops below the range or until memoryusage reaches the level for the next zone. Red – Memory load has reached 92%. To ensure that the system does not fail, dynamic flow control is applied to all incoming traffic (by writing the queued messages to disk or by completing transmission to remote Relay servers) until memory consumption falls below 88%. Note To avoid memory overload conditions and associated server shut-downs the Relay server sets a maximum number of allowable connections, based on the amount of installed memory. For example, for Groove Server 2010 Relay installations with 16 GB RAM or more, the system imposes the following hard Relay server connection limits: SSTP (ports 2492 and 443) - 52,500 HTTP (port 80) - 10,500 Total - 63,000
8030	Resource Monitor: MemoryLoad[92] above Red HWM[92]. All client sessions will be flow controlled until cleared.	All client sessions will be aggressively flow controlled until memory consumption falls below 88%.

See Also

Concepts

Monitoring Groove Server Relay
Groove Server Relay statistics reference
Operations for Groove Server 2010 Relay
Operations for Groove Server 2010 Manager