Nx Desktop client closes unexpectedly after clicking on dates in calendarAnswered
My Nx Witness Client closes randomly after clicking around on the dates in the calendar. To reproduce the error, open the calendar and keep clicking the dates. Sometimes it happens after one click, other times many clicks.
Nx Witness Client version 188.8.131.52745
OS: Windows 10 Enterprise 21H2 19044.2486
Processor: 12th Gen Intel® Core™ i7-12800H
I've had the client switch between graphics processors and same issue still occurs.
All drivers appear to be up to date.
I've tried uninstalling and reinstalling the client too.
Could you please try the latest official 5.0 patch? You could proceed with the upgrade by the following info,
Build Number: 36221 Password: 1odlmo
We've fixed one client crash issue which sounds similar to your scenario:
- Desktop Client would crash when hiding the calendar after searching on the Motion tab by selecting an area and multiple dates on the calendar. Fixed.
Please let me know if it can resolve your problem or not. Thank you.
I tried to upgrade through the In-Client upgrade. The client installed successfully but the servers were just hanging with 'installing...'. My servers are both VMs with Ubuntu 20.04. I found this post How to fix in-client upgrade issues on Ubuntu – Network Optix with the same issue so I've tried to manually update following that. But the patch seems to be looking for a package that doesn't exist and wont start up. I can't seem to find the package online either
Feb 16 18:08:14 vm-test systemd: Starting Network Optix Media Server...
Feb 16 18:08:14 vm-test systemd: Started Network Optix Media Server.
Feb 16 18:08:14 vm-test systemd_mediaserver_start.sh: GDB is not available on the host.
Feb 16 18:08:14 vm-test systemd_mediaserver_start.sh: /opt/networkoptix/mediaserver/bin/mediaserver: error while loading shared libraries: liblber-2.4.so.2: cannot open shared object file: No such file or directory
Feb 16 18:08:14 vm-test systemd: networkoptix-mediaserver.service: Main process exited, code=exited, status=127/n/a
Feb 16 18:08:14 vm-test systemd: networkoptix-mediaserver.service: Failed with result 'exit-code'.
Feb 16 18:08:15 vm-test systemd: networkoptix-mediaserver.service: Scheduled restart job, restart counter is at 5.
Feb 16 18:08:15 vm-test systemd: Stopped Network Optix Media Server.
Feb 16 18:08:15 vm-test systemd: networkoptix-mediaserver.service: Start request repeated too quickly.
Feb 16 18:08:15 vm-test systemd: networkoptix-mediaserver.service: Failed with result 'exit-code'.
Feb 16 18:08:15 vm-test systemd: Failed to start Network Optix Media Server.
Reverting back to the previous version works perfectly fine though.
Hey Wendy Chuang,
Any idea what I could try and do to get the server patch working on my Ubuntu 20.04 machines?
Correct Kieran. The software looks for the OS when you do a try an in-client update.
From 5.1 onwards, we'll support 22.04 LTS.
One workaround; if you just install the packages on the system through the command line, you should be able to apply the patch as well.
Here are the links to the packages:
- Ubuntu x64 - Client installer nxwitness-client-184.108.40.206221-linux_x64-patch.deb
- Ubuntu x64 - Server installer nxwitness-server-220.127.116.11221-linux_x64-patch.deb
Please note, that 22.04 LTS has some quirks in 5.0, so it is not recommended to deploy this in a production environment just yet.
Post is closed for comments.