When viewing a camera or multiple cameras in Focus View in the mobile app and you go to exit the view you will get a White X that will not go away. You have to close the app to get this to correct it’s self.
When this happens, the logs are showing an uncaught exception because the camera doesn’t support digital PTZ.
Update Exacq Mobile 3 to version 21.09 and if they can not there is a work around.
Work Around
Enable the PTZ on the client- under the cameras. This was confirmed as work around. If it is disabled then “Enable” checkbox should be checked.
Release notes: 10/04/2021 v21.09.0 * Bug Fix – Fixed focus view not exiting on some cameras
IMPORTANT** Please look at the below notes before updating SOLR APACHE.
Starting with December 2021 (20.12 build) we have included an update for the Apache updates via a pop up during installation to update Apache to version 2.4.51. IMPORTANT** It is important to note that During the Apache upgrade it will backup the entire apache2 folder creating a folder apache2.old. The install does not modify any added files or folders as it will essentially unpack the new Apache upgrade zipped folder. This means during an Apache upgrade all configuration files will be unpacked and reconfigured according to a normal enterprise manager install. If there was custom modification done to any configuration files it will have to be manually migrated over to the new configuration files from the apache2.old directory.
The Dashboard will not update Existing Solr Apache so it is recommended that you update using the installers found on our site. https://www.exacq.com/support/downloads.php
In addition 32 bit will no longer be supported for December release.
Ubuntu is not supported by the installer. A manual Upgrade is requires and will need to be performed.
The issue reported was that the drives will show up as offline when customers update to 21.09. If you were to roll back the server to 21.06 the drives would show up as healthy.
When setting up email notifications to work with a IP Camera Connection event there is setting in the Notifications to send on the event start and end.
Once the Email Profile has been tested and confirmed to be working we need to set up 2 rules for this to work properly
Event Linking
To set up the trigger to allow the notification to work we must set up an Event linking event. In this Example we are using a single camera to to send an email when the camera disconnects and reconnects to the server. The email profile will send out an email that will show the start of the event and the end of the event with a Start and End status in the email that is receive.
The event rule should be set similar to the picture above.
Event Type: IP Camera Connection Event Source: Is the camera that you want to monitor. Action Type: Notify (the Email Notifications) Action Target: The Email Profile Created in the Notifications section. Alert Emails.
Notification Email Message Profiles
To configure your email profile Page correctly to send the notifications with a start and an end see the picture below.
When setting up the Email Message Profile Page there are 2 things we need to make sure are selected from the menu options.
1.Make sure to Select the WHEN drop down menu and select Alarm Starts and Ends. (If you want only on start select Alarm Start) 2. In the Add Field drop down menu select EVENT STATE and a Date format.
When the event is triggered the email profile will send an email out on the start of that event and then at the end of that event.
This is not an exhausted list. Soft Triggers are not available in the Web Browser/Thin Client. Customers should use the Exacq Mobile 3 Client from a Web Browser instead.
The physical triggers are located in the menu of the mobile browser instead of on the live view.
For Example: If you are using a trigger for audio and the associations have been created. Connect to the Exacq Mobile 3 Client in a browser, navigate to the menu options, go to the Audio Devices, select Audio Input, and select Listen in Live. In the lower right corner you will see the option for activating that soft trigger.
When installing the web service the Service’s do not show up. The install seems if it completed successfully but does not create a service.
After installing the latest version of the Webservice the control panel and service page looks like this: You can see the application installed but the services do not.
Check to see if nvrg.exe is installed in the BIN folder. Run the Command Prompt as ADMIN: Note: You have to be in the bin directory or use full path. Type the following in CMD: cd C: \Program Files (x86) or (x64)\exacqVision\WebService\bin Then run: wfe.exe -k install IF you get the follow error we need to Make Sure that this error shows before moving to correcting the registry. If this does not give an error then do not move to the registry and escalate the case.
ERROR: If you get the above error: “this registry key already exists” seen as the return from the command follow the steps below to correct the install.
Run RegEdit as ADMIN and navigate to: Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\Application\webservice
You will delete the whole webservice key seen above. Delete the Folder in the left panel only.
Once that is done you can re run the command above and if it runs successfully you can validate the service shows up in the services. If it does start the service and in a browser browse to 127.0.0.1 (list port intended).
For the multi head camera when imported from a CSV file the client uses 4 camera licenses and not just one. This is true for all other manufactured multi head camera on the system in .CSV
Previously we did not support this in our client. Dev build 21.09.2294700.0 included the following fix: Enhancement – Added support for importing cameras with multiple inputs.
This is the Licensing Miscalculation Referred to.
One problem you might encounter is that when adding the input to the CSV file it should not say INPUT 1, 2,3,4. to allow the Input Name to show up correctly.
The input name should only be 1,2,3,4. See below example:
The reason why is that we convert that field to a number and when the camera comes back we match that number to the input number on the camera to determine if it’s the right input to set the name on.
Below is an example of what happened after we included the ability to import multi head cameras into the import of the CSV file.
Select the CSV file under “Camera Import” and it correctly identifies the columns (including Input) as shown in Fig 1.
The client correctly counts the camera as only one license. Though it says it imported 4 Cameras and confirmed it only used a single license shown in Fig 2.
The camera shows up only one time in the “Add IP Cameras” list. Fig 3.
The camera correctly shows four inputs under the “Camera Recording”. But it did not import the names. Fig 4.
As seen in Fig 3 The INPUT Column need to only add 1,2,3,4 and Not Input1,2,3,4.
This is for a specific customer that was reporting issues with Q series units using a KMV Startech Switch-Model SV431USB. The customer experiences NO DISPLAY on the monitor on boot. They also exhibit no display when switching the source at the switch from a windows based unit back to the Q Series. Tickets: 22721 and 23035.
Testing results: 14.04 <== won’t remediate – end users will have to re-image with 18.04 key. 16.04 <== won’t remediate – end users will have to re-image with 18.04 key. 2019-03 = first 18.04 with golden image: * Note that you’ll get a warning “old exacqdeploy package post-removal script sub process returned error exit 1”, but this is ok. Ignore it. This warning unfortunately cannot be suppressed. 2019-12 = first 18.04 with packer image: Verified at version 19.06.4 and newer. Verified 20.09.1 2021-03 = final 18.04-based key. Verified 21.03.5. If they are on a version older than 19.06.4 they will need to update to at least 19.06.4 or update to the latest release. Do not use this if they are on Ubuntu 14.06 or 16.04.
The URL below will allow you to download the .DEB file. That can be transferred to the local NVR and ran on Ubuntu 18.04 servers with at least 19.06.4 Server installed.
Download the file. 2.) You will have to put the file on the desktop of the NVR and then open terminal and run the following 2 commands. cd /home/admin/Desktop (press enter) sudo dpkg -i exacqdeploy_21.06.116.0_all.deb (press enter)
Updating from 19.12 through 21.06 could cause the event linking Inputs to be renamed. There is a developement build to correct this and will be release in the September release. This is contained to Axis A8027 cameras with relay inputs. The relays will work but the names of the inputs in event linking will be renamed. Rolling back to 19.12 Server will correct this. If this is the case please update to Dev build or our September release.
