Nx 5.0 update Event rule issue
CompletedHi.
When I update til Nx 5.0 Send email action are changes target to only owner.
Administrators is removed from the target.
Is it possible to update to Nx 5.0 without any changes in event rules?
Kai
-
That's quite annoying. I immediately created a task for our development team to investigate the issue.
Can you share the About.. window in the Nx Desktop client? You can open it with F1 after you have been logged into your system with the Nx Desktop client. In the bottom-left, you see a copy icon, if you click it, you can paste the required information as a reply.
JIRA-VMS-34667
0 -
Hi Norman.
Thanks, here is the about:
Nx Witness Client version 5.0.0.35064 (a0c38320252a).
Built for windows-x64 with msvc.
OpenGL version: 4.6.0 - Build 27.20.100.8681.
OpenGL renderer: Intel(R) UHD Graphics 630.
OpenGL vendor: Intel.
OpenGL max texture size: 16384.
Server 2 Vestre Torv (172.31.255.250): v5.0.0.35064
Server1 Vestre Torv (192.168.2.7): v5.0.0.350640 -
Thank you.
I was able to reproduce the issue, yesterday twice in a row. First to verify the issue, and second to create a screen recording for our developers. Unfortunately I failed the third time, when I wanted to collect the database before and after the upgrade, but I'll continue to work on it with our developers.
To be continued...
0 -
Hi Kai Magnus Nymann,
So far we weren't able to reproduce the issue after trying numerous times, but I'll enable some additional logging before executing the update to capture relevant data in case it happens again.We did release a hotfix, since the 35064 build had some issues this might be unexpected to be related to the issue you encountered.
At this stage I'll set this ticket to completed, since at this stage, nothing can be added.
0 -
Hi Norman:
That is strange.
I have update 3 servers with 5.0 35136, and still are target reset for only owner after update.
Screenshot of rules before update:After 35136 update:
0 -
My apologies. I didn't read your original request correctly and my attempt to reproduce it, was incorrect as well.
Thank you for reporting this, I have reproduced the issue and I have reported it to our developers.
To be continued...
JIRA-VMS-34867
0 -
Was resolved in v.5.0.0.35270+
-1
Post is closed for comments.
Comments
7 comments