When uninstalling Exacq EM server version 23.06 or above and reinstalling it again on the Windows unit, It will not complete the installation and ask to close the open session even if no sessions are open.
Root cause
The root cause of this issue is The Microsoft Open Database Connectivity (ODBC) that was not removed when uninstalling the EM server software
Solution
Uninstall the ODBC, reboot the Windows machine, and install the EM server again.
Support has identified an issue with updating Enterprise Manager to version 23.09.5.0 prior to running updates to ExacqVision server 23.09.6.0. This issue will manifest after updating Enterprise Manager by users experiencing disconnection from the client with errors ” log in failed / invalid username or password or account locked or disabled” or ” log in failed – invalid response”.
Product
ExacqVision Enterprise Manager
ExacqVision Server
Steps to Reproduce
Update Enterprise Manager to version 23.09.5.0 while leaving ExacqVision server versions on 23.06 or lower.
Expected Results
– Users should remain logged in successfully.
Actual Results
– Users will be disconnected from the Client with error – ” log in failed / invalid username or password or account locked or disabled” or ” log in failed – invalid response”
Solution
Engineering is currently working on a patch to resolve this issue.
For customers that updated from 23.06 to 23.09 prior to the patch, installing the version with the patch should fix all login issues customers are facing.
For customers that performed a fresh install of 23.09 prior to the patch, user server passwords will become scrambled and customers will need to change/reset user passwords.
Until the patch is released, if customer has an Enterprise Manager backup that contains no issues from 23.06 that can be applied, the following steps can be taken:
Take a backup from 23.09 prior to making any changes.
Access a recent prior backup off of Enterprise Manager (this must be taken on version 23.06 previously).
Completely remove Enterprise Manager.
Install Enterprise Manager previous version 23.06.0.0.
Follow on screen prompts during install.
Login to Enterprise Manager as the root admin user.
Upload previously taken backup using the upload button in the backups screen in Enterprise Manager user interface.
Wait for this to complete.
Restore from uploaded backup.
Wait for restoration completion.
Confirm log-in capability has been restored.
Re-setup scheduled backups as these will be defaulted.
It should be noted that downgrading is not a normal solution, and should be prevented with Enterprise Manager. These instructions are only for situations where the customer has already performed this update and is now locked out of Client software and critically needs to be restored in a timely manner.
By default VFBA uses port 28774 and TCP to communicate with EM and the Server from the Spare NVR. Rules need to be configured for outbound and inbound firewall rules on the SPARE server for failback to work as expected.
To check the settings Open up Windows Defender Firewall with Advanced Security and click on Inbound Rules on the SPARE server.
Look for a rule allowing communication on port 28774, if you do not see this in the list, then click on New Rule in the upper right hand corner in the Actions section.
Select Port and click on Next.
Select Port 28774.
Click on Next and Select Allow the connection.
Make sure all three boxes are checked.
Click on Next. In the Name box type a name for this rule. I.E.- VFBA or evFailover, and click Finish.
Repeat this action for Outbound Rules on port 28774. It is neccessary to have both INBOUND and OUTBOUND rules configured on port 28774 on the SPARE server.
After configuring the inbound and outbound rules you can check the status by doing the following:
Open up task manager and click on the Performance Tab>Open Resource Monitor
Look at the Network Tab and under Listening Ports, verify it says Allowed and Not restricted.
Once any changes were made it is recommended that we restart the SPARE server and EM services and then check EM failover to see if the process can succeed. In some cases it may be necessary to whitelist vfba.exe and ExacqVision program components (core.exe, edvrclient.exe, including .ps and .psi file types & ExacqVision Enterprise System Manager components) when Antivirus software is in use within the configuration of your Antivirus program.
When troubleshooting TCP/IP connectivity issues, it is often helpful to confirm that the network path is open over a specified port and that there is no interference from a firewall or antivirus. This also rules out software level problems that may be causing a failure to connect.
While there exists many utilities to accomplish this task (telnet, putty, nmap, etc…), often these utilities aren’t previously isntalled and can’t be accessed when troubleshooting.
This utility will attempt to make a TCP connection to a specified IP Address or hostname over a specified port and return either success or failure.
If you are unable to transfer the file, the contents can be copy and pasted into a file manually and run from command line.
::PortCheck.bat
::This utility will check the network path to the specified IP address/Hostname.
::It will accept the first argument as the IP Address/Hostname, and the second argument as the port.
::Author - Isaac Penrod
@echo off
set $IP=%1
set $PORT=%2
IF "%~1" == "" set /p $IP="Enter the IP Address or Hostname: "
IF "%~2" == "" set /p $PORT="What TCP Port: "
set $COMMAND="^(New-Object System.Net.Sockets.TcpClient^).ConnectAsync^('%$IP%', '%$PORT%'^).Wait^(800^)"
echo.
echo Checking connectivity to %$IP%:%$PORT%
echo If the network path is open and something is listening
at that location, the result will be "True"
echo.
powershell -command " %$COMMAND% "
echo.
pause
If you are unable to transfer the file, the contents can be copy and pasted into a file manually and run from terminal.
You will also need to make the file executable with – chmod +x portcheck.sh
#!/bin/bash
#This utility will check the network path to the specified IP address/Hostname.
#It will accept the first argument as the IP Address/Hostname, and the second argument as the port.
#Author Isaac Penrod
IP=$1
PORT=$2
if test -z "$IP"
then
read -p "Enter the IP Address or Hostname: " IP
fi
if test -z "$PORT"
then
read -p "What TCP Port: " PORT
fi
echo
echo Checking connectivity to $IP:$PORT
echo If the network path is open and something is listening at that location, the result will be "success"
echo
timeout 2 bash -c 'if > /dev/tcp/'$IP'/'$PORT'; then echo success; fi'
if [ $? != "0" ]; then
echo failure
fi
echo
Arguments
This utility will also accept command line arguments. $1 – IP Address/Hostname $2 – Port
Bug Fix – Fixed issue causing server crash due to missing microSD card in Illustra multisensor cameras. If camera has no microSD for one sensor, but does for another, network loss recording action caused a crash. (AESW-7549)
Bug Fix – Prevent offload from Illustra BWC from hanging
Bug Fix – If camera does not support metadata over HTTPS, allow metadata over HTTP when camera is added with “HTTPS if Available” setting with illustra3pi and illustramultipi
Bug Fix – Added camera detection for all Illustra 2023 released models, this includes Flex 4 PTZ, Pro 4 Bullet, Pro 4 Compact Dome, Pro 4 Corner, and Flex 4 Dome models (AESW-5896)
Bug Fix – Support for motion windows when adding Onvif cameras to server, some Onvif cameras would not detect motion after adding even with enabled motion windows (AESW-7220)
Bug Fix – Fix for issue when Onvif cameras send ‘out of bounds’ motion window coordinates (AESW-7373)
Bug Fix – Decouple iris and focus debuffering from PTZs using Onvif
Feature – Improvements to core, logpi, softtriggerpi, tdvrpi, and videotestpi for logging and performance (AESW-5801)
Feature – Updated database structure and management for eventpi to improve metadata search performance, queries, and data purging (AESW-6286)
Feature – Added new retention options for AI / Object metadata Provides ability to help manage eventpi database size (AESW-6082)
Feature – Onvif motion and transport ‘plug-n-play’ support removes the need for manually updated Onvif JSON files and now Onvif plugin can dynamically read the motion topics from Onvif cameras (AESW-6069, AESW-3746)
Feature – New ‘Power User (No Video)’ security user role Supports countries where strict laws exist around video access (AESW-6387)
Enhancement – Added ability to set oldest desired content age for Cloud Drive content (AESW-3064)
Enhancement – Axispi now supports upper and lower clothing color metadata (AESW-7031)
Enhancement – Added paging support for brivopi
Enhancement – Added support for additional WDR modes on illustra3pi and illustramultipi (AESW-4618)
Enhancement – Added audit and logging of Illustra BWC privacy mode (AESW-7546)
Enhancement – Support added for Illustra BWC GPS data (AESW-5429, AESW-5528)
Enhancement – Added support for PCM16 audio for live streaming from Illustra BWC (AESW-423)
Enhancement – Added encrypted password storage to notify.xml for notifications (AESW-2085)
Build – Plugins for Basler, IoImage, IPX, Sanyo, Stardot, and UDP now unchecked by default during installation
Build – Upgraded aws-sdk-cpp to version 1.11.1
Build – Upgraded cURL to version 7.87.0
Build – Upgraded OpenSSL to version 3.1
Build – Upgraded libwebsockets to version 4.3.2
Build – Upgraded zlib to version 1.2.13
ExacqVision Client
Bug Fix – Enable appropriate buttons on the Add IP Cameras page after deleting cameras (AESW-6809)
Bug Fix – Fixed issue where Live view navigation tree reloaded on camera double-click (AESW-5618)
Bug Fix – Properly display the disabled Analytics buttons on Linux. Buttons were appearing as enabled when they should be disabled (AESW-6662)
Enhancement – Client support for the Oldest Content setting for Cloud Drive content (AESW-6779, AESW-7710)
Enhancement – Added new UX field for Frame-by-frame metadata retention period (AESW-6307)
Enhancement – Optimization for search speeds (AESW-5121)
Enhancement – Live analytic support for Illustra BWC (AESW-2846)
Enhancement – Moved generic dewarper to top of fisheye dewarper selection list (AESW-7389) Client side support for new WDR settings (AESW-5690)
Enhancement – Client side support for the new ‘Power User (No Video)’ user role. ‘Not Allowed’ text displayed for camera panels, Cameras hidden entirely from search (AESW-6388)
ExacqVision Web Service
Bug Fix – Removed no longer supported SCGI proxy folder. Action taken to prevent cross site scripting errors when performing vulnerability scans (AESW-6677)
Enhancement – Added evAPI support for detecting restricted view configuration (AESW-4288)
Enhancement – Change endpoint for S2 integration to ‘video.web’ (AESW-4903)
Enhancement – Scale web client search playback buffer with the playback speed selected (AESW-4757)
ExacqVision Enterprise Manager
Bug Fix – Update VMS audit log entries to use valid JSON (AESW-7458)
Bug Fix – Use the correct logger sync
Bug Fix – Add missing Seq settings validation
Enhancement – Add support for ‘Power User (No Video)’ user role (AESW-7169)
Enhancement – Add VMS audit trails to the EM audit logs (AESW-5498)
Enhancement – Added API endpoint for retrieving individual audit log entries (AESW-1340)
Enhancement – Add slug to audit logs where applicable (AESW-7176)
Enhancement – Add a user configurable timer for VMS audit log retrieval (AESW-6087)
Enhancement – Integration of EM/ISP logs into Seq. Provides the ability to extract logs into external Seq logging systems
Enhancement – Add migration files to upgrade AES encryption over the older ARC4 to enhance security (AESW-7512)
Enhancement – Update Apache to version 2.4.57 (AESW-6957)
The license being transferred “From” must have a current SSA.<br><br>
“From” and “To” licenses must be the same level. (Start, Professional, Enterprise)<br><br>
An existing “To” license keeps its SSA end date. This includes “To” licenses with an expired SSA.<br><br>
New “To” or “Zero” licenses: NOTE: A “Zero” license is an existing license that has had all IP channels transferred away
If it is an Exacq-built server “Zero” license and the SSA end date is more than a year in the future, then it keeps its own SSA end date. If less than a year, it receives a full year.
If it is a new license then it receives the SSA end date of the “From” license regardless of the existing “From” SSA end date. Again, the “From” license cannot be expired. This may be the next day or five years in the future.
If it is a “Zero” license for server hardware built by a third-party, then it receives the SSA end date of the “From” license regardless of the existing “From” SSA end date. Again, the “From” license cannot be expired. This may be the next day or five years in the future.<br><br>
An Edge or Edge Plus (Edge+) IP channel may only be transferred to a new MAC address.<br><br>
A Lifetime SSA does not transfer when an IP channel is transferred from a Lifetime SSA server to a non-Lifetime SSA server.
Licenses with Lifetime SSAs can be renewed at no charge by the Exacq Orders Team at exacqorders@tycoint.com<br><br>
Enterprise Manager
IP channels transferred from an Enterprise Manager license pool come with one year of SSA. That SSA is then distributed among any existing IP channels on the “To” license.<br><br>
Channels cannot be transferred from an existing license to an Enterprise Manager pool.<br><br>
Per the above rule, once a license has been transferred from the license pool, it cannot be moved back to the pool.<br><br>
Some servers connecting to Integrator Services Portal or Enterprise Manager may show disconnected on outbound connections tab, then connected, and then disconnect again intermittently.
Product
ExacqVision Server software ExacqVision Client software
Steps to Reproduce
Connect the ExacqVision server to ISP or EM via the outbound connections tab in the Enterprise section or Configure System section of the ExacqVision Client software.
Expected Results
Status should remain “Connected”
Actual Results
Status will show “Connected”, then momentarily show “disconnected”, then back to “Connected”, continuously cycling through these statuses.
Solution
Observe if streampi.xml lists the MAC address for SerialNumber value & shows “unknown” as ModelNumber value (if it doesn’t, could be a different issue).
Remove server from ISP or EM instance and restart ALL EM services.
Remove entry from outbound connections tab in client for this server
Edit streampi.xml to reflect proper original values for both SerialNumber and ModelNumber and save the changes.
Restart ExacqVision Server service
Add server back to ISP/EM instance as outbound connection with proper serial number to match what is in streampi.xml (HAS to be SerialNumber).
Click on server details > edit > verify proper serial number is listed. If this is not the proper value ( this may show a different value than what you would expect to see for this server), change it to proper serial number and save the changes.
Add EM/ISP instance back to outbound connections tab of client.