Hi,
I'm facing the same issue. Is there any news on this, or is it still the best recommendation?
Cheers,
Frank
Hi,
I'm facing the same issue. Is there any news on this, or is it still the best recommendation?
Cheers,
Frank
Thanks a lot.
Sadly the DB upgrade for MSSQL fails because event_cfg.description is a TEXT column and the upgrade script compares it with VARCHAR in the WHERE clause.
Simple fix - please change all TEXT columns to VARCHAR(MAX). TEXT has been deprecated long time ago...
https://learn.microsoft.com/en-us/sql/t-sql/data-types/ntext-text-and-image-transact-sql
Cheers
Thanks a lot. I tried to set this via the context menu of the node. Maybe it's worth integrating there as well, or an "advanced" button that takes you to the Scheduled Tasks view?
Cheers
Somehow, I fail to find how to configure that recurring maintenance. That is the solution that I'm looking for...
Hi,
we have a couple of access points where wifi is disabled in the night and over the weekend. This leads to errors in NetXMS. What is the usual way to tell NetXMS, that it is perfectly normal for these nodes to error outside of business hours?
Cheers
Yay, it works again...
Hi,
updated today to NetXMS 4.0. Now the Server won't start as it cannot find the mssql.ddr.
Is there anything I can do about it?
Cheers
Ok, after loading the dumps in Visual Studio and trying to understand them, I started to delete all of the affected DCIs, one by one. Seems like they all did belong to the same node, that was not important to monitor. So I decided to delete the node in the database alltogether.
Now NetXMS finally started again and is currently gathering all the data of the last weeks.
Hi again,
finally got time to look into this a bit more.
Disabling that DCI didn't help. I guess it's just the last line in the log, but not necessarily the reason.
I turned on crash dumps and I get a Divide by Zero at 00007FFE4513ABE7 in nxcore.dll (using 3.9.334). Does this help? I could provide the dump as well...
Cheers
Sadly I'm not any further. Currently I'm trying to restore the database to the time that I upgraded to 3.9.280 from 3.9.235. But so far no luck...
I wonder what the cause is. Is it 3.9 altogether because 3.8 was rock solid for me. Or is it some weird configuration I might have?
I happen to like NetXMS for various reasons. But currently it does just nothing. And I have to way to recover from that. I don't want to switch away...
Thanks for getting back. This could actually help...
The last line in the log after a lot of startup tasks always is:
DCObject::updateTimeIntervalsInternal(.1.3.6.1.4.1.8072.1.3.2.4.1.2.8.103.101.116.116.101.109.112.115.{instance} [16574]): retentionTime=0, pollingInterval=0
Maybe it is that both are 0?
Nothing? 
Hi,
after update to 3.9.280 the server keeps crashing. No dump is created and I cannot see anything in the log besides a warning that the runtime OpenSSL version does not match the compile time version.
Windows Server 2019
Microsoft SQL Server 2017
What can I do?
Cheers
Hi,
I have one machine - an Intel NUC that is powering a Yealink Microsoft Teams room system - that constantly complains about System.ThreadCount being unsupported.
NetXMS 3.8 and 3.9
What can I do about this? It's just a Windows 10 machine...
Cheers
Having some TrueNAS myself, have you installed the Agent or did you carry on just using SNMP?
Thanks for your reply. Now I understand the different approaches. If you prepend the file path with * the "Event ID" becomes a field that is writable. Missed that before. It seems like you can do more flexible things with the traditional Log Parser.
I use the current 3.9.156, but 3.8.something before didn't have the parameters set as well. Maybe if I use the Log Parser instead of the Windows Event Parser?
Edit: Yes, indeed. It works if I use the Log Parser out of the Policies. But I guess that's better anyway.
Hi,
another topic that I try to wrap my head around. I'm trying to get alarms on different windows events. For the moment I just want a warning message.
So, I have configured Windows Event Log to be pushed to NetXMS server. Does work.
I have configured the Windows Event Parser like this:
<parser trace="0" name="WindowsEventLog">
<macros/>
<rules>
<rule name="SQL Login failed">
<match repeatInterval="0" reset="false">(.*)</match>
<event>WIN_EVENT_RECORD_MATCHED</event>
<id>18456</id>
<logName>Application</logName>
<agentAction action=""></agentAction>
</rule>
<rule name="SQL Login failed">
<match repeatInterval="0" reset="false">(.*)</match>
<event>WIN_EVENT_RECORD_MATCHED</event>
<id>18452</id>
<logName>Application</logName>
<agentAction action=""></agentAction>
</rule>
</rules>
</parser>
A couple of questions already:
Ok then I defined the Event WIN_EVENT_RECORD_MATCHED with severity of Warning and a message of: Windows event ID %3: "%1"
As I understood the documentation n+2 (= %3) should be the EventID - but it is just empty.
Furthermore, in Event Processing Policy I created an alarm with Message "%m" and Alarm key of "WIN_EVT_%i_%3" to group id by Event ID. But as %3 is empty all events from a single machine are merged.
What am I doing wrong?
Cheers
@wimpers said in Sending emails from a Windows server with Office365?:
Yes I know but then you need another Windows box and license.
Just for the record - you can install them on the same box. No extra machine is needed...
If you want a Microsoft only solution, you can use the smtp server that is built-in to IIS. There a plenty of guides out there how to set this up.
Wait, what? I just tested it again and it works... :-[
You shouldn't change too much in a script at the same time. I tried to return an array of arrays in the script to work with the individual array in the filter script, but it seems you only can return an array of strings.