2 Replies Latest reply on Dec 20, 2018 12:22 PM by Anandakrishnan

    Upgrade App Vol manager from 2.13 to 2.14

    Intox5 Lurker

      Author :

      URL : http:////docs.vmware.com/en/VMware-App-Volumes/2.14/com.vmware.appvolumes.install.doc/GUID-D97EDB98-378D-442F-A884-7D02E47F6C48.html

      Topic Name : Upgrade App Volumes Manager

      Publication Name : VMware App Volumes Installation Guide

      Product/Version : VMware App Volumes/2.14

      Question :

      After the upgrade I can see the dashboard page but all of the other tabs I get a spinning wheel and they never open. I noticed on the dashboard page that the update to 2.14 at the bottom was correct but the "Licensed to: App Volumes 2.13 production license" was still 2.13. I ran the install using as admin.

        • 1. Re: Upgrade App Vol manager from 2.13 to 2.14
          Ray_handels Master
          Community WarriorsvExpert

          The fact that you are able to log in means that the database is up and running, otherwise you couldn't connect to it.

          We did the exact same upgrade and haven't had any issues with upgrading the manager,


          This may sound stupid but did you try with another browser?

          And regarding the licensing, this is just a key with a specific name that adds a number of users that you can add in Appvolumes. You could download a new license file from the website but to be honest it is no really needed, the name is no indication for the license itself. As long as you see correct info on the dashboard there's no need to worry about the license.

          • 2. Re: Upgrade App Vol manager from 2.13 to 2.14
            Anandakrishnan Novice
            VMware Employees



            Try to access the AppVol manager window directly from AppVol server and check whether you can able to access. Reset cookies and cache from browser and then try access.


            Stop AppVol services from AVM server and login to DB and refresh AppVol DB then try accessing dashboard.


            If not then try to check in the logs.