Writable and Appstack not attaching after 2.16 upgrade

[maharajan_be]

Hey,

Writable volume & app stack are not attaching after I upgrade the App volume manager to 2.16 from 2.14.

I do see the below error on App volume manager

Not Connected - "Hypervisor <Multiple vCenters>"

[Ray_handels]

Seems as if the connection to the vcenter has been lost, the reason why, I have no idea.

Do you see any errors in the manager when you go to Configuration --> Machine managers? Maybe you can see an error there??

[maharajan_be]

Thanks for your quick response.

I do not see any errors in the Manager and am not able re-add the vcenter server. Is possible to remove vcenter server and re-add

[Ray_handels]

I would suggest raising a ticket with VMware if this is a production server. Technically you could do that but than all attached appstacks might be removed from all machines, not soemthing you would like to see in production..

[sjesse]

As Ray said I'd open a ticket if this is production, but what I've done in the past after vcenter disconnected because of ceritificate change was edit the current one and reenter the service account password. For me this has worked in the past and hasn't disconnected any currently attached volumes.

[maharajan_be]

I have opened a ticket with VMware Support. Writable volume is not attaching when App volume agent 2.16 is installed. Writable volume attaches without any issues on 2.14 or 2.15 app volume agent.

I updated the vCenter server certificate to the App volume Manager. That didn't help me to resolve the issue.

[Ray_handels]

So it's not a manager issue then?? What does the svservice.log file on the client say? Normally there should be an error message that indicates why the writable is not being attached to a machine with 2.16 agent.

[maharajan_be]

Ray,

I do see the below error on svservice.log file

LoadVolumeMeta: cannot load base meta file "\SnapVolumesTemp\MountPoints\{000022f1-0000-0000-0000-100000000000}\METADATA\_meta.yml" for load, error!

[Ray_handels]

Looking at the guid that is starting with 000 my suggestion is that there is an issue with one of your appstacks.

We only saw this error after we installed an application and it didn;t have an uninstall key in it so Appvolumes could not see an actively installed application and thus spitting out this error. This however should not block the attachment of the writable to be honest.

Do you happen to know what appstack this is and if so is it an option to rebuild this one?

[maharajan_be]

Even without assigning AppStack , the users are having same issue with Writable volume.. Newly created WV ( both UIA & UIA + profile) attaches for the first time and next time when the user connects, WV attaches to the VM but the user just see welcome screen. Both on Horizon view admin console and vSphere, I do see the WV is attached.

[Ray_handels]

What kind of template are you using?? It seems as if either you are using teh UIA only (which only holds user installed applications) or for some reason the local profile is being overwritten. Do you happen to use roaming profiles?

What you see happening when logging in is that the newly locally created profile is being removed and "replaced" (it's just how you look at it) by the profile that's in the writable volume.