Troubleshooting guide: Resolving invalid username and password errors for vCenter and ESX

Troubleshooting guide: Resolving invalid username and password errors for vCenter and ESX

If your vCenter or ESX monitor in Site24x7 displays an invalid username or password error, follow these steps to resolve the issue:

Step 1: Check your credentials

1. Ensure your credentials are correct
  1. Make sure the username and password entered in Site24x7 for vCenter or ESX are correct. 
  2. Verify the credentials by logging into the vSphere Client with the same credentials used in Site24x7.

2. Check if the credentials have expired
  1. Log in to the vSphere Client using a privileged account, such as the root user or an administrative account.
  2. Navigate to Administration > Single Sign-On > Users and Groups.
  3. Verify if the credentials for the Site24x7 user account have expired, been locked, or are disabled.

Step 2: Investigate if the login is successful

If you can log in successfully using the credentials, but the error persists in Site24x7, any of the following issues may need to be addressed on your end. Proceed with the checks below:

1. Review event logs
  1. Go to the Monitor tab in the vSphere Client, then click Events.
  2. Filter the events to identify messages or warnings related to failed login attempts from the IP address of the Site24x7 On-Premise Poller.
  3. Look for specific error codes or messages, such as invalid login, locked account, or session limits reached, originating from the IP address of the On-Premise Poller.


2. Verify session limits
  1. In the vSphere Client, go to the Monitor tab and select Sessions
  2. Review the number of active sessions. 
  3. If the active sessions have exceeded the maximum concurrent session limit for vCenter or ESX, Site24x7 might not be able to create a new session with the resource.
To resolve the issue, terminate unnecessary sessions in the vSphere Client or increase the maximum concurrent session limit in vCenter and ESX to allow Site24x7 to establish a new session.

If the number of Site24x7 sessions exceeds 50, contact Site24x7 support for further analysis.


3. Verify issues with LDAP settings
  1. Navigate to Administration > Single Sign-On > Configuration > Identity Sources in the vSphere Client.
  2. Check that the LDAP identity source settings are accurate and up to date.
If the issue continues even after completing these checks, contact us at support@site24x7.com for additional support.

    • Related Articles

    • Troubleshooting VMware ESX hardware monitor sensor data

      If your VMware ESX hardware monitor displays inaccurate or outdated sensor data that does not reflect the actual state of the ESX server, follow these steps to refresh the hardware health data: Steps to fix outdated sensor data: Log in to the VMware ...
    • Troubleshooting Steps for VMware Monitors

      Virtual Machine To troubleshoot the VM issues, check: The prerequisites for vMotion to be captured by Site24x7. Whether the VM is deleted in vSphere. Whether the VM name was changed in your environment. Whether the associated ESXi or vCenter is ...
    • Troubleshooting tips for log collection errors

      The following is a list of possible log collection errors and the solutions to fix them: Error message Reason Solution Upload Limit Reached You might have reached the maximum upload limit configured for this log type in the current billing cycle. ...
    • Different types of polling for VMware resources

      Site24x7 supports monitoring for different VMware resources like vCenter, clusters, ESX/ESXi host, virtual machines (VMs), datastores, resource pools, and snapshots using On-Premise Poller. You can monitor the discovered VMware child resources using ...
    • What are the common OAuth errors and how to solve them?

      While configuring OAuth,  here are a few errors that you might face. They are: Invalid Redirect URI - Error_invalid_redirect_uri Invalid Code - invalid_code OAuth Scope associated to the OAuth Access Token is disallowed. - error_code: 1120 Invalid ...