Info
Pleasant Password Server
A. Install
Activating Software
Next Steps
Updating Software
Updating Earlier Software Versions
Zero Knowledge Encryption
IIS Hosting
Cloud Hosting
Hardware and Software Requirements
Azure Integration
Redirect HTTP Requests to HTTPS
New Blank Install
Setup Switches
Digital Signatures and Checksum Hashes
Sitemap
Info  >  Pleasant Password Server  >  A. Install  >  Updating Software Page last modified Jan 21 2024, 10:28

Updating Software

Discover how Pleasant Password Server will enhance KeePass for business

We recommend keeping updated with security software upgrades, which can be downloaded from the website. Currently, for added safety precautions, the software will not auto-update itself.

Upgrades and Support are included in your subscription plan (renewed annually). Select to install a software version which was created before your License Expiry date.

Often customers may wish to also: 

Have Questions?  Contact Us 

This article applies to:

  • Versions 7.9.28 and later

  • For older Versions (7.9.27 and earlier):

Related Topics:

Overview:

  • Quick Install: 

    • Check software Prerequisites, e.g. .NET version 4.8.

    • The initial server install is expected to be very quick and takes a few minutes.

    • New version upgrades simply install overtop of the old version.

  • Upgrades - Site Startup: 

    • upgrades entail a database conversion process after the file installation. This means you will notice a long delay initially, when the site starts again (see below for more details). 

  • Steps Below: The steps below provide the complete scenario for detailed change implementation instructions, for the sake of best practices, and to avoid/handle installation issues.

Step 1: Confirm License Subscription

  • Check that the license expiry date includes the date of the version you are installing.

    • Click Check License Status button on License Status page to confirm expiry date in the Store.

  • License Expiry:

    • Expired in the store: 
      • Renew it before you continue to the steps below.
      • Enter your License Key on this page and click Upgrade/Renew
    • Expired in the application: 
      • Simply Re-Activate the license to synchronize the expiry date to your application.

 

  • You may wish to stop the service from running before the upgrade, and to be sure that your users realize the application is down for maintenance.

  • You may also consider upgrading the database on another machine, allowing your users to use the production application with Access Levels set to View Only actions, so that no changes can be made in the interim.

Step 2: Make a backup

Note: There is no way to restore a previous version without a backup.

  • Take a VM snapshot, if you wish

  • Check before proceeding:

    • Backup was successfully completed:

      • Open Event Logging | Logged Events - check that the backup file was created successfully

    • Encryption keys are saved. These are needed for Backup/Restore functionality, or opening encrypted SQLite databases.

      1. Backup encryption key
      2. SQLite: Regular encryption key (from the Connection String in your Service Config utility)

    • Decide if you want to manually save additional files / folders. Reference: Items included in the Database Backup

Step 3: Restart the Machine (Recommended)

  • Machine Restart(s) May Be Required:

    • You may wish to restart the machine, to release any file locks, or to resolve any pending OS updates first before beginning. This will still retain the database and connection information.

    • If the install takes longer than 5 - 10 minutes (before showing Install Successful), then stop, reboot, and restart the install. Note that there will be a delay after this, with the site startup (see below).

    • Some .NET / Framework / OS Files may require this.

  • More Notes:
    • Some delay in the install may be expected after upgrade, when starting up the site (see below).
    • However, an uninstall may be helpful if there were any errors installing. This will still retain the database and connection information.

Step 4: Stop the site / service (optional)

  • You may wish to stop the service from running before the upgrade, and to be sure that your users realize the application is down for maintenance.

  • You may also consider upgrading the database on another machine, allowing your users to use the production application with Access Levels set to View Only actions, so that no changes can be made in the interim.

Step 5: Download and Run the Installer

  • If you are running versions 7.9.27 or earlier: Update an Earlier Version

  • If you are running versions 7.9.28 or later, install these directly:

  • Latest  or Stable version

    • Latest Version contains the newest features and fixes. Some of these features may still be undergoing additional Quality Assurance (not recommended for large enterprise production implementations).

Step 6: Monitor Install Progress

  • There are 2 parts the install:

  • 1. INSTALL FILES - once the files are replaced, you will see: "Installation completed successfully"

    • If this process gets stalled and is not complete in 5-10 minutes:

      - Stop the install and reboot the machine. This is a safe step and with no risk during this update process.
      - Once restarted, begin the install again, so that any previously locked files should now be released. 

  • 2. DATABASE CONVERSION - at site/service startup, the database is the converted to the new version, you will see website is running: 

    Please be patient, as the service may take some time to start while processing changes for the upgrade. This time may depend on the number of releases between version updates with the amount of records to process.

    • During the update, database conversion changes are applied to the database, which may entail many changes, depending on the volume of change between version updates.

    • Monitoring progress:

      You may view progress in the default SQLite database folder: notice the Journal.db file changes - the database will grow to the size of the database file. This will continue until all changes are committed together all at once. If this process is interrupted, all changes are rolled back.

    • Startup delays:

      • We would recommend waiting for awhile and monitoring progress,
      • If there has been years since the last update, you may wish to download and install intermediate upgrades (with one or two Stable Versions found in Historic Versions),
      • Otherwise, see the Troubleshooting steps below.

  • Troubleshooting:

Step 7: Re-apply custom config settings

  • If you have changed advanced custom settings, e.g. Switched Databases, Moved to IIS Hosting, or Applied Custom Config File changes which are not managed in the install/upgrade, re-apply those custom settings now.

    • IIS HOSTING - stop and disable the service
    • CHANGED DATABASE (to MS-SQL, Postgres,...) running with the IISExpress Service - you will need to re-apply changes to the Service Account, and restart the service.

  • Now login to the website.

Step 8: Confirm Site is Started

  • Ensure the site is started and try logging into the web application with the admin account.
    • Reminder: If you have switched to hosting with IIS, then:
      • Ensure the Pleasant Password Server service (for IISExpress) is stopped and disabled.

Step 9: Reactivate License Key

  • Double-check on the License tab that the license displays and is not cleared, if not re-apply it. This is more important when migrating servers.

Step 10: Update KeePass on Client Machines

  • The KeePass client changes frequently, in correspondence with changes on the server. To keep compatible users should have an updated version.

  • Check Client Version Compatibility - on the Release Notes or Compatibility Chart:

    • Compatibility Chart: Enterprises can distribute new KeePass client versions to maintain full compatibility between the Server and KeePass clients

  • Automatic Method: IT staff can distribute the new KeePass version automatically to client machines using the methods listed below:

  • Manual Method: Users can download KeePass from the Client Download tab. This is the version that best corresponds to your Password Server version.

 

Have Questions?  Contact Us

Problems?

Stalled Upgrade

  • File Install:

    • If after 10 minutes the file install is not complete, please restart the machine.
      • Re-starting will unlock any files, or clear out Windows Upgrade processes 
      • The install requires .NET version 4.8, which should now be complete

  • Service Startup:

    • Monitor the upgrade, using the information in "Monitor" step above.

Site Startup problems

License details look wrong

  • Re-activate the license in the web application (License tab) to see any new renewal / license updates. This will show new expiry dates and user counts.

Upgrade Issues

  • Increase your Logging Details, and check if:

    • The Log output files are still changing, which means the Update is still in progress, or,
    • If there are errors.

  • Viewing Windows Events may provide some insight

  • Try clearing the browser cache.

  • Contact Support with your Detailed Logs, and a description of the problem you are seeing.

Changing Servers

Some users may choose to switch servers as part of their upgrade procedure. See Migration Steps, where all information and links are provided.

You can use the Database Backup and Restore feature to migrate your data to the new database. It is recommended to have the same version of the Password Server software running on the new server as on the old server.

However in instances of server failure or incompatibility with new versions, this may not be possible.

In such cases, move your database to the new server and follow the Updating Software instructions.

Further Reference: Items included in the Database Backup

Locating your database file

The default location of the Pleasant Password Server database can be found here: locating your database file.

Previous Versions