NetXMS Forum

Hi, it should be there now, please let us know if any further issues.

У меня это работает, возможно, вам придется указать полный путь, как показано во вложении.

Хм, это упоминается в разделе установки, возможно, нам нужно сделать реф-ссылку

Да, мы проверили отзывы о похожей ошибке в более ранних сообщениях на форуме, и, похоже, нам нужно указать полный путь. Мы исправим это в руководстве.
Спасибо за ваш вклад.

Hi, Попробуйте выполнить шаги миграции из руководства администратора. Также есть раздел для экспорта/импорта базы данных.

Appendix — NetXMS Administrator Guide (7.0.0)

(netxms.org)

Hi, could you pls let us know what OS are you using? Also, did you try to connect as user 'system' instead of 'admin' for dashboard access?

Hi, so first please try to reset system access rights to default for both groups. Then, if that fails you may wish to login as user system/system and access affected Dashboards. This is just a workaround to remedy current situation. We will check read only access functionality further. In the meanwhile, please let us know your feedback on suggested steps.

P.S. If user system is locked then you can unlock it with 'nxdbmgr  reset-system-account'

hi, is the issue observed with user "admin" or with some newly created user? If latter, then please check user setting and also enable UI and system access rights.

Hi, we are planning to build it next week or so. We will update once available.

Hi there, we have created tracker for this and will look into resolving it.

https://track.radensolutions.com/issue/NX-2651

We will check it internally, sure. In the meantime, could you please also share Interfaces tab output for both?

Hi, could you please share screenshots of Capabilities in Overview tab and Interfaces tab for both?

Hi, this should be fixed now. Thank you for your contribution.

Hi. It is still in pipeline. We have not had a chance to work on this due to limited resources, but this is scheduled for early January. We will share more info as and when. Thank you for your patience.

Hi, so I will be treading carefully here as all based on Google research. There is an indication that Win32_Product is not query optimized class and thus query on this class runs a consistency check and performs silent repairs. This would probably require for agent to have admin rights on Windows server(?).

Here is Microsoft guidance to use an alternative method and that is to query registry - https://learn.microsoft.com/en-us/troubleshoot/windows-server/admin-development/windows-installer-reconfigured-all-applications. 

Please let us know if that works for you.

Hi, could you please share your test scenario, also OS and debug logs if possible, etc? We have tried from your side and were not able to replicate this issue just yet.

Hi Alessio

We have raised this with the team and you can follow progress on https://track.radensolutions.com/issue/NX-2635

Thank you for your contribution!

Hi, we've created a ticket here https://track.radensolutions.com/issue/NX-2634, so you can also monitor progress on your request.

Hi, it seems you have upgraded client to version 5.0.8, but screenshot with version is from management console and version 5.0.6 is the last available. This module is being phased out, so please use client or web UI.

Hi, thank you for your feedback. Client should not be doing any requests to server when browsing objects in object tree. When client starts, it reads information about all objects from server and keeps cache of that in it's memory. When state of objects changes on the server, server sends updates to the client and client updates it's in-memory copy.
So first thing to check - if there's enough of free mem on PC where client is running, may be it starts swapping. Also to check - CPU load on the PC, may be java consumes a lot of CPU and this slows things down.

To check, may be client still requests something from the server and waits for it - on the server side it's possible to see client-related messages in log, lines look like this:

2024.11.05 13:12:25.297 *D* [client.session.0  ] Sending message CMD_REQUEST_COMPLETED (64 bytes)

you can do
debug client.* 6
this would show messages for all connected clients. In our example 0 in tag client.session.0 means that it's client session number 0. So you can do

debug client.session.0 6
and you will see messages in log which are related only to that specific client session.

On unrelated note, please check your server logs to see why so many SQL queries are failing.

Failed ......... 12131046