Category: exacqVision Server

Categories
Knowledge Support Support exacqVision Server Products

Samsung QNV-C8083R showing a 401 Error and invalid Credentials in Exacq Client

Description 

After reboot of server or restarting the service the camera will exhibit a invalid credential along with a 401 Error.

This was seen on a system that required restarting the system after every Windows Update.

Product 

  • Server 23.06.1.0
  • Windows Server 2016
  • Camera: Samsung QNV-C8083R FW 2.21.10.20230908_R

Steps to Reproduce 

Restart system and the camera would be locked out of the user attempt to log into the camera and would need to power cycle the camera to enable it to connect.
You can confirm this by logging into the cameras gui and finding the following error:

In our client we will show the following logs:

2/25/2024 10:11:25.925 AM (GMT-5:00)    SamsungPI    Error    7.230.122.80 - Initial discovery failed with error 401. The connection will NOT be retried.
2/25/2024 10:11:25.925 AM (GMT-5:00)    SamsungPI    Verbose    7.230.122.80 Network error 401 from request https://7.230.122.80/stw-cgi/system.cgi?msubmenu=deviceinfo&action=view using scheme https.

Expected Results 

We should be able to reconnect to the camera with no log in failures after a system / server restart.

Actual Results 

Camera will fail to connect to Exacq until you power cycle the camera.

Solution

Update the fw to FW version 2.21.10b_20240227-R6 by contacting Samsung to get this fw.
AES- 758 is still being investigated and requested that the IP Camera Integration page Be Updated with new test Records form FirmWare Version 2.21.10b_20240227-R6.

<br>

Categories
exacqVision Server Windows Knowledge Support Support exacqVision Server Products Uncategorized

Global At Most Rule 30 Days

Description 

There are some reports that after setting up Global At Most Rules the data is not removing older content off the drives. For example if recording has been taking place for a year and Global At Most Rule is set up after a year of recording some of the older content is not being removed from the data drives.

Product 

  • Server 23.09.9.0
  • Linux 18.04

Steps to Reproduce 

Oldest content on the storage drive will show content past the current Global At Most Rule that are configured. This was seen on units that had been recording for a long amount of time. Then at some point a Global At Most Rule was created. After the 30 days the data was not being removed from the system.

Expected Results 

We should purge older data. However if there is a year worth of data we may need to give it a hand to clear out in special cases where customer need to see a certain amount of Oldest content on the Storage page.

Actual Results 

If data is on the unit for 365 days, then it can take time for that data to be purged. It will keep showing Oldest content of 365 days until it successfully purges the data.

Solution

A work around is to delete some of the older content outside their current Global At Most Rule.

1. Stop the server and check the data folders on the drives.

2. NOTE: ALWAYS HOLD SHIFT and then hit the Delete Key. If you do not do this it can fill up the OS drive’s recycling bin.
Remove Years, Months as needed from the data folder.

3. Start the exacqVision Server Service and allow up to 5 minutes for the Sweeper to run. We delay the Sweeper service from starting right away on purpose.

4. Monitor the logs on the server around the 5 minutes, and search for a sweeper event, and then look for a fscleanup event in the logs. If this is seen you can validate on the Storage page if the Oldest Content numbers change within the next several minutes down to the size of the At Most Rule 30 Days.

In the following example we stopped the service and removed data off the drives down to 62 days and 9 hours.
After removing the data we started the service and waited 5 minutes.

After 5 minutes you should see the following in the logs.

PSFPI    Verbose    Sweeper - expiring all files older than Tue Apr 2 10:20:58 2024.


This indicates that the Sweeper is looking at the older content on the drive and preparing it to be removed.

After a few more minutes the oldest content was reduced down to the target Global At Most Rule of 30 days.




Current Ticket opened is AES-847.

<br>

Categories
Video Library Configuration Demo exacqVision Server Youtube Video Library Categories Products

Exacq Scenario Series – Audio and Email Notifications After Business Hours

Exacq Scenario Series – Audio and Email Notifications After Business Hours
The Scenario Series of videos addresses setup configurations for specific use cases. In this video our scenario is that of a car dealership that wants to play an audible alert to people on the property after hours, as well as send a notification to staff members. We walk through setting up AI Object Classification on three different cameras from Illustra IQ, Axis, and Hanwha, then show how to configure Event Linking different ways and two different methods for scheduling the action to occur. Chapters 00:00 Intro & Review of Scenario 00:56 Axis C1310 Setup 02:32 Camera Configuration 02:59 Illustra 04:28 Axis 05:46 Hanwha 07:01 Event Linking 09:43 Notifications 10:46 Scheduling 14:16 Wrap-up
Categories
Plugin Knowledge Support ArecontPI Support exacqVision Server Products Logs

Arecont Camera 12176DN on firmware 65216 is Causing the Video Stream to Timeout

Description 

Arecont Camera 12176DN on fw 65200 is causing the video stream to time out and the stream is reconnecting. CGI access to the camera is fine.

Product 

  • Client Version: “22.03.1.0”
  • Server Version: “23.06.1.0”
  • Arecont Camera 12276DN on fw 65200

Steps to Reproduce 

Connect to the camera and let it record.
The video stream is timing out and the stream is reconnecting. CGI access to the camera is fine.

Expected Results 

Motion / Free run should not attempt to reconnect.

Actual Results 

There are constant gaps in recording when searching.

Solution

Roll back the FW to version 65129 on the camera.

Per Arecont-
According to our internal documentation, the only change from 65192 to 65200 was to properly provide a handshake response for digest authentication.  

AES-662

Waiting on PM to decide how to appropriately resolve this.
According to one customer they rolled back the FW on the camera and all the behavior seen prior resolved.

OPTIONS:

  1. Arecont write fw to support onvif —> impossible, never happen.
  2. Schedule a task to bring native plugin into spec with rest of plugins as a final step for legacy support as they themselves are moving to all onvif.
    Big lift. Proper thing to do.
  3. Try a hack in the plugin to allow increasing the buffer size with an override. –> small lift (< 1 week) with understanding this may unnecessarily increase memory usage on a system with a lot of arecont native. An override to make this a per camera impact.

 4)Give them some gratis licenses –> problematic, no way to specify what licenses are used for and they lose all motion recording functionality.

Categories
exacqVision Server Windows Knowledge Support Support exacqVision Server Products

Windows Server 2022 Showing Only One Network Card

Description 

Some Exacq NVRs built with Microsoft Windows Server 2022 only acknowledge one network interface, rather than two, when being configured out-of-box.

<br>

Product 

Issue has been noted on BBE systems ASRock Industrial IMB-X1313 system boards, listed below.

  • Z-Series systems
  • Some A-Series systems, depending on the system options ordered

NOTE: Windows Server OS is an optional upgrade for many systems, so this will not apply to all systems listed above.

<br>

Steps to Reproduce 

  1. Power on unit<br><br>
  2. Check Windows Device Manager for listed network interfaces<br><br>
  3. Check exacqVision Client Network Settings

<br>

Expected Results 

All network cards are recognized and appear listed.

<br>

Actual Results 

Only one interface is listed.

<br>

Solution

Attempt solution starting with Step 9 first. If this still fails, repeat steps beginning with Step 1, which requires opening the system chassis.

  1. Power the system down gracefully using the shutdown option from the OS.<br><br>
  2. Unplug system and press the power button to drain any residual power off the board.<br><br>
  3. Open the system, locate and remove the CMOS battery from the system board. Wait 5 to 10 minutes before continuing.<br><br>
  4. Replace the CMOS battery.<br><br>
  5. Reconnect power to the system.<br><br>
  6. Power on the system.<br><br>
  7. Enter the system BIOS or Boot Option menu and boot to the UEFI partition.<br><br>
  8. Check for changes in recognition of the additional network interface(s). If no change, continue with next steps.<br><br>
  9. Restart the system and enter BIOS.<br><br>
  10. Open to the Exit menu and select Load Defaults.<br><br>
  11. Reboot and enter BIOS again, select the UEFI partition as the boot option.<br><br>
  12. Check Windows Device Manager and Network Settings to validate that the additional interface(s) are detected.

<br>

AES-842 Has been created to investigate this.

<br>

Additional Steps

Pull the logs from the UEFI

  1. Open CMD.<br><br>
  2. Enter the following:
    mountvol z: /S<br><br>
  3. Type cd z: and press Enter.<br><br>
  4. Type dir and press Enter.<br><br>
  5. Type cd EXACQ and press Enter.<br><br>
  6. Open File Explorer and locate the logs in the Z partition. This is hidden by default. If you make them visible using File Explorer options, be sure to set to hidden again after you are done collecting logs.<br><br>
  7. Collect the txt and xml files from the logs and add them to a newly created ZIP file to copy from the system.<br><br>
  8. When done collecting logs, return to CMD and enter
    mountvol z: /d
    to remove the temporarily mounted volume.

<br>

Categories
Knowledge Support Support exacqVision Server Categories Products

exacqVision License Recovery

Description

An event, such as OS failure, requiring a reimage of your Exacq NVR may leave you with unlicensed exacqVision Server software. If you cannot locate a copy of the emailed license key from the time of purchase, or an exported copy of the .KEY file to use, what should you do?

<br>

Import from Exacq.com

Perhaps the simplest method is to follow the steps below.

  1. Provide an internet connection to the system.<br><br>
  2. Open the exacqVision Client.<br><br>
  3. Select the cog wheel icon in the upper-left to enter the Configuration screen.<br><br>
  4. From the navigation tree along the left side, locate the server name and expand this option.<br><br>
  5. Beneath the server name, select Configure System.<br><br>
  6. On the System tab, locate the License area. Press the Import button and select ‘From exacq.com‘.<br><br>
  7. This method will automatically import the most recent license from Exacq. Note, that if the license key is expired you may need to change your installed exacqVision Server version to one released prior to the license’s expiration date.

<br>

If the import fails or you are in need of other licensing information, contact Orders as directed below.

<br>

Contact Orders

Orders may be contacted by phone or email. Please be prepared to offer the system’s serial number or licensed MAC address.

+1-317-845-5710 select option 3 for Orders when prompted.

exacqorders@jci.com

<br>

Related Articles

<br>

Categories
Software Categories exacqVision Server Linux x64 Knowledge Support Support Categories Products

De-elevation not working on Ubuntu 20.04 and higher

Product 

exacqVision Server

Steps to reproduce

Use the following command per the hardening guide

sudo dpkg-reconfigure –p low edvrserver

Expected Results 

De-elevating the exacqVision Server

Actual Results 

Getting the following error

Solution

The fix for this issue will be back patched to 24.03.X

We strongly recommend checking our Exacq server release notes to be aware of when the fix is available

https://cdnpublic.exacq.com/evserverRelNotes.txt

Categories
Exclude from Global Search Plugin Log Level Error exacqVision Server Categories Logs Illustra3PI

Camera did not send valid quality for codec H264

Camera did not send valid quality for codec H264

Description

exacqVision Client connection status for camera shows “unable to create video stream” status.

Notes

Often this is a firmware compatibility issue. There are some cases that this has been resolved by factory defaulting the camera and/or removing and recreating illustra3pi.xml file in server folder.



Categories
User Guides Knowledge Support Documentation Highlighted Support exacqVision Client exacqVision Server Categories Products

Deprecation of Legacy Installers – exacqVision 24.03 Update

As part of the exacqVision 24.03 software release, we are announcing the deprecation of specific installers that were previously part of the collection of software downloads available on the Exacq web site, https://exacq.com.

What installers are being retired?

On both Windows and Ubuntu – the 32-bit installers, also known as “x86” installers, of server, client, and web service will no longer be made available for new releases. The Enterprise Manager 32-bit installer had been deprecated from the 21.12 release. In addition, Illustra 610 and 825 (Edge), and ARM Debian (M-Series) installers will be retired as well.

Why is Exacq taking this step?

This change helps address cyber security/robustness concerns by removing support for those installations that are potentially deployed on operating systems no longer fully supported by the vendor. Additionally, retiring support for older/obsolete technology helps Exacq to streamline engineering resources to focus their efforts on faster delivery of customer outcomes that are needed now and in the future.

What if I have been using 32-bit installers for exacqVision all the time? How do I update to the 24.03 release?

If a customer is currently using 32-bit installers, they would have to move to the 64-bit installers – provided the hardware and the operating system are 64-bit enabled. 32-bit and 64-bit installers cannot co-exist. To move to the 64-bit installation, the 32-bit installation should be uninstalled.

So as to not lose the current configuration, it is recommended that the current configuration be backed up – then restored after the 64-bit installation has been deployed. Please refer to this user guide section for understanding how to do a backup and restore of the exacqVision Server configuration.

If Enterprise Manager is deployed, you may refer to this video to understand how to backup and restore configurations across multiple servers at once.

How do I know if the hardware and operating system on my NVR is 64-bit capable?

It will depend on how old the NVR is.

If the NVR was built by Exacq and is a Windows machine – Any system that shipped on or after May 2013 is capable of running a 64-bit installer.

If the NVR was built by Exacq and is a Ubuntu machine – Any system that shipped on or after August 2017 is capable of running a 64-bit installer.

Please refer to the following Support article to determine the age of your system based on the serial number:
How to Determine the Age of a System Using a Serial Number

If the NVR was not built by Exacq, please contact your IT department or the manufacturer of the NVR to assess if it is capable of running a 64-bit installer. As a reference point, Windows started 64-bit support from Windows Vista, with mainstream support adopted in Windows 7, and Ubuntu from Ubuntu 16.04. So it is more than likely that the NVR in question is 64-bit capable. With that said, please double-check with relevant departments and resources to be sure.

NOTE: Operating system vendors, whether or not they support 64-bit, have set time tables for end-of-life (EOL). It is not recommended to use a system for which critical cyber security patches are no longer available. For example, Microsoft no longer supports Windows 7 or 8. Ubuntu does not support systems older than 14.04 today – and they will continue to obsolete older versions as they release new ones.

I can see my NVR is not capable of running a 64-bit installer. What is the recommended course of action?

It is likely that you are running an old NVR that is probably not in compliance with the cyber security standards of your IT department. In addition, you will not benefit from new features, integrations, cyber security patches, and bug fixes that make up the 24.03 and future exacqVision releases. Our recommendation is that you upgrade to newer hardware and operating system for your NVR. Please reach out to your local exacqVision dealer or call Exacq Inside Sales for better understanding of your options.

<br>

Categories
User Guides Documentation exacqVision Server Categories Products

Recording different resolution or frame rates on event

Description

Some users may desire to record a different resolution or frame rate from a camera when an event such as motion or an analytic is triggered. Reasons for this vary by site, but often comes down to wishing to record a lower amount of data when very little is happening, but they require high frame rates or high resolution recordings for forensic playback.

In the steps below, we step through creating a secondary stream but configuring them with different settings and schedules. These steps are examples and you will need to adjust the settings for your site’s needs. Mix and match resolution, frame rate, or recording format as desired.

<br>

Setup Steps

  1. Navigate to the Camera Settings page for the camera you wish to configure.<br><br>
  2. Configure the settings for your first stream using the Recording tab on the bottom half of the page. It’s best to use this primary stream for your highest resolution and frame rate settings simply because most cameras provide fewer options for secondary streams.
    <br>In this example, our primary stream is configured for a resolution of 3840 x 2160 (4K/8MP) and an image rate of 25 fps.<br><br>
  3. Assuming your camera supports Multistreaming, select a new Context from the Multistreaming settings and click the Add Stream button.
    <br><br>
  4. After pressing the Add Stream a new sub-stream, or child stream, will appear on the system navigation tree to the left, nested beneath the primary, or parent, stream you just configured. The Camera Settings page should update to display the settings for this stream.
    <br><br>
  5. Configure the Format as needed, then configure the Resolution and Image Rate desired for your lower end stream.
    <br>In this example, the stream is configured for a resolution of 1024 x 576 and an image rate of just 10 fps.<br><br>
  6. Select the high resolution, high frame rate primary stream from the system tree and choose the Schedule tab. In this example, we’re going to configure the high resolution, high frame rate stream to only record on an analytic, in this case person detection.<br><br>
  7. Highlight the entire schedule grid and change these from the default of Motion to None. Apply your change.
    <br><br>
  8. Select the lower resolution, lower frame rate, secondary stream from the system tree, then select the Schedule tab. You could choose to set it to Free Run recording for continuous recording, or highlight the entire schedule and change it to Motion recording.
    <br><br>
  9. The low resolution, low frame rate stream will record based on the schedule configured on the Schedule tab. We need to tell the system when to record the higher resolution, high frame rate stream. Click the New button.<br><br>
  10. Navigate to the Event Linking node on the system tree.<br><br>
  11. We’re triggering off an analytic in this example, but you may use any Event Type you wish, such as Motion or an Input Trigger. We select Analytics, then choose the Enter Rule analytic, previously configured on the camera, from the Event Source panel.<br><br>
  12. Our Action Type will be Record Video.<br><br>
  13. The Action Target will be the high resolution, high frame rate primary stream.
    <br><br>
  14. Returning to the Schedule for this primary stream, we see the red corner flags are set indicating hours of the day in which our configured Event Link will record this camera stream. By default this will occur for all hours and days. Event Linking Source Groups could be used to configure specific days and hours to record on this event.
    <br><br>
  15. Save your configuration by selecting the Apply button.<br><br>
  16. Your configuration is complete and ready for testing. When performing a search you may search for recordings from either, or both, the primary and secondary streams but will likely rely on the primary stream for those high resolution or high frame rate forensic investigations of incidents.<br><br>
  17. Repeat these steps for other cameras where you may want the similar recording behavior.<br><br>

<br>