It has been observed that on some Q-Series Hybrid servers the exacqVision Server service will crash immediately after applying name changes to the System Audio Input/Outputs.
See trac ticket #23291 for additional information.
In rare cases, a camera’s firmware might not provide valid video as the first profile, causing the ONVIF plug-in to crash and producing a log message of “profile 0 missing video encoder configuration.” This was specifically observed with an APAC camera running version 1.1 firmware. This could affect exacqVision Server 6.2.x and later.
<br>
As a workaround, specify a valid profile with the IP hostname:
10.16.10.224#profile=1
10.16.10.224#profile=2
Windows
<br>
If a page file does not exist on a Windows-based exacqVision system, one or more of the following symptoms may be encountered:
exacqVision Server watchdog log message found in the server log. For example, 7/5/2015 12:02:54 AM tDVRpi Warning tDVR 0 proc 1 err -21 watchdog expired at 2015-07-05 04:00:28
Crash dump is present in the \Server\logs directory. If not corrupt, the dump indicates exception code 0x40000015
Event Log message ID 2004 for Resource Exhaustion is found in the System Event Log
Page File is disabled (see steps below to determine page file setting)
<br>
To resolve this problem, enable System page file by performing these steps:
exacqVision Server version 7.0.3 or earlier, on Windows systems
<br>
If the system drive free space falls below 100MB or exacqVision need to delete old audit logs to honor the maximum days setting, exacqVision will attempt to prune the audit trail logs and can crash if any audit log files are locked open by another process.
<br>
Do not set a maximum audit log retention time, and ensure the system has more than 100MB of free space on the system drive.
<br>
Update to exacqVision Server 7.2.0.85081 or higher
exacqVision 5.4 or later
<br>
When certain cameras are connected using the ONVIF plugin and the plugin is configured to use metadata streaming to receive motion and alarm events, a memory leak is possible. If memory usage increases enough exacqVision can crash. The crash is typically in ntdll which show a heap memory issue.
To validate this issue is the root cause of a crash, stop the Onvif plugin from requesting a metadata stream as described in the workaround.
<br>
Edit the /exacqVision/server/onvifnvcpi.json file to remove the manufacturer’s entry. This will result in the loss of motion-based recording, so modify the recording schedule to use free run recording.
<br>
No fix at this time.
Server crashes when deleting a UDP serial port. The crash happens for both the stand-alone UDP serial port or the Neo internal serial port.
<br>
8.4
<br>
Workaround is to disable the UDP serial port before deleting it. To disable a stand-alone UDP serial port, set the usage type to None. To disable the integration serial port, disable the integration connection.
<br>
8.5.x.
In exacqVision 5.4 and earlier, the following configuration can cause an exacqVision system to crash:
*On the Add Systems page, the Use Single Sign-On option is selected for the server.
*The LDAP tree that the system uses for authentication contains other LDAP servers that serve sub-trees.
*One or more the sub-tree LDAP servers aren’t running or aren’t allowing connections, which makes those parts of the LDAP tree unsearchable.
If a crash report is enabled and available, you will see that the “core” crashed in nsldap32v60.(dll/so).
NOTE: Starting with exacqVision 5.6, this configuration should not cause a system crash.
<br>
Certain-LDAP-Condition-Causes-exacqVision-Crash.pdfExacqVision Server crash dumps can be found in the server log folder, typically C:\Program Files\exacqVision\Server\logs. The location of ExacqVision Client crash dump files varies based on the operating system. <br>
