Hey Mark808
I'm in the exact same boat as you. Starting about a month after upgrading to 2.13.1, some of our users were reporting that they were getting an error 500, virtualization is disabled. When this happens the user doesn't get any applications. Looking into the logs, we get the same error that you're seeing. I put a support ticket in, and this is what I heard back. We're not able to change the pool's naming convention, but I was able to isolate the handful of problematic machines, and essentially make them unavailable to the end user. I heard from another tech, that they're currently testing the hot fix, and he verified that it resolved the errors he was getting. I hope to get my hands on the fix next week and implement it asap.
"I see from the case description some VDI desktops are throwing an Error 500 message upon log in. Inside the corresponding App Volumes Manager logs you are also seeing the error 'Unhandled request exception: undefined method `ngvc?' for nil:NilClass' followed by a stack trace. This is currently a known issue in the 2.13.1 App Volumes version. During the upgrade VMs that were reported offline by the manager, were powered off or in the middle of a refresh/recompose will keep throwing this error. . To work around the issue you could also take one of the following action plans:
1. How long ago was App Volumes upgraded? If yesterday or this week you could explore the option of downgrading back to App Volumes 2.12.1
2. How many VDI desktop pools are affected? You can also change the naming convention for the VDI desktop pools affected and when the new names provision they will create new entries inside the App Volumes Manager DB and the issue will not be seen for the new desktops. es 2.12.1"
Thanks,
Mike
