App stacks are not attaching immediately after assigned

[EshMallu]

Hi,

I have created my appstacks in appvolumes 2.11 version. Now I have installed app volumes 2.121 version in new server and copied all appstacks to new server.

I have assigned the appstacks to users with the option "Attach AppStacks immediately", but app stacks are not assigning.

If user log off and login again then app stacks are appearing and working.

Can any one please help me to find out why app stacks are not attaching immediately?

[nhickey]

Hi EshMallu,

App Volumes version 2.13.x is now available and should be used to help fix other known issues within version 2.12.x. That said, you could have a corrupted AppStack and maybe it is just timing out trying to connect. Have you checked the App Vols logs? have a look at the log "svservice.log" to review any errors. Is the stack very large?

Here are the release notes for version 2.13 (2.13.1 is also available): VMware App Volumes 2.13 Release Notes | 19 OCT 2017

Let us know your findings.

[EshMallu]

Hi Nigel,

Thanks for your reply. Initially, we have tried with 2.13 version but a couple of users are not able to connect app volume manager. Then we have decided to go back to 2.12.1.

Now we are getting the issue is everything working fine except attaching app stacks immediately.

We have 2.11 server and it's all working fine including attaching app stacks immediately. The issue is happening only in 2.12.1 version.

Is there any configuration changes need to apply?

If user logoff and login again all attached app stacks are appearing.

[techguy129]

Please review the appvol agent log. That will give you the answer to why its not working. This may happens if you are mixing both a user assigned appstacks and computer assigned appstacks to the same user/computer.