UIM sqlserver probe 5.61 fails authentication intermittently

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

SQLserver probe v5.61 appears to be working fine.  The probe is monitoring many database profiles without issues.  Then, intermittently, the following alarm is simultaneously generated for several profiles.

"Profile <profilename>, Cannot connect to database instance <profilename>: (Profile: <profilename>/check_dbalive/Connect - COM Error: Code=0x80040e4d Source=Microsoft OLE DB Provider for ODBC Drivers Description=[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user '<username>'.)."

The alarm automatically clears shortly afterward (on one of the next polling intervals) and everything returns to normal working order.  The issue rarely remains for several polling cycles.

The Code=0x80040e4d messages are also reported in the MSSQL logs and in the Windows event logs for the MSSQL server.  These indicate that there is a password mismatch.  However, no changes to the password are made in the probe configuration.

Environment

sqlserver probe 5.61

Cause

When there are many (30+) profiles, each profile requests password decryption to connect to SQL Server at regular intervals. At some point, one or more profiles request password decryption simultaneously, causing corruption in the process.  Each of these profile fail the authentication and generate a failure.

Resolution

A fix has been released to resolve this issue.  A locking mechanism has been added during the password decryption process to prevent simultaneous requests and resolve the issue.  The fix is included in sqlserver 5.62 released on April 18, 2025.