How To Configure The Exacqvision Client To Prompt For Credentials Whenever Launched
Description
The “Always prompt for credentials” option requires you to enter a username and password every time you start the exacqVision client. Product exacqVision Client
Solution
Select the Always prompt for credentials for the server(s) on the Add Systems Page.See the Manually adding a system section of the exacqVision Client User Manual for additional information.
When changing the windows for the HikVision cameras to the corridor mode, it will not trigger the motion on the bottom because it’s not supported by Exacq yet.
This feature will be supported on the ExacqVision Server version 22.03.
If you have an LDAP group that is listed on Exacq and set this group as the primary group for a specific user, this user will not be able to log in on Exacq Software.
The workaround for this issue:
Setting another group as an admin for this user.
Adding another group in which that user is a member.
ONVIF PTZ camera with two streams may display as two different cameras even if “Manage all streams as quality” is checked. This is because the XML is reporting the secondary context as being an independent PTZ which is something generally used for fisheyes where PTZing one stream doesn’t PTZ the other streams.
Beginning with exacqVision Server 9.8.x, enabling or disabling exacqVision core dumps may be performed as follows:
To Enable:
Open Terminal
sudo touch /usr/local/exacq/server/enabledumps
There is no need to restart the service for any reason
Within 1 second, SysmgmtPI will log SYSMGMTPI: enabled core dumps
If the server crashes, you may grab the dump file /usr/local/exacq/server/logs/core_dump.gz
(Prior to 19.03.x, the location was /usr/local/exacq/server/blob/core_dump.gz)
This file is overwritten with each new crash.
To Disable:
Open Terminal
sudo rm /usr/local/exacq/server/enabledumps
There is no need to restart the service for any reason
Within 1 second, SysmgmtPI will log SYSMGMTPI: disabled core dumps
NOTES
Core dump files in the blob folder caused the client to stall when attempting to export settings with map graphics (refer to #d17724 & #3496). Server >= 9.9.16 relocates core dump files to the logs folder (refer to #d17742). Now, it’s consistent with Windows, which is easier to remember anyway.
exacqVision Virtual Appliance and Ubuntu 10.04 are only supported starting with 19.05.17 trunk server.
M-Series does not support Core Dumps.
WARNING – If the OS partition is low on space (< 100 MB free), LogPI will probably delete all core dump files before you have a chance to use them, so recommended that you first ensure there’s multiple GB free on OS partition first, just to be safe.
If you need to enable core dumps on systems running older server or OS versions, you should be able to:
Get a copy of both SVN/edvrserver/core/scripts/config_core_pattern.sh and coredump.sh
Deposit both in server’s scripts subfolder.
Manually run /usr/local/exacq/server/scripts/config_core_pattern.sh enable to enable, or specify disable, as necessary.
Subsequent crashes should generate core dump files in server’s logs subfolder.
When exacqVision Server connects to an IP camera, it normally configures the camera with the IP address of an NTP time server, so that the camera will automatically keep time synchronized. Normally, cameras will then enable sync.
However, some ONVIF cameras, such as Honeywell H3W2GR1 or Tyco Security Products Essential 4, do not automatically enable sync. As a result, video timestamps may inadvertently drift.
<br>
Workaround
Check the camera’s web interface, to verify whether NTP sync has been enabled, and if not, to manually enable it.
<br>
Resolution
Beginning with 20.03.118, exacqVision Server now enables NTP sync as a precaution.
To install a replacement drive in an exacqVision system with an LSI 3ware RAID array, complete the following steps. <br>
NOTE: This procedure requires a Phillips-head screwdriver and approximately 20 minutes to complete. <br>
If applicable, close the exacqVision Client software, log out of the operating system user account, and log in as an administrator. To log out in Windows, click Start and then Log Off; to log out in Linux, click the power icon and then Yes. Then select the administrator account and enter the admin password to log in. <br>
Exit exacqVision Client and open 3DM2 so that you can verify the drive that needs to be replaced. To open 3DM2 In Windows, click Start/Programs/3Ware/Connect to 3DM2; to open 3DM2 in Linux, select the Mozilla Firefox icon in the menu bar. <br>
Select Continue to this Website. <br>
Select Administrator from the Login drop-down list and type admin256 as the password. <br>
Select Maintenance from the Management menu. <br>
Verify the drive to be replaced. Note that the drive numbering begins with zero; thus, if the page indicates that drive 3 is not present, replace the fourth physical drive. <br>
Remove the drive to be replaced. Unlock the drive bay containing the drive by sliding the latch to release the caddy. It could look like either of the following examples. <br>
Remove the drive by sliding it toward you. <br>
Use the screwdriver to remove the four screws from the sides or bottom of the drive caddy.
<br>
Remove the drive from the caddy and place the new drive in the caddy. Secure the drive to the caddy using the screws removed earlier.
Insert the new drive and caddy into the system and lock the latch down. The drive will provide some resistance when the drive reaches the back of the slot. DO NOT FORCE THE DRIVE INTO THE SLOT.
Verify that the power light (white or green) has been activated for that drive slot.
Open 3DM2 as instructed previously.
NOTE: If using Internet Explorer, you might need to enable Compatibility Mode by clicking the broken page icon: <br>
Verify that the drive array is rebuilding. <br>
Close the browser and open exacqVision Client. <br>