vCenter Server 4.0 installation error: Setup cannot create vCenter Server directory Services instance


Symptoms


  • You see the following error when installing vCenter Server 4.0:

    Setup cannot create vCenter Server directory Services Instance
    Refer to C:\TEMP\....\jointool-0.log for more details.
    Click Yes to force this operation.
  • If you click Yes Error comes Setup cannot create vCenter Server Directory Services instance. Error 28038or No, the vCenter Server installation rolls back.
  • The jointool-0.log contains entries similar to:

    [Date Time ServerName] Operation "Create standalone instance VMwareVCMSDS" failed: : Action: Create Standalone Instance
    Action: Creation of standalone instance
    Action: Create Instance
    Problem: Creation of instance VMwareVCMSDS failed: The folder C:\Program Files\VMware\Infrastructure\VirtualCenter Server\VMwareVCMSDS is compressed. Active Directory cannot be installed in a compressed folder. Select a folder that is not compressed.
    [Date Time ServerName] Recovering from failed Operation "Create standalone instance VMwareVCMSDS"
    [Date Time ServerName] Recovery successful
    [Date Time ServerName] Execution error.
Resolution:
Method 1 : This error is caused by the fact that the “Network Service” does not have enough permissions on the root of the drive you’re installing vCenter on. The solution is pretty straight forward and has been described in the KB article.

1. Right-click the root drive and click Properties.
2. Click the Security tab.
3. Under Group and user names, click Add.
4. Enter Network Service and click OK.
5. Check Allow for the Read permission for the Network Service account in the Permissions for Administrators pane.
6. Click App y and OK.
Method 2:   If above does not work , Make sure .NET 3.5 SP1 is installed http://www.microsoft.com/en-in/download/details.aspx?id=22 or turn on  the feature  from "Programs and Features"

Comments

Post a Comment

Popular posts from this blog

Enterprise CA option is greyed out / unavailable

Many times, when installing Active Directory Certificate Services they cannot choose to install Enterprise Certification Authority, because it’s unavailable as in following picture: Well, you need to fulfill basic requirements: Server machine has to be a member server (domain joined). You can run an Enterprise CA on the Standard, Enterprise, or Data Center Windows Edition. The difference is the number of ADCS features and components that can be enabled. To get full functionality, you need to run on Enterprise or Data Center Windows Server 2008 /12/R2/ Editions.  In order to install an Enterprise CA, you must be a member of either Enterprise Admins or Domain Admins in the forest root domain (either directly or through a group nesting). If issue still persists, there is probably a problem with getting correct credentials of your account. There are many thing that can cause it (network blockage, domain settings, server configuration, and other issues). In al...
Read more

Rearm the Office 2013 installation

Image
There is a 25-day grace period from the time of installation of Key Management Service (KMS) clients before notifications to activate are displayed to the user. If you want to deploy an image, you must rearm your Office 2013 installation before you capture the image. If you do not rearm, users see notification dialog boxes at the time that the image is deployed, instead of 25 days after deployment. The 25-day grace period gives ample time for a KMS host to be found and activation to succeed. If activation is successful, users do not see notifications to activate. Rearm the Office installation Rearming does the following important tasks: Resets the grace timer to 30 days. Freezes the grace timer until either an Office application is run, or the ospp.vbs script is run. Resets the client computer ID (CMID). This is important because the KMS host uses the CMID to determine the num...
Read more

MP has rejected registration request due to failure in client certificate

Image
Issue:- We have System Center Configuration Manager 2012 R2 deployed on Windows Server 2008R2 host. Recently we have moved our Certification Authority to Windows Server 2012 , renewed Root CA Certificate and intermediate Certificates also migrated Hashing algorithm from 'sha1' to 'sha2'  . New Root CA and intermediate CA also present on client machines and on SCCM. However, i have discovered these errors on MP: MP has rejected registration request due to failure in client certificate (Subject Name: ) chain validation. If this is a valid client ,  Even though Newly imaged machines are getting SCCM client installed but won't see all the client cycle under 'Actions tab' and also  'client certificate shows "None".  The operating system reported error 2148204809: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.  Solution:- Register  new Certificate of Root CA    under SCCM20...
Read more