Question
Glenn van Bavel · Apr 11, 2017

SNMP: Terminal is "Unable to open Registry key"

Hi,

Terminal says "Unable to open Registry key 'SOFTWARE\Microsoft\Windows\CurrentVersion\CommonFilesDir.1" when I execute $$Register^SNMP().

For monitoring purposes I want to use SNMP in Ensemble. One of the steps I have to do is to use the method $$Register^SNMP() in the terminal "%SYS" namespace. This is mentioned in a Intersystems Docs page.

Monitoring Caché Using SNMP

  • Caché expects the SNMP service to be installed before you install Caché, so it can add iscsnmp.dll to the proper Registry keys. Once Caché is installed, the SNMP service must be restarted so that it properly loads iscsnmp.dll and will find and communicate with the new Caché instance.

    Note:

    If Caché is installed before the SNMP service, iscsnmp.dll cannot be properly registered, and you must use the $$Register^SNMP() function to do this after the Windows SNMP service is installed. Once this is done the SNMP service must be restarted.

However I get the following error. When I execute "    w $$Register^SNMP()    " in the "%SYS" namespace.

"Unable to open Registry key 'SOFTWARE\Microsoft\Windows\CurrentVersion\CommonFilesDir.1"

Is there a way to run the terminal in administrative mode if it doesnt already? It sounds like a security issue to me. 

Does anyone know what the problem may be?

Greetings,

Glenn 

0
0 1,043
Discussion (5)3
Log in or sign up to continue

Launch an admin-level command window, then run csession.exe in the bin directory of your Caché install, giving your instance name as the argument, e.g.

If this works for you please click the checkmark alongside the answer.

Please try this:

C:\InterSystems\Ensemble\bin>ccontrol console ENSEMBLE

csession for Windows was added in 2017.1, so that explains why you do not have it.

Hi John, thankyou for the quick response. Unfortunately "csession" isnt anywhere to be found in my Intersystems folder. 

C:\InterSystems\Ensemble\bin>csession ENSEMBLE
'csession' is not recognized as an internal or external command,
operable program or batch file.

We're running

Version:Cache for Windows (x86-64) 2016.1.2 (Build 206U) Mon Jul 25 2016 16:42:32 EDT

Yes. That did the trick. The registry update went succesful. 

Thanks for your help,

Glenn,