NetXMS 2.2.1 released

[lindeamon]

thank you very much for the hard work and this great app.

[StanHubble]

Yes, Thank you very much for your great work....

p.s. Why the number shift (2.2.1 vs 2.1.3)?

[iGodunoff]

All the netxms agents had stopped working right after upgrade to 2.2.1. Config files of all agents contain the following lines:

RequireEncryption = yes
RequireAuthentication = yes
EncryptedSharedSecret = B/Cx9iK3RpLCpgp+8SvHuMKmCn7xK8e4wqYKfvErx7g=

It worked fine with all previous agent versions but causes 2.2.1 agents to crash soon after they started. Very sad What should I do now to get NetXMS working again? I've lost connection with all network nodes...

P.S. Error in Windows logs:

H_PdhObjectItems: PDH Error C0000BB8 in call to PdhEnumObjectItems

Right after this NetXMS Agent service crushes.

[victor]

@stanhubble said in NetXMS 2.2.1 released:

p.s. Why the number shift (2.2.1 vs 2.1.3)?

We had internal build with version number 2.2.0 distributed to our support clients with some important changes backported from 3.0 branch. Before this release we decide to make it new stable branch - because changes are important. To avoid version clashes and uderscore that there are significant changes inside we decide to number this release 2.2.1.

Best regards,
Victor

[victor]

@igodunoff said in NetXMS 2.2.1 released:

All the netxms agents had stopped working right after upgrade to 2.2.1. Config files of all agents contain the following lines:

RequireEncryption = yes
RequireAuthentication = yes
EncryptedSharedSecret = B/Cx9iK3RpLCpgp+8SvHuMKmCn7xK8e4wqYKfvErx7g=

It worked fine with all previous agent versions but causes 2.2.1 agents to crash soon after they started. Very sad What should I do now to get NetXMS working again? I've lost connection with all network nodes...

P.S. Error in Windows logs:

H_PdhObjectItems: PDH Error C0000BB8 in call to PdhEnumObjectItems

Right after this NetXMS Agent service crushes.

From the context I assume it is Windows. Do you have crash dumps from agent? If not, please enable crash dump generation in agent config and send them to us. As a workaround I recommend to rollback to agent version 2.1.2 (they will work with new server).

Best regards,
Victor

[iGodunoff]

If it's Windows then it seems very strange as I have multiple Windows versions (from XP to 10, 31 and 64 bit) but the agents crash everywhere. OK, I'll try to enable dumps and send them.

[user54119]

Thanks to all for the new release.

On WinXP 32bit (I know it's too old) I get Error missing "api-ms-win-crt-runtime-l1-1-0.dll" when I update V2.1.2 to V2.2.1 with package deploy. It seems to be something from a C++ Runtime. Is it not included in the installer? Which C++ is needed?

thanks
Dani

[victor]

Hi,

try to install runtime from Visual Studio 2017. Seems that we pack it incorrectly.

Best regards,
Victor

[user54119]

Is C++ Runtime 2017 installable on WinXP?

edit:
I tried it on a test VM. It works on WinXP with Visual C++ Runtime 2017 x86.

thanks
Dani

[lindeamon]

Hi Victor,

there were threads about agents crashing and threads about packaging issues, does the links in download section lead to the latest and fixed packages ?

Best Regards,
Lindeamon

[victor]

Hi,

current download links points to repackaged agents. It should work fine without separately installed VC++ runtime. We didn't fix agent crash issue yet, but was unable to reproduce it either.

Best regards,
Victor

[lindeamon]

thank you very much !!!

[xchema]

New Android management console filename suggests it's 2.2.1 version, but when installed it seems to be still 2.1.2, is it me or the apk is wrong?

[wizard]

Hi Victor!

Would you implement nxsl's functions for dealing with persistant storage, please. I see a few functions in ps.cpp, but it seemed those not exported into nsxl.

[victor]

Hi,

persistent storage is implemented. You can access persistent storage entries using # operator. It has two forms:

#identifier

and

#(expression)

If your key conforms to NXSL identifier requirements you can use first form, otherwise (or if you are building key name dynamically) you should use second form. Examples:

1. Set value of key "test":

#test = 123;

or

#("test") = 123;

2. Set value of a key whose name built from prefix "node_" and current node ID:

#("node_" . $node->id) = 42;

3. Print value of key from example 2 multiplied by 10:

println #("node_" . $node->id) * 10;

Best regards,
Victor

[wizard]

Thank you very much, Victor! It's really nice and convenient.

[yordi]

@xchema said in NetXMS 2.2.1 released:

New Android management console filename suggests it's 2.2.1 version, but when installed it seems to be still 2.1.2, is it me or the apk is wrong?

Same problem for me also with the android apk manager ..

[yordi]

Hey Victor,

After update server to 2.2.1 (database check ok )
update de Windows manager to 2.2.1 I can not login anymore --> Connection Error  org/netxms/base/GeoLocation

restart the Netxms server (ubuntu) does not help ...

UPDATE:
after deleting user date on management pc + delete NETXMS manager (new version was extracted over the older version)
and re-unpack the new version i could start the manager again .

[volkoff]

Android console version is broken or didn't recompile properly or whatever reason it is.
Filename suggests it's 2.2.1. But after launch program says 2.1.2 and didn't connect to the server due to incompatible version of exchange protocol.

Thanks for your work. You do a great job. It makes our lives much easier

P.S. Oh, and Android AppManager says it's 2.1.0

[victor]

Hi,

we just updated download link for Android client to properly packaged apk.

Best regards,
Victor