hi victor, thank you for answering. i know i say it a lot but every time i have to script something it comes back again. how can you help us know what you know ? can you think of a way to insert this information in way that i will be able to think of it my self Best Regards, Lindeamon

Hi Victor, Thank you very much. I will be happy to be a beta tester! Regards, Marco

Yes, it is still considered. But it is much more complicated then template graphs, so we need more time/resources for implementation. Best regards, Victor

Hi! You can uninstall NetXMS server completely (it will left database intact), and then install it without installing bundled SQL Server client and attach to existing database. Best regards, Victor

Hi, I've managed to install reporting server to run in Windows environment on MSSQL Server 2016 and AzureSQL. If I try to execute the default report "Alarm Resolution Timer" what I get is this error in the report server log (attached to the post there is the complete log): 20:30:30.089 [quartzScheduler_Worker-1] ERROR o.h.id.enhanced.TableStructure - could not read a hi value com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'hibernate_sequence'. at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:216) ~[sqljdbc4-4.0.jar:na] at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1515) ~[sqljdbc4-4.0.jar:na] at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:404) ~[sqljdbc4-4.0.jar:na] The only similar error I found is this: https://www.netxms.org/forum/installation/reporting-server-4315/msg20119/#msg20119 But no useful hints... Any other suggestions on how to solve? Regards, Marco reportserverlog.txt

Thank you, now the script and instance discovery works fine

insert a line below the "# start daemon" comment: sleep 300 # wait 5 minutes You might want to read a little about shell programming .... Kind regards, Thomas

That's it. Thanks for the hint.

That would make sense then. We're using 2.1-M2 as well. At present we detect when the Agent crashes and restart the service automatically. (That doesn't always work either, as we also use quite a few ExternalParameters which call PowerShell. For some reason sometimes a PowerShell process will just keep running and lock port 4700. So when NetXMS stops, it can not start again until the PowerShell process in question is terminated. But that's probably a different issue to the Event Log one.)

We run an inhouse help desk system. We already have procedures in place to create tickets using a MSSQL sql stored procedure. I have written a database trigger that will generate the ticket from the alarm table and update the hd_ticket field in the alarm table. It is possible to make that ticket number appear in the GUI?

Meanwhile i figured out that one system spams NetXMS with thousands and thousand of windows eventlog entrys. I killed the agent on that system and restored the NetXMS database from yesterday. Now, NetXMS runs like before...

I use the NetXMS server as proxy for SSH, it works too. Don't forget the 'trusted nodes'. Dani

Not sure if I'm missing something in the config but I'm unable to show the full name of some of our nodes seems only 20 characters are shown on network maps. If I hover over they show fine. Please see attached screen grab. [image: netxms-hostname too long network map.png]

I want to get a MAC value from an SNMP table shown as a formatted MAC address in the table, I wanted to achieve this through a DCI Table Transformation script.

Appears the issue is related to DCI Tables. All segfault backtraces mention DCTable. I then ran netxmsd with -D9 option for testing and found several prepare statements for a DCI Table prior to the crash - but no completed sync. I had such an issue in the past with a template for Intel Modular servers. When I could not determine the underlying cause, I "simply" switched all tables in all templates to instances and the system had been stable since. Appears I missed one: a single template (for a Netgear ReadyNAS) with a single device bound to it still had DCI tables in use. It appears the NAS performed an automatic firmware upgrade to version 6.6.1 and within an hour NetXMS started crashing. It is not clear if the template for the NAS had not been applied until after the upgrade (auto-apply rules) or if the upgrade simply triggered something in the SNMP responses that caused the crashes of the server. Since I disabled the DCI Tables, the server has not crashed (around 90 minutes of uptime now, over 6 times as long as the longest interval between crashes before that). It looks like there is some kind of issue within the DCI table code that can lead to segfaults and server crashes.

Hi looking for a bit of assistance. I'm trying to setup the report server on a Linux server. So we can send out weekly reports of up time for our servers / network devices. I've gone though the report server setup https://wiki.netxms.org/wiki/Reporting_server_setup running version reporting-server-2.1-M2.jar But failing to be able to connect from the NetXMS management console to reports  - Failed to load reports from the server: Communication failure Any ideas on troubleshooting steps we can take to get this working?

it's ok, I solved it....  ;D

Check why it's failing: > See "systemctl status nxagentd.service" and "journalctl -xe" for details.

Hello, I tried the following steps by myself: Clone NetXMS VM to other more robust erver (up today it doesnt report more transformation script or dci errors) Rediscover DCI instances on nodes where they disappear, also changing a bit their names to trigger the db update (https://www.netxms.org/forum/general-support/deleted-instanced-dcis-appear-again-after-restart/msg20528/#msg20528) Regards.

Create a cluster with two nodes, configure DCIs on the cluster itself - it will be propagated to both nodes