OPERATIONAL DEFECT DATABASE
...
...
Linked clones fail to be provisioned during a VMware Cloud Foundation VDI Workload Domain deploymentAn external Active Directory domain is specified during the VDI Workload Domain configurationIn the Horizon View Composer sever logs, you see entries similar to: 2017-06-23 01:03:05,871 | UFA main thread 21 | FATAL | CommonLib.UfaSubsystem.UfaSubsystem - UFA error: failure in operation with soap fault: SysimageFaultFileOpenErrorFault VMware.Sim.CommonLib.Exception.SimUfaSubsystemException: UFA soap fault error. ---> System.Web.Services.Protocols.SoapException: sysimage.fault.FileOpenError at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Sysimage.SysimageService.UfaClientOpenComputer(ManagedObjectReference _this, SysimageComputerSpec spec, SysimageComputerOptions options, SysimageSlaveSelectionPolicy policy) at VMware.Sim.CommonLib.UfaSubsystem.UfaWorkItem.OpenComputer(HostServiceTicket diskAccessTicket) at VMware.Sim.CommonLib.UfaSubsystem.InitializeDiskUfaWorkItem.DoWork() at VMware.Sim.CommonLib.UfaSubsystem.UfaWorkItem.Run() --- End of inner exception stack trace ---, Machine Name: TESTCOM1-1, Timestamp: 6/23/2017 8:03:05 AM, App Domain Name: SviWebService.exe, Thread Identity: , Windows Identity: NT AUTHORITY\SYSTEM, OS Version: Microsoft Windows NT 6.2.9200.0, reason: DiskUnreachable access host: host1.corp.local access port: 902 disk datastore path: [vsanDatastore] xxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/Testvm-1-1-6-vdm-user-disk-D-0413fac1-171d-4d1e-bfb4-4699d819d3ac.vmdk expected certificate thumbprint: , ufaFaultName: SysimageFaultFileOpenErrorFault ufaFaultDetails: <reason xmlns="urn:sysimage">Invalid fault</reason> 2017-06-23 01:03:05,871 | UFA main thread 21 | FATAL | CommonLib.UfaSubsystem.InitializeDiskSetUfaWorkItem - Error: CompletionCallbackProxy failed to init disk with result VMware.Sim.CommonLib.Exception.SimUfaSubsystemException: UFA soap fault error. ---> System.Web.Services.Protocols.SoapException: sysimage.fault.FileOpenError at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Sysimage.SysimageService.UfaClientOpenComputer(ManagedObjectReference _this, SysimageComputerSpec spec, SysimageComputerOptions options, SysimageSlaveSelectionPolicy policy) at VMware.Sim.CommonLib.UfaSubsystem.UfaWorkItem.OpenComputer(HostServiceTicket diskAccessTicket) at VMware.Sim.CommonLib.UfaSubsystem.InitializeDiskUfaWorkItem.DoWork() at VMware.Sim.CommonLib.UfaSubsystem.UfaWorkItem.Run() --- End of inner exception stack trace ---, Machine Name: TESTCOM1-1, Timestamp: 6/23/2017 8:03:05 AM, App Domain Name: SviWebService.exe, Thread Identity: , Windows Identity: NT AUTHORITY\SYSTEM, OS Version: Microsoft Windows NT 6.2.9200.0, reason: DiskUnreachable access host: host1.corp.local access port: 902 disk datastore path: [vsanDatastore] xxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/Testvm-1-1-6-vdm-user-disk-D-0413fac1-171d-4d1e-bfb4-4699d819d3ac.vmdk expected certificate thumbprint: , ufaFaultName: SysimageFaultFileOpenErrorFault ufaFaultDetails: <reason xmlns="urn:sysimage">Invalid fault</reason> 2017-06-23 01:03:05,871 | UFA main thread 18 | FATAL | CommonLib.UfaSubsystem.UfaSubsystem - UFA error: failure in operation with soap fault: SysimageFaultFileOpenErrorFault VMware.Sim.CommonLib.Exception.SimUfaSubsystemException: UFA soap fault error. ---> System.Web.Services.Protocols.SoapException: sysimage.fault.FileOpenError at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Sysimage.SysimageService.UfaClientOpenComputer(ManagedObjectReference _this, SysimageComputerSpec spec, SysimageComputerOptions options, SysimageSlaveSelectionPolicy policy) at VMware.Sim.CommonLib.UfaSubsystem.UfaWorkItem.OpenComputer(HostServiceTicket diskAccessTicket) at VMware.Sim.CommonLib.UfaSubsystem.InitializeDiskUfaWorkItem.DoWork() at VMware.Sim.CommonLib.UfaSubsystem.UfaWorkItem.Run() --- End of inner exception stack trace ---, Machine Name: TESTCOM1-1, Timestamp: 6/23/2017 8:03:05 AM, App Domain Name: SviWebService.exe, Thread Identity: , Windows Identity: NT AUTHORITY\SYSTEM, OS Version: Microsoft Windows NT 6.2.9200.0, reason: DiskUnreachable access host: host1.corp.local access port: 902 disk datastore path: [vsanDatastore] xxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/Testvm-1-1-4-vdm-disposable-c21d9f5a-93d2-4b01-b5c4-ea7ea98e6888.vmdk expected certificate thumbprint: , ufaFaultName: SysimageFaultFileOpenErrorFault ufaFaultDetails: <reason xmlns="urn:sysimage">Invalid fault</reason> 2017-06-23 01:03:05,871 | UFA main thread 18 | FATAL | CommonLib.UfaSubsystem.InitializeDiskSetUfaWorkItem - Error: CompletionCallbackProxy failed to init disk with result VMware.Sim.CommonLib.Exception.SimUfaSubsystemException: UFA soap fault error. ---> System.Web.Services.Protocols.SoapException: sysimage.fault.FileOpenError at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Sysimage.SysimageService.UfaClientOpenComputer(ManagedObjectReference _this, SysimageComputerSpec spec, SysimageComputerOptions options, SysimageSlaveSelectionPolicy policy) at VMware.Sim.CommonLib.UfaSubsystem.UfaWorkItem.OpenComputer(HostServiceTicket diskAccessTicket) at VMware.Sim.CommonLib.UfaSubsystem.InitializeDiskUfaWorkItem.DoWork() at VMware.Sim.CommonLib.UfaSubsystem.UfaWorkItem.Run() Note: This log excerpt is an example. Date, time, and environmental variables may vary depending on your environmentNone of the hostnames noted in the messages above are resolvable by systems in external Active Directory domain
This issue can occur when the DNS in the external Active Directory domain is not configured to point to the SDDC Manager Controller virtual machine to resolve the hostnames of the systems in the VMware Cloud Foundation environment.
To resolve the hostnames of the systems in the VMware Cloud Foundation environment, the DNS in the external Active Directory domain must be configured to point to the SDDC Manager Controller virtual machine (or VRM virtual machine for 2.1.x versions).
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
