*There appears to have been a slight bug in the presentation recording where the video recording did not capture the videos being played on the screen. The links below will provide access to the PowerPoint file and individual demonstration videos.
Bug Fix – Removed limit of 256 devices displayed for Access Control plugins, only visible when using Access Control with Associations or Maps
Bug Fix – Fixed issue with Illustra3 and Illustramultipi that could cause cameras to be stuck in a Connecting state after reboot
Bug Fix – Fixed issue where Edgestor was not backfilling data from Illustra3pi cameras due to Edgestor crash, leaving gaps on server recordings
Bug Fix – Fixed quality setting for Illustramultipi
Bug Fix – Fixed issue with trigger inputs/alarm outputs for Illustramultipi
Bug Fix – Added retry logic on API errors for napcopi, Napco uses IIS which has a recycle time that caused authentication to fail, fix adds retry logic if error received
Bug Fix – Fixed issue causing credentials for RTSP Server not to be updated properly
Bug Fix – Corrected issue where Date/Time page was greyed out on Win7 machines
Bug Fix – Fixed issue where Dynacolor devices may repeatedly reset after user presses Reset button on PoE port in Client.
Bug Fix – Fixed viewing Live Analytics for Flex3 cameras
Bug Fix – Fixed issue where closing video stream did not close metadata stream from Illustra3pi
Bug Fix – Fixed propagating motion alarms on disabled context streams on Illustra3pi
Bug Fix – Fixed setting transport and re-reading URL for continuous metadata from Illustra3pi
Bug Fix – For Illustra3pi and Illustramultipi, use friendly name for analytics that provide bounding box
Enhancement – Added motion support for March Network cameras using Onvif
Enhancement – Support for Redvision RVX2 added to Onvif plugin
Enhancement – Support for Sunell with transport RTSP added for Onvif
Enhancement – Improvements made for Last Motion event on context streams
Enhancement – Adjustments made to parsing Audio Output name for Illustramultipi
Enhancement – Removed eDVR and XDVAPI license handling
Enhancement – §Homogenized analytic values for Axis, Samsung/Hanwha, Tycodlpi; Presents “Person” instead of “Human”, “Bicycle” instead of “Bike”
Enhancement – Added support for Axis’ new metadata style used in their 11.0 firmware
Feature – Added support for vehicle and clothing color provided by Illustra3pi and Illustramultipi cameras
ExacqVision Client
Bug Fix – Reset search item flags when sending new search requests, fixes issue when Search stops working if server connection lost mid-search
Bug Fix – Don’t send scrub request if waiting for summary response
Bug Fix – Prevent potential crash on Association config page if a camera with associations was deleted
Bug Fix – Initialize Digital PTZ settings to Client settings when plugin does not send them, related to changes made for body worn cameras
Bug Fix – Prevent toast messages for streaming BWCs on system disconnect
Bug Fix – Reset camera connection status on system disconnect
Bug Fix – Prevent security integration sources from being displayed twice in bookmark editing tree
Bug Fix – Fixed potential crash when adding new IP serial port and config update occurs
Bug Fix – Prevent client crash with double-clicking on grid divider in List View
Bug Fix – Prevent client crash on OSX when clicking calendar controls
Bug Fix – Fixed issue with export failure if config page options in settings file
Enhancement – Prevent some analytic search filters that didn’t make sense, non-sensical combinations of operator logic
Enhancement – Don’t request event data in response to Show Conditions panel, caused Search to stop working when connection to Server was lost mid-search
Instructions for how to use PSchange tool in order to manipulate files located on a remote archive server. This guide is for running the tool on a windows OS although it can still manipulate files stored on a linux archive server.
Product
PSchange.exe
Steps
Gather current camera ID by right clicking on the live video and clicking properties. Make a note of these as they will be used later.
Launch Exacq as Administrator on the server where the camera is located.
Change the plugin to the one you want to use.
Note: Exacq will now try to convert the existing local video to the new device ID. This may take some time so be patient and don’t force close the exacq client. You can check it is still working in the background by opening task manager and checking the CPU percentage for the “edvrclient” program. If it is above 0% it is still working.
Open powershell as administrator.
Map your remote drive to a drive letter not in use.
Commands are: net use P: \\NETWORK_PATH\
This path should include everything up until but not including the date folders that are created during the archiving process. E.g. if the path is \\192.168.1.1\StorageFolder30Days\2022\05\12\3\ then your command should look like this: net use P: \\192.168.1.1\StorageFolder30Days\
Use cd to change directory to where the pschange.exe program is located.
Pschange arguments: -v verbose -d dry run -o Old camera ID -n New camera ID -l (Lowecase L) Include all local Drives -p Include the path specified in the scan. Note:it may take pschange a couple of seconds before it gets started. Be patient.
Pschange should list all files it finds and will list the new names it will give them, giving you a total files number once it finishes.
If you are happy to proceed enter the pschange command without the dryrun argument. E.g.
Windows 7/10: C:\Users\%username%\AppData\Roaming\edvrclient\edvrclient.xml Windows XP: C:\Documents and Settings\%username%\edvrclient.xml Ubuntu: ~/.edvrclient.dir/edvrclient.xml Mac: /Users/%username%/Library/Application Support/edvrclient/edvrclient.xml
Replace %username% with the user account name.
<br>
Each operating system user account maintains separate settings for its exacqVision Client. The settings stored include usernames, passwords, and network addresses required for exacqVision Client to access exacqVision Servers, as well as settings configured on the Client Setup page and memory of the position and live mode state of multiple Client instances. Passwords are encrypted within the file.
<br>
The file is stored in an operating system user-specific location. The user-specific directory is specified by an environment variable. The following environment variables are searched in order to determine the user specific directory: HOME, HOMEDRIVE/HOMEPATH, USERPROFILE, application directory. On Windows 7 and later, this directory is C:\Users\%username%. If you experience trouble when saving Client settings, ensure that a valid directory is specified by one of these environment variables. You can check this by running Start->Settings->Control Panel->System, selecting the Advanced tab, and then clicking the environment variable button. You must restart the exacqVision Client after making any changes.
<br>
It is possible to specify a settings file independent from the operating system user account by using the -I command line parameter. Examples where this might be useful are:
A regional manager might have several sites to monitor. They could create a Client settings file to connect to all the Servers in Indiana and a second settings file to connect to all the Servers in Ohio. Then, when looking for something in Indiana, the connection process would be faster and there would be fewer servers and cameras to navigate through in the tree.
A user with Admin permission on several exacqVision Servers might want to connect to them from a Client workstation that does not normally have Admin permission on the Servers. Instead of changing the login credentials through the Add Systems page in the Client, the user could store the settings file on a USB Flash drive and start the exacqVision Client on the workstation pointing to the USB drive’s settings file.
<br>
To add this command line parameter into a shortcut, create a shortcut to the exacqVision Client, right-click the shortcut, select Properties, and edit the target field as follows:
Any settings changed during this Client session are stored to the XML file specified on the command line. If the file does not exist at Client startup, it is created automatically. If a path is not specified with the filename, it will be assumed to be in the same directory as the exacqVision Client application
<br>
Linux: For Linux the file is located in the Start>places>home folder. Click view at the top and select Show Hidden Files. Open the .edvrclient.dir folder to locate the edvrclient.xml file
<br>
Mac: In Finder, select Go and then Go To Folder. Type /Users/%username%/Library/Application Support/edvrclient/
IMPORTANT For Instructions on current versions of exacqVision Enterprise Manager versions 22.06 or higher see Knowledge Base Article #12804
This document details how to enable HTTPS connections to exacqVision Enterprise System Manager on versions 22.03 or lower.
For a trusted certificate, it is recommended that you purchase a third-party intermediate certificate from one of many online providers. If you are using a third-party certificate you may skip ahead to the section titled, “Obtaining a Third-Party Certificate”.
These steps will detail how to create a self-signed certificate, but be aware that web browsers will warn users that the certificate is untrusted if you are using a self-signed certificate or one from a private/internal certificate authority.
CREATING A SELF-SIGNED SSL CERTIFICATE
Windows
1) Click on the Windows Start button and type ‘CMD’. Right-click on the CMD icon and choose ‘Run as Administrator’.
2) Set the environmental variable that will be used by OpenSSL later by typing:
set OPENSSL_CONF=C:\Program Files\exacqVision\EnterpriseManager\apache_solr\apache2\conf\openssl.cnf
Press Enter.
3) Change your working directory by typing:
cd "C:\Program Files\exacqVision\EnterpriseManager\apache_solr\apache2\bin"
You will be prompted to enter a PEM pass phrase. Enter anything you like but you will need to re-enter this in the following steps.
PEM pass phrase:
5) You will be prompted with several questions for the certificate, answer these according to your needs. COMMON NAME should be the IP address or FQDN that users will access to reach the ESM web site (ex. www.domain.com or esmserver.domain.com).
You will be prompted with a series of questions. – Use data specific to your site. – Items can be left blank with the exception of Common Name – Common Name (e.g. server FQDN or YOUR name) should be the IP address of EM Server
Verify the md5 hashes match, if they DO NOT then see the troubleshooting section below before proceeding.
Step 3 Edit Apache Configuration
cd /usr/local/exacq/esm/apache_solr/apache2/conf/extra
sudo gedit httpd-ssl.conf
Make the following changes, save the file and then close gedit.
Step 4 Restart the enterprise-webservice
sudo service enterprise-webservice stop
sudo service enterprise-webservice start
<br>
OBTAINING A THIRD-PARTY CERTIFICATE
If you are planning to acquire a third-party certificate from a trusted provider, you may need to provide them with a Certificate Signing Request (CSR) file.
Enter all the fields click on the ‘Submit’ button to download the ZIP file. Inside this ZIP file is the CSR file and RSA key to give to your certificate provider.
If you purchased a chained certificate, be sure to download the appropriate intermediate bundle.
Once you have downloaded the files from your provider:
Rename the .crt file to ‘server.crt’.
Rename the .key file to ‘server.key’.
If you have a chained certificate, rename the chain file to ‘server-ca.crt’.
Place the renamed files from your Certificate Authority (CA) into the following directory:
When purchasing an SSL certificate, many providers offer an Intermediate Bundle, or additional certificates that must be present to link your certificate to a root certification authority. Usually the provider will have documentation on how to accomplish this with Apache, but it is a good idea to ask them before or during the purchasing process. Exacq is not responsible for making your certificates capable of working with Apache.
It is possible to combine all the intermediate certificates that a provider may give you into one file. Consult your provider for more information.
<br>
ENABLING SSL FOR HTTPS CONNECTIONS
Be sure that you have followed the steps above to place the certificate files necessary for either a third-party certificate or a self-signed certificate into the correct directory before continuing with the following steps.
Windows
1) Click on the Windows Start menu and find the Windows Notepad program. Right-click on this and choose to ‘Run as Administrator’. If you do not run Notepad as an administrator you will be unable to save your changes.
2) With Notepad open, click on the ‘File’ menu and choose ‘Open’ or press CTRL-O on the keyboard.
In the Open browser, change the drop-down menu for File Type from ‘Text Documents (*.txt)’ to ‘All Files (*.*)’.
Use the Open browser to open the C:\Program Files\exacqVision\EnterpriseManager\apache_solr\apache2\conf directory and highlight the file titled ‘httpd.conf’ then click ‘Open’.
3) Find the following line:
LoadModule ssl_module modules/mod_ssl.so
Remove any pound (#) sign in front of this line if there is one.
Now, find the following line:
Include conf/extra/httpd-ssl.conf
Remove any pound (#) sign in front of this line if there is one.
Save the file.
4) Still using Notepad, open the file titled ‘httpd-ssl.conf’ located in C:\Program Files\exacqVision\EnterpriseManager\apache_solr\apache2\conf\extra
Find the following line:
ServerName www.example.com:443
Change the ‘www.example.com’ portion of this line to ‘localhost’.
Save the file and close the window.
5) Restart the solrApache service in Windows services (services.msc).
Linux
1) Open a Terminal prompt.
2) Change your working directory by typing:
cd /usr/local/exacq/esm/apache_solr/apache2/conf
Press Enter.
3) You may use any editor you feel comfortable with, such as vi or nano, but if your are more inclined to using a graphical interface you may use a program called ‘gedit’ to make the following changes.
In the Terminal, type:
sudo gedit httpd.conf
Press Enter.
4) Find the following line:
LoadModule ssl_module modules/mod_ssl.so
Remove any pound (#) sign in front of the line if there is one.
Now, find the following line:
Include conf/extra/httpd-ssl.conf
Remove any pound (#) sign in front of the line if there is one.
Save the file and close the ‘gedit’ editor window to return to the Terminal prompt.
5) In the Terminal, type:
sudo gedit extra/httpd-ssl.conf
Press Enter.
Find the following line:
ServerName www.example.com:443
Change the ‘www.example.com’ portion of this line to ‘localhost’.
Save the file and close the window to return to the Terminal prompt.
6) Restart the service in the Terminal by typing:
sudo service ESMWebservice restart
<br>
FORCED REDIRECT FROM HTTP TO HTTPS
If you want to force users who try to access the site on port 80, using HTTP, to use the secure HTTPS connection you will need to enable a redirection.
Windows
1) Click on the Windows Start menu and find the Windows Notepad program. Right-click on this and choose to ‘Run as Administrator’. If you do not run Notepad as an administrator you will be unable to save your changes.
2) With Notepad open, click on the ‘File’ menu and choose ‘Open’ or press CTRL-O on the keyboard.
In the Open browser, change the drop-down menu for File Type from ‘Text Documents (*.txt)’ to ‘All Files (*.*)’.
Use the Open browser to open the C:\Program Files\exacqVision\EnterpriseManager\apache_solr\apache2\conf directory and highlight the file titled ‘httpd.conf’ then click ‘Open’.
Remove the pound (#) signs in front of these two lines.
Save the file.
4) Restart the solrApache service in Windows services (services.msc).
Linux
1) You may use any editor you feel comfortable with, such as vi or nano, but if your are more inclined to using a graphical interface you may use a program called ‘gedit’ to make the following changes.
Remove the pound (#) signs in front of these two lines.
Save the file and close the ‘gedit’ window to return to the Terminal prompt.
3) Restart the service in Terminal by typing:
sudo service ESMWebservice restart or sudo service enterprise-webservice restart
<br>
TROUBLESHOOTING
1) Some versions of Internet Explorer do not easily work with services running locally or may display pages incorrectly. If this happens, try clearing the browser’s cache by pressing CTRL-F5 on the keyboard. If the problem is persistent try installing another web browser, such as Chrome.
2) If the solrApache service fails to start after configuring it for SSL:
[Wed Mar 04 09:08:54.512004 2017] [ssl:emerg] [pid 19116] AH02565: Certificate and private key www.example.com:443:0 from server.crt and server.key do not match AH00016: Configuration Failed
c) If you see this log entry, complete the following steps:
1) Change your working directory to the location of openssl.exe
Windows (CMD) – cd C:\Program Files\exacqVision\EnterpriseManager\apache_solr\apache2\bin
3) Compare the resulting values output after running each of the preceding commands. Each resulting string should be identical. If the values do not match, confer with the certificate authority that issued the certificate.
Actual log example (Title of KB and first line should match)
Description
Describe
Notes
Notes, suggestions, KB’s, examples, etc…
REMOVE THIS SECTION
Categories Selections: Exclude from Global Search Categories __Products ____%product% Logs __Plugin ____%plugin% (use ‘GerericCameraPI’ for things that apply to all/many camera plugins __Log Level %loglevel% Tags are optional but we may use the Internal/Level2/Guest in the future to hide some from public
The processing loop has taken too long *** times. The longest time was ***ms for *** passes.
Description
A calculation is made by each camera plugin to determine if network operations ever took longer than 32ms. Once a minute, this data is logged. If it logs that it has “taken too long” this may indicate that the CPU is not able to keep up with the load.
Notes
A plugin that is not connected to any cameras will log this message once a minute and is not concerning.%BR% Antivirus software may cause a delay in processing data. The processing loop may take too long during heavy use, such as lots of reconnects to cameras, or many CGI commands (PTZ) and could be a sign that the system (CPU) is not powerful enough to process the current amount of camera data.
The processing loop performed *** passes and took ***ms to process the data.
Description
A calculation is made by each camera plugin to determine if network operations ever took longer than 32ms. Once a minute, this data is logged. If it logs that it has “taken too long” this may indicate that the CPU is not able to keep up with the load.
Notes
Antivirus software may cause a delay in processing data. The processing loop may take too long during heavy use, such as lots of reconnects to cameras, or many CGI commands (PTZ) and could be a sign that the system (CPU) is not powerful enough to process the current amount of camera data.