PostgreSQL 9.6 is currently bundle with exacqVision Enterprise Manager. This version will reach end of life in November 2021.
The PostgreSQL Global Development Group will release the final update for 9.6 on November 11, 2021. See their versioning page for details at https://www.postgresql.org/support/versioning/
The Volume and Hardware tabs or not present on the Storage page even though the server has a MegaRAID RAID controller and the drive is present on the Drive tab.
Resolution
This can occur when the path to storcli is not present in the Windows system Path environmental variable. Use the following steps to correct.
Steps
Verify that StorCLI.exe and StorCLI64.exe are located in the default directory. “C:\Program Files (x86)\MegaRAID Storage Manager”
In Windows open the Environmental Variables system properties .
Under System variables locate and edit the path variable.
Add the MegaRAID Storage Manager path to the path variable.
Stop and start the exacqVision Server Service. Note: A reboot may be necessary
The Volume and Hardware tabs should now be present on the Storage page.
Before adding the path to storcliAfter adding the path to storcli
In CCURE 2.80 CCURE introduced a breaking change to their API in their primary login, so our code had to be modified to let people login. So the first thing to note is that Exacq Server version 20.09 or later is required to be able to login to Victor Web 2.80 or later.
The next issue is that the new login API requires that we pass several new fields including a special GUID which is unique to Exacq. This GUID enables CCURE to track integrations. However, CCURE did not add Exacq’s GUID to their installer package’s database in version 2.80, which means that login attempts will fail with message “The client with the specified ClientID/ClientVersion is not licensed” (you can see this in the exacq server logs).In order to fix this, we will need to run a script that CCURE provides that inserts the Exacq GUID into CCURE’s database.
Instructions are below on how to execute the script. If you need assistance or run into trouble with this procedure, we would be glad to setup a remote session.
The script is located in
C:\Program Files (x86)\Tyco\CrossFire\Tools and is named InsertLicenseOption.exe
In order to execute the script follow these steps.
Open a PowerShell window with administrator privileges
navigate to
C:\Program Files (x86)\Tyco\CrossFire\tools
Determine your CCURE database name by opening SQL Server Management Studio (SSMS) and looking for the “server name” associated with your CCURE installation (see picture).
After you have determined your database name, you should replace the argument “PM-INTEGRATIONS\SQLEXPRESS” with the name of your CCURE database in the following command
Paste the above command (with your database name) into your PowerShell window and push enter to run. If your script has run successfully, you will see something similar to the following output .
Restart all crossfire services. You will need to open the Windows Services app (also can be done through CCURE’s software) and look for ‘crossfire’ (right click and click restart) or you can use the application CCURE provides called Server Configuration Application, where you will need to click Stop and then Start for each of the services with Crossfire in their name.
Note that restarting the Crossfire services takes a long time (I experienced up to 10 minutes).
After you have done all of the above, and have properly licensed the Exacq analytics, the integration should work just fine.
NOTE: See KB Number: 6305 “C-Cure Integration License” for licensing details
Video is not recording to customers iSCSI targets after a reboot. Drive was reporting a status of “Recording Not Possible” on exacqVision Server 21.03.10. Servers running exacqVision Server version 20.06 or older were showing a status of healthy, but were not recording.
Identification
Use the following to properly identify the issue before applying the fix.
Update to exacqVision Server version 21.03 or later.
Check the drives status on the storage page.
If the status is “Recording Not Possible”
Enable debug level logging
Restart the exacqVision Server service
Monitor for log entries similar to those listed below, specifically Store Fails and GRV Fails
Check Extended Storage or Enterprise Storage for conflicting entries like those displayed below.
Once positively identified follow the steps outlined in the resolution section
Log files (debug level enabled)
Before Fix
After Fix
Enterprise Storage page was showing the Type as Local (iSCSI) on the servers which were not recording. Servers which were recording report the volume type as Local. Note: The server showing the Status of “Recording Not Possible” was running newer exacqVision Server software 21.03.10 vs 20.06 or older for the others.
Another indication was that the iSCSI targets populated both the Targets and Partitions Section of the Storage page, Extended tab. Whereas the servers which were recording normally populated only the iSCSI Targets.section
Resolution
rename archivepi.xml
rename psfpi.xml
restart exacqVision Server Service
Verify that storage targets are only listed in the Partition section of the Storage page (Configuration > Storage > Extended Tab)
Verify that the volume now has a type of Local on the Enterprise Storage page (Configuration > Enterprise > Storage)
The Status of the Direct Search section on the Archiving page shows “Invalid username or password” However the target can be accessed through a file explorer and direct search can find video only present on the archive target and play it back.
While only cosmetic this issue can cause unnecessary concern and confusion and has been present since at least exacqVision Server Version 19.03
When configuring motion windows on Panasonic cameras, and clicking the Apply Defaults button in Client in order to create a default motion window that matches whole imager size, the window does not save.
Workaround
Manually draw a window within the video window boundaries.
Some Vivotek cameras require Basic Authentication. This should be indicated in the Notes section of the cameras test record. The camera will not connect if digest authentication is selected.
Product
Vivotek IP Cameras
exacqVision Server
Steps to Reproduce
Add a Vivotek Camera
Expected Results
Camera connects
Actual Results
The camera does not connect and a connection error “Connection error (403)” is returned
Sample from exacqVision Server Logs
Solution
Disable the camera in the exacqVision Client
Access the camera configuration page via a web browser
Navigate to Network > Streaming Protocols > Authentication
Change Authentication from digest to basic for both HTTP and RTSP protocols
Navigate to Security > Miscellaneous
Uncheck the Enable Cross-Site Request Forgery (CSRF) protection option
Save the changes
Reboot the camera
Access the camera configuration page via a web browser
Navigate to Network > Streaming Protocols > Authentication
Verify the authentication mode is set to basic
Navigate to Security > Miscellaneous
Verify CSRF is not enabled
Enable the camera in the exacqVision Client
Important: The camera seems to require a reboot to fully apply the change in authentication mode.
The DMP panel uses a ‘disconnect’ command to gracefully close a socket. The original release of the DmpPI plugin did not implement this command. As a result, after a connection to a panel was made, then was disabled and quickly enabled again, the connection attempt failed several times until the panel timed out and closed its end of the socket.
Workaround
Wait a minute before enabling the panel, be patient.
exacqVision Server may cause incorrect frame timestamps for some cameras that are using RtspPI or AxisPI plugins.
Workaround:
None
Version Affected
20.06.4 and earlier
Resolution:
A new Override is available for RtspPI and AxisPI
The Override will prevent the server from auto adjusting timestamps and will trust verbatim what comes from camera.
The server generates and caches a timestamp offset when starting a stream, which is applied to every frame as a time correction. Normally, the camera then continues to perform NTP sync operations with the server for timestamp accuracy.
However, with a busy network, some NTP packets may fail to arrive at the camera, and in some cases the camera’s time may drift beyond a 60 second threshold, which causes server to incorrectly adjust and freeze its cached offset, which will be applied to every frame regardless whether the camera successfully NTP syncs with server.
Most noticeable in multi-sensor cameras and encoders.
When viewing cameras, the user would occasionally see the following exacqVision Client Error message:
Unable to exclusively lock file<br>
C:\Users\<username>\AppData\Roaming\edvrclient\edvrclient.xml with file<br>
C:\ProgramData/boost_interprocess/1615401609/QzpcVXNIcnNicQ05Pc3N6XEFwcERhdGRcU…<br>
Error The system cannot find the path specified.
It was observed that the C:\ProgramData\boost_interprocess\ folder is being renamed by software running in their corporate environment.
The exacqVision Client uses the boosts IPC folder which is sometimes used by the other software.
