Categories
Video Library Knowledge Support Demo Release Notes Support exacqVision Enterprise Other exacqVision Client exacqVision Server Categories exacqVision Webservice Products exacqVision Integrations

2023-03 March Quarterly Release Training

ExacqVision Server

Bug Fix – Fixed PTZ preset administration for custom users to create presets for analog cameras (AESW-4357)

Bug Fix – Fixed monitoring RAID background tasks, like consistency checks and background initialization (AESW-4387)

Bug Fix – Fixed reporting incorrect RAM, was displaying MB instead of GB (AESW-2498)

Bug Fix – actipi – Reduce metadata channel reconnects for cameras with S3L chips, this caused cameras to stop recording after a while (AESW-4327)

Bug Fix – illustramultipi – Fixed ability to enable motion zones per sensor, accommodated changed to camera firmware (AESW-4456)

Bug Fix – illustramultipi – Fixed direct input/output triggers, fixed output numbering that was preventing trigger status from updating (AESW-3474)

Bug Fix – onvifnvcpi – Fixed motion issues with AVCostar-Contera (AESW-4464)

Bug Fix – onvifnvcpi – Increased maximum SOAP read size to accommodate Clinton encoders, see Enhancements (AESW-3474)

Enhancement – Modified all emissions from eventpi and notifypi to use separated IDs rather than compressed IDs, fixed in part, this is an enhancement to affect problems with searching the event database with very large amounts of records (AESW-3333)

Enhancement – Added camera detection of several Illustra Standard cameras to be discovered as Illustra3
(AESW-1668)

Enhancement – axispi – Added support for color metadata (AESW-1725)
Only vehicle color is currently provided by Axis

Enhancement – illustra3, illustramultipi – Added support for “final color” (AESW-2850, AESW-2844)

Enhancement – samsungpi – Added support for Area Zoom (AESW-4003)

Enhancement – onvifnvcpi – Added support for Advidia cameras (AESW-3521)

Enhancement – onvifnvcpi – Added support for Clinton Electronics encoder (AESW-2489)

ExacqVision Client

Bug Fix – Don’t reorder keywords when building conditions panel tree
Ensures ‘Upper Clothing Color’ is listed above ‘Lower Clothing Color’ in Filters (AESW-4502)

Bug Fix – Allow live analytic keyword colors to be processed before bounding boxes (AESW-4458)

Bug Fix – Fixed an issue with display of multiple trigger events (AESW-3861)

Bug Fix – Fixed issue saving image from Live view where OSD background color was removed from the saved image (AESW-4277)

Enhancement – Support for “final color”, choose search type based on “final color” (AESW-3345)

ExacqVision Web Service

Bug Fix – Updated nvrg version to fix group type retrieval (AESW-3340)

Bug Fix – Updated nvrg version to fix a soft trigger bottleneck (AESW-3816)

Enhancement – Disabled search playback in browser client until buffer threshold is reached (AESW-3622)

Enhancement – Enabled ability to detect an invalid session in browser client (AESW-3621)

ExacqVision Enterprise Manager

Bug Fix – Removed architecture change logic from NSIS (AESW-491)

Bug Fix – Support added for Windows authentication login for MS-SQL (AESW-3378)

Illustra

Enhancement – New Pro Gen4 6.0 firmware adds new Object Classes
Trolley, Backpack, Handbag, Suitcase

Enhancement – Improved face detection

Enhancement – “Final color” sent after object tracked leaves FOV

Categories
Plugin Exclude from Global Search Log Level Warning exacqVision Enterprise Logs Other

The DELETE statement conflicted with the REFERENCE constraint “auditlogger_auditlog_user_id_fbf03342_fk_organization_enterpriseuser_id”. The conflict occurred in database “NA”, table “dbo.auditlogger_auditlog

The DELETE statement conflicted with the REFERENCE constraint “auditlogger_auditlog_user_id_fbf03342_fk_organization_enterpriseuser_id”. The conflict occurred in database “NA”, table “dbo.auditlogger_auditlog

Description

when the Datarolloff service is failing to start you may see this error or a similar error in the datarolloff log file. There is a foreign key constraint that is failing to delete which in turns stops the service from running, you must delete this constraint manually via the Database

Notes

You must delete the key constraint from the database

Categories
Knowledge Support Documentation Support exacqVision Enterprise Products

Starting ElasticSearch service with a service account

Description

In some production environments, service accounts are used to run Enterprise Manager services. In order for the ElasticSearch to run it creates a tmp directory from the account it was installed under, this can cause the service to not run if you try starting the service as a different user. there are two ways you can get this service to run, the first way is to install Enterprise Manager as the service account by either logging in and installing the exe or right clicking the exe and selecting ” run as different user”. Another way to get this service to run is to go into the C:\Program Files\exacqVision\EnterpriseManager\Elasticsearch\bin , you must run elasticsearch-service-enterprise-manager.bat go to java options and change the user from this line

Djava.io.tmpdir=C:\Users\UserAccount\AppData\Local\Temp\elasticsearch

hit apply and go to services, right click the elasticsearch service, select log on and input the user account you wanted to start.

Product
Enterprise Manager

Categories
exacqVision Enterprise

Corrupted Failover group causing EM to drop servers

Issue

When running EM version 22.09 or lower if you see your servers constantly connecting and then disconnecting, please check the EM logs specifically the importer log you should find something similar to this log..

[02/Dec/2022 09:52:52] WARNING [MainProcess:6016,Thread-1:8532,importer.py:292] FailoverProcess died unexpectedly
[02/Dec/2022 09:52:52] INFO [MainProcess:6016,Thread-1:8532,importer.py:575] Shutting down brain.
[02/Dec/2022 09:52:52] INFO [MainProcess:6016,Thread-1:8532,importer.py:444] Cleaning up importer resources
[02/Dec/2022 09:52:52] INFO [MainProcess:6016,Thread-1:8532,importer.py:478] Allowing sub-processes to shutdown’

The failover process is dying constantly which is killing the importer, if you check your failover groups the issue would show as “data restore pending” if you aren’t able to abandon the data please delete the failover group via EM shell.

Product

  • exacqVision Enterprise Manager version 22.09 or lower

Solution

Abandon data from corrupted failover group or delete failover group via EM shell

Categories
Knowledge Support exacqVision Enterprise Support Products

EM Editing the Group ROOT Synchronization Conflict Resolution Option

Knowledge Base Article Template

Description 

EM does not allow for the Root Group to select the option of Synchronization Conflict Resolution for Automatically Resolve Conflicts and remove Unauthorized Users as seen below.

Note: That even on a New Group- that the Group Name Needs to be provided and the Synchronization Conflict Resolution is able to be Applied.

Product 

EM All Versions.

Solution

If this is seen on a Group with a Users in that Group of ROOT- then in order to select the Synchronization Conflict Resolution with Auto Resolve conflicts and remove unauthorized Users- you must create a New Group other than ROOT.

Categories
Video Library Knowledge Support Demo Support exacqVision Enterprise exacqVision Client exacqVision Server exacqVision Mobile Categories exacqVision Webservice exacqVision Hardware Products

2022-12 September Quarterly Release Training


ExacqVision Server

Bug Fix – Fixed issue preventing archiving of analog video to Cloud Drive

Bug Fix – Motion Detection not working on Holis cameras

Bug Fix – Corrected issue setting NTP server for illustra3pi and illustramultipi camera plugins

Bug Fix – Fixed issue with missing frames from PTZ cameras causing image tearing in recorded video

Bug Fix – Fixed issue with core hanging when attempting to stop server service

Bug Fix – Addressed issue with high memory usage

Bug Fix – Fixed logging issue with LDAP with potential to cause crash

Bug Fix – Corrected reporting issue for object classification from all sensors when using illustramultipi camera plugin

Bug Fix – Fixed issue reading blur and tamper detection from individual sensors using illustramultipi plugin

Bug Fix – Fixed handling of metadata/motion timeouts on Samsung/Hanwha/Illustra

Enhancement – Support added for Axis’ new Time API calls

Enhancement – Support added for Arecont Contera series

Enhancement – Support added for Protego devices

Enhancement – Added support for ACTi Z94

Enhancement – Added JSON support for additional Dahua models

Enhancement – evAPI changes to support sustained soft triggers

Enhancement – Phase 1 of improved support with Illustra Enhanced Security Mode… handle metadata with HTTPS

ExacqVision Client

Bug Fix – Corrected issues with keyword tree resetting scroll position

Bug Fix – Fixed issue saving edits to Event Monitoring profile when Source name begins with the system name

Bug Fix – Prevent client crash when clicking Show Keywords checkbox

Bug Fix – Fixed issue where event metadata fails to be included for first selected device with some Access Control integrations

Bug Fix – Fixed issue where client did not display keywords when more than 20 values were returned

Bug Fix – Fixed icon display on Storage > Hardware tab device tree

Enhancement – Hide metadata keywords panel by default

Enhancement – Hide conditions panel when not needed

Enhancement – Cloud Drive integration to only list cameras from systems in the system list

Enhancement – Improvements to reduce false positives based on color filtering for people and vehicles

ExacqVision Web Service

Bug Fix – Fixed potential gateway deadlock when closing streams

ExacqVision Mobile

Feature – Update SDK for Android 12 support

Feature – New Scrollable timeline for search

ExacqVision Enterprise Manager

Bug Fix – Fixed infinite camera permissions from bad user roles

Exacq Hardware

2nd Generation of G-Series PoE system replacing 1st Gen

Categories
Knowledge Support Support exacqVision Enterprise Categories

Unexpected Results When Updating Groups or Users in exacqVision Enterprise Manager

Description 

Customer was getting odd results when trying to edit the name of either a group or username in EM.

Product 

  • exacqVision Enterprise Manager 21.06
  • exacqVision Enterprise Manager 22.09

Steps to Reproduce 

From the EM dashboard access either Users or GroupsSelect an existing user or group Click the pencil icon to edit Change the name of the group or change either the first or last name of a userClick Apply

Expected Results 

The change is saved, and you are returned to either the group or users page

Actual Results 

The save fails and returns the following

Solution

It was discovered that REST POST and PUT operations were being blocked by firewall and once exceptions were made EM began working normally.

Categories
Support exacqVision Enterprise

Using NT authentication when connecting to MSSQL database

ExacqVision currently doesn’t support NT authentication when validating credentials to a MSSQL database (Enterprise Manager), we require to use SQL server authentication. A feature enhancement ticket has been submitted for NT authentication.

Categories
exacqVision Enterprise

Invalid column error after updating Enterprise Manager using MSSQL database from 21.12 or lower to 22.06 or higher

Description 

If you are using mssql database with EM and updating from 21.12 or lower to 22.06 you will get the crying stickman when trying to log into the web gui. When checking the webservice logs you will get invalid column errors such as..

][ODBC Driver 17 for SQL Server][SQL Server]Invalid column name ‘lastSaveOrUpdate’. (207) (SQLExecDirectW);

Product 

EM version 21.12 or lower

EM version 22.06 or higher

Steps to Reproduce 

Download Enterprise Manager 22.06 (or higher) installer package

Install the package

Try to reach EM via web Gui

Log in using known credentials

Expected Results 

Logs in successfully and able to see configuration

Actual Results 

You will get the crying stickman page

Solution

WORKAROUND: AES 2868
Which contains the workaround and backpatch

Categories
exacqVision Enterprise

The failover is not working on the EM, and the protected server is stuck on Failed over however, the spare server is still on standby mode.

Issue

The failover is not working on the EM, and the protected server is stuck on Failed over however, the spare server is still on standby mode.

When checking the EM logs, it shows.

[23/Aug/2022 15:23:17] INFO<br>[FailoverProcess:11068,MainThread:14776,transitions.py:326]<br>Config contents not found for server id 2

Solution

This issue has been fixed on Exacq EM version 22.09.2.0 or newer.