Unable to Add Host Back to vCenter: "Can't Complete Login Due to an Incorrect Username or Password"
search cancel

Unable to Add Host Back to vCenter: "Can't Complete Login Due to an Incorrect Username or Password"

book

Article ID: 372474

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

  • After replacing the vCenter Certificate, the host went into a disconnected state.
  • The host was removed from vCenter and now cannot be added back.

Environment

VMware vCenter Server 7.x

Cause

This issue occurs when the cached password for vpxuser is incorrect on the host, or if your account has expired within vCenter Server, or User lookup failed for 'vpxuser'.

Resolution

1. To update the vpxuser account on the host:

  • Remove the host from the inventory within vCenter Server.
    Caution: When an ESXi host is removed from the vCenter Server inventory, the virtual machines are removed from their respective folders, performance data for the host is lost, and any Distributed Virtual Switch configurations on the host need to be reconfigured.

  • Connect to the host through SSH and type the below command to stop the vpxa service :

/etc/init.d/vpxa stop  

  • Use the below command to delete the vpxuser :

esxcli system account remove -i vpxuser

  • Reconnect the host in the vCenter Server.

2. If issue still exists and hostd logs shows:

/var/run/log/hostd.log:

YYYY-MM-DDTHH:MM:SS.5002 info hostd(18540283) (Originator@6876 sub=Solo.Vmoma opID=a905XX87) Result: --> (vim.fault.InvalidLogin) ( --> msg = "", --> 1
YYYY-MM-DDTHH:MM:SS.5302 warning hostd(18540280] [Originator@6876 sub-UserDIrectory opID=a905XX8a] User lookup failed for 'vpxuser' 

YYYY-MM-DDTHH:MM:SS.530Z info hostd(18540280) (Originator@6876 sub=AdapterServer opID=a905XX8a) AdapterServer caught exception: N3Vim5Fault12InvalidLogin9ExceptionE(Fault cause: vim.fault.InvalidLogin 

 /var/run/log/vmkernel.log:

YYYY-MM-DDTHH:MM:SS.218Z cpu45:2101635)Admission failure in path: host/vim/vmvisor/esxtokend:esxtokend.2100226:uw.2100226
YYYY-MM-DDTHH:MM:SS.218Z cpu45:2101635)Admission failure in path: host/vim/vmvisor/esxtokend:esxtokend.2100226:uw.2100226
YYYY-MM-DDTHH:MM:SS.219Z cpu45:2101635)Admission failure in path: host/vim/vmvisor/esxtokend:esxtokend.2100226:uw.2100226
YYYY-MM-DDTHH:MM:SS.219Z cpu45:2101635)Admission failure in path: host/vim/vmvisor/esxtokend:esxtokend.2100226:uw.2100226
YYYY-MM-DDTHH:MM:SS.219Z cpu45:2101635)Admission failure in path: host/vim/vmvisor/esxtokend:esxtokend.2100226:pt.2100226
YYYY-MM-DDTHH:MM:SS.219Z cpu45:2101635)Admission failure in path: host/vim/vmvisor/esxtokend:esxtokend.2100226:pt.2100226

  • Restart the esxTokenCPS service using command :

/etc/init.d/esxTokenCPS restart

  • Stop the vpxa service using command :

/etc/init.d/vpxa stop

  • Reconnect the host in the vCenter Server.