Troubleshooting missing inventory items from the vSphere Web Client 6.0
Article ID: 341810
Updated On:
Products
VMware vCenter Server
Issue/Introduction
Symptoms:
- After upgrading to vSphere 6.0, some of the inventory items are missing or unavailable in the vSphere Web Client.
- “The inventory items are visible in the vSphere Client
Environment
VMware vCenter Server Appliance 6.0.x
VMware vCenter Server 6.0.x
VMware vCenter Server 6.0.x
Resolution
If you are unable to see the vCenter Server in the inventory, see vCenter Server not listed in the inventory after installing or upgrading to vSphere 5.5 / 6.0 (2059528) before continuing.
To troubleshoot this issue, perform the steps in the order specified:
Note: If the vCenter Server has been restarted recently, it may take up to 15 minutes for all components to be synchronized.
Note: If the vCenter Server has been restarted recently, it may take up to 15 minutes for all components to be synchronized.
- Confirm that logging in to the vSphere Web Client with the [email protected] user displays the same missing items.
Note: If required, replace the @vSphere.local with domain configured for your environment. - Open the vSphere Web Client log, vsphere_client_virgo.log file, using a text editor. These log files are located at:
- For Windows vCenter Server:
%ALLUSERSPROFILE%\VMWare\vCenterServer\logs\vsphere-client\ - For vCenter Server Appliance:
/var/log/vmware/vsphere-client/logs/ - Search for errors that reference failures to contact the Inventory Service:
You may see some errors similar to: - Unable to connect to VMware Inventory Service
- Connection refused
- Confirm if the Inventory Service is running:
- For Windows vCenter Server:
- Click Start > run, type services.msc and click OK.
- Search for the VMware Inventory Service and confirm it is running.
- For vCenter Server Appliance:
- Open a console session to the vCenter Server Appliance.
- Type shell.set --enabled true and press Enter.
- Type shell and press Enter.
- Run this command to check the status of the Inventory Service:
service-control --status vmware-invsvc - If the service is running you will see the output:
Running:
vmware-invsvc (VMware Inventory Service) - If the service is stopped you will see the output:
Stopped:
vmware-invsvc (VMware Inventory Service) - If the service is stopped, you have to start it before further troubleshooting. For more information on starting services, see Stopping, starting, or restarting VMware vCenter Server 6.0 services (2109881).
- Allow ten to fifteen minutes for the service to finish loading.
- If the issue persists, open the Inventory Service log, inv-svc.log file, located at:
- For Windows vCenter Server:
%ALLUSERSPROFILE%\VMWare\vCenterServer\logs\invsvc\ - For vCenter Server Appliance:
/var/log/vmware/invsvc/ - If the error DATA CORRUPTION is seen in the log, the Inventory Service database is corrupted. For more information on recovering from this, see Resetting the VMware vCenter Server 6.0 Inventory Service database (2119422).
- For specific issues related to specific components see these log files:
- Storage Profile: isp-SPS-xxxxxxxx.log
- Connection issues to vCenter Server: isp-vpx-xxxxxxxx.log
- Inventory service performance issues: inv-svc-perf.log
These log files are located at: - For Windows vCenter Server:
%ALLUSERSPROFILE%\VMWare\vCenterServer\logs\invsvc - For vCenter Server Appliance:
/var/log/vmware/invsvc/
Note: The logging levels are controlled by the: - For Windows vCenter Server:
C:\Program Files\VMware\vCenter Server\invsvc\lib\server\config\log4j.properties - For vCenter Server Appliance:
/usr/lib/vmware-invsvc/lib/server/conifg/log4j.properties
Additional Information
Feedback
Yes
No
Powered by
