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

Deploying or Installing an additional Platform Service Controller 6.0 Update 1b fails during vmafd firstboot (2144612)

  • 2 Ratings

Symptoms

  • Installing or deploying an additional Platform Services Controller 6.0 Update 1b or vCenter Server 6.0 Update 1b with Embedded Platform Services Controller fails during vmafd first boot when joining an existing Single Sign-On Domain.
  • In the C:\ProgramData\VMware\vCenterServer\logs\vmdird\vmdir.log file for a Windows based Platform Services Controller Appliance or vCenter Server with Embedded Platform Services Controller or /storage/log/vmware/vmdird/vmdird-syslog.log file for a Platform Services Controller Appliance or vCenter Server Appliance with Embedded Platform Services Controller file, you see entries similar to:

    2016-02-10T11:22:12.957566+00:00 info vmdird  t@139998579447552 : Vmkdc: initializing directory
    2016-02-10T11:22:12.957571+00:00 info vmdird 
    t@140020327442176 : VmDir State (3)
    2016-02-10T11:22:12.957576+00:00 info vmdird 
    t@140020327442176 : Lotus Vmdird: running..., run mode = normal
    2016-02-10T11:22:24.660505+00:00 info vmdird 
    t@139998571054848 : Setting up a host instance (vsphere.local).
    2016-02-10T11:22:24.816473+00:00 err vmdird 
    t@139998571054848 : _VmDirSchemaATCompatibleCheck failed (9601)(missing attributetypes)
    2016-02-10T11:22:24.818387+00:00 err vmdird 
    t@139998571054848 : _VmDirSchemaOCCompatibleCheck failed (9601)(incompatible objectclass/contentrule (vmwSTSSingleLogoutService))
    2016-02-10T11:22:24.818421+00:00 err vmdird 
    t@139998571054848 : CoreLogicModifyEntry failed, DN = cn=aggregate,cn=schemacontext, (9623)(PreModifyPlugins failed - (9623))
    2016-02-10T11:22:24.818429+00:00 err vmdird 
    t@139998571054848 : InternalModifyEntry: VdirExecutePostModifyCommitPlugins - code(9623)
    2016-02-10T11:22:24.818437+00:00 err vmdird 
    t@139998571054848 : VmDirCopyPartnerSchema,421 failed, error(9623)
    2016-02-10T11:22:24.818442+00:00 err vmdird 
    t@139998571054848 : VmDirSrvSetupHostInstance failed. Error(9623)
    2016-02-10T11:22:24.818446+00:00 err vmdird 
    t@139998571054848 : VmDirSrvInitializeHost failed (9623)(SSO_Domain_Name)(Administrator)(Site_Name)( ldap://partner_psc_fqdn)(1 )
Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

This issue occurs if the existing Platform Services Controller is updated to 6.0 Update 1b 3343019 from a previous version. The deployment of an additional Platform Services Controller 6.0 Update 1b fails due to a schema mismatch during the VMware Directory Services vdcpromo operation.

Resolution

This is a known issue affecting vCenter Server and vCenter Server Appliance 6.0.

This issue is resolved in vCenter Server and vCenter Server Appliance 6.0 Update 2, available at VMware Downloads.

To work around this issue, correct the VMdir Schema on the existing Platform Services Controller 6.0 Update 1b. If you have multiple existing Platform Services Controller 6.0 Update 1b instances, perform this operation on all Platform Services Controllers.

Note: Ensure to take a backup or a Virtual Machine Snapshot of the Platform Services Controller before proceeding. For more information, see the Backing Up and Restoring a vCenter Server Environment section of the vSphere Installation and Setup guide.

Appliance Based Platform Services Controller:
  1. Connect to the Platform Services Controller with an SSH session as root.
  2. Run this command to enable access the Bash shell:

    shell.set --enabled true

  3. Type shell and press Enter.
  4. Stop the Platform Services Controller services with this command:

    service-control --stop --all


  5. Run this command to update the VMdir Schema:

    /usr/lib/vmware-vmdir/sbin/vmdird -c -u -f /usr/lib/vmware-vmdir/share/config/vmdirschema.ldif


  6. Start the Platform Services Controller services with this command:

    service-control --start --all


  7. Re-deploy the failed Platform Services Controller instance.

Windows Based Platform Services Controller:
  1.  Log in to the Platform Services Controller machine as an Administrator.
  2. Open an administrative command prompt.
  3. Change to the Platform Services Controller installation directory:

    cd C:\Program Files\VMware\vCenter Server\bin


    Note: This is the default installation path. If you have installed the Platform Services controller to another location, modify this command to reflect the correct install location.

  4. Run this command to stop all services:

    service-control --stop --all


  5. Run this command to update the VMdir Schema:

    C:\Program Files\VMware\vCenter Server\vmdird\vmdird.exe -c -u -f C:\ProgramData\VMware\vCenterServer\cfg\vmdird\vmdirschema.ldif


    Note: This command uses the default installation path. If you have installed the Platform Services controller to another location, modify this command to reflect the correct install location.

  6. Run this command to start all services:

    service-control --start --all


  7.  Re-install the failed Platform Services Controller instance.

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.

Feedback

  • 2 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.
  • 2 Ratings
Actions
KB: