hi victor, i have installed v1.2.3 this morning and by now i would expected the system to find the FC Management nodes, but it didn't therefor my problem is not solved. i have done db check and nothing. i hope you have access to a blade center to try and solve this problem Best Regards, Lindeamon

Many thanks Victor, 1.2.3 has sorted the dB import error. Best regards, David

Hi! Try to omit port number, and use only host name, or loopback address 127.0.0.1. Check that MySQL server is running. Best regards, Victor

NetXMS Server Version 1.2.3 installed on Windows 7 32 bit. SMSDriver set to generic.sms SMSDrvConfig set to COM1: Tried Tools -> Send SMS, no SMS received. In Actions Configuration, I have configured one to Send SMS and have assigned this in Event Processing Policy. Sending emails alerts work, but SMS does not work. Is there any way to debug SMS?

hi, i want to monitor my sharepoint site with the http service. i have configured the server's agent to run dci using the defaults posted in the forum but i did not work since the first GET command returns an error cause the 1st time it is trying to use annoy. user and only in the 2nd time the sharepoint is using the windows credentials and the site is opened. how do i configure the dci ? Best Regards, Lindeamon

Thanks! I'm adding my new nodes and container Claudio

This question has been posted two years ago, but I still experience the same problems. I installed Alarm Viewer 1.2.2. and it still has some problems with refreshing. Currently we have to restart the application to see a refreshed alarm list. Is there an option to set refresh time? We do not use the web viewer, but the nvav.exe application.

@victor said in Ping through a proxy node: Hi! Looks like something is broken in 1.2.2 regarding zone support. You do all configuration absolutely right, it must be a bug. I'll try to reproduce and fix this in a next few days. Best regards, Victor Thank you very much for your support. Let me know if I can be useful for any other test. Best regards, Marco

Hi! Looks like a bug in console. I'll try to fix it in next release. So far as workaround you can use legacy console (nxcon.exe) tio edit syslog parser in XML form. Best regards, Victor

Hi Victor, Thanks! Regards, SPK

Hi! "agent not responding" means that NetXMS server cannot communicate with agent (but node may still be alive and reachable), and "node down" means that node cannot be reached by NetXMS server with any allowed protocol - agent, SNMP, and ICMP. Usually you get "agent not responding" event before "node down", but it will be correlated to "node down" and will not be passed to event processing policy. Best regards, Victor

I think I may have found my own answer.  Should have done a search on the topic before posting.  My bad. https://www.netxms.org/forum/configuration/transformation/msg5758/#msg5758 Tony M.

thank you!

Hi! I don't see any problem in parser configuration. Could you please send me debug output of the agent? Best regards, Victor

Hi! I suppose that connection to server was dropped by timeout or due to some other reason, and ODBC subagent does not reconnect. I'll check it. Best regards, Victor

Hi! Yes, this is a bug in the Java console. Just fixed it - version 1.2.3 will work correctly. Best regards, Victor

I'll try to. It shouldn't be hard to fix, so most important is not to forget about it Added to bugtracker: https://www.radensolutions.com/chiliproject/issues/58. Best regards, Victor

Learning more about this each day and it only keeps getting BETTER!  Thanks for the reply, this will solve the issue very well and offers exactly what I need.

@lweidig said in problem with tranformation tool in DCI: Just a couple of comments: Try changing your data type on the General tab to Unsigned integer 64 bit.  With your transformation anything over 4GB may fail. Update your transformation to '$1 * 1024' as that is the correct conversion from KB to bytes, not 1000 I cannot comment on the test transformation window, I have NEVER had it actually pop up for me.  My only guess is that it is using the base type provided by the SNMP value as its type for processing which means anything over 2,147,483,647 (MAX for 32 bit signed) bytes becomes negative You are absolutely correct - test uses DCI data type, so it must be changed to 64 bit integer to get correct result. Best regards, Victor

Thank you Victor!