Enhancement Request: Active Roles DatabaseGuidLookup and Event ID 2512 errors due to SQL connection pool exhaustion (4383653)

Enhancement Request: Active Roles DatabaseGuidLookup and Event ID 2512 errors due to SQL connection pool exhaustion

Active Roles may log repeated DatabaseGuidLookup timeout errors and Event ID 2512 “Connection to database has been lost” in Windows Event Viewer during heavy backend processing.

Example symptoms:

Event ID 2001
Policy: DatabaseGuidLookup
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.

Event ID 2512
Connection to database has been lost.

An enhancement request (712233) has been created detailing the feature above. 

Active Roles can exhaust the default ADO.NET SQL connection pool limit of 100 connections during high-throughput operations, such as SQL Merge Replication, dynamic group processing, or other backend activity. This is not a connection leak. Connections are returned to the pool, but burst activity can still reach the pool limit and cause timeouts.

Broken Managed Units, stale policy references, or invalid membership rules may increase backend lookups against the Active Roles database views such as GuidLookupView, adding more SQL load and contributing to the issue.

STATUS
The product team will evaluate the request, and this feature may become available on a future release of the product.
Please refer to this article for updates or contact support referencing the Enhancement Request ID: 712233.

WORKAROUND:

- Identify which Active Roles server is creating the highest SQL session count.
- Run Active Roles Health Checks and clean up broken Managed Units, stale policy links, and invalid references. Please contact OneIdentity support if necessary.
- Review Dynamic Groups and broken membership rules.
- Restart the affected ARAdminSvc during a maintenance window if sessions build up and the service becomes unresponsive.
- Monitor Event ID 2001, Event ID 2512, and SQL session count after cleanup.

712233

There are no guarantees that this specific enhancement request will be implemented in a future release. For more information regarding our Enhancement Request policy, refer to our Global Support Guide on the Support Portal at: Guide to One Identity Support.