mssql.ddr in agent on windows server 2022

[MarcusH]

Hi,

Are there any known issues with mssql driver in agent for windows server 2022?

I am migrating servers and exact same config and agent version fail on new server with error [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

logs from old server with windows server 2016

2024.03.18 10:34:20.066 *I* [db.drv             ] Database driver "mssql.ddr" loaded and initialized successfully
2024.03.18 10:34:20.098 *D* [db.conn            ] New DB connection opened: handle=000002538F7AD490
2024.03.18 10:34:20.098 *I* [dbquery            ] Connected to database "db1"
2024.03.18 10:34:20.113 *I* [subagents          ] Subagent "DBQUERY" (dbquery.nsm) loaded successfully (version 4.4.2)

logs from new server with windows server 2022

2024.03.18 10:40:18.546 *I* [db.drv             ] Database driver "mssql.ddr" loaded and initialized successfully
2024.03.18 10:40:18.546 *W* [dbquery            ] Cannot connect to database "db1" ([Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified)
2024.03.18 10:40:18.546 *I* [subagents          ] Subagent "DBQUERY" (dbquery.nsm) loaded successfully (version 4.4.2)

agent config:

DebugLevel = 6
LogFile = C:\NetXMS\log\log.txt
MasterServers = *.*.*.*
ConfigIncludeDir = C:\NetXMS\etc\nxagentd.conf.d
FileStore = C:\NetXMS\var
SubAgent = winperf.nsm

SubAgent = dbquery.nsm
*DBQUERY
Database = id=db1;driver=mssql.ddr;server=server;dbname=db;login=user;password=pwd

I tried latest agent version and same issue.

I have tried adding ODBC DSN same issue

[MarcusH]

Moved SQL queries to use ExternalMetric instead more control over connections and errors that way so in general better way so far.

[victor]

Most likely you have to install SQL Server Native Client which is needed for mssql.ddr to work.

Best regards,
Victor