| Event Id | 130 |
| Source | PMDirectoryStore |
| Description | Consecutive DB connect failures exceed threshold with connect string Driver ={SQL Server};SERVER=dmqsqlcluster;DATABASE=ldap1;UID=ldap_server; PWD=*****;NETWORK=dbmssocn.dll. Putting DB in recovery mode. |
| Event Information | According to Microsoft: Cause: If the network configuration includes routers that are configured to invalidate inactive sessions, the LDAP server is not able to reconnect to the SQL Server data store. As a result, the session must remain regularly active. RESOLUTION: To prevent a networking device, such as a router, from invalidating a session, you can disable ODBC connection pooling. This ensures that a TCP session is established when database connection requests are performed. To disable ODBC connection pooling, perform the following steps: 1. In Control Panel, double-click Settings. 2. Select ODBC Data Sources. 3. Click the Connection Pooling tab. 4. Select the SQL Server ODBC Driver from the list. 5. Double-click SQL Server to set the Connection Pooling attributes. 6. Select Dont pool connections to this driver. When you do this, the LDAP service performs the operations required to establish a session when a connection operation is performed. This results in a TCP handshake operation that is performed between the LDAP and SQL Server computers. A session is established, and as a result, if there has been no activity between the LDAP and SQL Server computers for some time, a new session is established when a connection request is made. This is a valid new session that the firewall configured should recognize. |
| Reference Links | LDAP Service Fails to Reconnect to the SQL Server Store Due to Sessions That Are Invalidated by a Router |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.