The new F2A, A-Series chassis models will have front-loading drive bays. The front-loading bays will resemble the Z-Series, but these drives are not hot-swappable. This new model is a 2U chassis with 2 rows of drive bays in 4 columns for a total of 8 drive bays. Bay 1Bay 2Bay 3Bay 4Bay 5Bay 6Bay 7Bay 8… Continue reading Non-RAID A-Series Systems with LSI HBA Should Have Adjacent Drive Placement
Month: April 2021
Service Status Command Fails on M-Series or Ubuntu 10.04
Symptom: Unable to check status of exacqVision Server. <br> Problem: Running the Terminal command, ‘sudo service edvrserver status’ fails. Introduced with exacqVision Server version 7.6. <br> Solution: Update to exacqVision Server version 9.6.4
PoE Interfaces Created on Non-PoE Server
Symptom: After importing a configuration file, PoE interfaces appear on a machine with no PoE interfaces. <br> Problem: Configuration exports are primarily intended for backing up configuration of the same machine, not for migrating a configuration to another piece of hardware. When importing a configuration file from a PoE capable device (M-series or Una LC),… Continue reading PoE Interfaces Created on Non-PoE Server
Legacy Authentication disabled by default on new installations
Description “Legacy Authentication” refers to the less secure connection methods used prior to our current authentication mode introduced in exacqVision Server/Client version 6.8. This article explains how to enable legacy authentication mode, so newer clients using advanced authentication methods can connect to older server software versions. Product Steps to Reproduce Expected Results Actual Results Solution Workaround… Continue reading Legacy Authentication disabled by default on new installations
Exacqd handle leak
Symptom: It is possible after a very long period for the server to stop functioning, requiring a restart. Problem: There is a slow handle leak in exacqd introduced in server version 9.5.25/9.6.0. This handle is never used, so a slow memory leak is the result. Windows has a limit of 16 million handles. A server… Continue reading Exacqd handle leak
Motion and input trigger events stop working for Illustra cameras
Affected platforms exacqVision Server 5.10 or later with Illustra cameras using the Illustra3 plugin <br> Symptom When exacqVision reconnects to an Illustra camera during a stream restart, the socket connection communicating motion events and input trigger events could fail. If this happens, exacqVision will stop processing motion events and input trigger events.This is caused by… Continue reading Motion and input trigger events stop working for Illustra cameras
Server Email Notifications Broken
Symptom: Server fails to send email notifications. Problem: This issue was introduced with trunk 9.7.15, server will fail to send notification. Server logs may show the following: 10/8/2018 9:41:30 AM NotifyPI Error Failed to execute curl smtp operation using server gmail. (Profile Description: Gmail Profile) 10/8/2018 9:41:30 AM NotifyPI Error Failed to send notification using profile… Continue reading Server Email Notifications Broken
Duplicate cameras returned in the camera scan results
Affected platforms exacqVision Server 7.2.0 <br> Symptom If multiple NICs are installed on the exacqVision server and one or more NICs are disconnected from the network, the camera scan may list the same camera more than once in the results. <br> Workaround Connect the NIC in the disconnected state or disable the disconnected NIC. <br>… Continue reading Duplicate cameras returned in the camera scan results
HTTPS for Illustra Essentials / Dahua cameras
To set the HTTPS mode for Illustra Essentials and any Dahua OEM cameras: Go to camera web pageEnable the HTTPS option in the Network/Connection section The camera will auto generate a self-signed certificate so that exacqVision may connect with HTTPS. Note that if the camera is in HTTPS mode and the camera’s IP address is changed,… Continue reading HTTPS for Illustra Essentials / Dahua cameras
Mobile OEM Toolkit produces invalid iOS packages when the OEM does not include support for Push Notifications
Affected platforms Mobile OEM Toolkit v1.3.1.8525 <br> Symptom If an OEM is attempting to create an iOS package using the Mobile OEM Toolkit v1.3.1.85257 and does not have their iOS provisioning profile set up for Push Notifications, the OEM will be unable to submit the application to iTunes Connect.This script error will cause the web… Continue reading Mobile OEM Toolkit produces invalid iOS packages when the OEM does not include support for Push Notifications