issues with analytics enabled where-as the server will eventually become unresponsive and reboot after a short time.
Product
ExacqVision Server versions 23.09 & 24.03 & 24.06
Steps to Reproduce
1) install 23.09.9.0 exacqvision server software 2) connect illustra Pro4 20mp IPS20-M12-OIA4 using firmware SS017.06.05.00.008 3) Verify analytics are enabled on the cameras – analyticmetadata, objectdetection, motiondetection 4) verify maximum days to keep events is configured for 30 days 5) verify maximum days to keep bounding box metadata is configured for 1 day 6) Allow the system to run over a period of time and observe D
Expected Results
ExacqVision server and software should continue to run normally as expected.
Actual Results
ExacqVision server and software will continue to consume resources until the system needs to reboot, while displaying acquiring video status on camera live panels and filling up OS drive with eventpi.db file.
When connecting exacqVision Server to Entrapass versions 8.62 & 8.70 or updating Entrapass to these versions, it will stop showing the inputs in exacqVision.
Product
exacqVision Server any version with Kantech Entrapass ver 8.62 & ver 8.70.
Steps to Reproduce
Connect the exacqVision server to Kantech version 8.70 or 8.62.
Expected Results
All Kantech inputs are displayed.
Actual Results
Kantech inputs do not appear
Connections drop leading to loss of inputs within exacqVision.
Solution
The Kantech team has provided a solution with the following steps.
Stop Smartlink
As a precaution, make a backup copy of the following directory: C:\Program Files (x86)\Kantech\Smartlink_CE
Copy the following 2 executables to C:\Program Files (x86)\Kantech\Smartlink_CE\Bin
Users may note that within the exacqVision Client on the System Information page, within the Version Information panel that the analyticpi plugin shows a Status of “Failed – – 1” and the Version column displays “load code – 1”.
<br>
Product
exacqVision Server 20.09.0 and above
<br>
Expected Result
Users expect the analyticpi plugin to show a Version number and Status of ‘OK’.
<br>
Actual Result
Status: “Failed – – 1”
Version: “load code – 1”.
<br>
Solution
The analyticpi plugin is made available for specific analytic appliances and systems, such as the Tyco Analytics Appliance and the Avigilon Analytics Appliance. If there is no such integration the exacqVision Server will not load this plugin, leading to the status shown.
This does not affect cameras with on-board AI analytics as these are supported by the individual camera plugins.
Over many years the number of Illustra camera related plugins had grown. An engineering effort was aimed at consolidating these to make selection of the appropriate plugin easier for users. exacqVision Server 24.03 represents a configuration shift which could affect users that attempt to downgrade the server application to versions earlier than 24.03. This could affect users of Illustra multisensor devices where noted in the article below.
Description
Fresh installations of exacqVision Server 24.03 and above will now leave the illustramulti plugin unchecked for installation at the Choose Components stage of the server software installation. This was previously the preferred selection from the Device Type menu when adding Illustra multisensor cameras when using exacqVision Server 22.06 through 23.09. The exception being the 4-Sensor IFS16-M10-BT03 Flex Multisensor, which uses the Onvif plugin.
Updates to existing installations which already had the illustramulti plugin installed will continue to provide this plugin and not be affected.
Changes to the illustra3 plugin in exacqVision Server 24.03 now permit this plugin to work with Illustra multisensor cameras.
When adding Illustra multisensor devices to exacqVision Server 24.03 and higher, users will now select the illustra3 plugin from the Device Type menu.
This change in Device Type means that users that have already added Illustra multisensor cameras using the illustra3 plugin cannot downgrade to earlier server versions without losing those cameras from their system configurations.
Product
exacqVision Server 22.06 through 23.09 | exacqVision Server 24.03 and later
exacqVision Server versions prior to 22.06 did not offer Illustra multisensor support.
Camera Models:
IPS20-M12-OIA4
IPS32-M13-OIA4
IPS20-M12-OTA4
IPS32-M13-OTA4
IPR20-M12-OIA4
IPR32-M13-OIA4
IFS16-M10-OIA4
IFS10-M10-OIA4
IFS10-M10-OTA4
Illustra IFS16-M10-BT03 not affected, this camera requires the Onvif Device Type.
Notes
It is recommended to backup the server configuration prior to upgrading to exacqVision Server 24.03 or higher.
If a multisensor device was added using illustra3 prior to updating to exacqVision Server 24.03, it must be removed prior to updating.
IMPORTANT: While exacqVision provides some support for changing the plugin of an existing IP camera since exacqVision Server/Client 19.12, there is NO official support for changing the plugin type in this use case, nor is migrating events supported. Users may change plugin types between illustramulti and illustra3 at their own risk.
Email notifications are sending the video attachment but iPhone devices are not able to play back the .mov attachment from the email.
Product
exacqVision Server 23.09.6.0
Steps to Reproduce
The event is triggered and sent via notifypi.
The email is sent and received with an attachment.
When a user clicks on the attachment it will not play back the .mov file.
Expected Results
Users should be able to play back the native attached file.
Actual Results
The attachment will open, but only shows an empty out player with a scroll bar.
Solution
The current release of exacqVision Server 23.09.6.0 uses an old custom code module. This module has been replaced with ffmpeg and we plan to package video as .mp4 as an option in the March 2024 release.
Workaround
Use the VLC application on the mobile device.
Once installed:
From the email received on the device, press and hold the attached file in the email to bring up an iPhone menu.
Axis P3247-LVE “Axis Object Analytics” not passing through the Exacq Mobile 3 app Analytic Rules. If seen please see AES-609. Escalate the case to be added to ticket.
Product
exacqVision Server: 23.06.1.0
exacqVision Web Service: 23.06.2.0
Steps to Reproduce
Set up the camera to allow analytics. Note we do not support line cross for axis cameras.
Once camera is set up navigate to the mobile app and connect to the NVR.
Once Connected navigate to the main menu.
Select Push Notifications
Select Analytics
You should see any analytic that cameras are sending.
Expected Results
We should be able to see the Analytics from the Axis cameras.
Actual Results
Analytics do not show up in the mobile app but do on the NVR’s Server when creating event linking and on the camera settings page.
In order to succeed in the remote client authentication via LDAP, We will need to make sure that we have the following three points.
ExacqVision Server uses an enterprise license and is connected to an AD/LDAP server.
ExacqVison Client is able to reach the Exacq Server via port 22609, and the LDAP via port 636 if LDAP with SSL or 389 if LDAP without SSL.
Active Directory server can reach the Exacq Server and Exacq Client workstation.
The way Kerberos tickets work is that we need all three points able to see and connect to each other, so we need to check these requirements before establishing the Exacq client connection to the Exacq server via the SSO method.
Some drives may show an “offline” status on the hardware tab in ExacqVision Client when Server Version 23.03.1.0 is installed on Q-series models, though data can be read from and written to the drive.
Note: This issue manifests itself cosmetically by appearing as if the drive is offline but has no bearing on functionality for video searching.
Product
ExacqVision Server Version 23.03.1.0
Steps to Reproduce
Update to Server Version 23.03.1.0 from a previous server software version.
Expected Results
Drives should populate hardware tab with a healthy status.
Actual Results
One or more drives may appear as “Offline” on the hardware tab.
Solution
Update to ExacqVision Server 23.03.2.0 if SSA is current and up to date, or alternatively rollback to ExacqVision Server 20.12.8.0 as a workaround.
