SQL Server connections timeout if the collectors are far from the manager.
You might get an error message like this:
An error has occurred. Windows will automatically restart the service. Supercharger Fatal Exception caught
Maximum number of retries (3) exceeded while executing database
operations with 'SuperchargerSQLExecutionStrategy'. See inner exception
for the most recent failure.
System.Data.Entity.Core.UpdateException: An error occurred while
updating the entries. See the inner exception for details.
System.Data.SqlClient.SqlException: Execution Timeout Expired. The
timeout period elapsed prior to completion of the operation or the
server is not responding. The statement has been terminated.
System.ComponentModel.Win32Exception: The wait operation timed out
Supercharger uses SQL Server to store certain settings and other
information and to communicate with the collectors. This communication
happens through standard SQL Server protocols. If the network is slow, for example because of great geographical distance between the collector and manager, these communication connections could result in a timeout.
Supercharger introduced some registry values to be able to control the timeouts. These are to be set in regedit on the respective collector under HKEY_LOCAL_MACHINE\SOFTWARE\MTG\Supercharger\Controller
Please remember that regedit defaults to hexadecimal values when entering the values. The values in this table are decimal values.
|Default value (decimal)
|Sample values used by a customer between the USA and Europe (decimal)
|Sample values used by a customer between the USA and Asia (decimal)
Optionally provide private feedback to help us improve this article...
Thank you for your feedback!