Author: Isaac Penrod
Error in executing media test (*** query) for status refresh (error ***)
Description
Indicates there is no media in the Servers DVD/CD drive.
Notes
This message will come up on service start, and if you hit Refresh Status in the Exacq Recall page.
This is a normal message if there is no disk in the drive.
*XXX buffer full state = 0 content true
Description
Unable to buffer larger than 2MB image size. Older version of Server (pre 8.2) had a smaller buffer for video frames.
Notes
Update beyond 8.2, or reduce either the quality or record resolution.
Description
Several customers have reported that exacqVision Servers are spamming the CCure Server with video loss alerts.
Product
- exacqVision Server
- CCure9000
Solution
Investigation of the exacqVision Servers show that no Video Loss events were logged. The Journal View in CCure reports:
"Video Loss alert ended for exacqVision/HDVR Video Camera '%CameraName%' on exacqVision/HDVR Video Server '%ServerName%'"
In some cases, the alarms were reported for events that supposedly happened hours or days off from the time it was logged.
The Software House engineering team is currently investigating the issue and have provided a workaround, see their attached internal Knowledge Base Article for details.
To apply the workaround perform the following:
Put this file, AlarmExclusionConfig.xml, in the location “..\Program Files (x86)\Tyco\CrossFire\ServerComponents”
Restart the HDVR driver service
Note: Please remember to remove the file after an official SP with fix has been installed. A CCure update will not remove or overwrite the file in the folder.
Software House will update accordingly with an official fix via SP the moment they have clarity on this.
>
Starting in 9.6, the web service migrated completely from storing its config in the ini format to json. The config filename has been normalized as well:
- Linux: webservice.conf -> wfe.json
- Located at /etc/webservice/wfe.json
- Windows: WebService.ini -> wfe.json
- Located at C:\ProgramData\Webservice\conf\wfe.json
The name, location, and format of .evws-login (holding web service config credentials and has also changed. .evws-login is now stored as json, has been renamed to .evws-login.json on both platforms, and is located at
- Linux: /etc/webservice/.evws-login.json
- Windows: C:\ProgramData\Webservice\conf\.evws-login.json
Description
Refer to #d17458.
Apparently, DMP intrusion panel model XR550 requires the remote key to be 8 characters long, all capitalized.
If your remote key is less than 8 characters, you need to enter trailing spaces into exacqVision to get 8 characters.
If your remote key contains any lower-case characters, you need to enter capitals into exacqVision in order to connect.
Product
- exacqVision Server
Steps to Reproduce
- Connect to the XR550 using a remote key less than 8 characters.
Expected Results
- The XR550 is connected successfully.
Actual Results
- Connection attempt results in ‘Invalid credentials’
Solution
After entering the remote key, continue adding spaces until the total number of characters is 8.
Description
Servers with Windows 10 or Linux allow bonding to be configured via exacqVision Client.
However, servers with Windows Server 2016 currently do not. Instead, bonding must be configured via Windows Server Manager:
- Start Server Manager.
- Click “Local Server” in left pane of window.
- Locate the “NIC Teaming” item in window, and click its “Disabled” link.
- In the NIC Teaming window, you can add, remove, and edit bonds.
Product
- exacqVision Server
- Windows Server 2016
Expected Results
- NIC Bonding options are available in the exacqVision Client
Actual Results
- NIC Bonding options are not available in the exacqVision Client on systems running Windows Server 2016.
Solution
- Configure NIC bonding using the OS Server Manger
<br>
Description
Exacq Mobile 3, version 19.09, allows a user to subscribe to and receive push notifications for triggered analytic rules.
As part of this feature, showing the details for an analytic notification in the app will show a frame from the associated camera (if there is one) at the time of the event.
In order for this frame to be available, the camera must be configured to record at the time of the event. This is achieved in several ways:
- The camera records on free run.
- The camera records on motion, and the analytic triggers on motion-based events in its video stream.
- An event link is configured on the server for triggers of the analytic rule to cause the associated camera to record.
Product
- Exacq Mobile 3
Expected Results
- Push Notification shows a video thumbnail from the time of the analytic event.
Actual Results
- Push Notification arrives with no video thumbnail.
Solution
- Ensure that a recording rule is active during the times when thumbnails are required for Push Notifications from analytic events. Free-run recording is the easiest solution, but this will increase the storage required for the camera.
<br>