OPERATIONAL DEFECT DATABASE
...
...
Editing an existing pool in the VMware Horizon View Portal interface fails.Errors similar to the below appear as an alert. One of the required objects is not found in the VirtualCenter server IP address/hostname You may also see the error: Server Error Unknown You may also see the error: "Cannot look up datacenter from Virtual Center. If the Desktops Virtual Center has provisioning disabled, it must be re-enabled to retrieve this information" Horizon Server Logs can report more specifics on the cause Reference: Collecting VMware Horizon View log bundles (1017939) 2023-11-22T08:35:33.226+01:00 ERROR (23DC-2XX4) <ajp-nio-127.0.0.1-8009-exec-5> [FaultUtilBase] UnexpectedFault: Cannot look up datacenter from Virtual Center. If the Desktop's Virtual Center has provisioning disabled, it must be re-enabled to retrieve this information. 2023-11-22T08:35:33.226+01:00 ERROR (23DC-2XX4) <ajp-nio-127.0.0.1-8009-exec-5> [RestApiServlet] Unexpected fault:(vdi.fault.UnexpectedFault) { errorMessage = Cannot look up datacenter from Virtual Center. If the Desktop's Virtual Center has provisioning disabled, it must be re-enabled to retrieve this information
Add vCenter Server Instances to Horizon 8 Warning: After adding a vCenter Server to Horizon and creating managed desktop pools or farms, do not rename any vSphere objects in use by those pools or farms, such as Data Centers, Clusters, Datastores, or Resource Pools. Renaming these objects can cause Horizon to lose its reference to those objects, causing future provisioning and power operations to fail. Rename vSphere objects before creating pools or farms, or when those objects are not referenced by existing Horizon pools or farms. One common issue that can occur is when the vCenter Server is unable to locate the object for a particular pool due to a renaming error.To avoid this issue, it is crucial to ensure that any changes made to the datacenter, cluster, or host are also reflected in VMware Horizon View. This will ensure that the vCenter Server can properly locate the object for the pool and prevent any potential disruptions to your virtual environment. Please also be aware of the following: Migration Recommendations and Restrictions for Horizon VDI Desktops (57368)
If you're experiencing issues with the object location in your VMware Horizon View pool, you can quickly resolve this issue by checking the object name and its location in the summary of the pool, and then comparing it with the corresponding vCenter Server information. Ideally utilize the same account on Horizon and Vcenter to rule out the possibility of a permission or rights issue being the cause. Horizon View: Procedure to verify object name and location Log in to your VMware View Administrative portal using the URL: https://ip_address_or_fully_qualified_domain_name/admin Locate the pool that is experiencing this issue.From the pool summary, note the object and its path. This object path includes the name of the datacenter and the folder in which you can find the host and any appropriate folders within this folder. For example: /Datacenter/vm/Testing/Automated/Non-persistent/ExampleTest vCenter Server: Procedure to verify object name and location Log in to the vCenter Server using the vSphere Client. Please see Using the vSphere ClientNavigate to Home > Inventory > VMs and Templates. This gives the most accurate information of the folder paths in your vCenter Server environment.Ensure that the location of the object in the vCenter Server is the same as the path noted in the pool summary in Horizon View. For Example: /Datacenter/vm/Testing/Automated/Non-persistent2/ExampleTest With the above example, there is a discrepancy with the path.Options to Resolve: Reverse the change if an object has been renamed Move the object back to the location specified in the Horizon View Pool Summary if this still exists.Recompose or push out your pool using the new path. Note: If it is not possible to perform the solution described, you must recreate your pool.Page last reviewed: October 2023Next review due: December 2023
VMware View Web 管理インターフェイスでの既存のプールの編集に次のエラーで失敗する： VirtualCenter Server で必要なオブジェクトの 1 つが見つかりません MoId cannot be null Instant Clone Creation Error (90572) This KB is referenced in Product Documentation: Add vCenter Server Instances to VMware Horizon 8
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.
