Troubleshooting
- 08 Sep 2023
- 1 Minute to read
- Contributors
- Print
- DarkLight
Troubleshooting
- Updated on 08 Sep 2023
- 1 Minute to read
- Contributors
- Print
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
If you have a problem with the a module, please contact us and provide all of the following:
- Logs
- How to reproduce the issue
- Data to reproduce
Database extract
Extract database SQL Server
Extract Database Postgres
Logs
Depending on which module is affected by the problem, you will have a different log recovery process. Here is the list of the modules troubleshooting module links:
Cross module errors
| ID | Problem | Reason | Resolution |
|---|---|---|---|
| Z-1 | The timeout period elapsed prior to completion of the operation or the server is not responding | There are several potential causes of this error message, including network congestion, server overload, or incorrect network configuration. In some cases, the issue may be resolved by simply retrying the operation after a short delay. | Check the server status, if it is available. Check your login informations. Make sure the database is open and accessible. |
| Z-2 | Invalid column name | The error message indicates that the SQL query that was executed referenced a column name that is not present in the specified table. This can happen if the column name is misspelled, if the column was deleted or renamed, or if the query is referencing the wrong table altogether. | Make sure you have an up-to-date database |
| Z-3 | The timeout period elapsed prior to completion of the operation or the server is not responding | Check the server logs to see if there are any errors or issues that may be causing the server to slow down. | If the issue persists, you may need to consider upgrading the server hardware or software. |
| Z-4 | Unable to read data from the transport connection: Connection reset by peer. | Check the firewall settings: If the client or server is behind a firewall, make sure that the firewall is not blocking the connection. Check the firewall logs to see if any traffic is being blocked or rejected. Check for any network issues such as dropped packets, high latency, or intermittent connectivity. | Try using a different protocol or port: If the issue persists, try using a different protocol or port to connect to the server. For example, if you're using HTTPS, try using HTTP instead, or try using a different port such as 8080 instead of 443. |