Unable to attach volume (appstack) to VDI

[khann015]

Hi,

We have a user who's appstacks are attaching to his VDI session. The activity logs has the following.

Can anyone shed some light on this?

Thanks,

[sjesse]

If you go to system messages, instead of the activity log tab, you'll see more detailed messages why the appstack won't attach. Take a look and please share, I believe the get highlighted red as well, but I could be wrong.

[khann015]

Hi sjesse,

Thank you for response. I have had a look at System Messages and found the following for the affected user.

Writable volume named "xxx" already exists for "User <xxx>"

The logs only appear to go back 1000 entries.

Thanks,

[sjesse]

If its his writeable and it won't attach, its probably because its attached to another machine, I'd see if he has another session opened somewhere else. Writables can only be attached to one virtual desktop at a time.

[khann015]

I checked his writable volume and it is not attached.

Other user writable volumes and the same appstacks are being used successfully by other users in the pool.

I have tried reassigning the user to a new VDI in the pool and this has not worked. 

Thanks,

[khann015 · Accepted solution]

I have checked the location that the writable VMDK is stored to. It appears to be missing from this location but the the VMDK.metadata for the writable volume is still present. I may delete the writable volume from AppVolumes and recreate to test if this resolves the issue.

[Ray_handels]

Do you delete the machine after use? Try and do a refresh. If a writable is attached to a VDI machine and it is being removed the writable will be deleted as well if you dont enable the option to prevent this from happening. What it does than is that it marks it as undeletable when attached to a machine.