Home > Blogs > Support Insider > Author Archives: Rick Blythe
Rick Blythe

About Rick Blythe

Social Media Program Manager for VMware, Rick Blythe manages the Twitter handle @vmwarecares and curates the Support Insider Blog.

Top 40 Horizon View articles for April 2016

Here is an update for the top Horizon View articles list for April 2016. This list is ranked by the number of times a VMware Support Request was resolved by following the steps in a published Knowledge Base article.

  1. Manually deleting linked clones or stale virtual desktop entries from the View Composer database in VMware View Manager and VMware Horizon View
  2. Using Microsoft Certreq to generate signed SSL certificates in VMware Horizon View
  3. VMware View ports and network connectivity requirements
  4. Removing invalid linked clone entries automatically using the ViewDBChk tool in VMware Horizon View 5.3 and later versions
  5. Provisioning View desktops fails due to customization timeout errors
  6. Linked Clone pool creation and recomposition fails with VMware Horizon View 6.1.x and older releases
  7. Finding and removing unused replica virtual machines in the VMware Horizon View
  8. Configure security protocols for PCoIP for Horizon 6 version 6.2 and later, and Horizon Client 3.5 and later
  9. Removing a standard (replica) connection server or a security server from a cluster of connection/security servers
  10. Restart order of the View environment to clear ADLDS (ADAM) synchronization in View 4.5, 4.6, 5.0, 5.1, 5.2, 5.3, 6.0, and 6.1
  11. Recommended restart cycle of the VMware Horizon View environment
  12. Troubleshooting SSL certificate issues in VMware Horizon View 5.1 and later
  13. Manually deleting replica virtual machines in VMware Horizon View 5.x
  14. Provisioning VMware Horizon View desktops fails with error: View Composer Agent initialization error (16): Failed to activate software license
  15. Black screen when logging in to a Horizon View virtual desktop
  16. Generating a Horizon View SSL certificate request using the Microsoft Management Console (MMC) Certificates snap-in
  17. Recompute virtual disk digest tasks storm in vCenter Server
  18. Performing an end-to-end backup and restore for VMware View Manager
  19. Forcing replication between ADAM databases
  20. View Connection Server fails to replicate
  21. The View virtual machine is not accessible and the View Administration console shows the virtual machine status as Already Used
  22. Configuring USB device filters and redirecting Human Interface Devices (HIDs) in View Client
  23. Poor virtual machine application performance may be caused by processor power management settings
  24. Network adapter disappears from a Windows virtual machine
  25. Changing the log file behavior in the VMware View components
  26. Troubleshooting USB redirection problems in VMware View Manager
  27. Administration dashboard in VMware Horizon View reports the error: Server’s certificate cannot be checked
  28. Connecting to the View ADAM Database
  29. View Manager Admin console displays the error: Error during provisioning: Unexpected VC fault from View Composer (Unknown)
  30. Troubleshooting and Frequently Asked Questions for space reclamation in VMware Horizon View 5.2.x and 5.3.x
  31. Troubleshooting VMware Horizon View HTML Access
  32. VMware View SVGA driver reports newer version than the installed View Agent version
  33. Troubleshooting Agent Unreachable status in VMware Horizon View
  34. Intermittent provisioning issues and generic errors when Composer and vCenter Server are co-installed
  35. Disabling the HotAdd/HotPlug capability in ESXi 5.x and ESXi/ESX 4.x virtual machines
  36. Troubleshooting frequent PCoIP disconnects in a VMware View environment
  37. Increasing the video memory on VMware View desktops
  38. Determining which replica disk is used for a linked clone virtual machine
  39. VMware View Administrator shows the virtual machine status error: Configuration Error
  40. View Connection Server reports the error: [ws_TomcatService] STDOUT: java.lang.OutOfMemoryError: Java heap space

Inventory objects fail to display in the vSphere Web Client

An issue recently causing a few calls into our support lines happens after installing or upgrading to vCenter Server 6.0. The issue also impacts the vCenter appliance and is not specific to Windows. The issue occurs in the vSphere Web Client due to caching within the VMware Inventory Service.

  • When browsing inventory under Host and Clusters, some or no object are displayed
  • When using the Search function in the vSphere Web Client the object is found
  • The Issue does not occur in the vSphere Client
  • When browsing inventory under Related Objects at multiple levels you see this message:
no object found

If you suspect you have run into this head on over to KB: In the vSphere Web Client 6.0 inventory objects fail to display (2144934) for more details on what to check in your logs and what can be done about it.

 

Inventory objects

Important KB updates for current NSX for vSphere users -May 2016 Edition

NSXOur NSX support team would like all of our customers to know about important KB updates for current NSX for vSphere issues. Here’s what’s new and trending-

Please take note of key updates to the following important End of General Support and End of Availability events:

New and important issues:

NSX for Multi-Hypervisor:

New master playbook KBs:

How to track the top field issues:

 

Top 20 vRealize Operations Manager articles for April 2016

Top 20Here is our Top 20 vRealize Operations Manager articles list for April 2016. This list is ranked by the number of times a VMware Support Request was resolved by following the steps in a published Knowledge Base article.

  1. After upgrading to VMware vRealize Operations 6.2.0a, vCenter adapters remain in Starting state
  2. vRealize Operations Manager 6.1 and 6.2 Sizing Guidelines
  3. Update sequence for vSphere 6.0 and its compatible VMware products
  4. Resetting the Administrator password in VMware vRealize Operations Manager appliance
  5. Important information before upgrading to vSphere 6.0
  6. Manually removing a node from the VMware vRealize Operations Manager 6.x cluster
  7. After cancelling the selected alerts in VMware vRealize Operations Manager 6.0.x, one or more of the selected alerts remain
  8. VMware vRealize Operations Manager for Horizon 6.2 Broker Agent fails to pair with the Horizon adapter
  9. High garbage collection occurs on the VMware vRealize Operations Manager (vROps) 6.1.x Master node
  10. Enabling SSH access in VMware vRealize Operations Manager 6.0.x
  11. vRealize Operations Manager 6.0.1, 6.0.2, and 6.0.3 Sizing Guidelines
  12. Using custom email templates in VMware vRealize Operations Manager 6.x
  13. Searching for any of the migrated objects in the Inventory Explorer displays two copies
  14. VMware vRealize Operations Manager 6.1.x upgrade hangs if expired projects are present
  15. Disable TLS 1.0 in vRealize Operations Manager 6.2
  16. Cassandra service in VMware vRealize Operations Manager 6.1 and 6.2 fails with the error: Connection refused
  17. Configure a certificate for use with vRealize Operations Manager
  18. Disable SSL version 3.0 in vRealize Operations Manager 6.0
  19. Cluster Status is stuck at Going Online in VMware vRealize Operations Manager 6.0.x
  20. Restarting VMware vRealize Operations Manager 6.0.x fails with a Waiting for Analytics message in the Admin UI

Top 20 vRealize Automation articles for April 2016

Top 20Here is our Top 20 vRealize Automation (vRA) articles list for April 2016. This list is ranked by the number of times a VMware Support Request was resolved by following the steps in a published Knowledge Base article.

  1. Repairing or updating the trust between all components within a VMware vRealize Automation environment
  2. Update sequence for vSphere 6.0 and its compatible VMware products
  3. Important information before upgrading to vSphere 6.0
  4. Deleting an endpoint in vRealize Automation fails with the error: This endpoint is being used by # compute resources and # storage paths and cannot be deleted
  5. Logging in to a tenant with verified administrator credentials or user credentials fails in VMware vRealize Automation 6.2.x
  6. Removing a virtual machine from Management in VMware vRealize Automation 7 using Cloud Client
  7. Renaming the VMware vSphere Cluster used in a VMware vRealize Automation environment
  8. Removing a virtual machine from Management in VMware vRealize Automation or VMware vCloud Automation
  9. Migrating to a new SSO or recovering from a reinstallation of SSO in VMware vRealize Automation
  10. Various tasks fail after upgrading or migrating to VMware vRealize Automation 6.1.x or 6.2
  11. Setting the Kerberos token size for VMware vRealize Automation 6.x deployments
  12. Unable to add Active Directory users or groups to vCenter Server Appliance or vRealize Automation permissions
  13. Using JXplorer to update the LDAP string for an identity source for VMware vRealize Automation 6.0.x, 6.1.x
  14. Using the VMware vRealize Production Test Tool to validate and test your vRealize Automation configuration
  15. Provisioning fails after creating a new blueprint from VMware vRealize Automation 7.0.1
  16. Provisioning Virtual Machine from catalog fails after upgrading to VMware vRealize Automation 6.2.4
  17. Network profile is not assigned to new virtual machines in VMware vRealize Automation 6.1.x and 6.2.x
  18. Changing the VMware vRealize Automation IaaS service account or updating the vRealize Automation IaaS service account password
  19. Logging in to the VMware vRealize Automation 6.2.x Appliance Management website fails with the error: Unable to authenticate user. Please try again
  20. Connection between VMware vRealize Automation and embedded vRealize Orchestrator fails with the error: Cannot connect to Orchestrator server

Top 20 vSAN articles for April 2016

Top 20Here is our Top 20 vSAN articles list for April 2016. This list is ranked by the number of times a VMware Support Request was resolved by following the steps in a published Knowledge Base article.

  1. Certification of Dell PERC H730 and FD332-PERC Controllers with VSAN 6.x
  2. Best practices for Virtual SAN implementations using Dell PERC H730 or FD332-PERC storage controllers
  3. VMware Virtual SAN 6.0 Requirements
  4. Following maintenance, hosts in a Virtual SAN cluster may erroneously report the error: Host cannot communicate with all other nodes in virtual SAN enabled cluster
  5. Avoiding a known drive failure issue when Dell PERC H730 controller is used with VMware Virtual SAN 5.5 or 6.0
  6. Required VSAN and ESXi configuration for controllers based on the LSI 3108 chipset
  7. vSphere 5.5 Virtual SAN requirements
  8. VMware Virtual SAN 6.2 on disk upgrade fails at 10%
  9. Powering on virtual machines in VMware Virtual SAN 5.5 fails with error: Failed to create swap file
  10. VMware Virtual SAN 6.1 or 5.5 Update 3 Disk Groups show as Unmounted in the vSphere Web Client (DDH)
  11. Upgrading from ESXi 5.5 to ESXi 6.x in a Virtual SAN cluster can cause permanent loss of data
  12. VMware Virtual SAN 6.2 on disk upgrade fails due to CBT enabled virtual disks
  13. Requirements and considerations for the deployment of VMware Virtual SAN (VSAN)
  14. Creating new objects on a VMware Virtual SAN Datastore fails and reports the error: Failed to create directory VCENTER (Cannot Create File)
  15. Support statement for 512e and 4K Native drives for VMware vSphere and VSAN
  16. ESXi 5.5 host in a VMware Virtual SAN cluster reports a warning alarm: Host vendor provider registration
  17. Virtual SAN Health Service – Cluster Health – VSAN Health service installation
  18. Upgrading from VMware vSphere 5.5 EP06 or 5.5 P04 to vSphere 6.0 GA can cause VMware Virtual SAN Data Unavailability
  19. Upgrading the VMware Virtual SAN (VSAN) on-disk format version from 1 to 2
  20. Virtual SAN Health Service – Performance Service – Stats DB object check

Top 20 vCenter articles for April 2016

Top 20Here is our Top 20 vCenter articles list for April 2016. This list is ranked by the number of times a VMware Support Request was resolved by following the steps in a published Knowledge Base article.

  1. Purging old data from the database used by VMware vCenter Server
  2. After upgrading an ESXi host to 5.5 Update 3b and later, the host is no longer manageable by vCenter Server
  3. Permanent Device Loss (PDL) and All-Paths-Down (APD) in vSphere 5.x and 6.x
  4. Unlocking and resetting the VMware vCenter Single Sign-On administrator password
  5. Consolidating snapshots in vSphere 5.x/6.0
  6. Deprecated VMFS volume warning reported by ESXi hosts
  7. Upgrading to vCenter Server 6.0 best practices
  8. Resetting the VMware vCenter Server and vCenter Server Appliance 6.0 Inventory Service database
  9. Linked Clone pool creation and recomposition fails with VMware Horizon View 6.1.x and older releases
  10. Replacing default certificates with CA signed SSL certificates in vSphere 6.0
  11. Update sequence for VMware vSphere 5.5 and its compatible VMware products
  12. ESX/ESXi host keeps disconnecting and reconnecting when heartbeats are not received by vCenter Server
  13. VMware vSphere Web Client displays the error: Failed to verify the SSL certificate for one or more vCenter Server Systems
  14. Updating vCenter Server 5.5 to Update 3 fails with the error: Warning 32014. A utility for phone home data collector couldn’t be executed successfully
  15. Reducing the size of the vCenter Server database when the rollup scripts take a long time to run
  16. vCenter Server fails immediately after starting with the error: Fault Module: ntdll.dll
  17. Replacing a vSphere 6.0 Machine SSL certificate with a Custom Certificate Authority Signed Certificate
  18. In the vSphere Web Client 6.0 inventory objects fail to display
  19. Migrating virtual machines with Raw Device Mappings (RDMs)
  20. Cannot take a quiesced snapshot of Windows 2008 R2 virtual machine

Top 20 NSX articles for April 2016

Top 20Here is our Top 20 NSX articles list for April 2016. This list is ranked by the number of times a VMware Support Request was resolved by following the steps in a published Knowledge Base article.

  1. Virtual machine performance issues after upgrading VMware tools version to 10.0.x in NSX/VMware vCloud Networking and Security 5.5.x
  2. Update sequence for vSphere 6.0 and its compatible VMware products
  3. vCenter Server or Platform Services Controller certificate validation error for external VMware Solutions in vSphere 6.0
  4. Downloading and enabling VMware vShield Endpoint 5.x on supported VMware vSphere platforms
  5. Important information before upgrading to vSphere 6.0
  6. Network connectivity issues after upgrade in NSX/VCNS environment
  7. Windows virtual machines using the vShield Endpoint TDI Manager or NSX Network Introspection Driver (vnetflt.sys) driver fails with a blue diagnostic screen
  8. Response to OpenSSL security issue CVE-2014-0160/CVE-2014-0346 a.k.a: “Heartbleed”
  9. Understanding and troubleshooting vShield Endpoint / Guest Introspection with VMware vCloud Networking and Security 5.x and NSX for vSphere 6.x
  10. Changing the VMware NSX for vSphere 6.x License from virtual machine to CPU
  11. Understanding and troubleshooting IPSec VPN in VMware NSX for vSphere 6.x
  12. Fixing NSX for vSphere IPSEC VPN disconnects
  13. Netcpa issues in VMware NSX for vSphere 6.x
  14. When upgrading VMware ESXi 5.5.x to 6.0 host, you experience a purple diagnostic screen with the error: Failed to load kernel modules: dvfilter-switch-security, bfd, traceflow, vdl2, vdrb
  15. Cannot disable the NSX distributed firewall (DFW) on a host in VMware NSX for vSphere 6.x
  16. In VMware NSX for vSphere 6.x, installing or upgrading NSX VIBs fails with the error: ERROR: The pending transaction requires xxx MB free space, however the maximum supported size is xxx MB
  17. Installation Status shows as Not Ready on the Host Preparation Tab under Installation object in NSX
  18. Deploying vShield Edge fails when vShield Manager is connected to a vCenter Server
  19. Inventory data collection in VMware vCloud Networking and Security fails with the error: vRealize Orchestrator returned an error: browseInventory()
  20. No Flow Records displayed in NSX Manager flow monitoring

Top 20 ESXi articles for April 2016

Top 20Here is our Top 20 ESXi articles list for April 2016. This list is ranked by the number of times a VMware Support Request was resolved by following the steps in a published Knowledge Base article.

  1. VMware ESXi 5.x host experiences a purple diagnostic screen mentioning E1000PollRxRing and E1000DevRx
  2. Commands to monitor snapshot deletion in VMware ESXi/ESX
  3. After upgrading an ESXi host to 5.5 Update 3b and later, the host is no longer manageable by vCenter Server
  4. Determining Network/Storage firmware and driver version in ESXi/ESX 4.x, ESXi 5.x, and ESXi 6.x
  5. Permanent Device Loss (PDL) and All-Paths-Down (APD) in vSphere 5.x and 6.x
  6. Powering off a virtual machine on an ESXi host
  7. Consolidating snapshots in vSphere 5.x/6.0
  8. Recreating a missing virtual machine disk descriptor file
  9. Reverting to a previous version of ESXi
  10. Installing patches on an ESXi 5.x/6.x host from the command line
  11. ESXi 6.0 Update 2 host fails with a purple diagnostic screen containing the error: Vmxnet3VMKDevRxWithLock and Vmxnet3VMKDevRx
  12. Cloning individual virtual machine disks via the ESX/ESXi host terminal
  13. Deprecated VMFS volume warning reported by ESXi hosts
  14. Restarting the Management agents on an ESXi or ESX host
  15. Enabling or disabling VAAI ATS heartbeat
  16. Downloading and installing async drivers in VMware ESXi 5.x and ESXi 6.0.x
  17. Configuring a diagnostic coredump partition on an ESXi 5.x/6.0 host
  18. Issuing a 0x85 SCSI Command from a VMware ESXi 6.0 host results in a PDL error
  19. Information about the error: state in doubt; requested fast path state update
  20. Committing snapshots when there are no snapshot entries in the Snapshot Manager

User account locked in vCenter Server Appliance

vCSAWe’ve recently noticed a number of cases where vSphere administrators become locked out of their accounts or receive reports of incorrect passwords in the vCenter Server Appliance. If you find yourself in this position, here are two articles that address these issues:

KB 2034608
When attempting to log into the VMware vSphere 5.1, 5.5, or 6.0 Web Client you observe the following symptom: “User account is locked. Please contact your administrator.” This often occurs if the wrong password was entered multiple times. Waiting the default 15 minutes lockout period will allow to attempt the login again. If after multiple attempts, you are still not successful, you may need to reset the password.

KB 2069041
When attempting to log into the vCenter Server 5.5 and 6.0 Appliance, you experience symptoms where the root account is locked out. This often occurs because the vCenter Server appliance has a default 90 password expiration policy. Steps on how to modify the password expiration policies and to unlock the password.