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

Upgrading or Installing vCenter Server 4.x (or later) fails with the error: Setup cannot create vCenter Server Directory Services (1015887)

Last Updated: 3/20/2024Categories: How toTotal Views: 40922Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Upgrading to vCenter Server 4.x (or later) fails

The upgrade rolls back before completion.

You see one or both of these errors:

Setup cannot create vCenter Server Directory Services instance.

Error 28038. Setup cannot create vCenter Server Directory Services instance.

The %TEMP%/jointool-0.log file generated during the upgrade attempt contain entries similar to:

[2009-11-17 12:28:38 INFO] JoinTool started
[2009-11-17 12:28:38 INFO] Storage directory for LDAP instance: D:\VMware Infrastructure\VirtualCenter Server\VMwareVCMSDS
[2009-11-17 12:28:38 INFO] Operation Mode: initialize
[2009-11-17 12:28:39 INFO] Unable to recover from existing data:
Action: Get Recovery info from DB
Problem: No records in the database for recovery policy : "MOST_RECENT"
[2009-11-17 12:28:39 INFO] This is not an error unless the install attempt was on a pre-existing database on which vCenter Server was installed already.
[2009-11-17 12:28:39 INFO] Creating directory services instance VMwareVCMSDS
[2009-11-17 12:28:39 INFO] LDAP port = 389
[2009-11-17 12:28:39 INFO] Base DN = dc=virtualcenter,dc=vmware,dc=int
[2009-11-17 12:28:39 INFO] Storage dir = D:\VMware Infrastructure\VirtualCenter Server\VMwareVCMSDS
[2009-11-17 12:33:57 INFO] Creation complete
[2009-11-17 12:33:57 INFO] Resetting VC LDAP service SSL port
[2009-11-17 12:33:58 INFO] Service 'VMwareVCMSDS' is shutdown
[2009-11-17 12:33:58 INFO] Importing "D:\VMware Infrastructure\VirtualCenter Server\ldif\vc_schema.ldf". Host: 127.0.0.1; Port: 389
[2009-11-17 12:33:59 INFO] Importing LDIF on 127.0.0.1 failed with Action: LDIF Import
Action: Process execution
Problem: Import LDIF failed: 8224. Output: Connecting to "127.0.0.1"
The connection cannot be established
The error code is 8224
No log files were written. In order to generate a log file, please
specify the log file path via the -j option.
Possibly pure IPV6 machine.
Attempting to import LDIF to ::1
[2009-11-17 12:33:59 INFO] Importing "D:\VMware Infrastructure\VirtualCenter Server\ldif\vc_schema.ldf". Host: ::1; Port: 389
[2009-11-17 12:33:59 ALLVARLIG] Operation "Create standalone instance VMwareVCMSDS" failed: : Action: Create Standalone Instance
Action: Creation of standalone instance
Action: LDIF Import
Action: Process execution
Problem: Import LDIF failed: 8224. Output: Connecting to "::1"
The connection cannot be established
The error code is 8224
No log files were written. In order to generate a log file, please
specify the log file path via the -j option.
[2009-11-17 12:33:59 ALLVARLIG] Recovering from failed Operation "Create standalone instance VMwareVCMSDS"
[2009-11-17 12:33:59 INFO] Removing directory services instance VMwareVCMSDS
[2009-11-17 12:34:01 INFO] Removal complete
[2009-11-17 12:34:01 ALLVARLIG] Recovery successful
[2009-11-17 12:34:01 ALLVARLIG] Execution error.

[2009-11-10 23:39:49 INFO] JoinTool started
[2009-11-10 23:39:49 INFO] Storage directory for LDAP instance: D:\Program Files (x86)\VMware\Infrastructure\VirtualCenter Server\VMwareVCMSDS
[2009-11-10 23:39:49 INFO] Operation Mode: initialize
[2009-11-10 23:39:49 INFO] Recovery info : ID : 1073741833 Date : 2009-11-10 23:15:06.34 Change Id : 24584
[2009-11-10 23:39:49 INFO]
Database LDAP backups found. Launching recovery mode.
[2009-11-10 23:39:49 INFO] Recovery info : ID : 1073741833 Date : 2009-11-10 23:15:06.34 Change Id : 24584
[2009-11-10 23:39:49 INFO]
Restoring as a standalone instance.
[2009-11-10 23:39:49 INFO] Creating directory services instance VMwareVCMSDS
[2009-11-10 23:39:49 INFO] LDAP port = 389
[2009-11-10 23:39:49 INFO] Base DN = dc=virtualcenter,dc=vmware,dc=int
[2009-11-10 23:39:49 INFO] Storage dir = D:\Program Files (x86)\VMware\Infrastructure\VirtualCenter Server\VMwareVCMSDS
[2009-11-10 23:39:56 SEVERE] Operation "Recover" failed: : Action: Recover LDAP instance
Action: Creation of standalone instance
Action: Create Instance
Problem: Creation of instance VMwareVCMSDS failed: The wizard could not access the registry.
Error code: 0x800706fd
The trust relationship between this workstation and the primary domain failed.

[2009-10-14 11:51:23 INFO] JoinTool started
[2009-10-14 11:51:23 INFO] Storage directory for LDAP instance: C:\Program Files\VMware\Infrastructure\VirtualCenter Server\VMwareVCMSDS
[2009-10-14 11:51:23 INFO] Operation Mode: initialize
[2009-10-14 11:51:23 SEVERE] Failed to load certificate: : Failed to load certificate
[2009-10-14 11:51:23 SEVERE] Execution error.

Resolution

This issue may occur for numerous reasons.

A third-party antivirus program prevents the installer from completing.

To resolve this issue, disable any third-party antivirus programs during the upgrade or installation.

Ensure that your passwords do not contain spaces or special characters. For more information, see Troubleshooting errors resulting from non-ASCII names (1003866).

If you are upgrading to vCenter Server 4.x (or later) on Windows Server 2003 or Windows Server 2008, this issue may occur if the Active Directory Lightweight Directory Services (AD LDS) role is already installed on Windows Server 2008 or if the Active Directory Application Mode Service Pack 1 is already installed on Windows Server 2003.

To resolve this issue, remove the role and retry the upgrade. For more information on removing the role, see http://technet.microsoft.com/en-us/windowsserver/2008/dd448612.aspx.

If you are upgrading to vCenter Server 4.x (or later) on Windows Server 2003, there may be an issue with ADAM. To resolve this issue, follow these steps, then retry the upgrade:

Remove ADAM from the vCenter Server.

Browse to C:\Windows and delete the ADAM directory.

Ensure that the Windows Network Service has Read permission on the root drive of the directory where vCenter Server is being installed.

For more information, see vCenter Server installation might fail due to insufficient permissions on the root directory or registry (1010938).

Reboot vCenter Server.

Ensure that the vCenter Server system has an Ethernet port assigned (physical or virtual) and an active network connection before performing the installation.

If you see an entry similar to The trust relationship between this workstation and the primary domain failed in the %TEMP%/jointool-0.log file, add the vCenter Server host to the domain and retry the upgrade.

If you see an entry similar to 2009-10-14 11:51:23 SEVERE] Failed to load certificate: : Failed to load certificate in the %TEMP%/jointool-0.log file, check if the custom rui.crt file has text before the -----BEGIN CERTIFICATE----- line. This text may cause problems with jointool.

Ensure that the rui.crt file starts with -----BEGIN CERTIFICATE----- and ends with -----END CERTIFICATE-----.

Note: Ensure to use a plain text editor that does not insert white space or special characters into the file. Editors such as Notepad and Wordpad may insert white space or special characters into the file.

During installation, the service VMwareVCMSDS is created. You must wait until the point of the installation when this service is created. From the Services view in the Computer Manager, change log on as: to SYSTEM instead of NETWORK SERVICE, then manually start the service. Retry the upgrade.

You may need to truncate the VPX_BINARY_DATA table in the vCenter database if you see these errors. Run this SQL query on the vCenter Server database to truncate VPX_BINARY_DATA, which contains the ADAM backup:

truncate table VPX_BINARY_DATA

Note: Ensure to delete only the data from table and not the table itself.

Verify if you get the following error in the %TEMP%/jointool-0.log file:

Problem: Creation of body failed VMwareVCMSDS: An unknown error occurred while installing Active Directory.
Error code: 0x800705dc Error code: 0x800705dc
The event log file is corrupted. The event log file is corrupted.
[2009-09-01 00:00:00 GRAVE] Recovering from failed Operation "Create standalone instance VMwareVCMSDS" [2009-09-01 00:00:00 SERIOUS] Recovering from Operation failed "Create standalone instance VMwareVCMSDS"
[2009-09-01 00:00:00 GRAVE] Recovery successful [2009-09-01 00:00:00 SERIOUS] Recovery successful
[2009-09-01 00:00:00 GRAVE] Execution error. [2009-09-01 00:00:00 SERIOUS] Execution error

If you get this error, re-installing ADAM or giving Windows Network Service Read permission on the root drive of the directory where vCenter Server is being installed does not resolve the issue.

To resolve this issue, you must correct the following permissions in the Windows registry.

Go to Start > Run, type regedit, and click OK.

Navigate to the following registry keys:

HKLM\SYSTEM\ControlSet001\services\eventlog\ADAM (VMwareVCMSDS)
HKLM\SYSTEM\ControlSet001\services\eventlog\ADAM (VMwareVCMSDS)

Right-click each key and select Permissions. Modify the key with the following settings:

Administrators – Full Control

NETWORK SERVICE – Full Control

SYSTEM – Special Permissions

Navigate to the following key:

HKLM\SYSTEM\ControlSet001\services\eventlog\Application

Right-click this key and select Permissions. Modify the key with the following settings:

Administrators – Full Control

NETWORK SERVICE – Full Control

SYSTEM – Full Control

Upgrade to vCenter Server 4.x (or later).

Related Information

For related information, see:

vCenter Server installation fails if the root drive of the directory where it is installed does not have Read permission (1010938)

Install process of vCenter Server 4.0 and 4.0 Update 1 might not be completed on Windows Server 2008 (1013822)

Troubleshooting errors resulting from non-ASCII names
vCenter Server installation might fail due to insufficient permissions on the root directory or registry
vCenter Server 4.x および 5.0 のバックアップとリストア
升级到 vCenter Server 4.x 失败，并显示以下错误：安装程序无法创建 vCenter Server 目录服务
vCenter Server 4.x へのアップグレードがエラー「Setup cannot create vCenter Server Directory Services」で失敗する

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

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

KB
•
VOMA(vSphere On-disk Metadata Analyzer)를 사용하여 VMFS 메타데이터 일관성 확인 (2036767)

KB
•
启动 RHEL Linux 虚拟机时，您将看到以下消息： 无法在 CPU 上设置 NMI 监视程序 (2031297)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-4 of 4

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