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

Joining the VMWare vCenter Server Appliance or VMware vRealize Automation Identity Appliance to a domain fails with the error: Error trying to join AD, error code [31] (2134063)

  • 33 Ratings

Symptoms

  • Joining the vCenter Server Appliance to a Domain fails with the error:

    Idm client exception: Error trying to join AD, error code [31], user...

  • Joining vRealize Automation Identity Appliance to a Domain fails with the error:

    Error invoking Active Directory tools

  • In the ssoAdminServer.log file in the vCenter Server Appliance, you see entries similar to:

    [YYYY-MM-DDTHH:MM:SS.xxxx pool-12-thread-4 opId=cebe1692-a4e4-4dd8-9922-e57217646849 ERROR com.vmware.identity.admin.server.ims.impl.SystemManagementImpl] Exception occurred: 'com.vmware.identity.idm.IDMException: Error trying to join AD, error code [31], user [administrator], domain [mydomain.net], orgUnit []'; stack='com.vmware.identity.idm.IDMException: Error trying to join AD, error code [31], user [administrator], domain [mydomain.net], orgUnit []
    at com.vmware.identity.idm.server.IdentityManager.joinActiveDirectory(IdentityManager.java:9925)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)

  • In the /var/log/messages file in the vRealize Automation server, you see entries similar to:

    2015-11-10T15:22:30-08:00 localhost lsassd[5933]: 0x7fe831aec700:Failed to run provider specific request (request code = 8, provider = 'lsa-activedirectory-provider') -> error = 31, symbol = ERROR_GEN_FAILURE, client pid = 15446

    Note: These log excerpts are an example. Date, time, and environmental variables may vary depending on your environment.

     For more information on log file locations, see:

Cause

This issue occurs when Windows 2012 uses Server Message Block version 2 (SMB2) and, by default, SMB1 is disabled.

Resolution

 This is a known issue affecting vCenter Server Appliance 5.5.x, vCenter Server Appliance 6.0.x and vRealize Automation Identity Appliance 6.0.

Currently, there is no resolution.

To work around this issue, enable the SMBv1.0 by running this command from an elevated command prompt on all Windows 2012 Domain Controllers:

sc config srv start=auto

For more information on enabling and disabling SMBv1.0, see the Microsoft Knowledge Base article 2696547.

Note: The preceding link was correct as of December 22, 2015. If you find the link is broken, provide a feedback and a VMware employee will update the link.

See Also

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

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