Search the VMware Knowledge Base (KB)
View by Article ID

Cannot log in to the vRealize Operations UI after importing LDAP accounts (2013440)

  • 8 Ratings


  • Users cannot log in to the vRealize Operations UI after importing LDAP accounts.
  • User accounts in one of the domains do not see the metrics.
  • Users in other domains and the administrator are able to see the metrics.


This issue occurs if there are duplicate accounts for users. For example, when the user's domain account is authorized in vCenter Server and the account is also imported into the Enterprise version of vRealize Operations Manager (formerly known as VMware vCenter Operations Manager) via the LDAP Integration feature. The vRealize Operations Standard/Enterprise versions (formerly known as VMware vCenter Operations Manager Standard/Enterprise) do not support direct LDAP integration.


To resolve this issue, check for duplicate user accounts and disable the duplicate account.
To disable duplicate accounts:
Note: Ensure to take a backup of the database before making any changes. To accomplish this for vApps, shut down the vApp and then take a snapshot of the individual virtual machines. Remember to commit the snapshots after you verify that the issue is resolved.

  1. Log in to the vRealize Operations appliance virtual machine via SSH or the vSphere Client as the root user.

    Note: vRealize Operations 5.x vApp consists of two virtual machines. The postgres database is on the Analytics virtual machine. Login to the Analytics virtual machine as root.

  2. Run these commands to login to the integrated postgres database as the postgres user:

    vRealize Operations 1.0.x:

    # su postgres
    # psql -U alive -d alivevm

    vRealize Operations 5.0.x:

    # su postgres
    # psql alivevm

    Note: The psql command is not in the PATH statement for the postgres user if you see the error:

    bash: psql: command not found

    To resolve this issue:

    1. Change to the psql directory:

      cd /opt/vmware/vpostgres/9.0/bin

    2. Run the command:

      ./psql alivevm

  3. Run these commands at the psql prompt to export the user account table:

    alivevm=> \o /tmp/useraccount.csv

    alivevm=> SELECT userid, username, description FROM useraccount ORDER BY userid;

    Note : The \o option pipes the command output to a file. In this example, the output is piped to the /tmp/useraccount.csv file.

  4. Exit the psql session with \q:

    alivevm=> \q

  5. Run this command:

    # more /tmp/useraccount.csv

  6. Review the useraccount.csv file and determine if there are any duplicate usernames and make note of the related userid(s).
  7. To disable the duplicate user accounts:

    Note: This does not disable a user, it simply renames the account.

    1. Repeat Step 2 to log in to the database again.
    2. Run this update statement to rename the username of the user account

      alivevm=> UPDATE useraccount SET username = username||'_disabled' WHERE userid in ('2','3','N');

      Note: Replace the user ID in the IN statement (in this example, 2,3,N) with the user ID(s) of the duplicate user accounts you want to disable.

  8. Run these commands to restart the vRealize Operations services on the virtual machine:

    # su admin
    admin@firstvm-external:> vcops-admin restart

    Note: The vcops-admin restart command works only if you log in as an admin user.

See Also

Update History

05/03/2012 - Added the vCenter Operations 5.0.x commands to log in to the integrated postgres database

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 8 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)

Please enter the Captcha code before clicking Submit.
  • 8 Ratings