> ## Documentation Index
> Fetch the complete documentation index at: https://syteca.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# System Error and Warning Reference
> Causes and recommended actions for the specific error and warning messages that appear in the System Health Transaction Log.
**NOT AVAILABLE IN SAAS.**
The table below explains common error and warning messages logged in the [System Health Transaction Log](/docs/administration/dashboards/system-health-dashboards#view-system-errors-and-warnings).
| Message | Cause | Action |
| ----------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| "The underlying provider failed on Open. Connection already open." | Lost connection to the database — network issues, high CPU/RAM on the database server, or a rotated database user password. | Check network connectivity, database server load, and whether the connection password changed (update it in [Database Parameters](/docs/administration/database/database-parameters) if so). |
| "Running out of free space" | Less than 2.5 GB average free space per Client in the data storage location. | See [Fix the "Running out of free space" warning](/docs/resources/troubleshooting/management-tool-troubleshooting#fix-the-running-out-of-free-space-warning). |
| "An error occurred while updating the entries. See the inner exception for details." | A record failed to write to the database — often a transient error or connection issue. | Check network connectivity, database server load, and the connection user's password. |
| "Error managing cluster: Failure setting up connection." / "A transport-level error has occurred when receiving results from the server." | A transient fault, typically from a lost or newly-failed connection (hardware or network issues). | Usually resolves automatically once the connection stabilizes. |
| "23505: duplicate key value violates unique constraint" | Varies by case — check the Application Server logs for specifics. Several causes were fixed in recent Syteca versions. | Review Application Server logs; update Syteca if outdated. |
| "A Client with GUID and hostname attempted to connect while another Client with the same hostname and GUID was already connected" | Often caused by VPN connectivity issues preventing a clean reconnect — the Client's logs show a "Lost connection" message while the server still considers it connected. | Potentially resolved in Syteca 7.0.611 and later; update if on an older version. |
| "Npgsql.NpgsqlException: Exception while reading from stream" | A transient fault from a lost database connection. | Usually resolves automatically once the connection stabilizes. |
| "DatabaseUnknownSessionException" | Offline pool data is being transferred for a session that was never registered, or has already been deleted. | No action typically required. |
| "`` is in Rescue mode. User activity monitoring is stopped." | A Linux Client entered Rescue mode. | See the Linux Client's [Rescue mode](/docs/administration/clients/linux#yellow-status-icon-rescue-mode) documentation. |
| "53300: sorry, too many clients already" | PostgreSQL's default 100-connection limit was reached. | See [Fix "53300: sorry, too many clients already"](/docs/resources/troubleshooting/postgresql-performance-tuning#fix-“53300-sorry-too-many-clients-already”). |
| "Execution Timeout Expired" (cluster management) | In High Availability mode, a second node isn't responding. | Check every Application Server node in the Failover Cluster or load balancer configuration. |
| "Cleanup/archiving failed. Reason: The following sessions were not cleaned" | Varies — check the Application Server log for the specific cause. | Review Application Server logs. |
| "A task was canceled" | The Management Tool was closed, the Application Server stopped, or the task timed out while a long task was running. | No action typically required unless it recurs. |
| "There is not enough space on the disk" (in various forms, including PostgreSQL `53100: could not extend file`) | No free space on the database server's storage. | Add storage, or run [Cleanup](/docs/administration/deployment/database-management) to free space. |
| "Some data was not copied for destinationPath" | Session screen captures are in a folder with an incorrect date during archiving. | On the Client Sessions tab, find the session's ID and correct date, then move its screen capture folder to the correctly dated folder. |
| "ExportRecordWasDeletedMessage" | Multiple attempts to cancel an already-deleted, or already-canceled, Forensic Export task. | No action typically required. |
| "An error occurred while writing to the binary data store. Access to the path is denied." | The **EkranServer** service account lacks permission to the binary data folder. | Run the **EkranServer** service under a specific user, and grant that user full control over the binary folder. |
| "Sending the logs for SIEM integration failed when connecting to..." | Lost connection to the SIEM system. | On **Configuration > SIEM Integration**, verify the IP address and port, and confirm the port is open in your firewall. |
| "25P02: current transaction is aborted, commands ignored until end of transaction block" | A transient fault from a lost database connection. | Usually resolves automatically once the connection stabilizes. |
| "Unable to detect the storage space" | Storage monitoring parameters aren't defined for the Storage Usage dashboard. | On the System Health page, enter the exact allocated storage size under the Storage Usage dashboard settings. |
| "57P03: the database system is in recovery mode" | Lost connection to a PostgreSQL database, similar to the general connection-lost case above. | Check network connectivity, database server load, and the connection user's password. |
| "Sequence contains no elements" | A dataset is missing data expected to be written — sometimes follows a Cleanup operation. | Download Application Server and Management Tool logs and send them to the [Syteca Support team](https://www.syteca.com/en/support/contact-support). |
For an error not listed here, contact the [Syteca Support team](https://www.syteca.com/en/support/contact-support).
`EkranServer` is a literal system identifier, preserved verbatim from source.
## Related
Where these errors and warnings are displayed and filtered.
Common database connectivity FAQ and fixes.
Collect Application Server logs for deeper diagnosis.