VMware Horizon Community
VirtualParadox
Contributor
Contributor
Jump to solution

Failed to mount persistent disk - Trying to deploy first desktop pool and failing. - View Composer agent initialization failed

Hello all,

Full errors:

View Composer agent initialization state error (22): Failed to mount persistent disk. Please check the parent VM if an existing disk is using the same drive letter. (waited 0 seconds)

Pairing state:In pairing...

Configured by:xxx.xxx.xxx.local

Attempted theft by:

Provisioning error occurred for Machine xxx: View Composer agent initialization failed

I am currently rolling out VMWare view for the first time in a test environment and have hit an issue I have not been able to work around despite various google searches and trial and error.

Hoping someone here could suggest something.

VMWare view versions are all 6.0.1.

vCenter is on an appliance.

VMWare view connection manager is on a server 2012 R2 VM.

VMWare view composer is on a seperate server 2012 R2 VM.

I have an SQL server 2012 install on a separate server 2012 R2 VM.

SQL databases have been configured for the view composer to be able to reach it, it is using ODBC 64-bit via SQL Server Native Client 11.0.

I have tried troubleshooting this by swapping to 32-bit but this did not connect, so seems 64-bit is correct.

I have a windows 7 64-bit enterprise VM as my golden image. It has VMWare tools on it and VMWare agent on it.

The VM had ipconfig/release performed on it, it was then shut-down and a snapshot taken as my source.

The issue is that when I go to deploy a desktop pool I am getting the error shown above.

If I connect to the created VM via vCenter the persistent and temporary drives show fine.

Based on the error I have tried various adjustments such as changing the path for the VMs DVD drive from :anguished_face: to Z:, spreading the persistant and temporary drives over multiple data-stores or single data-stores and even removing the VMs DVD drive altogether. I have also looked at the logs under view composer but can find nothing to explain the behaviour.

SQL server seems to be working for the setup as error logs are going through and the VMs themselves are being created and added to AD as intended.

I should note the VMs are being done as linked clones.

Can anyone offer a clue as to the cause or something I can check please, have done all the areas I can think of and googling the error does not come up with anything helpful so far.

Thanks,

1 Solution

Accepted Solutions
Gaurav_Baghla
VMware Employee
VMware Employee
Jump to solution

IF you are using a 6.0.2 Agent Please downgrade the agent to 6.0.1 and let me know the Outcome

Regards Gaurav Baghla Opinions are my own and not the views of my employer. https://twitter.com/garry_14

View solution in original post

5 Replies
vNEX
Expert
Expert
Jump to solution

Hi,

please check solutions mentioned in this thread:

https://communities.vmware.com/message/2462014

_________________________________________________________________________________________ If you found this or any other answer helpful, please consider to award points. (use Correct or Helpful buttons) Regards, P.
VirtualParadox
Contributor
Contributor
Jump to solution

Hi,

That link has some useful information.

Unfortunately I have already tried all options mentioned there and am still facing the issue.

Reply
0 Kudos
Gaurav_Baghla
VMware Employee
VMware Employee
Jump to solution

IF you are using a 6.0.2 Agent Please downgrade the agent to 6.0.1 and let me know the Outcome

Regards Gaurav Baghla Opinions are my own and not the views of my employer. https://twitter.com/garry_14
VirtualParadox
Contributor
Contributor
Jump to solution

Agent is currently 6.0.2.2331487.

This has now been replaced by 6.0.1.2089044.

I am happy to report that this has resolved the error.

So for future reference it looks like a bug or similar in 6.0.2.2331487.

Thanks Gaurav!

Reply
0 Kudos
DevX81
Contributor
Contributor
Jump to solution

Is it possible to obtain a copy or download link to said 6.0.1 Agent? I am having the same issue, Windows 7 x64 Pro, fresh build. Errors at the same location, same error. I've checked and re-checked, deleted all snapshots, etc. I have one drive letter on my master.. 'C'. No mapped drives, nothing. I am a few days into an evaluation, so I do not have access to past versions. I contacted support and they indicated that trial/eval users only have access to the most recent. 6.0.2 in this case (no way to get 6.0.1).


Any help you can give would be appreciated.. it's doubly frustrating on an eval to not be able to do a true proof of concept. I did not have this issue on Windows 8.1 Pro x64, linked clone pool provisioned just fine.

Thanks!

Reply
0 Kudos