5 Replies Latest reply on Jul 21, 2015 1:02 AM by FJ1200

    Is a v5.0 Update Mismatch causing  "Timed waiting for vpxa to start"?

    FJ1200 Enthusiast

      Morning all


      A customer has a vCenter 5.0 U1 managing ESXi 5.0 U2 hosts.  One host has had to be removed from the cluster and needs adding back in, but now we get the "Timed waiting for vpxa to start" error message when we try.  Personally I think the Update mismatch is causing the problem even though we're not going from esxi 5.1 to a vC 5.0, the differences are still there. Am I correct?  I haven't seen this error message before until now, and have checked all the possible reasons I've come across.