"Server was unable to processrequest. ---> System.Exception: insert into snmpqlProfiles" error message is seen when trying to rediscover or refresh a router and/or in the WatchdogLog causing SNMP polling to fail for devices and Watchdog System Status.

Document ID : KB000003968
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

WatchDog and/or SNMP Polling of Routers may fail with the Errors below despite using the correct SNMP Community string and verifying SNMP connectivity between all devices.

The WatchdogLogXXXX-XX-XX.log shows errors similar to the one below:

Processes - Error getting SNMP processes list :
System.Web.Services.Protocols.SoapException:
System.Web.Services.Protocols.SoapException: Server was unable to process
request. ---> System.Exception:
insert into snmpqlProfiles (
snmpqlProfilesName,
snmpqlProfilesSnmpVersion,snmpqlProfilesSnmpPort,
snmpqlProfilesUserName, snmpqlProfilesContext,
snmpqlProfilesSecurity,
snmpqlProfilesAuthProtocol, snmpqlProfilesAuthPassword,
snmpqlProfilesPrivProtocol, snmpqlProfilesPrivPassword)
values ('profileId=44444',2,161,'1trilli0n42','',0,0,'',0,'') --->
System.Data.Odbc.OdbcException: ERROR [IM003] Specified driver could not be
loaded due to system error 126 (RedPoint SnmpQL Driver).

Rediscovering or Refreshing Routers in the Enable Interfaces screen will throw the following error:

Figure 1

Figure 2

Figure 3

 

Environment:
RA 9.0
Resolution:

This is due to incorrect or missing registry settings on the RA console server and the Harvester servers if you are receiving this when trying to rediscover/refresh devices in a distributed architecture.

To fix this follow the steps below.

  1. Run "regedit" to open your registry editor

  2. Go to one of the following registry paths on the RA console and each Harvester server if you are using a distributed architecture.

    • On 32 bit Operating Systems go to:
      HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\PollingProxySnmpQL

    • On 64 bit Operating Systems go to:
      HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI\PollingProxySnmpQL

  3. Check to make sure the following values are set and not missing.

    Also make sure they are set correctly to the path that matches the actual paths to the bin directly and DLL file below.

    **Note that the paths may be different if you installed to a non-default drive or path**

    DIIDirectory with data=D:\netqos\proxyservices\bin
    DLLDirectory with data=D:\netqos\proxyservices\bin
    Driver with data=D:\netqos\proxyservices\bin\odbcsnmp.dll

    Figure 4

  4. Once the changes are made, recycle services and test the WatchDog settings and Rediscovering routers again.

    It may be necessary to reboot in some cases for the changes to take effect.