Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Cannot log in to vCenter Server after editing the ADAM database (1024329)

Last Updated: 2/15/2016Categories: TroubleshootingTotal Views: 9613Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Unable to log in to the vCenter Server instance after using ADSI Edit to manually remove the vCenter Server instance from a problematic Linked Mode setup.

Note: For information on manually removing a vCenter Server instance using ADSI Edit, see Removing a linked vCenter Server from vSphere Client fails with the error: vCenter server not connected (1017631).

You are unable to log into vCenter Server after deleting the OU=Instance data from the ADAM database.

The VMware VirtualCenter Server service and the VMware VirtualCenter Management Webservices service start successfully.

Cause

This issue occurs if the vCenter Server instances are linked, even though they do not appear to be. When deleting the OU=Instance entry from the ADAM database on one vCenter Server, it is deleted from the linked vCenter Server because they share the ADAM repository. The missing OU=Instance impacts the functionality of the vCenter Server instance.

Resolution

To resolve this issue, the ADAM database must be rebuilt on the problematic vCenter Server instance.

To rebuild the ADAM database:

Note: Ensure that you have the vCenter Server license keys before proceeding.

Using the vCenter Server Linked Mode Configuration option on the Start menu, ensure that Linked-Mode is disabled on the working vCenter Server instance.

Stop the VMware VirtualCenter Server service and the VMware VirtualCenter Management Webservices service on the problematic vCenter Server instance.

Open a command prompt (as Administrator on Windows 2008) and run this command to navigate to the vCenter install directory:

In 32-bit vCenter Server 4.0 or 4.1:

cd "C:\Program Files\VMware\Infrastructure\VirtualCenter Server\"

In 64-bit vCenter Server 4.0:

cd "C:\Program Files (x86)\VMware\Infrastructure\VirtualCenter Server\"

Run this command:

jointool.bat init --name hostname --vimURL https://hostname:443/sdk --webServiceURL https://hostname:8443/vws --force

Where hostname is the resolvable name of the local vCenter Server.

Note: If custom ports are used for vCenter or Webservices, modify the command appropriately. This command may take two to three minutes to complete.

Click Start > All Programs > Administrative Tools > ADSI Edit.

Right-click ADSI Edit and click Connect to.

Under Connection Point, select Select or type a Distinguished Name or Naming context and type:

dc=virtualcenter,dc=vmware,dc=int

Under Computer, select Select or type a domain or server, enter the local vCenter Server host name, and click OK.

Expand the tree items in the left pane and find the OU=Instances entry.

Right-click OU-Instances > Properties for the instance, locate the vmw-vc-URL, and verify that the correct local vCenter host name is set.

Start the VMware VirtualCenter Server service and the VMware Management Webservices service.

Log into the problematic vCenter Server instance and re-enter any missing vCenter license keys. A warning indicating that the evaluation mode has expired is displayed until valid license keys are provided.

Re-license all hosts.

Related Information

Notes:

All custom roles are removed through this process. If required you must re-create custom roles and reassign permissions accordingly.

If this vCenter Server is a part of a Linked Mode configuration, information pertaining to the problematic VC instance should be removed from ADAM on the remaining VC instances. For more information, see Removing a linked vCenter Server from vSphere Client fails with the error: vCenter server not connected (1017631).

Removing a linked vCenter Server from vSphere Client fails with the error: vCenter server not connected

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
主机处于锁定模式时的权限问题 (1003117)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server

Related Versions:

VMware vCenter Server 5.5.x

VMware vCenter Server 5.1.x

VMware vCenter Server 5.0.x

VMware vCenter Server 4.1.x

VMware vCenter Server 4.0.x

Take Our Survey

Support Assistant