Agents are not connecting to the Coordinator (4306612)

Consider the following scenario

 

Agent cannot connect to the Coordinator with the following error in the ChangeAuditor.dll.nptlog

[WARN][TorzagLib::Agent::CCoordinatorConnection::Open(226)] Failed to connect to coordinator at endpoint 'net.tcp://Coordinator FQDN:xxxxxx/Agent/v1'

 

AgentServiceProxy.nptlog records this error:

[ERROR][ChangeAuditor.AgentServiceProxy.CAgentServiceProxy.Connect(0)] Exception caught in proxy Coordinator FQDN(GUID) - failed to connect to coordinator

 

Checking the Coordinator log the following warning and error are noted: 

[WARN][ChangeAuditor.Coordinator.EventAggregatorTask.IsCriticalQueueSize(0)] Too many events in Scheduler task queue: 1012 (maximum: 1000), cannot accept more

 

[ERROR][ChangeAuditor.Coordinator.Agent.AgentServiceBase.GetConfiguration(0)] Timeout expired.  

 

The ideal solution would be to install additional Coordinators to balance the load but if that is not possible then there are two Registry values that can be added:

 

SQL Command Timeout 

Location: Registry 

Version 6.0 and earlier Path: HKEY_LOCAL_MACHINE\SOFTWARE\Quest Software\ChangeAuditor

Version 6.5 and later Path: HKEY_LOCAL_MACHINE\SOFTWARE\Quest\ChangeAuditor

Value Name: SQLTimeout 

Value Type: DWORD 

Value: Default = 30 seconds (Decimal) change to 300 seconds (Decimal)

Value: Maximum time in seconds for SQL command to execute. Impacts most client and Coordinator queries. 

Note:   Consider increasing this if you have SQL Timeout errors in Coordinator logs.

 

Bulk SQL Command Timeout 

Location: Registry 

Version 6.0 and earlier Path: HKEY_LOCAL_MACHINE\SOFTWARE\Quest Software\ChangeAuditor

Version 6.5 and later Path: HKEY_LOCAL_MACHINE\SOFTWARE\Quest\ChangeAuditor

Value Name: BulkSQLTimeout 

Value Type: DWORD 

Value: Default = 30 seconds (Decimal) change to 300 seconds (Decimal)

Value: Maximum time in seconds for bulk SQL command to execute. This includes bulk insertion of SQL events from agents.   

Note:  This effects Coordinator event inserts and the CA Database Checker. Consider increasing this if Coordinator logs show timeouts by the EventAggregatorTask or bulk inserts.. 

 

Once the above Registry subkeys have been added, restart the Coordinator and then the SQL Server instance that is hosting the Change Auditor database if the 'Timeout expired.  The timeout period elapsed prior to obtaining a connection from the pool.  This may have occurred because all pooled connections were in use and max pool size was reached.' continues to be logged in the Coordinator log.

 

Upgrading to Change Auditor 6.7 would be a signifcant benefit due to enhanced Coordinator to SQL server connection handling

 

 

Quest does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article ID 256986 “Description of the Microsoft Windows registry” at Microsoft Support (http://support.microsoft.com/default.aspx?kbid=256986)