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
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 Categories

Samsung Cameras not connecting to Client after Updating to 23.06.1

Description 

Certain Samsung Cameras are not pulling in camera details or live streams after updating to exacqVision Server version 23.06.1.

Product 

  • exacqVision Server 23.06.1
  • Cameras:
    • Samsung QND 7010R, firmware 4.00 2016
    • Samsung QND-7020, firmware 4.00 2016

Steps to Reproduce 

  • Update to exacqVision Server 23.06.1
  • Camera connected and working as intended on Server Version 23.03.1.
  • After updating, cameras will sometimes connect and not show camera details or live streams. Sometimes the camera’s will not connect at all.

Expected Results 

Cameras should connect and show details and live streams.

Actual Results 

Cameras will sometimes connect and not show camera details or live streams. Sometimes the Camera’s will not connect at all.

Solution

We have seen changing the plugin type to Onvif will allow the cameras to function properly in the client.

Note: If you are using Motion Detection please make sure that the cameras are set up properly.

A fix might be in AES-596 is scheduled to be released in Oct, 2023.
AES-554 Testing AES-596 on cases from AES-554

<br>

Categories
Knowledge Support Support exacqVision Client exacqVision Integrations

Moving an existing IP Camera From One Plugin to Another

Title

Moving an existing IP Camera From One Plugin to Another in exacqVision

Description 

Introduced  in exacqVision Client 19.12 we now have the ability to change an existing IP camera from one plugin to another, automatically locate and rename existing video files, ensuring that previously recorded video will be associated with the new plugin.

Product 

  • exacqVision Client
  • exacqVision Server

Solution

Beginning with exacqVision Client version 19.12 existing cameras can be switched from one plugin to another.  When applied the camera is switched to the new plugin and existing video files located on any LOCAL disk including iSCSI will be automatically renamed.  This will ensure previously recorded video is associated with the new plugin and can be searched and played back normally.

Archived or Cloud Video

  • Video Files residing on archived drives or stored in the cloud are not renamed.  
  • This could result in files named with the original plugin, that still exist on local drives, will be  renamed and if scheduled to archive, could result in duplicate video on the archive target,  some with the old filename and some with the new.
  • In certain cases, support may be able to assist in renaming archived or cloud video.  Please contact exacqVision Support (https://exacq.com/support/techsupport/) for information, make sure to reference this Knowledge Base Article and a utility called psChange.

The Device Type will remain grayed out until the following requirements are met. 

Requirements

  • Client must be running on the NVR
  • Client must be launched with administrative privileges.
    • Windows – right-click on the exacqVision Client Icon and run as admin
    • Linux – launch edvrclient with “sudo”

WARNING

Certain plugins are listed with the OEM name, yet in the background are using the Onvif plugin.  That being the case you cannot convert from say Onvif to Bosch or Bosch to Samsung as they are all using the Onvif plugin already.
​The list below is current as of 03/15/2022  but a current list can be generated easily using  the appropriate command

Windows – Powershell
Linux 
Onvif OEM List current as of 03/15/2022 
Categories
Knowledge Support Support exacqVision Server Categories Products

Illustra Corridor Mode Motion masks do not match between the client and the camera web application

Issue:

Tyco Illustra Pro Gen3 cameras placed in Corridor Mode will not have motion masks/detection zones that match between the exacqVision Client’s camera settings page and the camera’s web browser graphical interface. Nothing can be done to properly synchronize the motion masks/detection zones between the two interfaces.

In the exacqVision Client, Motion masks are created to block out areas where motion detection IS NOT DESIRED and are displayed in red. In the Illustra camera, the Motion Detection Zones are created to define areas where motion detection IS DESIRED and are displayed in yellow. Essentially, the displays should be the inverse of each other but the respective zone area(s) in the field-of-view should match.

Figure 1 displays one possible symptom where the Illustra camera has the entire field-of-view defined for motion detection but the corresponding zone in the exacqVision Client shows an area “masked” for exclusion. The client motion mask CANNOT be deleted. This is an error condition.

Figure 1. Side by side comparison of Illustra web page Motion Detection tab vs. exacqVision Client Motion tab.

In other words, a full-screen motion detection area set in the camera is displayed as masked for ignoring motion events in some areas from within the client. Smaller zones do not match either.

Illustra Pro Gen3 2MP, 3MP, 5MP, & 8MP Mini-Dome and Bullet camera models are affected. Verified with firmware versions:  

  • Illustra.Pro3.02.02.00.0053
  • Illustra.Pro3.02.03.00.0038
  • Illustra.Pro3.02.07.00.0015

Workaround:

None available.

Version Fixed:

  • Development build 21.03.111.0
  • Expected release 21.06