"The maximum number of concurrent operations for this user has been exceeded" (4301932)

While adding databases to Foglight, the SQL Server OS validation fails even though the SQL Server connection test is successful from the FglAM to the monitored, and the WBEMTEST for WMI connection is successful.

The following errors may be found in the agent logs 

WinRM relies on a set of configuration parameters that establish the level of system resources the WinRM service needs to address incoming requests. In certain cases, some parameter values do not provide sufficient configuration levels which can lead to run-time errors.

Depending on how WinRM is used, some parameter values may not provide sufficient configuration levels which can lead to connection issues. The Agent Manager makes an attempt to diagnose some of these situations and communicate appropriate recommendations using Warning messages.

The configuration levels that the Agent Manager attempts to diagnose are:

• MaxConcurrentOperationsPerUser: This parameter specifies the maximum number of concurrent Enumeration operations allowed by an individual user. The value must be in the range of 1 to 4294967295.
  This parameter is only available for WinRM version 2.0 and later. In version 1.1, the MaxConcurrentOperations parameter is used instead.
  To increase the value assigned to this parameter, issue the following command:
  
  winrm set winrm/config/service @{MaxConcurrentOperationsPerUser=""}

• Tip: WinRM parameters can also be edited using the Group Policy Object Editor. To start the editor, type gpedit.msc at the command line, and then navigate to Local Computer Policy | Computer Configuration | Administrative templates | Windows Components | Windows Remote Management (WinRM) and Windows Remote Shell.
  

• MaxConcurrentOperations: This parameter specifies the maximum number of concurrent shells any user can remotely open on the same system. Any number from 1 to 4294967295 can be used. For more information about this parameter, you can visit the following Web page: http://msdn.microsoft.com/en-us/library/cc251426.aspx.
  
  This parameter is only available for WinRM version 1.1. It is deprecated for version 2.0 and later, and MaxConcurrentOperationsPerUser is used instead. To increase the value assigned to this parameter, issue the following command:
  
  winrm set winrm/config/service @{MaxConcurrentOperations=""}

• MaxShellsPerUser: This parameter specifies the maximum number of concurrent shells any user can remotely open on the same system. Any number from 0 to 2147483647 can be used, where 0 means unlimited number of shells. If this policy setting is enabled, the user cannot to open new remote shells if the count exceeds the specified limit.
  To increase the value assigned to this parameter, issue the following command:
  
  winrm set winrm/config/winrs @{MaxShellsPerUser=""} 

• AllowRemoteShellAccess: This parameter controls access to the remote shell. It must be set to true.
  To set this parameter to true, issue the following command:
  
  winrm set winrm/config/winrs @{AllowRemoteShellAccess="true"}

For additional information, visit the following Web page: http://msdn.microsoft.com/en-us/library/windows/desktop/aa384372%28v=vs.85%29.aspx