HouK005
Contributor
Contributor

Horizon View 6.1.1 pool with persistent disk

Jump to solution

I have pool that using Persistent Disk

When detach persistent disk from vm and recreate machine in the same pool machine is created with new name (old is deleted from view console and vcenter) but in events i have 16 000 error  events with message:

"Provisioning error occurred for Machine VMKP005: Unable to remove Machine from inventory"

I tried this KB VMware KB: Manually deleting linked clones or stale virtual desktop entries from the View Composer d...
and machine with that name is not existing in ADAM or composer DB.

In connection server log

2015-07-21T17:03:37.496+02:00 INFO  (103C-0A7C) <propagate-af856f12-0a3d-417d-83cb-ea185ede0cd6> [PendingOperation] Pool control for desktop kp_2015_07 is deleting VM VMKP005

2015-07-21T17:03:27.464+02:00 WARN  (103C-1A30) <PendingOperation-vm-25907-DeletingLC> [PendingOperation] Failed to remove VM: /View/vm/Kanal_Partnerski_2013.02/KP_2015_07/VMKP005 from the View Composer inventory - Unable to retrieve VM information.

2015-07-21T17:03:27.468+02:00 ERROR (103C-1A30) <PendingOperation-vm-25907-DeletingLC> [PendingOperation] Failed to mark VM /View/vm/Kanal_Partnerski_2013.02/KP_2015_07/VMKP005 as ERROR after failing to remove from SVI[LDAP: error code 32 - 0000208D: NameErr: DSID-0310020A, problem 2001 (NO_OBJECT), data 0, best match of:

Any idea?

When detach is from one poll then edit persistent disk to switch to another pool and then recreate machine in new pool there is no error and working fine.

0 Kudos
1 Solution

Accepted Solutions
SanjaySP1
VMware Employee
VMware Employee

Please try below steps:

1. Firstly reboot View and vCenter servers as suggested in below KB.

VMware KB: Recommended restart cycle of the VMware Horizon View environment

2. If the issue persists, Connect to Composer DB using management studio and run the below script against Composer DB.


DELETE

FROM [dbo].SVI_TASK_STATE

WHERE SIM_CLONE_ID = (SELECT ID FROM [dbo].SVI_SIM_CLONE WHERE VM_NAME like 'vmkp005')

DELETE

FROM [dbo].SVI_SC_PDISK_INFO

WHERE PARENT_ID = (SELECT ID FROM [dbo].SVI_SIM_CLONE WHERE VM_NAME like 'vmkp005')

DELETE

FROM [dbo].SVI_SC_BASE_DISK_KEYS

WHERE PARENT_ID = (SELECT ID FROM [dbo].SVI_SIM_CLONE WHERE VM_NAME like 'vmkp005')

DELETE

FROM [dbo].SVI_SIM_CLONE

WHERE VM_NAME = 'vmkp005'

DELETE

FROM [dbo].SVI_COMPUTER_NAME

WHERE NAME = 'vmkp005'

DELETE

FROM [dbo].SVI_VM_NAME

WHERE NAME = 'vmkp005'

View solution in original post

0 Kudos
5 Replies
SanjaySP1
VMware Employee
VMware Employee

Hi

In View administrator do you see the desktop "VMKP005" under problem vCenter VMs.

If the answer is yes, may I know the status of the desktop ?

0 Kudos
HouK005
Contributor
Contributor

No, vmkp005 not existng in view admin.

0 Kudos
SanjaySP1
VMware Employee
VMware Employee

Please try below steps:

1. Firstly reboot View and vCenter servers as suggested in below KB.

VMware KB: Recommended restart cycle of the VMware Horizon View environment

2. If the issue persists, Connect to Composer DB using management studio and run the below script against Composer DB.


DELETE

FROM [dbo].SVI_TASK_STATE

WHERE SIM_CLONE_ID = (SELECT ID FROM [dbo].SVI_SIM_CLONE WHERE VM_NAME like 'vmkp005')

DELETE

FROM [dbo].SVI_SC_PDISK_INFO

WHERE PARENT_ID = (SELECT ID FROM [dbo].SVI_SIM_CLONE WHERE VM_NAME like 'vmkp005')

DELETE

FROM [dbo].SVI_SC_BASE_DISK_KEYS

WHERE PARENT_ID = (SELECT ID FROM [dbo].SVI_SIM_CLONE WHERE VM_NAME like 'vmkp005')

DELETE

FROM [dbo].SVI_SIM_CLONE

WHERE VM_NAME = 'vmkp005'

DELETE

FROM [dbo].SVI_COMPUTER_NAME

WHERE NAME = 'vmkp005'

DELETE

FROM [dbo].SVI_VM_NAME

WHERE NAME = 'vmkp005'

View solution in original post

0 Kudos
HouK005
Contributor
Contributor

Finally before downtime error event counter reach 110 000 and i have second machine with the same behavior.

First step working for both.

Thank You

Any solutions to avoid this situation in future?

0 Kudos
SprintJG
Contributor
Contributor

Hello,

We have experiencing the same situation every X days. We have restarted cycle of VMware Horizon View environment and fixed provisionally, but the same issue appears for every Detach operation.

Did you find a final solution?

0 Kudos