NetXMS Support Forum

As far as I know you can install 64 bit native client on the same machine alongside 32 bit client (but I could be wrong, I'm not an expert on SQL Server at all).

Best regards,
Victor

We don't use .NET, only Visual C++ runtime. What if you install Visual C++ 2017 runtime on such machine?

Best regards,
Victor

I finally assign one of our developers to this task in late December (as part-time task). Hopefully we will get at least a prototype soon.

Best regards,
Victor

It's actually visible on screenshots that aliases are empty. Please contact me directly so I can debug this issue.

Best regards,
Victor

Hi,

what is your settings for using interface aliases? And what are aliases for those interfaces?

Best regards,
Victor

Hi,

current 3.0 branch does not have much visible differences from 2.2 now besides sensor objects. These changes aimed at simplifying work with different sensors - currently we have support for LoraWAN sensors and integration with this open source LoraWAN server - https://gotthardp.github.io/lorawan-server/, as well as DLMS sensors with commercial extension. We did some internal changes as well aimed at improving internal architecture and simplifying functionality extension. Major changes planned for 3.0 branch (in no particular order) are:
- UI redesign (for better usability - it is quite cluttered and complicated now)
- Sub-policies in event processing policy
- Replace built-in email sender and SMS drivers with "communication channels" - so it will be possible to use Slack and SMS simultaneously for example
- User-based notifications (just select "notify user" in event processing policy and server will pick up appropriate communication channel from user profile)
- Better virtual infrastructure integration and visualization
- Improved network topology visualization (OSPF routes, default routes on IP topology maps, etc.)
- Tight Unimus (https://unimus.net/) integration
- Analytical tools for collected data
- Not decided yet: support for JavaScript or Python server extensions

Best regards,
Victor

Quote from: Brown_Leaf on January 09, 2018, 08:21:26 PM
Hi, I would like to upgrade NetXMS server from 2.1 to 2.2.2. I am looking for a Server installer for Windows x86. NetXMS download site has links to Server Binaries only for Windows x64. Why is the 32-bit installer discontinued? Thanks.

Hi,

we are trying to reduce release efforts by excluding old and rarely used targets. We consider that since Windows Server 2008 R2 all server operating systems are 64 bit 32 bit server build is not necessary. What OS you are using for running NetXMS server?
I can make 32 bit installer for 2.2.2, but we will discontinue 32 bit builds sooner or later anyway.

Best regards,
Victor

We switched to Visual Studio 2017 for building Windows binaries. It should support Windows XP SP3 and higher (but Windows XP before SP3 is not supported). What exact Windows version you have?

Best regards,
Victor

Hi all,

NetXMS version 2.2.2 is released. Changes since previous release:

- Server command line tools working with agents (nxaction, nxap, nxget, nxupload) use encryption by default
- "Floor plan" display mode for objects on network map
- Access to zone data in network discovery filters
- Automatic target configuration in PING subagent
- Implemented option to display object status map in radial form ("sunburst diagram")
- Fixed issues:
        NX-513 (add toString() to all data objects in netxms-base)
        NX-599 (Delete single collected value from a DCI)
        NX-669 (DRBD monitoring is not working in some configurations)
        NX-689 (Pass found SNMP configuration while discovery for new node creation)
        NX-890 (Passive elements in rack)
        NX-1169 (Encryption is not set by default between agent and server)
        NX-1297 (Copying Files inside File Manager using CTRL and Drag&Drop is not working)
        NX-1299 (Add username filter to CountEx(*) and Process.XXX(*) parameters in Linux subagent)
        NX-1306 (Show system FQDN in tunnel manager)
        NX-1350 (Invert Values option for performance tab DCIs; Performance tab graph configuration is maintained on double-click)
        NX-1366 (Edit option for "group box" decorations on network maps)
        NX-1369 (Title not displayed for dashboard element "Rack")
        NX-1370 (Rack page not displayed correctly when switch between rack objects)
        NX-1372 (PING subagent is not working)
        NX-1374 (Element DashboardGroup not displayed in Dashboard perspective)
        NX-1373 (Error message "Error loading RSA keys from ..." in all server-to-agent command line tools)
        NX-1375 (Add functionality to switch off multipliers for graphs)
        NX-1376 (Windows agent reports incorrect OS version on Windows 10)
        NX-1379 (Rack width calculated incorrectly if only front/back selected)
        NX-1380 (Database error when node has LLDP ID longer than 63 characters)
        NX-1381 (Unjustified NXSL errors "cannot do automatic type cast")
        NX-1384 (Automatic ping target configuration on first data request)
        NX-1385 (Configurable status colors in UI)
        NX-1387 (Performance tab graph sorting in not working with groups)

Best regards,
Victor

Hi,

we plan to make first milestone release in 3.0 branch in late January or early February.

Best regards,
Victor

Hi,

looks like really weird bug. Are you using web or desktop UI? Can you send UI log file (for desktop it will be $HOME/.nxmc/data/.metadata/.log, for web UI it will be somewhere within runtime data for application, but with the same name)?

Best regards,
Victor

Hi,

do you have other tunnels working? It could be certificate validation issue - you can check tunnel log on server side for more information.

Best regards,
Victor

Hi,

what exact error you are getting? Did you check that web server is running and listening?

Best regards,
Victor

Hi,

we will fix it in release 2.2.2. As a workaround, edit file /usr/share/netxms/sql/dbinit_mysql.sql and change line

var_name varchar(255) not null

to

var_name varchar(63) not null

Best regards,
Victor

Hi,

In 2.2 we have switched to using Visual Studio 2017 for building Windows components. I've seen exactly this effect on Windows XP SP2 which is not supported by VS 2017 runtime (only XP SP3 is supported). For Windows Server 2003 minimum requirements is Windows Server 2003 SP2. Do you have it?
For older systems I recommend to continue using latest agent in 2.1 branch.

Best regards,
Victor