App Volume VMDK is not attached to a client (Failed to add disk 'scsi0:2')

[mrjohndoe]

Hello,

I have built a new linked clone pool from a golden image which is Win 10 with .net35 (for a software) and app volumes client. Also I have used the VMWare Optimazation Tool.

I have also built a "standard application App Volume" which I have mapped to an AD User (also a group but there is another thread for this).

When I now log in on my linked clone I don't get the virtual applications. When I look in the activity log on the App Vol Server I see that he tries to attach the volume to the client but this line in the log is filled with a red background color.

After some search in the log files I found the part where he tries to attach and everything seems fine on the first look. He authenticates, he recognize the volumes to attach and then he declines the attachment. In the log there is following line:

[2018-10-30 14:05:41 UTC] P4200R1053RA ERROR   RvSphere: vSphere operation failed: Failed to add disk 'scsi0:2'.

[2018-10-30 14:05:41 UTC] P4200R1053RA  INFO        Cvo: Async completed for Machine <Virt18-HOff002> (50386119-c629-09e1-159b-538cf3f77642) with result false, Total time taken 0.44 secs

[2018-10-30 14:05:41 UTC] P4200R1053RA  INFO        Cvo: Incrementing unmount count for volume #32, now 1

[2018-10-30 14:05:41 UTC] P4200R1053RA  INFO        Cvo: Incrementing incomplete mount count for volume #32, now 1

[2018-10-30 14:05:41 UTC] P4200R1053RA ERROR        Cvo: Declined all 1 attachments for "User <HM1\grossman>" on "Machine <Virt18-HOff002> (50386119-c629-09e1-159b-538cf3f77642)"

I have googled the error and someone suggest to look for other VMs which have the vmdk mapped but I couldn't find any (the system is new and so here are only few other machines). No I don't know where to search further. Can you see anything what helps me with that problem?

Regards

[Ray_handels]

Did you fully ran thoruhg the process of packaging the appstack?

We do see this happening when I try to attach a read only disk (which an appstack is) as persistent.

You could try and edit the .vmdk file (not the flat file itself) and change the value of ddb.deletable=true to ddb.deletable=false. Normally, after you "Seal" the appstack it should do this by itself.

[mrjohndoe]

Thank you for your post. Yes, I have finished the process. I also had copied (via Upgrade) the Volume but it also doesn't work. I have problems recognizing the exact fault with the log files ...

[Ray_handels]

You are using appstacks right? This is not a writable that needs to be attached?

Could you try and update the appstack and then provisioning it without actually doing something? So reboot right after attaching it?