NetXMS Forum

Thank you!

Hi,

thank you for your answer - maybe i found the problem.

THe error message is like (in German): The message resource exists, but the message was not found in the string/message table.
Maybe this is the 251?

---

Hi, thank you for your answer - sorry i was on holidays.

Now i tested it again:

406 is creating a warning - this is working
251 should trigger a Critical warning - i have triggers for: 251 without level, 251 with Level 1 and 2 and 3

But nothing with 251 is working. 406 is triggering fine everytime.

---

Hi,

yes it is from the LSA Software from Broadcom which is writing to eventlog.
Here is the XML from EventID 251 and 404/406.

Thank you!

---

Hi,

i have problems when using the log parser.
I try to catch Error 251 from the windows Application Log and forward to NetXMS.

When i just change the EventID to 404 or 406 it is working and i see an entry in the Monitor from Server.
I cant figure out why it is not working with "Error" "EventID 251".
I never see a entry in the Debuglog from client with EventID 251.
I tried with Filter of Source "LSA_MONITOR" or without, doesnt change anything.
Logwatch is enabled in Client Agent.

Thank you!

Sorry i forgot: client and Server are 6.1.1

---