NetXMS Support Forum

Hello @all,

i have following code in a template:


<config>
<core>
<ExternalMetric>WindowsADUserGroup.Count(*):powershell -NoProfile -NonInteractive -Command "Write-Host ((Get-ADGroupMember -Identity '$1' -Recursive | Where-Object { $_.objectClass -eq 'user' }).count)"</ExternalMetric>
</core>
</config>

If i run the code directly on a server, there are no errors..

If i run the script via NetXMS DC, i getting the error that "_.objectClass" is not found...

Where is my fault? I didn't get a solution for that... Many thanks for any help...

Greetings
Marco

Hi Filipp,

unfortunately, we cannot confirm that this fix works.
We have been experiencing this behavior since updating the NetXMS Agent from 5.0.8 to 6.1.1. Is there a setting to disable these messages during user logins?

We have also noticed that the system is now detecting more non-essential installed software, which is flooding our alarm browser.  For example:

CapturePicker 10.0.17763.1 was installed
Hello-Setup 10.0.19585.1001 was installed
File Explorer 10.0.17763.1 was installed

Is there perhaps also a way to hide specific notifications?

Thanks for your help 

But this topology issue seems to persist. I'm not sure if it's due to my wrong configuration. Could you please give me some guidance? Thanks a lot!

The model is deployed using vLLM with the configuration --tool-call-parser=hermes. Could you please provide guidance?

Below is a current example:
[root@ai-app-0l apps]# curl http://IP:8001/v1/chat/completions \
-H "Content-Type: application/json" \
-H "Authorization: Bearer <your_token>" \
-d '{
  "model": "qwen3.6-35b-a3b",
  "messages": [
    {"role": "user", "content": "What's the weather like in Beijing today?"}
  ],
  "tools": [
    {
      "type": "function",
      "function": {
        "name": "get_weather",
        "description": "Get the current weather for the specified city",
        "parameters": {
          "type": "object",
          "properties": {
            "location": {
              "type": "string",
              "description": "City name, e.g., Beijing, Shanghai"
            }
          },
          "required": ["location"]
        }
      }
    }
  ]
}'

Response:

{
  "id": "chatcmpl-a914ca7d228bc903",
  "object": "chat.completion",
  "created": 1779196243,
  "model": "qwen3.6-35b-a3b",
  "choices": [
    {
      "index": 0,
      "message": {
        "role": "assistant",
        "content": "\n\n<tool_call>\n<function=get_weather>\n<parameter=location>\nBeijing\n</parameter>\n</function>\n</tool_call>",
        "refusal": null,
        "annotations": null,
        "audio": null,
        "function_call": null,
        "tool_calls": [],
        "reasoning": "Here's a thinking process:\n\n1. **Analyze User Input:**\n - User asks: \"What's the weather like in Beijing today?\"\n - Key entity: Beijing\n - Request: Current weather\n\n2. **Identify Available Tools:**\n - I have one tool: 'get_weather'\n - Tool description: Get the current weather for a specified city\n - Parameters: 'location' (string, required) - City name, e.g., Beijing, Shanghai\n\n3. **Map User Input to Tool Parameters:**\n - 'location' should be \"Beijing\"\n\n4. **Execute Tool Call:**\n - Call 'get_weather' with 'location: \"Beijing\"'\n\n5. **Process Tool Response (Simulation/Expectation):**\n - Since I don't have real-time access, I'll simulate the tool call and assume it returns a reasonable weather response. However, in this environment, I will actually make the tool call and let the system handle it. I'll generate the tool call now.\n\n Tool Call:\n```json\n{\n  \"name\": \"get_weather\",\n  \"parameters\": {\n    \"location\": \"Beijing\"\n  }\n}\n```\n\n6. **Formulate Response:**\n After receiving the tool response, I will present the weather information clearly to the user in Chinese.\n - For now, I'll just make the tool call."
      },
      "logprobs": null,
      "finish_reason": "stop",
      "stop_reason": null,
      "token_ids": null
    }
  ],
  "service_tier": null,
  "system_fingerprint": null,
  "usage": {
    "prompt_tokens": 284,
    "total_tokens": 656,
    "completion_tokens": 372,
    "prompt_tokens_details": null
  },
  "prompt_logprobs": null,
  "prompt_token_ids": null,
  "ky_transfer_params": null
}

V6.1.2

Большое спасибо

После такого завершения с ошибкой посмотрите в /var/log/netxmsd - если там видно что сервер рестартовал, то он вероятно крешится. Тогда нужно посмотреть, создался ли core файл (crash dump). Если ubuntu, то они обычно создаются в /var/crash

Уведомление здесь с задержкой, я бы посмотрел в Configuration -> Scheduled tasks (там есть галочка show system tasks) живет ли этот таймер и не пропадает ли раньше времени.

В русском канале https://t.me/netxms_ru есть @me_is_nem0, он занимался драйверами для девайсов специфичных для РФ, попробуйте с ним пообщаться.

Даб там в логе Cannot compile report /var/lib/netxms/nxreportd/definitions/WAN-int-1.0.1/main.jrxml
 net.sf.jasperreports.engine.JRException: org.xml.sax.SAXParseException; lineNumber: 2; columnNumber: 232; cvc-complex-type.3.2.2: Attribute 'uuid' is not allowed to appear in element 'jasperReport'.

Так что да, директория создалась, но скомпилироваться он не смог и поэтому его и в списке нет.

Я забыл упомянть выше, что нужна версия Jasper Studio 6.20.5 или младше. Тут похоже что версия более новая.

Я в принципе у claude такие вещи спрашиваю, вот его ответ по этой ошбике:
The error is a JRXML schema validation failure: the bundled JasperReports library in nxreportd is validating against an XSD that does
   not allow uuid on the root <jasperReport> element. This usually means the JRXML was produced by a Jaspersoft Studio newer than the
  JR runtime on the reporting server.

  A couple of options to unblock the deploy:

  1. Quick fix — open main.jrxml and delete the uuid="..." attribute from the <jasperReport ...> root tag, then rebuild. If validation then
   complains about uuid on a nested element (e.g. <band>, <textField>), strip those too. A one-shot scrub:
  sed -i 's/ uuid="[^"]*"//g' src/main/resources/main.jrxml
  2. Real fix — design the report in a Jaspersoft Studio version aligned with the JR library shipped with this NetXMS server. The two
  sample JRXMLs in this repo are produced with Jaspersoft Studio 6.16/6.19 (JasperReports Library 6.x), and they're known to deploy.
  Anything noticeably newer (7.x / 9.x) will emit XML features the server's older XSD rejects.

  For context: the samples in this repo (users/src/main/resources/main.jrxml and user-input/src/main/resources/main.jrxml) do carry
  uuid on <jasperReport> and deploy fine, so the user's server is matched to a stricter/older XSD than the one the samples were
  validated against — confirming the version-mismatch diagnosis. Designing with Studio 6.16–6.19 is the safest path.