1 2 Previous Next 29 Replies Latest reply on May 8, 2019 2:18 AM by Ray_handels Go to original post
      • 15. Re: Appvolumes 2.16 has been released
        KjellO Enthusiast

        Hi,

         

        The main issue was our oldest AppStacks captured with 2.9 Agent, these would cause logon delays, timeouts with App volumes Managers and sluggish performance.

        VMware informed that we should have atleast upgraded AppStacks to 2.13 Agent, so we upgraded all to 2.15 (around 80 AppStacks * 5 minutes per AppStack since you are just performing upgrade and not doing any changes).

         

        BTW, Microsoft have fixed the MSI issues in March updates so no point in not updating Windows. Works as normal with 2.15 so I don’t see why it should not work with older versions.

         

        • Addresses an issue that may cause users to receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files.

         

        /Kjell

        • 16. Re: Appvolumes 2.16 has been released
          bcross64 Novice

          I was able to do some testing on this. The "type" column is there in my 2.15 environment, but it is null. This did not change when doing a fresh install of App Volumes Manager with no existing install of App Volumes Manager present on the server or when doing an upgrade. I never saw Appstack as a value in that column. My upgrade was a success.

          • 17. Re: Appvolumes 2.16 has been released
            Anobix67 Enthusiast

            Interesting bcross64, so your upgrade went just fine and you could still see the old appstacks in the list?

             

            That's good to hear if so, maybe something else is causing the issue to happen for others that have tested it. Possibly the number of upgrades done in their environment versus starting from a newer version (our PoC setup started at 2.14, for example). I haven't done the upgrade yet for the fear of what others have said.

            • 18. Re: Appvolumes 2.16 has been released
              bcross64 Novice

              My environment started with 2.14 if I remember correctly. I installed 2.16 fresh on a new server first and then upgraded the existing installs. Maybe that helped. Uninstall and install would probably do the same thing.

              • 19. Re: Appvolumes 2.16 has been released
                Ray_handels Master
                Community WarriorsvExpert

                The issue is not in the manager itself but in the database. As said, if you have the value AppPackage in the column type in the table snapvols and you upgrade to version 2.16 you wont be able to see these appstacks in the manager unless you change that value.

                If the value in all of those rows is NULL you can safely upgrade (at least, it seems like that). Still, if you cannot see the appstacks, you can always downgrade to 2.15 manager just as long as you don't overwrite the database.

                 

                My guess is that it only happens when you have an older database (or database created/upgraded with an older version of Appvolumes manager). Still check this for yourself, before upgrading make sure to back-up the database (as always).

                • 20. Re: Appvolumes 2.16 has been released
                  LukaszDziwisz Enthusiast

                  Ray,

                   

                  This is what I have in my Snapvol table

                   

                   

                  does it mean that we should be fine upgrading to 2.16?

                  • 21. Re: Appvolumes 2.16 has been released
                    Ray_handels Master
                    vExpertCommunity Warriors

                    You should check the value of all columns of your appstacks. The only thing this printscreen shows you is that the default value of that record will be NULL or doesn't need to have a value.

                    Just do the following query and see what happens

                     

                    select * from snapvols

                    where writable <> 1  (only if you have writables)

                    and type is not null

                     

                    If you have 0 rows returned your good to go. As stated before, make a back-up of the database, you can always revert back to version 2.15 manager if you do not overwrite the database and do this at your own risk, I'm not a VMware employee...

                    • 22. Re: Appvolumes 2.16 has been released
                      LukaszDziwisz Enthusiast

                      Great thank you Ray, I have checked the query and I have no rows affected. Thank you for your help

                      • 23. Re: Appvolumes 2.16 has been released
                        dbrutus Enthusiast

                        Which March update fixed it exactly? I recently installed April 9 (KB4493509)  and I'm still seeing the issue. And it seems like if I don't install that update, it breaks modern authentication for Office365.

                        • 24. Re: Appvolumes 2.16 has been released
                          sjesse Master
                          vExpert

                          I'm testing 2.16 in our environment that uses vhd attachments instead of vmdk attachments, and it looks like spaces in the appstack names fail to attach. This did work in 2.15 , and I haven't tested a vmdk yet.  Looks like it isn't adding %20 anymore as the error says

                           

                           

                          Which I has appstack test as the volume name. I'm opening an SR, but figured I'd share here as well.

                          • 25. Re: Appvolumes 2.16 has been released
                            Ray_handels Master
                            Community WarriorsvExpert

                            What happens if you do an update and use an underscore instead of the space?

                            • 26. Re: Appvolumes 2.16 has been released
                              sjesse Master
                              vExpert

                              I'll have to try that, I was able to make one without a space an everything worked fine, and a new one with an underscore. We've always had always encoded the file names to replace them and other characters. Luckily I only have a few appstacks in this case, I'm  hoping it doesn't show up in our main production one that uses vmdk mounts, as there are quite a few,

                              • 27. Re: Appvolumes 2.16 has been released
                                SchwarzC Enthusiast

                                We did do the upgrade to 2.16 and all went fine (new-installation), but I see now that certain users are getting their AppStacks deattached after some time and our vRealize goes crazy now. Is there a new timeout in 2.16 that de-attaches after some time?

                                • 28. Re: Appvolumes 2.16 has been released
                                  vXav Hot Shot
                                  vExpert

                                  So from 2.13.2, would you recommend to upgrade to 2.15 then to 2.16 ?

                                  Or will it make no difference?

                                  • 29. Re: Appvolumes 2.16 has been released
                                    Ray_handels Master
                                    Community WarriorsvExpert

                                    I would suggest testing it. There is no official statement saying you would need to go to 2.15 first, right?

                                    It all depends on how your database is build up. If upgrade on test goes well I don't see any apparent reason not to upgrade to 2.16 directly

                                    1 person found this helpful
                                    1 2 Previous Next