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

Java Control Panel Icon "Application Not Found"

Image
Howto: Fix the "Application not found" error in the Java Control Panel icon. These same steps may be useful for other malfunctioning Windows Control Panel icons. In Windows 7, the Java Control Panel icon may be damaged / corrupted. Attempting to launch the icon results in "Explorer.exe : Application not found". Note the generic icon: When working properly, the circled icon should look like this: This problem appears to be an artifact from previous JRE installations and Sun's installation routines were flawed. Re-installing JRE (the Java Runtime Environment) does not resolve the problem. Immediate workaround: If needed, the Java Control Panel can be manually launched using this location: C:\Program Files (x86)\Java\JRE6\bin\Javacpl.exe As a side note, when launching, other-mouse-click the .exe and choose "Run as Administrator".  Running as Administrator resolves a bug where changes in the Control Panel (especially Auto-update changes) do not stic
Read more

Enterprise CA option is greyed out / unavailable

Image
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 all ca
Read more

Unable to connect to Wireless profile being pushed using GPO

Image
Today , some laptop users started reporting as they are unable to connect to ‘Wireless profile’ after SCEP installation has taken place. I found, most of the laptop users were having this issue. I immediately uninstalled SCEP but that didn’t help , tried removing Wi-Fi profiles under the path ‘C :\ProgramData\Microsoft\Wlansvc\Profiles\Interfaces\ Interface’ but that didn’t help too. Error - When checking event viewer, the only error that showed up is as follows 5 times in a row.          “Error skipping EAP method DLL path name validation failed. Error: typeId=25, authorId=0,vendorId=0,vendorType=0”, This error indicates a registry or missing corrupt file issue. ‘ EAPHost is a Microsoft Windows Networking component that provides an Extensible Authentication Protocol (EAP) infrastructure for the authentication of following protocols such as   802.1X   and   Point-to-Point (PPP). Cause - Symantec didn’t uninstall properly caused this issue. Resolution – After chec
Read more