Possible Causes of System Errors and Warnings

NOT AVAILABLE IN SAAS

The table below is intended to explain the possible causes of the system errors and warmings displayed in the System Health Transaction Log grid.

#	Warning/Error Event	Cause	Action
1.	The underlying provider failed on Open. Connection already open.	The connection to the database was lost due to any of the following issues: network issues. high CPU and RAM usage on the database server. the password of the user under which you are connected to the database was changed.	Check the network and the connection between Syteca Application Server and the database server. Check the load on the database server computer. Check the user under which you are connecting to the database, as the password may have been rotated (where the password can be changed by using the Database Parameters (DbSetupToolUI) application).
2.	Running out of free space/Insufficient free space.	If the location where the Syteca data is stored has an average of less than 2.5 GB of free space available for each Client machine, the notification "Running out of free space" will start being added to the System Health Transaction log regularly. e.g. if there are 10 Clients installed on your system, then there needs to be a total of at least 25 GB of free space in the storage location, so that these notifications will not occur.	How Can I Fix the Warning Notification in the System Health Transaction Log: “Running out of free space”?
3.	An error occurred while updating the entries. See the inner exception for details. An error occurred while updating the entries. See the inner exception for details.	This error message is displayed when the system failed to write some record to the database. There are various reasons for this message, such as a transient error or connection issue between Syteca Application Server and the database server.	Check the network, and the connection between Syteca Application Server and the database server. Check the load on the database server computer. Check the user under which you are connecting to the database, as the password may have been rotated (where the password can be changed by using the Database Parameters (DbSetupToolUI) application).
4.	Error managing cluster: Failure setting up connection. A transport-level error has occurred when receiving results from the server.	A transient error, also known as a transient fault, is an error that may resolve itself. Most typically, these errors manifest themselves when the connection to the database server is lost. Also new connections to the server can't be opened. Transient errors can occur, for example, when hardware or network failures occur.	A transient error may be fixed (i.e. resolved) automatically by the system, or when the connection between Syteca Application Server and the database server stabilizes.
5.	An error occurred while executing command definition. See the inner exception for details. A transport-level error has occurred when receiving results from the server.
6.	An error occurred while scanning for the next trigger to fire. A transport-level error has occurred when receiving results from the server.
7.	23505: duplicate key value violates unique constraint.	There are various reasons for displaying this message, and the Application Server logs will contain the required information that may cause the issue.	Some of the errors regarding this message were fixed in recently-released versions of Syteca.
8.	An error occurred while executing command definition. See the inner exception for details. Internal connection fatal error.	This error message is displayed when the system failed to write some record to the database. There are various possible reasons for this message, such as a transient error or connection issue between Syteca Application Server and the database server.	Check the network and the connection between Syteca Application Server and the database server. Check the load on the database server computer. Check the user under which you are connecting to the database, as the password may have been rotated (where the password can be changed by using the Database Parameters (DbSetupToolUI) application).
9.	A Client with GUID and hostname attempted to connect while another Client with the same hostname and GUID was already connected,	This error message is displayed when the Syteca Client has issues with the connection to Syteca Application Server. This can often be due to the use of a VPN, when the Syteca Client cannot properly connect to Syteca Application Server and the "Lost connection" message is displayed in the Client logs. On the other hand, Syteca Application Server may contain information in the logs, that the Syteca Client has already been connected. The Syteca Client is trying to reconnect to Syteca Application Server, and the system detects it as a duplicate.	The issue was potentially fixed in Syteca version 7.0.611.
10.	An error occurred while executing the command definition. See the inner exception for details. ---> Npgsql.NpgsqlException: Exception while reading from stream.	A transient error, also known as a transient fault, is an error that may resolve itself. Most typically these errors manifest themselves when the connection to the database server is lost. Also new connections to the server can't be opened. Transient errors can happen, for example, when hardware or network failures occur.	A transient error may be fixed automatically by the system, or when the connection between Syteca Application Server and the database server stabilizes.
11.	Exception of type "WcfService.Activities. Registraitor.DatabaseUnknownSessionException" was thrown.	This error occurs when data is being transferred from the offline pool for data that has not been registered, or has already been deleted.
12.	<hostname> is in Rescue mode. User activity monitoring is stopped.	This error message is displayed when a Linux Client goes into Rescue mode.	The Linux Client Status after an Application Server Update
13.	The underlying provider failed on Open. 53300: sorry, too many clients already connected,	By default, PostgreSQL has a limitation of only 100 concurrent connections. In this article (see the Action column), the connection logic is described.	How Can I Resolve the Issue with PostgreSQL when the Error is Shown in the Logs: "53300: sorry, too many clients already"?
14.	Error managing cluster: Failure setting up connection. Execution Timeout Expired. The timeout period elapsed prior to completion of the operation, or the server is not responding. The wait operation timed out.	This issue occurs in the event that the system is deployed in High Availability mode, and the second node is not responding.	Check the availability of all Syteca Application Servers in a Microsoft Failover Cluster or the Load Balancer settings.
15.	Cleanup/archiving failed. Reason: The following sessions were not cleaned:	This error may occur for various possible reasons, and the Application Server log file may indicate the exact reason.
16.	A task was canceled.	This error may occur for several possible reasons: A long task was running and the user closed the MT. A long task was running and the Application Server was stopped. A long task was running on the Application Server and was cancelled by being timed out.
17.	The is not enough space on the disk.	This error message is caused due to insufficient free space on the computer with the database server (MS SQL/PostgreSQL) installed on it.	Add more space to your storage location or run Cleanup to remove existing data.
18.	Action: "ITaskListProvider/DownloadGeneratedReports" faulted with message: There is not enough space on the disk.	This error message is displayed in the event that there is no free space available in the storage location where the database is installed.	Add more space to your storage location or run Cleanup to remove existing data.
19.	An error occurred while writing to the binary data store. There is not enough space on disk.	This error message is displayed in the event that there is no free space available in the storage location where the database is installed.	Add more space to your storage location or run Cleanup to remove existing data.
20.	Some data was not copied for destinationPath:	This error may occur during the archiving process, when the session screen captures are located in a folder with an incorrect date.	Check the session start date Client Sessions tab (on the Activity Monitoring page), and open the session that was not archived. Copy the session_id number and find the folder with the session screen captures in the file system, then move the folder with the screen captures to the folder with the correct date.
21.	Action: "IexportService/DeleteForensicExportTask" faulted with message: "ExportRecordWasDeletedMessage"	This error message is displayed in the event that multiple attempts are made to cancel a Forensic Export task (on the Tasks List tab, on the System Health page). Another case may be that there was an attempt to manipulate a Forensic Export entry that has already been deleted.
22.	An error occurred while writing to the binary data store Access to the path is denied.	This error is displayed in the event that the user does not have the permissions required to work with the binary folder.	You need to run the EkranServer service under a specific user, and then share access with the specific user to the binary folder and give full control in the binary folder permissions.
23.	Sending the logs for SIEM integration failed when connecting to:	This error is displayed in the event that the connection with the SIEM system was lost.	Open the Configuration page, and on the SIEM Integration tab, check the values entered in the Network IP address and Port fields. Also check, if the required port is enabled in the firewall settings.
24.	Error retrieving the misfired trigger: 'DEFAULT.MT_340333716052378556' 25P02: current transaction is aborted, commands ignored until end of transaction block.	A transient error, also known as a transient fault, is an error that may resolve itself. Most typically, these errors manifest themselves when the connection to the database server is lost. Also new connections to the server cannot be opened. Transient errors can happen, for example, when hardware or network failures occur.	A transient error may be fixed automatically by the system, or when the connection between Syteca Application Server and the database server stabilizes.
25.	An error occurred while scanning for the next trigger to fire. 53100: could not extend file "base/49037/53946": No space left on device.	This error message is displayed in the event that there is no free space available in the storage location where the database is installed.	Add more space to your storage location or run Cleanup to remove existing data.
26.	An error occurred while updating the entries. See the inner exception for details. An error occurred while updating the entries. See the inner exception for details. DUPLICASTED 53100: could not extend file "base/50127/50430": No space left on device.	This error message is displayed in the event that there is no free space available in the storage location where the database is installed.	Add more space to your storage location or run Cleanup to remove existing data.
27.	An error occurred while scanning for the next trigger to fire. 53100: could not extend file "base/49037/53919_fsm": No space left on device.	This error message is displayed in the event that there is no free space available in the storage location where the database is installed.	Add more space to your storage location or run Cleanup to remove existing data.
28.	DbException while firing trigger Trigger 'DEFAULT.MT_340333716052378556': triggerClass: 'Quartz.Impl.Triggers.SimpleTriggerImpl calendar: '' misfireInstruction: 0 nextFireTime: 05/09/2022 12:28:54 +00:00 53100: could not extend file "base/49037/53919_fsm": No space left on device.	This error message is displayed in the event that there is no free space available in the storage location where the database is installed.	Add more space to your storage location or run Cleanup to remove existing data.
29.	Error updating misfired trigger: '6.59.201.JobRecordCleanup' 53100: could not extend file "base/49037/53946": No space left on device.	This error message is displayed in the event that there is no free space available in the storage location where the database is installed.	Add more space to your storage or run Cleanup to remove existing data.
30.	Unable to detect the storage space. Please define the storage monitoring parameters for the Storage Usage dashboard.	This error message is displayed in the event that there is no free space available in the storage location where the database is installed.	Open the System Health page, in the Storage Usage dashboard settings, enter the exact storage size in the Disk space allocated for the database (GB) field, and save the settings.
31.	The underlying provider failed on Open. 57P03: the database system is in recovery mode.	This error occurs due to Syteca Application Server losing the connection with the PostgreSQL database.	Check the network and the connection between Syteca Application Server and the database server. Check the load on the database server computer. Check the user under which you are connecting to the database, as the password may have been rotated (the password can be changed by using the DBSetupToolUI).
32.	Sequence contains no elements.	This error is displayed when a table (i.e. list or data set) lacks certain data that should be written to the database. This error may be caused for various reasons, e.g. after running a Cleanup operation.	To get detailed information about the cause of the error, you need to download the Syteca Application Server and Management Tool logs, and send them to the Syteca Support team.

NOTE: If you see an error message that is not included in the table above, please contact the Syteca Support team at: info@syteca,com