“A general system error occurred: No connection could be made because the target machine actively refused it” error when powering on VMs on vCenter Server 6.0

To resolve this issue, start the VMware vCenter workflow manager service.
Windows vCenter Server
  1. On the server that runs vCenter Server, open Start > Run, type services.msc and press Enter.
  2. Right-click VMware vCenter workflow manager service and click start.
  3. Attempt to power on the virtual machine again.
vCenter Server Appliance (VCSA)
  1. Connect to the VCSA shell as root.
  2. Run this command to restart the VMware vCenter workflow service (vmware-vpx-workflow):

    # service vmware-vpx-workflow restart

  3. Attempt to power on the virtual machine again.

Comments

Post a Comment

Popular posts from this blog

enable TLS 1.2 and disabling TLS1.0 and SSL 3 on all exchange servers and Clients

Image
1)       Table depicting support for various SSL/TLS versions on different Windows OS   2)       SMTP – key piece of Exchange server infrastructure – support for TLS 1.1 and 1.2 were added in Exchange Server 2013 CU8 and Exchange Server 2010 SP3 RU9. This means if you want to add support for the latest ciphers and TLS versions, you may need to apply an update. 3)        Disable SSL  3.0 on all windows exchange servers Steps to disable support for the SSL 3.0 protocol on Windows by following these steps: ·          Click Start, click Run, type regedt32 or type regedit, and then click OK. ·          In Registry Editor, locate the following registry key: ·          HKey_Local_Machine\System\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 3.0\Server ·          Note If the complete registry key path does not exist, you can create it by expanding the available keys and using the New -> Key opti
Read more

HP 3PAR storage Commands to troubleshoot performance issues

The quick reference guide below will help diagnose and rule out some common issues experienced in the 3PAR arrays.  CLI COMMAND – “STATVLUN” measures the round trip time of an IO as seen by the system. Running STATVLUN in the following order should lead to the resolution of a few performance issues: 1)      “statvlun –ni”   – The STATVLUN command without any switches will show the round trip time of IO on each path for exported Virtual Volumes. This is helpful to determine if there is a multipathing issue. The “-ni” flag will eliminate any inactive volumes. 2)      “statvlun –vvsum –ni –rw”   This will show you the round trip time of the IO to each volume with the paths condensed for consolidated reporting.  This is great to see an overall picture of what is going on The “-rw” flag will break the IO down into Reads & Writes. 3)      “statvlun –hostsum –ni –rw”   The output of this command will show you the round trip time of the IO organized to the host le
Read more