Hi, it is a process that started within each desktop session, and can be used to take screenshots from workstations (via "take screenshot" option in node's context menu). Best regards, Victor

I figured it out. GetDCIValueByName is able to return table objects, so it's quite simple: sub main() { table = GetDCIValueByName($node, $event->parameters[1]); if (table == null) { return "[GetDCIValueByName(" . $node->name . ", " . $event->parameters[1] . ") failed.]"; } colNum = 1; alertMsg = table->get($event->parameters[4], colNum); if (alertMsg == null) { return "[table->get(" . $event->parameters[4] . ", " . colNum . ") failed.]"; } return alertMsg; }

Hi, [14-Oct-2014 15:37:40.350] [DEBUG] LDAPConnection::initLDAP(): Connecting to LDAP server [14-Oct-2014 15:37:40.851] [DEBUG] LDAPConnection::syncUsers(): LDAP could not get search results. Error code: Size limit exceeded Here is other thread: https://www.netxms.org/forum/configuration/ldap-config-exceed-size-limit-ms-active-directory/ Win2003/2008 AD have default value of MaxPageSize = 1000. Rgs  TM

Hi There, is there someone who can share a senseble Windows Server/Client template with me/us? I tried to start to configure all from bottom up but it is very hard and time consumeing if you have no standard values to start from. Any help would be great. Thank you in advance.

Thanks, that worked great!

Yes, your changes are correct – I attached wrong file Proper fix attached. fix.diff

Due to a lot of issues I've encounter on this version (1.2.17) such as sudden stop of netxms core service, dci errors, I've revert my installation to previous version 1.2.16 and still on windows 2008 R2 SP1 64bit. No issues encounter so far on netxms version 1.2.16.

10x, i will look at it tomorrow Lindeamon

Hi Victor, Thanks! Sounds really nice. We will upgrade as soon as we find time Kind regards, AP_ops

I did a quick test with your configuration files (except loading IST module) – they are working fine with latest release (1.2.17). I don't have 1.1.1 installed anywhere to check it. I highly recommend you to upgrade.

Hello. Could you please provide us with stack trace? https://wiki.debian.org/HowToGetABacktrace#Running_gdb

 ::) ::) ::) ::) ::) ::) ::) Well the Problem was soved , ist was my own stupidity .......... Netxms Was sending the Mails but our Exchange was blocking the for some Reason ... no it works fine for me SOLVED

for a more elegant methode (in NetXMS V1.2.17) see this thread: https://www.netxms.org/forum/configuration/node-with-question-mark-on-the-icon-of-object-browser/

ok. I made my tests to this new feature: node created with no interfaces (for an unmanagable device) in polling properties of this node I deactivated all except 'Disbale data collection' DCI created on this node which checks the status of the switch port (gives back 4 for down and 0 for up) and 'use this DCI for node status calculation' = ON Now when I switch off the device, I get an event 'SYS_NODE_CRITICAL'. When I switch on the device again, I get a 'SYS_NODE_NORMAL' event. But for my existing event processing policy I need 'SYS_NODE_DOWN' and 'SYS_NODE_UP' events. So I created a threshold on the DCI (!=0 -> SYS_NODE_DOWN, deactivation event SYS_NODE_UP) and everything works as expected. I will first use it for unmanageble provider-modems and switches. Maybe this helps someone.

For me it seems also fixed. No old topology info anymore. Thanks Victor.

Is there some way how I can find out why the network discovery does not work? I've set the DicoveryPollingInterval = 100 ActiveDiscoveryInteval = 7200 ActiveNetworkDiscovery = 1 Do I have to set anything else. Did I miss to activate a service?

thank you.

Thanks for your help.  I'll download the new version tomorrow, then.

@victor said in Action is not taken (executed)?: try to set debug level to at least 4 (add DebugLevel = 4 to netxmsd.conf) and check server's log. Thanks, I can see clearly that script was executed but actually it was not because I had a typo in command line. I think return value (of cmd.exe /c) in log file would be a help.

You are using extremely old version (I'd say 1.1.11), which was released in the 2012.