Tag: Fail

Categories
exacqVision Server Categories Products

Pelco Motion Notification Could Fail on exacqVision System with Windows Server 2012

A Pelco Pro Sarix camera (IMP-1110) failed to send motion notifications on a Windows Server 2012 system running the the Explicit Congestion Notification (ECN) service. The ECN service and Pelco plugin use the same TCP port 8575; if the ECN starts automatically after system startup, the notification subscription from the Pelco plugin can fail, meaning that motion detection notifications are not sent from the camera.

<br>

As a workaround, stop the ECN service in Windows Server 2012. The Pelco plugin could be changed to use a different listener port in a future release.

Categories
Knowledge Support Support exacqVision Server Categories Products

tDVR board fails to initialize after cold starting a system

Symptom

When starting a system from power-off the tDVR board fails to initialize, causing one or more of the following symptoms:

  • Blinking red LED lights near the processor.
  • Device Manager misreporting an 8008, 8016, or half of an 8032 as hardware ID 8000 in the Device Properties detailt tab.
  • Ispci not listing an Exacq Technologies 8008, 8016, 8032 device at all.

<br>

Affected platforms

All exacqVision systems with tDVR boards using tDVR Hybrid version < 1.2.20

<br>

Workaround

Power the system off, let it sit for 60 seconds or more. Power on the system again.

<br>

Resolution

Install tDVR Hybrid Driver 1.2.20 or greater and update the tDVR board bootloader.

<br>

Instructions:

For Windows:

  1. Download tDVR Hybrid Driver 1.2.20 exe file.
  2. Stop the exacqVision server in the Windows Service Control Manager
  3. Open the Command Prompt and Run “C:\Program Files\tdvr\board_info” -U
  4. View the output to verify that the bootloader was updated to version 1.1.1.665 or greater

<br>

For Linux:

  1. Download tDVR Hybrid Driver 1.2.20 deb file.
  2. Open a terminal session and stop the exacqVision server: sudo service edvrserver stop:
  3. Install the tDVR Setup version 1.2.20 sudo dpkg -i tdvr.deb
  4. Run the bootloader update command: /usr/local/tdvr/board_info -U
  5. View the output to verify that the bootloader was updated to version 1.1.1.665 or greater.
  6. Start the exacqVision server: sudo service edvrserver start
Categories
Knowledge Support Support exacqVision Enterprise Categories Products

Disabling or enabling of a camera will cause ESM importer to crash

Affected platforms

ESM version 3.6.1, trunk builds 3.7.3 through 3.7.5

<br>

Symptom

When a camera is enabled or disabled in the exacqVision client, ESM backend will crash. In the UI in the upper right corner, you will notice servers dropping and reconnecting. Inspection of importer log will show the crash.

<br>

Workaround

Do not disable/enable cameras

<br>

Resolution

Update ESM to version 3.6.2 or later (excluding the 3.7.3 – 3.7.5 trunk builds)

Categories
Knowledge Support Support exacqVision Enterprise Categories Products

ESM does not uniquely display multiple groups with the same name in rules engine

ESM does not uniquely display multiple groups with the same name in rules engine

Effected platforms

ESM 2.6 or greater

<br>

Symptom

When multiple groups with the same name exist, the user may not be able to discern the individual groups when creating rules.

On ESM versions before 3.6, all the servers that are on groups with the same name would be listed under a single displayed group on the server dropdown.

On ESM 3.6 or greater, if the number of servers on ESM are less than 500, the behavior is the same as above. If there are more than 500 servers on that ESM, the user has to click on the group in order to see the servers belonging to it, and clicking on this group shows only servers in one of the groups with that name. It doesn’t show servers in the other group that shares the same name.

<br>

Workaround

Rename groups to have unique names.

<br>

Resolution

None at this time.

Categories
Knowledge Support Support exacqVision Enterprise Categories Products

ESM fails to process events due to server disconnect stop alert rule crashing the importer

Affected platforms

exacqVision ESM 3.7.6 or later

<br>

Symptom

If a rule is created to display an alert when the server disconnected state stops (that is, the server reconnects), the ESM importer will crash when that alert rule fires. To confirm, check the following logs:

Open the log file logfile-importer and look for an entry like the following:
[23/Sep/2015 15:06:45] WARNING [importer:101] Importer processes died for following importer ids: [2]

Next, open the log file corresponding to the importer id, in this case logfile-Importer2. Look for the following error in the log file:

Exception: Error saving

 ‘DisconnectEvent’ object

If this error is found then the ESM importer has failed due to the disconnect stop rule.

<br>

Workaround

Edit the rule to only trigger on a server disconnect state starting, or remove the rule.

<br>

Resolution

Update to exacqVision ESM version 3.8.0.89234 or higher

Categories
Knowledge Support Support exacqVision Enterprise Categories Products

ESM downgrade fails with newly added users

Description

Downgrading ESM from 4.5.10 or newer down to 4.5.9 or earlier can cause the following error. Also the installer fails not able to communicate with database.

ERROR [installer:74] Exception in run_backward_migrations: Traceback (most recent call last):

File "", line 40, in run_migration_command

File "south_utils\run_migrations.py", line 127, in run_backward_migrations

File "south_utils\run_migrations.py", line 45, in run_migration_command

File "site-packages\django\core\management\__init__.py", line 120, in call_command

File "site-packages\django\core\management\base.py", line 445, in execute

File "site-packages\django\core\management\commands\migrate.py", line 222, in handle

File "site-packages\django\db\migrations\executor.py", line 112, in migrate

File "site-packages\django\db\migrations\executor.py", line 168, in unapply_migration

File "site-packages\django\db\migrations\migration.py", line 162, in unapply

File "site-packages\django\db\migrations\operations\fields.py", line 206, in database_backwards

File "site-packages\django\db\migrations\operations\fields.py", line 201, in database_forwards

File "site-packages\django\db\backends\base\schema.py", line 484, in alter_field

File "site-packages\django\db\backends\postgresql_psycopg2\schema.py", line 113, in _alter_field

File "site-packages\django\db\backends\base\schema.py", line 656, in _alter_field

File "site-packages\django\db\backends\base\schema.py", line 111, in execute

File "site-packages\django\db\backends\utils.py", line 64, in execute

File "site-packages\django\db\utils.py", line 98, in __exit__

File "site-packages\django\db\backends\utils.py", line 64, in execute

OperationalError: cannot ALTER TABLE "organization_enterpriseuser" because it has pending trigger events

<br>

Version Introduced

4.5.10

<br>

Platform

ESM with Postgres 9.2

<br>

Steps to reproduce

  • Setup ESM with Postgres 9.2
  • Install 4.5.10 or later
  • Add a new user to ESM
  • Downgrade ESM to 4.5.9 or earlier

<br>

Expected result

Successful downgrade.

<br>

Actual result

Failed downgrade with the error above

<br>

Work Around

  • Connect to db
  • Set ‘last_login’ for all users in table ‘organization_enterpriseuser’

<br>

Version Fixed

4.5.17

Categories
Knowledge Support Support exacqVision Server Categories Products

user-admin fails to update own username on Start system

Description

A user-admin cannot successfully change their own name on a Start system.

<br>

Version Introduced

4.6.3.25895 May 11, 2011

<br>

Platform

All

<br>

Steps to reproduce

On a system with a Start license
Create a ‘test’ user in the User Admin group
Your choice of name and password
Login to the system as the ‘test’ user
Change your username

<br>

Expected result

Expected username to change

<br>

Actual result

Client logged in as admin will see the new username.
Client login attempt with new username will fail.
Can still login with the old username.

<br>

Workaround

Login as ‘Admin’ or a Full Admin user or a different User Admin user.
Change the username.

<br>

Version fixed

8.7.10703

<br>

Categories
Knowledge Support Support exacqVision Enterprise Categories Products

Enterprise user names length check on long names fails

Description

Even though the default max user name length on Django base classes is set to 30, ESM code attempts to override it with a max length of 255. However, while actually trying to create user names longer than 30, ESM fails with the database save length check error. For example, this error can be recreated when attempting to login with a LDAP, with ESM trying to create long user name ‘abcdefghijklmno@cfsad.com (domain)’ in the database

<br>

Tested version

4.9.23

<br>

Platform

All

<br>

Steps to reproduce

Attempt to login into ESM from the client’s ‘Synchronize with ESM’ page using a LDAP name that is longer than 25 (will be > 30 by the time ESM appends ‘(domain)’ to the user name).

<br>

Expected result

User login succeeds

<br>

Actual result

User login fails with a client pop up “Please check your URL”.

<br>

Workaround

None

<br>