A couple of tips from our dev team:
- You'll need eset remote administrator installed - the nod32 connector is intended to connect to the centralized remote administrator database, not the database at each endpoint.
- You'll need to create the system DSN using the 32-bit ODBC administrator (c:\windows\syswow64\odbcad32.exe) - since the agent runs in 32-bit.
If both of those are good, let me know, and we'll see where we go from here.
Having a very similar issue and while I've configured a SystemDSN I'm not clear on how to specify it in the Data Source Name of the NOD32 connector.