Skip to main content

Resetting the vCenter SSO Administrator Password

 Symptoms

SSO administrator is locked or expired.
Purpose
You must unlock and reset the vCenter Single Sign-On (SSO) password if you have entered an incorrect password for three times and you see the error:
 
User account is locked. Please contact your administrator.
Resolution
By default, the account lockout policy is set to unlock after 15 minutes. If the account does not get unlocked even after 15 minutes, you must unlock the account using another session that is still logged into the SSO server or using another user account with SSO administrator privileges.
 
To unlock/reset the administrator account, see:
Related Information
For more information on account lockout policies for the Platform Services Controller (PSC), see the vCenter Server Password Requirements and Lockout Behavior section in the vSphere Security Guide.

More information here:
Configuring and troubleshooting vCenter Single Sign On password and lockout policies for accounts
vSphere 5.1 Single Sign On (SSO) installation fails with error: Error 29133. Administrator login error.
Understanding vCenter Single Sign-On (SSO) command line options
Resetting the SSO admin password after upgrading to vCenter Server 5.1.0b fails with the error: Key [com.rsa.db.msserverinstance] is not defined
vSphere 5.5 Single Sign-On administrator@vsphere.local password issues
Error: "VmDirForceResetPassword failed" while resetting the SSO administrator password using vdcadmintool

Read the article in different language here:
vCenterSSO管理者パスワードをリセット
Como desbloquear e redefinir a senha do administrador do SSO do vCenter
Restablecer la contraseña del administrador de vCenter SSO
重置 vCenter SSO 管理员密码
Entsperren und Zurücksetzen des VMware vCenter Single Sign-On-Administratorkennworts

Comments

Post a Comment

Popular posts from this blog

Error [403] The maximum number of sessions has been exceeded in the H5 client during login or logout

  Symptoms In virgo log, you see messages similar to: [2020-05-19T07:25:45.285Z] [ERROR] http-nio-5090-exec-130 72026859 142953 501051 com.vmware.vise.security.spring.DefaultAuthenticationProvider logout failed for sessionId 142953, clientId 501051 java.lang.IllegalStateException: The specified cardinality of 1..1 for osgi:reference implementing com.vmware.vcenter.apigw.api.ApiGatewaySessionManager in bundle com.vmware.h5ngc requires that exactly one OSGI service satisfies the filtering criteria but no such service was found.         at com.vmware.o6jia.context.ExternalServiceTargetSource.getTarget(ExternalServiceTargetSource.java:99)         at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:192)         at com.sun.proxy.$Proxy159.logout(Unknown Source)   ...
Post a Comment
Read more

Investigating virtual machine file locks on ESXi

      Details Adding an existing virtual machine disk (VMDK) to a virtual machine that is already powered on fails.                 Failed to add disk scsi0:1. Failed to power on scsi0:1   Powering on the virtual machine results in the power on task remaining at 95% indefinitely. Cannot power on the virtual machine after deploying it from a template. Powering on a virtual machine fails with an error: Unable to open Swap File Unable to access a file since it is locked Unable to access a file <filename> since it is locked Unable to access Virtual machine configuration In the /var/log/vmkernel log file, you see entries similar to: WARNING: World: VM xxxx: xxx: Failed to open swap file <path>: Lock was not free WARNING: World: VM xxxx: xxx: Failed to initialize swap file <path>   When opening a console to the virtual machine, you may receive ...
Post a Comment
Read more

"Failed to configure vAPI Endpoint Service at the firstboot time" while installing Windows VC 6.5

  Symptoms While configuring the vAPI EndPoint Service, you experience these symptoms: Windows vCenter Server 6.5 installation fails while configuring the vAPI EndPoint Service vCenter Server 6.5 installation on a Windows Server fails during the vAPI EndPoint Service during the firstboot time. You see the error: Error: An error occurred while starting service 'vapi-endpoint'. Failed to start the vAPI Endpoint Service. Failed to configure vAPI Endpoint Service at the firstboot time. Please file a bug against VAPI   In vapi_firstboot.py_2948_stderr.log file, you see entries similar to: No valid files with pathname: C:\ProgramData\VMware\vCenterServer\logs\vapi\endpoint* found. ERROR starting vapi-endpoint rc: 2, stdout: , stderr: Start service request failed. Error: Service crashed while starting^M vapi firstboot failed Traceback (most recent call last): File "C:\Program Files\VMware\vCenter Server\firstbo...
Post a Comment
Read more