- storage/log directory is full in vCenter Server Appliance 6.0
- Purging old data from the database used by vCenter Server
- Permanent Device Loss (PDL) and All-Paths-Down (APD) in vSphere 5.x and 6.x
- vCenter Appliance root Partition 100% full due to Audit.log files not being rotated
- Windows vCenter Server upgrade fails with the error “Installation of component VMware vCenter Server failed with error code 3010”
- “invalid credentials LDAP Error 49” error when starting Inventory Services in vCenter Server 6.x
- Unable to log in to the root account of vCenter Server Appliance
- Increasing the disk space for the VMware vCenter Server Appliance in vSphere 6.0
- “Deprecated VMFS volume(s) found on the host” error in ESXi hosts
- vSphere handling of LUNs detected as snapshot LUNs
- “Failed to verify the SSL certificate for one or more vCenter Server Systems” error in the vSphere Web Client
- Cannot extend datastore through vCenter Server
- Lost or degraded connectivity to storage device
- Uploading files to a vSphere service might fail
- Replacing a vSphere 6.x Machine SSL certificate with a Custom Certificate Authority Signed Certificate
- “fsck failed” error when starting vCenter Server Appliance
- Resetting the VMware vCenter Server 5.x Inventory Service database
- Cannot remove or disable unwanted plug-ins from vCenter Server and vCenter Server Appliance
- Joining the VMWare vCenter Server Appliance or VMware vRealize Automation Identity Appliance to a domain fails with the error: Error trying to join AD, error code [31]
- Updating vCenter Server 6.0 to a later release fails on VCSServiceManager with error code ‘1603’
Related Articles
