SQLite Repository File Corruption

[EY_C]

Dear Qlik Support,

We encountered an issue where the Qlik Replicate service failed to start due to a corrupted repository file:
D:\Replicate\data\GlobalRepo.sqlite.

Based on our log analysis, the last successful execution was recorded at:
2025-04-02 10:51:17.
However, just a few minutes later, at 2025-04-02 10:56:11, the system reported a failure to connect to the SQLite repository, and the service stopped with the following error:

[ERROR] REPO-E-FACSQLREP, Failed to connect to SQLite repository 'D:\Replicate\data\GlobalRepo.sqlite'.

Additionally, we noticed an earlier warning in the log on 2025-03-31 15:21:05 indicating a TLS-related error:

[WARN ] The underlying connection was closed: An unexpected error occurred on a send.
System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send.
---> System.IO.IOException: Authentication failed because the remote party has closed the transport stream.

We would like to confirm the following:

1. Could this TLS-related communication error have contributed to the corruption of the GlobalRepo.sqlite file?

2. What are the recommended actions for recovering from this issue and preventing it in the future?

Thank you for your assistance.

[john_wang]

Hello @EY_C ,

GlobalRepo.sqlite is the import repository file used by Qlik Replicate.

TLS-related communication errors do not affect this file; however, issues such as a full disk or random disk errors could potentially impact it.

Please try the following steps:

1. Stop the Qlik Replicate services.

2. Copy the GlobalRepo.sqlite file to another drive or folder, and then rename the original file.

3. Copy the backup file (from the other location) back to the original folder.

4. Restart the Qlik Replicate services and check if the issue is resolved.

If the problem persists, please open a support ticket and attach the files from the DATA folder. Our support team will be glad to assist you further.

Regards,

John.