Chris_Nodak Posted July 15 Share Posted July 15 I was cleaning up old packages that have not been in use for some time and I have one that has no attachments that I can find, where the delete option is grayed out. There is a newer package for the application that is set current and is 100% in use by end users. I know I ran into this once some time ago but cannot find a solution while searching. Looking for any suggestions folks may have to help with this. Currently on App Volumes 2209. Quote Link to comment Share on other sites More sharing options...
Robin Harmsen Posted July 16 Share Posted July 16 Does the package still has a Attachements count higher then 0? And you are sure there are no real attachements... Then you will need to update the counter manually in the SQL Database. We have been doing that in the past to fix these kind of issues. I thought there was a KB about this. Quote Senior Engineer (SDDC, EUC, DBA, Applications) at the Netherlands Cancer Institute - Antoni van Leeuwenhoek Hospital (NKI-AVL) Link to comment Share on other sites More sharing options...
Chris_Nodak Posted July 16 Author Share Posted July 16 It does show 6 attachments on the package screen, but none on the attachments tab and all VMs have been maintained since the new package was set current so the 6 is clearly invalid. I vaguely remember this happening before and having to make a change in the DB but have not found the KB on how to update it. I'll dig some more. Thanks. Quote Link to comment Share on other sites More sharing options...
Solution Chris_Nodak Posted July 16 Author Solution Share Posted July 16 https://kb.omnissa.com/s/article/91256?lang=en_US I found the KB article. I was able to mark the package for deletion but it hasn't yet deleted. Will monitor. 1 Quote Link to comment Share on other sites More sharing options...
Chris_Nodak Posted July 16 Author Share Posted July 16 It did delete after some time. Quote Link to comment Share on other sites More sharing options...
Robin Harmsen Posted July 16 Share Posted July 16 6 hours ago, Chris_Nodak said: It does show 6 attachments on the package screen, but none on the attachments tab and all VMs have been maintained since the new package was set current so the 6 is clearly invalid. I vaguely remember this happening before and having to make a change in the DB but have not found the KB on how to update it. I'll dig some more. Thanks. Yea.. only happend a few times for us... so I also was vaguely remembering it had to do with a field in the database 5 hours ago, Chris_Nodak said: https://kb.omnissa.com/s/article/91256?lang=en_US I found the KB article. I was able to mark the package for deletion but it hasn't yet deleted. Will monitor. Good find! 5 hours ago, Chris_Nodak said: It did delete after some time. Glad it worked out for your envrionment Quote Senior Engineer (SDDC, EUC, DBA, Applications) at the Netherlands Cancer Institute - Antoni van Leeuwenhoek Hospital (NKI-AVL) Link to comment Share on other sites More sharing options...
Chris_Nodak Posted July 16 Author Share Posted July 16 I had to do some deep searching in the KB articles. Sadly all the old links don't map with all the changes from VMware to Broadcom and Omnissa. I feel like a lot of great information from the communities has been lost forever. Quote Link to comment Share on other sites More sharing options...
Hans Straat Posted August 19 Share Posted August 19 (edited) We once had VMware engineers messing around in our database but that only deleted it in the GUI. Does this also delete the affected vmdk's etc? Also stopping all appvolume manager services in a 24/7 health environment isn't a workable solution 😞 Edited August 19 by Hans Straat Quote Senior technical specialst at Leiden University Medical Center (lumc) Link to comment Share on other sites More sharing options...
Administrators Radina Ivanova Posted August 19 Administrators Share Posted August 19 On 7/17/2024 at 12:08 AM, Chris_Nodak said: I had to do some deep searching in the KB articles. Sadly all the old links don't map with all the changes from VMware to Broadcom and Omnissa. I feel like a lot of great information from the communities has been lost forever. Hello @Chris_Nodak, sorry to hear you had troubles finding the information you needed easily! The migration of our websites might have created some difficulties in finding the right resource. So, first of all, thank you for sharing about your experience here! I can see from your previous comments that you have successfully found the migrated KB website but I'd like to provide a few links of migrated sites containing all Omnissa resources, as you might find them useful: Product documentation can now be found at https://docs.omnissa.com . A wealth of technical blog posts and resources on Omnissa products at https://techzone.omnissa.com (also linked at the top Forums menu) All the content from the old VMTN forums has also been migrated and is available in a separate subform: https://community.omnissa.com/forums/forum/171-migrated-content/ (can be found in the Forums section) Hope you find this helpful! Let us know if there is a specific resource you're looking for, so we can try to help. Best, Radina Quote Link to comment Share on other sites More sharing options...
Robin Harmsen Posted August 19 Share Posted August 19 (edited) 2 hours ago, Hans Straat said: We once had VMware engineers messing around in our database but that only deleted it in the GUI. Does this also delete the affected vmdk's etc? Also stopping all appvolume manager services in a 24/7 health environment isn't a workable solution 😞 The method described in the KB, only changes a wrong counter of number of attachements for the specific appvolume. If the number is higer then 0, appvolumes things the package is attached at least once, while in practice it is not attched. When appvolumes thinks an attachement is still there, you are not able to do a delete from the GUI. By changing the counter to 0, you are again able to use the delete from the GUI. I can confirm this method works fine in a productiuon environment without stopping the managers, as I have used this in our environment sometimes. Edited August 19 by Robin Harmsen correction of some spelling Quote Senior Engineer (SDDC, EUC, DBA, Applications) at the Netherlands Cancer Institute - Antoni van Leeuwenhoek Hospital (NKI-AVL) Link to comment Share on other sites More sharing options...
Hans Straat Posted August 19 Share Posted August 19 Well your in the same business as I am in Leiden 🙂 lumc , thanks for confirming we can do it without stopping the managers Robin! 1 Quote Senior technical specialst at Leiden University Medical Center (lumc) Link to comment Share on other sites More sharing options...
Robin Harmsen Posted August 19 Share Posted August 19 (edited) 2 minutes ago, Hans Straat said: Well your in the same business as I am in Leiden 🙂 lumc , thanks for confirming we can do it without stopping the managers Robin! We should ask for a Dutch Healthcare subforum 🤪 Edited August 19 by Robin Harmsen 2 Quote Senior Engineer (SDDC, EUC, DBA, Applications) at the Netherlands Cancer Institute - Antoni van Leeuwenhoek Hospital (NKI-AVL) Link to comment Share on other sites More sharing options...
Hans Straat Posted August 27 Share Posted August 27 We where thinking what happens if we reset all attachement_count to 0 ? we think attached appstacks will remain attached or will it create mahem? Anyone tested this? Just out of curiossity 🙂 Quote Senior technical specialst at Leiden University Medical Center (lumc) Link to comment Share on other sites More sharing options...
Robin Harmsen Posted August 27 Share Posted August 27 I Did not test! But I will expect AppVolumes will not create mahem and just keep the appstacks attached. But why would you reset all counts to 0? It might break the failsafe for deleting still used appstacks.... I would only change/reset the count for the specific appstack(s) I have issues with and I confirmd there are no attachements for. Quote Senior Engineer (SDDC, EUC, DBA, Applications) at the Netherlands Cancer Institute - Antoni van Leeuwenhoek Hospital (NKI-AVL) Link to comment Share on other sites More sharing options...
Hans Straat Posted August 29 Share Posted August 29 It was just a thought like the -what if 😉 parameter. We tested it in our acceptance environment and it works excellent. Next is deleting the greyed out production appstacks. Quote Senior technical specialst at Leiden University Medical Center (lumc) Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.