vCenter Search

[MrVmware9423]

Dear Team,

while trying to serach or arranging VM, IP etc in a ascending order i m getting the following error.

help me how to resolve the above reported issue...

Regards

MrVMware

[Mouhamad · Accepted solution]

http://kb.vmware.com/kb/1018203

Resolution

This issue occurs if there is a failure in the database upgrade process while upgrading from VirtualCenter 2.5.x to vCenter Server 4.0.x. A successful upgrade populates the VPX_VIRTUAL_SCSICONTROLLER table with all of the virtual machines that use the LSI Logic or BusLogic virtual SCSI adapter. This issue occurs when one or more virtual machines that use the LSI Logic or BusLogic virtual SCSI adapter do not have an entry in the VPX_VIRTUAL_SCSICONTROLLER table. To identify the virtual machines that do not have an entry in the VPX_VIRTUAL_SCSICONTROLLER table and create an entry for them:

1. Run the following SQL query in Microsoft SQL Management Studio against the vCenter Server database to find any virtual machines that use the LSI Logic or BusLogic virtual SCSI adapter but do not have an entry in the VPX_VIRTUAL_SCSICONTROLLER table.
   
   SELECT e.name,vm.ID, DESCRIPTION, ANNOTATION, CONFIG
   FROM VPX_VM vm, vpx_entity e
   WHERE (CONFIG IS NOT NULL)
   AND ((CONFIG LIKE '%VirtualLsiLogicController%')
   OR (CONFIG LIKE '%VirtualBusLogicController%'))
   AND (vm.ID NOT IN (SELECT VM_ID FROM VPX_VIRTUAL_SCSICONTROLLER))
   AND e.id = vm.id
   
2. Shut down any virtual machines returned from this query.
   
3. Remove the virtual machine from the vCenter Server inventory.
   
   Note: Typically, only a few (less than five) virtual machines are returned from this query (even in very large environments of over 1000 virtual machines).
   
   Warning: Removing a large number of View virtual machines can cause issues with View provisioned desktops. Engage an action plan to provision new desktops after this change. Affected View desktops need to be removed, which results in deleting the desktop.
   
4. When they are removed from the inventory, add them back.
   
5. Rerun the query in step 1 to confirm that no virtual machines are returned.
   
6. Restart the VMware vCenter Server and the VMware Management Webservices service. For more information, see Stopping, starting, or restarting vCenter services (1003895).
   
   Note: You may need to wait one to two hours before all Tomcat based features of vCenter Server return to a normal state.
   

[MrVmware9423]

my issue has been resolved with the help of this KB article

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=101064...