When iVMD analytic support was added in exacqVision Server version 20.03.0, it caused motion data to be ignored from older or non-iVMD camera models. Resulting in video not being recorded when using motion-based recording.
<br>
Use free-run recording or downgrade to exacqVision Server version 19.09
<br>
Same for resolution 10pt
<br>
exacqVision Server 20.03.0 thru 20.03.9
<br>
exacqVision Server 20.03.10
LDAP users (or LDAP administrators) have all the tools needed to administer their LDAP account credentials. We do not provide (or need to or want to provide) any tools to administer LDAP credentials.
This evServer fix is a guard to block this setting in the xml. If config is sent to the server containing this value, it is removed. No evAPI changes are needed or expected.
<br>
v8.6.0
<br>
All
<br>
<br>
<br>
Core crash on Start system when user changes their own username. This was seen in a unit test. It has not been seen from an evClient.
<br>
8.6.0
<br>
All
<br>
<br>
Expected the username to be changed.
<br>
Exacq service crashed
<br>
Downgrade
<br>
This article applies only to the stand alone RTSP Server Integration not the built-in RTSP support available in exacqVision Server version 19.12 and higher.
The original stand-alone RTSP Server has the exacqVision Server listed as one of its dependencies. This causes scripts to fail and has been observed to prevent the following:
<br>
To remove exacqVision Server dependency from RTSP Server integration. (Windows Only)
<br>
<br>
<br>
Large Kantech integration was failing to get relay events from all zones.
<br>
None
<br>
Kantechpi polls devices by identifier and had a limit of 1600 devices. This is an arbitrary limit and has now been doubled to support 3200 devices.
<br>
exacqVision Server 19.09 and lower
<br>
exacqVision Server 19.12
Enterprise Manager uses a package called Solr which in turn uses Java. Currently, we do not offer an update path for Solr that will update the Java version. The following instructions can be used if the need arises were Java needs to be updated.
Windows 64-bit
jre-8u231-windows-x64.exe /s INSTALLDIR="C:\Program Files\exacqVision\EnterpriseManager\apache_solr\java" STATIC=1
jre-8u231-windows-i586.exe /s INSTALLDIR="C:\exacqVisionEM\apache_solr\java" STATIC=1
sudo tar -zxf jre-linux-*.tar.gz -C /usr/local/exacq/esm/apache_solr
From the client’s “Synchronize with ESM” page, using an LDAP username and password results in ‘Check your URL’ error. This happens even though the LDAP domain and group associations (with ESM access) is correctly configured on ESM.
<br>
4.8.2
<br>
All
<br>
<br>
The client shows ‘Connected’ and downloads the server list from ESM.
<br>
The client shows ‘Check your URL’ error message dialog box.
<br>
The work around is to attempt the same action twice from the client. The client does not enable the ‘Apply’ button unless one of the parameters changes. So in order to attempt the same action again, the user will have to modify one of the parameters and revert it back.
Another option is to login to ESM using the same credentials and then attempt to do the sync action from client.
A NotifyPI enhancement was released with 8.4 which added the ability to specify ‘when’ to send an email: ‘Alarm Starts’, ‘Alarm Ends’ or ‘Alarm Starts and Ends’). However, the ‘Alarm Ends’ selection was failing to send the email when the trigger event (alarm) duration was shorter than the ‘Send Rate Limit’.
If the event duration was longer than ‘Send Rate Limit’, the email was sent as expected.
<br>
8.4
<br>
All
<br>
* Configure a Notifications email server
* Configure a Notifications email profile
– Alarm Ends
– Send Rate Limit 10
* Configure a new ‘Event Linking’ entry
– Soft Trigger
– – new trigger
– Action Type: Notify
– Action Target: the email profile
* Set, then within 10 seconds, clear the Soft Trigger
<br>
Expect to receive an email
<br>
No email was sent
<br>
* Create an event Source Group
– Add the Soft Trigger
– Select ‘Any source’
– Select ‘When not alarmed’
– Modify the Notification email profile ‘When’ to ‘Alarm Starts’
The Enterprise Manager browser interface will display red banners indicating that data stopped importing, data stopped rolling off, and sendmail has stopped when the OS time on the client/browser workstation doesn’t match the time on the EM server. Below are screen shots illustrating the issue.
<br>
Ensure that the EM server and client workstation are syncing to a time server or manually adjust client workstation time to match EM server time
Cameras will not record on motion due to a firmware issue. Currently there is a ticket that needs to be re opened and worked on with Illustra.
Motion will not work on JPEG/H264/H265 if the camera was originally configured with the Enhanced Security Mode enabled by default.
<br>
Default the camera and log into the GUI of the camera and select Standard security mode.
<br>
All