Press CTRL+K to open search

Pharos Blueprint: Secure Release Service Will Not Start Because The SQLite Database Is Corrupt

  • Updated on Oct 19, 2026
  • Published on Feb 28, 2024
  • 2 minute(s) read
Prev Next

Overview

The Pharos Systems Secure Release Service may fail to start when its local SQLite database is corrupt, empty, missing required tables, or incompatible with the installed service version.

This article covers Blueprint 5.0 through Blueprint 5.4 environments, including cases where the service reports that the database version does not match the expected version.

Applies to

  • Pharos Blueprint Enterprise 5.0 and later

  • Blueprint 5.4 Update 4.1

  • Pharos Systems Secure Release Service

  • Blueprint Collector servers

  • Environments using the local Secure Release SQLite database

Symptoms

One or more of the following symptoms may occur:

  • The Secure Release Service will not start.

  • The Pharos Systems Job Service will not start on older Blueprint installations.

  • Blueprint health checks report that Secure Release or related services are not running.

  • The Windows Application Event Log reports an SQLite error such as:

    - file is encrypted or is not a database

    - database disk image is malformed

    - The Secure Release database version '1.0' does not match the expected current version '4.1'

  • The SQLite database opens as empty or does not contain the tables required by Secure Release.

  • Restarting the server or restarting the Pharos services does not resolve the issue.

Cause

The local SQLite database used by Secure Release has become corrupt or structurally invalid.

The triggering event may be related to a failed write from the in-memory database, an abrupt server shutdown, disk or file-system problems, or security software interfering with the database write. In some cases, the available logs cannot identify the exact triggering event.

Resolution

Important: Stop and preserve the affected database files before attempting recovery. Database replacement can affect held print jobs on the affected Collector.

  1. Stop the Pharos Systems Secure Release Service. On Blueprint 5.0 systems, stop the Pharos Systems Job Service if it is the service using the affected database.

  2. Collect the Blueprint logs and the Windows System and Application Event Logs.

  3. Navigate to the Secure Release database folder, normally: C:\ProgramData\PharosSystems\SecureRelease\Database

  4. Back up the existing database file and any .bak file to a separate location. Do not delete the backups.

  5. If another working Collector has a compatible Secure Release database, follow the existing database-replacement procedure and use a database from the same Blueprint version.

  6. If the affected database is empty, missing required tables, or no compatible working database is available, contact Pharos Support before continuing.

  7. Under Support direction, use matching Blueprint installation media to restore a clean Secure Release database file.

  8. Confirm that the restored database file is in the expected Secure Release database folder and that its permissions allow the Secure Release Service to access it.

  9. Start the Secure Release Service.

  10. Confirm that the service remains running and that Blueprint health checks no longer report the Secure Release failure.

  11. Submit a test page to a printer managed by the affected Collector.

  12. Confirm that the test job appears, can be released, and completes successfully.

Important: Do not copy a database from a different Blueprint version, delete the only available database copy, or remove the .bak file until Support confirms that the backup is no longer required.

Validation

The recovery is successful when:

  • The Secure Release Service starts and remains running.

  • Blueprint health checks report the service as healthy.

  • New print jobs can be submitted to the affected Collector.

  • Jobs appear at the release device.

  • A test job can be released successfully.

  • The customer confirms normal printing behavior.

Notes

  • The case was resolved by restoring a valid SQLite database from Blueprint installation media and successfully submitting a test page.

  • The exact cause of the database corruption may not be recoverable from the available logs.

  • Preserve the original database and event logs for Support analysis.

  • Blueprint and Uniprint are separate products. Do not apply this procedure to Uniprint without confirming the applicable product documentation.

Related articles