Month: April 2021

Categories
Knowledge Support Support exacqVision Enterprise Categories Products

Bulk delete server actions on ESM on MySQL database fails

Description

Attempting to bulk delete server actions on ESM on MySQL database fails

<br>

Version Introduced

not provided

<br>

Platform

All

<br>

Steps to reproduce

Attempt to bulk delete server actions on ESM on MySQL database

<br>

Expected result

Server actions are successfully deleted

<br>

Actual result

Error page is returned and server actions are not deleted

<br>

Work Around

Deleted server actions individually

<br>

Version Fixed

none

<br>

Keywords

ESM MySql

Categories
Knowledge Support Support exacqVision Enterprise Categories Products

esmAPI GET exacqVision License file and csvfile both returns Internal Server Error 500

Description

esmAPI GET exacqVision License file and csvfile both return 500 internal server error

<br>

Version Introduced

v4.2.0.97638

<br>

Platform

*All

<br>

Steps to reproduce

  • Using ESM API get exacqVision licence file
  • using ESM API get exacqVision license csvfile

<br>

Expected result

license file is returned with HTTP status code 200

license csv file is returned with HTTP status code 200

<br>

Actual result

On both occasions Internal Server 500 Error is returned

<br>

Work Around

Use ESM IU to download exacqVision server license csvfile/file

Use exacqVision Client to Download exacqVision Server license csvfile/file

<br>

Version Fixed

none

<br>

Keywords

esmAPI

<br>

Categories
Knowledge Support Support exacqVision Server Categories Products

Onvif with incorrect profile parameter in host name would crash server

Description

Onvif plugin does allow additional parameters in the host name for added supports. Such as profile/tranport settings(#Profile=1 or #transport=udp). Profile expects a number but would crash the server if a string is entered.

<br>

Version Introduced

r38461

<br>

Platform

All

<br>

Steps to reproduce

connect onvif camera with host name and profile with string.

example: 10.16.1.1#profile=test

<br>

Expected result

string in profile is ignored and defaulted to the first profile.

server does not crash.

<br>

Actual result

server crashes with invalid string entry.

<br>

Work Around

remove profile entry or reconnect with valid profile number.

<br>

Version Fixed

r103382 dev build 8.1.8.103450

<br>

Keywords

Onvif

Categories
Knowledge Support exacqVision Enterprise Support Categories Products

esmAPI POST to upload/apply server license return 500 Internal server Error

Description

ESM API ability to upload and apply server license is not working.
An attempt to use the API to use the apply server license will return a 500 Internal Server Error.

<br>

Version Introduced

v4.2.0.97638

<br>

Platform

All platforms

<br>

Steps to reproduce

Use ESM API to apply exacqVision Server license

<br>

Expected result

ESM API response should have HTTP status code 200, with the applied/scheduled to be applied license detail on data.

<br>

Actual result

ESM API response returns Internal Server 500 Error

<br>

Work Around

Use ESM UI (server degtail/server list page to schedule/apply exacqVision Server License

Use exacqVision Client to apply exacqVision Server

<br>

Version Fixed

4.5.2.103025

<br>

Keywords

esmAPI

Categories
Knowledge Support Support exacqVision Server Categories Products

ArchivePI fails to purge old archives for space

Description

When at-most archive expiration was introduced in 2016-09, it introduced a defect in the operation that deletes-for-space. When no expiration is configured (as will be the case for all existing customers), the delete-for-space will be incorrectly skipped because nothing will be expired (obviously), and the archive target will be stuck at full. They will then cease to archive anything new.

<br>

Version Introduced

Affects versions 7.9.33 through 8.1.6, and RCs 8.0.0/8.0.1

<br>

Platform

All

<br>

Steps to reproduce

  • Configure archiving (free run will accelerate condition). Do not configure expiration.
  • Allow archive target to fill.
  • Once full, recorder will routinely attempt to delete oldest content on target to make space for archiving newer content.

<br>

Expected result

Successful deletion of oldest, continued archiving of newest, no archive task errors.

<br>

Actual result

No longer delete oldest content, no archiving of newest, task repeatedly fails with PURGE_FAILED and never proceeds, repeated log message pair:

9/12/2016 12:07:29 PM ArchivePI Warning Archiving error – ran out of target space
9/12/2016 12:09:27 PM ArchivePI Warning Archiving task error status PURGE_FAILED

<br>

Work Around

Configure expiration slightly less than the day capacity of your target, and expiration will actually provide analogous behavior.

Upgrade to fixed version 8.0.2.

<br>

Version Fixed

8.0.2

<br>

Keywords

at-most, archive, expiration, archivePI

Categories
Knowledge Support Support exacqVision Server Categories Products

Sony generates excessive configuration events with invalid ntp server

Description

sony generates excessive configuration events with invalid ntp server

<br>

Version Introduced

v3.3.3.15350

<br>

Steps to reproduce

enable an ip camera time server override with characters requiring url encoding

<br>

Expected result

time server override value is set in camera

<br>

Actual result

plugin continuously fails to update camera

<br>

Work Around

configure the ntp server using the camera’s web interface

<br>

Version Fixed

none

<br>

Keywords

Sony NTP

Categories
Knowledge Support Support exacqVision Mobile Categories Products

iOS sometimes shows a magnifying glass on long press

Description

iOS sometimes shows a magnifying glass on long press.

<br>

Introduced Version

  • Exacq Mobile 3, version 3.0.0

<br>

Fixed Version

  • Exacq Mobile 3, version 7.9.8

<br>

Platform

iOS

<br>

Steps to reproduce

  1. Enter text into a jquery mobile text input
    • This includes all places where you can input text except the security integrations login dialog and the filter boxes on list search and system alerts pages
  2. Go to the live page
  3. Long press on a video panel

<br>

Expected result

An iOS magnifying glass is not shown.

<br>

Actual result

An iOS magnifying glass is shown.

<br>

Work Around

None

<br>

Categories
Knowledge Support Support exacqVision Server Categories Products

IPCamDetect crashes on Una server when camera disconnected from port during discovery/addressing

Affected platforms

exacqVision Server 7.4 on Una LC servers

<br>

Description

When a discovery scan and auto-addressing is interrupted by unplugging a camera from the Una POE ports or the port is power cycled, IPCamDetect could crash. This can happen when a camera is connected to one of the UNA ports, which triggers an auto scan on the port. Then during the auto-addressing, the camera is unplugged.

<br>

Workaround

None

<br>

Resolution

Update exacqVision Server to version 7.6.2.94278 or higher

Categories
Knowledge Support Support exacqVision Mobile Categories Products

Exacq Mobile 3 missing push notifications settings

In the Exacq Mobile 3 application a user can configure Push Notifications in the Push notifications sections of the settings page.

The following are the scenarios where the Push Notifications settings will not be shown and the user will not be able to use the Push Notifications feature of the Exacq Mobile 3 application:

  1. [Browser] The user is running the mobile application in a browser.

    We do not support push notification for browser based instances of the mobile application.<br><br>
  2. [Android] The user is running an Exacq Mobile 3 application that was installed from Amazon app store for Android.

    Push Notifications are only supported on Android devices that install the Exacq Mobile 3 application from Google Play.<br><br>
  3. [Android or Windows Phone 8] The application was unable to register with the either the Google Cloud Messaging Service or the Microsoft Push Notification Service.<br>
    This might be encountered if the user started the application while not connected to the internet.

    If the user does not see the push notifications settings they can try the following steps to correct the issue:
    1. Exit the application by pressing the ‘Back’ button on the device until the Exacq Mobile 3 application is no longer shown.
    2. Verify that the device can connect to the Internet by navigating to an external website such as https://www.exacq.com.
    3. Open the Exacq Mobile 3 application.<br><br>
  4. [iOS] The user is on an iOS device that has disabled push notifications for the Exacq Mobile 3 application.<br>
    To verify this and enable push notifications on iOS devices perform the following steps.
    1. Open the iOS settings app
    2. Scroll to the bottom of the page and find the “Exacq Mobile 3” entry in the list
    3. Click on the “Exacq Mobile 3” list item
    4. You should now be on the Exacq Mobile 3 settings page
    5. Click on the “Notifications” list item
    6. You should now be on the Notifications settings page
    7. Ensure that the “Allow Notifications” item is in the ‘on’ position
    8. Close the Exacq Mobile 3 application by pressing the home button on the iOS device 2 times and swiping up on the application window.
    9. Open the Exacq Mobile 3 application.

<br>

Categories
Knowledge Support Support exacqVision Client exacqVision Server Categories Products

Frequent Restarts on Linux Systems Archiving over Slow Network

Linux-based exacqVision servers could reboot frequently in certain conditions:

  1. Linux operating system
  2. Active hardware monitoring
  3. Archiving over a slow network (WAN or other network with limited resources)

This issue was fixed in version 6.3.33.65575, and it is available in public release 6.4.

To work around this issue in affected versions, complete the following steps to configure an archiving SMB share:

  1. In exacqVision Client, delete the currently enabled archive task. DO NOT disable the archive target.
  2. Open the /etc/fstab file on the server for editing.
  3. Locate the line with mount paths for the archive target.
  4. Add a flag to the comma-separated section of the line specifying other flags (normally, this should immediately follow rw). The flag added depends on the Linux kernel version used:

    Linux kernel 3.0-3.1 (archiving performance will be impacted)

    //10.16.2.4/disk1 /mnt/10.16.2.4.disk1 cifs _netdev,username=admin,password=admin256,rw,forcedirectio 0 0

    Linux kernel 3.2-3.7 (archiving performance will NOT be impacted if oplocks are supported on the archive target)

    //10.16.2.4/disk1 /mnt/10.16.2.4.disk1 cifs _netdev,username=admin,password=admin256,rw,strictcache 0 0

    Linux kernel 3.8 and later

    //10.16.2.4/disk1 /mnt/10.16.2.4.disk1 cifs _netdev,username=admin,password=admin256,rw,cache=strict 0 0
  5. Save the changes to the /etc/fstab file.
  6. Via shell terminal, execute umount [share path]. For example:

    sudo umount /mnt/10.16.2.4.disk1
  7. Via shell terminal, execute sudo mount -a.
  8. Verify that step 5 was implemented correctly by executing cat /proc/mounts in the shell terminal and locating the line corresponding to the share (such as “directio” if you used the forcedirectio option for kernel 3.0-3.1).
  9. In exacqVision Client, re-create the archive task.