4) Changing databases for Pleasant Password Server

By default, Pleasant Password Server includes a Securely Encrypted SQLite database on the designated computer. It's possible to replace this database with a different database type.



Have Questions?  Contact Us

Overview - Following the steps below will:

  • Part 1: Prepare a New Database Instance
    • Prepare a fresh database instance on the new database type

  • Part 2: Migrate Password Server Info (Enterprise)
    • The "Restore from Backup" feature will migrate all: Folders, Entries, and Application Settings across into the new database instance.

Supported Databases

See Supported Databases for more information on database types and user size recommendations.

For performance considerations, see when to upgrade the database.

Database Encryption

When changing to a new database, ensure that the database is secured and review these steps to Encrypt your Database.

Create a Backup

Ensure you have created a backup:

Configuring an Alternative Database or Moving a Database

To change or move the database used by Password Server, follow these steps:

  1. Before starting: make sure you've read sections above:
    • Create a Backup,
    • Encrypt your DB (above).
  2. Stop the Password Server service.
  3. Open the Service Configuration Utility (see the steps above in the Backup section)
    • Click Database Configuration & Choose Database Provider:
      • for Azure SQL DB choose MS SQL
    • Enter the Connection String for connecting Password Server to a fresh new database.

    • Click Save Changes and exit the Service Configuration Utility.

  4. Change the Pleasant Password Server Service Account User:

    • Note: This particular setting will not persist in an upgrade! and will need to be updated. Please keep this step in your upgrade plans.
    •  This step can be skipped if using SQL Authentication (connection string has username/password).

  5. Start the Password Server service. This will automatically create all the tables in the database and set up the default admin user.

  6. Login with your browser to your server.

  7. (optional) To restore all your credentials and settings from a previous backup:

  8. Double-check license activation.

  9. See the Troubleshooting section below if necessary.


These settings will persist through future updates of Pleasant Password Server (except step 6).


If you run into any issues with your chosen database please check the items below:

  • Ensure your Firewall or Anti-Virus are not interfering with network traffic
  • Temporarily increase logging details for the Password Server. Restart the service, and review the log outputs.
  • MS-SQL connection specific:
    • SQL Server requires that TCP/IP connectivity is turned on (under SQL Server Network Configuration - Note: restart the server)
    • SQL authentication (userid/password), requires enabling Mixed Mode or SQL authentication (under the Instance properties security)
    • Services are running: SQL Server and SQL Server Browswer (run services.msc)
    • Detailed MS-SQL troubleshooting: see Connectivity issues

  • Problem 1:
    • Error: "The target principal name is incorrect" (found in EventViewer / Log files)
    • Resolution: 
      • Add "TrustServerCertificate=true" to your Connection String
  • Problem 2:
    • Service fails to start, after an upgrade
    • Error in Weblogs file:
      • Cannot open database "CustomerDatabase" requested by the login. The login failed.
      • Login failed for user 'DOMAIN\USERNAME'.
    • Resolution:
      • The database was changed to MS-SQL, and the Service User Account was switched.
      • On Upgrade, this information is lost, and needs to be re-applied.
      • Close the upgrade’s “Starting the service” window
      • Open Services.msc, make the change, and re-start

  • Problem 3:
    • Empty database; no tables
    • Resolution:
      • Double-check the security permissions for the user
      • Double-check that the service account in format: Domain\UserName
        • Note: Pleasant Password Server does NOT currently support authentication with a UPN (User Principal Name) format, i.e. username@domain.


If you continue to experience problems, please don't hesitate to send us your detailed log files (at Contact Us), and let us know your situation.


Previous Versions Notes


Version 3.5.0 or Older

Tag page
You must login to post a comment.