Category: Log Level

Categories
Exclude from Global Search Plugin Log Level exacqVision Enterprise Warning Logs Other

The DELETE statement conflicted with the REFERENCE constraint “auditlogger_auditlog_user_id_fbf03342_fk_organization_enterpriseuser_id”. The conflict occurred in database “NA”, table “dbo.auditlogger_auditlog

The DELETE statement conflicted with the REFERENCE constraint “auditlogger_auditlog_user_id_fbf03342_fk_organization_enterpriseuser_id”. The conflict occurred in database “NA”, table “dbo.auditlogger_auditlog

Description

when the Datarolloff service is failing to start you may see this error or a similar error in the datarolloff log file. There is a foreign key constraint that is failing to delete which in turns stops the service from running, you must delete this constraint manually via the Database

Notes

You must delete the key constraint from the database

Categories
Exclude from Global Search Knowledge Support Plugin Log Level Support Warning exacqVision Server Categories Products Logs NotifyPI

Profile Description: %1. Notification attempt return code= 26

Profile Descriptìon: %1. Notification attempt return code= 26

Description

%1 – This is the name of the Email Message Profile %BR% %BR%

Notifications are sent using curl, so the return codes are curl status/error codes. %BR%

Curl error 26 means “Read Error”

Notes

Notifications which include attaching a clip will attempt to create, then read a file locally on the Server. If there was a failure when the clip was created, you’ll see this error. Also, you could see this error due to a permissions limitation. %BR%
Other curl errors can be found here:%BR%
https://curl.se/libcurl/c/libcurl-errors.html

Categories
Knowledge Support Plugin Exclude from Global Search Log Level Support Warning exacqVision Server Categories Products Logs NotifyPI

Profile Description: %1. Notification attempt return code= 67

Profile Descriptìon: %1. Notification attempt return code= 67

Description

%1 – This is the name of the Email Message Profile %BR% %BR%

Notifications are sent using curl, so the return codes are curl status/error codes. %BR%

Curl error 67 means “Login Denied”

Notes

Failed logins to SMTP servers can result due to username/password problems, or no authentication was supplied and the SMTP Server does not support anonymous connections. %BR%
Other curl errors can be found here:%BR%
https://curl.se/libcurl/c/libcurl-errors.html

Categories
Knowledge Support Exclude from Global Search Log Level Support Warning exacqVision Server Categories Products Logs NotifyPI

Profile Description: %1. Notification attempt return code= 7

Profile Descriptìon: %1. Notification attempt return code= 7

Description

%1 – This is the name of the Email Message Profile%BR% %BR%

Notifications are sent using curl, so the return codes are curl status/error codes. %BR%

Curl error 7 means “Couldn’t Connect”

Notes

Connection failures to SMTP servers result when the TCP connection to a given host/port fails. This could mean a firewall is blocking communication.%BR%
Other curl errors can be found here: %BR%
https://curl.se/libcurl/c/libcurl-errors.html

Categories
Knowledge Support Exclude from Global Search Log Level Support Warning exacqVision Server Categories Products Logs NotifyPI

Profile Description: %1. Notification attempt return code= 28

Profile Descriptìon: %1. Notification attempt return code= 28

Description

%1 – This is the name of the Email Message Profile %BR% %BR%

Notifications are sent using curl, so the return codes are curl status/error codes. %BR%

Curl error 28 means “Operation Timeout”

Notes

Timeouts to SMTP servers can result due to routing problems between the exacqVision Server and the SMTP Server, or a configuration problem, such as using the wrong address/port.

Categories
Plugin Exclude from Global Search Log Level ArchivePI Warning exacqVision Server Products Logs

error 86 (invalid password)

error 86 (invalid password)

Description

If the main server, you are setting up to connect to an archiving target on a s-series is joined to a domain there is a local group policy that needs to be configured or you will get a disconnected status ad error 86 invalid password in the server logs

Notes

KB 12873

Categories
Plugin Exclude from Global Search Log Level exacqVision Client Error exacqVision Server Categories Products Logs StreamPI

LICENSE: Ignore update – unrecognized MAC address.

LICENSE: Ignore update – unrecognized MAC address.

Description

This indicates that the MAC Address registered to the license was not found.

Notes

See suggestions in KB 12830: https://support.exacq.com/#/knowledge-base/article/12830

Categories
Plugin Exclude from Global Search Log Level Warning exacqVision Client exacqVision Server Categories Products Logs StreamPI

LICENSE: Error loading active – Required MAC address missing.

LICENSE: Error loading active – Required MAC address missing.

Description

This indicates that the MAC Address registered to the license was not found.

Notes

See suggestions in KB 12830: https://support.exacq.com/#/knowledge-base/article/12830

Categories
Plugin Exclude from Global Search Log Level Verbose exacqVision Server Products Logs GenericCameraPI

The processing loop has taken too long *** times. The longest time was ***ms for *** passes.

The processing loop has taken too long *** times. The longest time was ***ms for *** passes.

Description

A calculation is made by each camera plugin to determine if network operations ever took longer than 32ms. Once a minute, this data is logged. If it logs that it has “taken too long” this may indicate that the CPU is not able to keep up with the load.

Notes

A plugin that is not connected to any cameras will log this message once a minute and is not concerning.%BR%
Antivirus software may cause a delay in processing data.
The processing loop may take too long during heavy use, such as lots of reconnects to cameras, or many CGI commands (PTZ) and could be a sign that the system (CPU) is not powerful enough to process the current amount of camera data.

Categories
Exclude from Global Search Plugin Log Level Verbose exacqVision Server Products Logs GenericCameraPI

The processing loop performed *** passes and took ***ms to process the data.

The processing loop performed *** passes and took ***ms to process the data.

Description

A calculation is made by each camera plugin to determine if network operations ever took longer than 32ms. Once a minute, this data is logged. If it logs that it has “taken too long” this may indicate that the CPU is not able to keep up with the load.

Notes

Antivirus software may cause a delay in processing data.
The processing loop may take too long during heavy use, such as lots of reconnects to cameras, or many CGI commands (PTZ) and could be a sign that the system (CPU) is not powerful enough to process the current amount of camera data.