edit:
Well after some testing i noticed a few things. If i configure my pools to automatically Delete after logoff, the attached appstack, the .vmdk, GETS DELETED AS WELL! If i set to Refresh after logoff, the appstack stays attached to the linked clone and of course won't attach to another VM when i log in again!
I'm hoping i'm an idiot and some config is totally wrong. Any ideas?
edit2:
After changing the hypervisor config in Appvolumes Manager to mount over the vCenter (instead of on the hosts) i have the following problem when logging off my view session, when the linked clone is supposed to delete.
VIEW ADMIN:
VCENTER:
VMWARE-VIEWCOMPOSER.LOG
| 2015-05-13 13:18:24,383 | VC thread | | FATAL | CommonLib.VcSubsystem.LroVcTask - Got VcFault: VMware.Sim.CommonLib.Exception.SimVcSubsystemException: Ein allgemeiner Systemfehler ist aufgetreten: Error deleting disk The disk cannot be deleted. ---> System.Web.Services.Protocols.SoapException: Ein allgemeiner Systemfehler ist aufgetreten: Error deleting disk The disk cannot be deleted. |
--- Ende der internen Ausnahmestapel??wachung ---, Machine Name: vcenter.domain.local, Timestamp: 13.05.2015 11:18:24, App Domain Name: SviWebService.exe, Thread Identity: , Windows Identity: NT-AUTORITR\SYSTEM, OS Version: Microsoft Windows NT 6.1.7601 Service Pack 1, vcFaultName: vcFaultDetails: System.Xml.XmlElement for task: task-297041
| 2015-05-13 13:18:24,383 | VC thread | | FATAL | ServiceCore.Action.VcAction - The VC Operation failed with error: VMware.Sim.CommonLib.Exception.SimVcSubsystemException: Ein allgemeiner Systemfehler ist aufgetreten: Error deleting disk The disk cannot be deleted. ---> System.Web.Services.Protocols.SoapException: Ein allgemeiner Systemfehler ist aufgetreten: Error deleting disk The disk cannot be deleted. |
--- Ende der internen Ausnahmestapel??wachung ---, Machine Name: vcenter.domain.local, Timestamp: 13.05.2015 11:18:24, App Domain Name: SviWebService.exe, Thread Identity: , Windows Identity: NT-AUTORITR\SYSTEM, OS Version: Microsoft Windows NT 6.1.7601 Service Pack 1, vcFaultName: vcFaultDetails: System.Xml.XmlElement
====================================================================================================================================
I'm having trouble with Appvolumes since updating to 2.7 (manager, agent and appstacks). Manager is configured for vCenter, the service account has the correct permissions.
Sporadically appstacks will not attach and i'm seeing the following messages in the activity log, any ideas? They appear every 2-5 minutes for different linked clones.
| May 13 2015 08:54AM | Unable to find known VM with InstanceUUID "501e3386-14f4-41d2-5b08-09b137f4xxxx" (templates? false) |
| May 13 2015 08:54AM | Unable to find "Machine <Appvol-003> (501e3386-14f4-41d2-5b08-09b137f4xxxx)" on "esxi-05.domain.local" -- Using default hypervisor instead |
| May 13 2015 08:54AM | Unable to find known VM with InstanceUUID "501e3386-14f4-41d2-5b08-09b137f4xxxx" (templates? false) |
| May 13 2015 08:54AM | Unable to find known VM with InstanceUUID "501e3386-14f4-41d2-5b08-09b137f4xxxx" (templates? false) |
| May 13 2015 08:54AM | Unable to find "Machine <Appvol-003> (501e3386-14f4-41d2-5b08-09b137f4xxxx)" on "esxi-05.domain.local" -- Using default hypervisor instead |
The agent logfiles are not to be found VMware KB: Location of VMware App Volumes log files in C:\Windows.
Running a Horizon View 6.0.1 environment with linked-clones.
Thanks.