NetXMS Support Forum

Hi!
This bug is specific for web UI on Windows. If you open C:\NetXMS-WebUI\jetty-home\etc\webdefault.xml file and change
    <init-param>
      <param-name>useFileMappedBuffer</param-name>
      <param-value>true</param-value>
    </init-param>
to
    <init-param>
      <param-name>useFileMappedBuffer</param-name>
      <param-value>false</param-value>
    </init-param>
this should solve the issue. This setting will be set to false in next releases.

I would probably try once again with mssql.ddr driver according to Victor's recommendations above.

Also if you do not have exact requirement to use MsSQL, you can install Postgres

Please check if there is anything in web ui log. E.g. for tomcat you can run

journalctl -u tomcat9.service -f

and then open a map to trigger the error. Also it would be beneficial if you can show screenshot of your map to see what elements are present on it.

Зависание на инициализации расширений в старом клиенте в 4.4.4. должно быть починено.

Звуки в новом будем доделывать.

Hi!

By the way, we have two days of reading windows event log - one is agent log parser (set up in policy in template that is applied to agent) and the second is windows event log synchronization. Which one you are using? Anyways, both of these ways should work similarly on the following:

When netxms event is created, additional information from windows event should be added as parameters:
https://www.netxms.org/documentation/adminguide/log-monitoring.html#passing-parameters-to-events

If you your Teams_Alarm_AD_Anmeldung event in netxms event log and double-click it, you should see detailed information about the event, including values of it's parameters. Is the information you need present in these parameters?

Let me list some approaches that can be used for integration:
- sending events into netxms using nxevent / nxaevent command line tools
- pushing DCI values - nxpush / nxapush tools
- netxms agent can monitor a log file and create events on matching lines
- web services can be used to get data from other systems - it's also possible to use nxsl script to parse received jsons.
- some external app can connect to netxms via Web API or nxshell

В патч релизе попробуем поменять на utf-8 по умолчанию

Проверьте в логах томката какую версию джавы он использует.
В этой теме было что-то очень похожее: https://www.netxms.org/forum/oe-oo/oshibka-soedineniya-incompatible-version-of-communication-protocol/

I don't remember exactly, but there probably was a bug with default values of these named parameter of NetworkService.Status. Your URL contains IP address, but certificate was probably issued for a domain name, so host verification fails. To skip host verification, add the following:

NetworkService.Status(https://212.70.163.157,verify-peer=false,verify-host=false)

Documentation on all available parameters should be up to date:
https://www.netxms.org/documentation/adminguide/service-monitoring.html#network-service-monitoring-using-dci

If you are on Linux, check if netxms-dbdrv-pgsql package is installed

Install https://netxms.org/download/releases/4.4/nxmc-legacy-4.4.3.war along with nxmc-4.4.3.war

Note that legacy UI is planned to be discontinued after a few months, so if you are new to the system, it's better to use new UI.

Да, MailEncoding был выкинут с мыслью, что сейчас все почтовые клиенты должны понимать utf8.
А Outlook какой версии и на какой ОС?

Можно настроить какой-нибудь MTA - тогда NetXMS будет посылать письма на 127.0.0.1, а тот уже пересылать дальше. Под линуксом например postfix, под windows тоже что-то было

У версии сервера и клиента первые две цифры должны быть одинаковыми, т.е. если сервер 4.4.х то и клиент (десктопный или web ui) то же должен быть 4.4.х

Hi!

Simplest would be to store this in DCI's comment, and since recently we have %D macro that resolves to that comment, but the problem is that editing that comment from NXSL (e.g. in transformation script) is not currently possible. But we will add that at some point.

Currently you can use custom attributes on node to store such information, e.g. if DCI's tranformation script has
$node->setCustomAttribute("DCI_DESC_".$dci->name, 123);
this will update a custom attribute.

Then in script library you can have e.g. GetDciDescFromCustomAttribute script with the following:
return $node->getCustomAttribute("DCI_DESC_" . $dci->name);

And now in event's message you can have %[GetDciDescFromCustomAttribute] macro that would call above script and will get value of the custom attribute.

We are currently working to improve maps in v5.0. There will be option to define link color by script and other fixes.

Can you explain a bit on multiple links - what information/benefits it gives if you see all links separately? Status of these links? Understanding how many links there are? Throughput for each link separately?