Recently we encountered repetitive problems with connections to MSSQL database on a given server. The probe is installed locally on the MS SQL server. There are no network issues or other known problems from the server infrastructure side. We created a few connections and one profile. Test connection is "green" state OK, test sql query inside profile is responding OK too, but when we use "run profile" a connection error is appearing in sql_response log like this:
sql_response: Profile: K1_vemaCorba_too many, operation: Open, COM Error [0x80040e4d] IDispatch error #3149 - [Microsoft OLE DB Driver for SQL Server] Login failed for user '<username>'.
Username and password were confirmed.
There are other errors in the log such as:
sql_response: (NimCryptographerCfgKeyReadEncryptedValue) failed to write. Permission denied. RC=0
sql_response: Unable to retrieve encoded password.. using current configuration.
sql_response: profile K1_vemaCorba_too many, connection connect_EcXXXXX_VWW35_K99 not found, profile set to 'inactive', change configuration...
Controller: Max. restarts reached for probe 'sql_response' (command = sql_response.exe)
When we first started using the probe, everything was working fine for a while, but after few more config/test steps the probe is collapsing.
Release : 20.3
Component : UIM - SQL_RESPONSE
- sql_response 1.80 on a given server
Downgraded sql_response probe to version 1.63 and the probe proved to be 100% stable whether using a local or remote connection for monitoring MS SQL Server.