Community and Support

            Instructions to apply the Upgrade Pack while using MS SQL server as back end database

            Instructions to apply the Upgrade Pack (MS SQL server as back end database)


            1. In Windows, right-click the PMP tray icon and then click "Exit"
            2. Shutdown both Password Manager Pro primary and secondary services, if running
            3. IMPORTANT: Take a copy of the entire Password Manager Pro installation folder before applying the upgrade pack and keep it in some other location. If something goes wrong with the PMP upgrade, you can rely on the copy. All your settings will remain intact. Additionally, take a backup of the PMP database.
            4. If you have configured High Availability, login to MS SQL Server management studio and delete the following files/folders as explained in the screenshots below: (If High Availability not configured, skip this step)

            If you have configured High Availability, before applying the upgrade pack, PMP requires that the 'subscriptions' and 'publications' related to PMP replication data be deleted AND 'publishing and distribution' be disabled. To do these, carry out the steps below:

            • Deleting Subscription

              First, navigate to Replication >> Local Publications >> <Name of PMP database:PMP-HA>. You will see a file with <PMP server name>. <Name of PMP database>. Right click the file and press 'Delete' in the menu.




            • Deleting Publication

              Then, navigate to Replication >> Local Publications >> <Name of PMP database:PMP-HA>. Right click the folder <Name of PMP database:PMP-HA> and press 'Delete' in the menu.


            • Disabling Publishing & Distribution

              Then, right click the 'Replication' folder and click the option "Disable Publishing and Distribution"




            Applying Upgradepack

            1. The upgrade Pack is to be applied through a tool named UpdateManager bundled with PasswordManager Pro. Navigate to <PMP_Installation_Folder>/bin directory and execute UpdateManager.bat (in Windows) or sh (in Linux) to start the Update Manager.
            2. When configuring the MS SQL server as the backend database for PMP, if you have chosen the option to use 'Windows Authentication', you need to start the command prompt using the service account with which the PMP service has been configured to connect to the SQL server (that means, instead of running as administrator, you need to run as the service account). To check which service account has been configured, navigate to <PMP-Installation-Folder>/conf directory and open the file database_params.conf. Search for the word 'password' in this file. If you find this entry, it means that you are just running as 'administrator' and you have to start the command prompt as administrator. In case, you do find 'password' at all, search for 'username'. The value against this provides you the name of the service account.
            3. If you are applying multiple upgrade packs one-by-one, exit the Update Manager tool after applying one upgrade pack and make sure that the database process is not running. Then proceed with running the Update Manager tool to apply the next upgrade pack and so on
            4. Click Browse and select .ppm file that you downloaded. Click Install to install the upgrade pack. Wait until the upgrade pack is fully installed. [Normally, it takes a few minutes for PPM installation]
            5. Click Close and then click Exit to exit the Update Manager tool. If you are applying more than one upgradepack, apply them one-by-one and follow this step after applying each upgrade pack
            6. After applying the upgrade pack, check if database process is running. If it is running, terminate that process
            7. Start the PasswordManager Pro server / service
            8. Once you upgrade to the latest version, the High Availability or Failover Service set up has to be reconfigured again. The old HA or FOS set up will not work. In addition, the existing secondary server has to be uninstalled and a new secondary server has to be installed. You may download a fresh, full build and install it as SECONDARY.
            Help us to make this article better
            0 1