|
Search:
Advanced search
|
Browse by category:
|
Contact Us |
sdd was not found |
|||||
Problem
This issue has been observed in environments where linked clones are in use. Provisioning of new VMs may suddenly stop working and throws the error "File [datastore] VMname/sdd was not found": ![]() We have seen this error showing up after some temporary networking problems at the VDI desktop client network. We are still not 100% sure if that networking issue was the root cause of this issue. But we know that the VMware Universal File Access service is the problem. Solution The solution was to restart the VMware Universal File Access service at the vCenter Server. ![]() If we look in the Application Log of the Event Viewer of the vCenter Server we have also found error messages like these: ![]() Related articles http://vmfaq.com/entry/84/ After upgrading VMware View from 4.6 to 5.0 desktop pools fails with the error message: Diskfault: Selected parent VM is not accessible http://kb.vmware.com/kb/1010841 Provisioning a linked clone fails with the View Manager error: Provision error (missing) Desktop Composer VcFault message http://kb.vmware.com/kb/2002051 View Composer fails with the error: Disk management service is not available |
|||||
Powered by
KBPublisher (Knowledge base software)


