Skip to main content
NetApp Knowledge Base

WFA custom workflow fails while joining CIFS server to AD

Views:
55
Visibility:
Public
Votes:
0
Category:
oncommand-workflow-automation-wfa
Specialty:
legacy
Last Updated:

Applies to

  • OnCommand WorkFlow Automation (WFA)5.1.x
  • ONTAP 9.x

Issue

  • WFA custom workflow fails first time while executing the step vserver joining to AD
  • However it is always successful in next attempt when the failed workflow is rerun again manually
  • Errors in the wfa.log:
ERROR [com.netapp.wfa.command.execution.instance.impl.ExecutionInstanceDaoImpl] (Thread-2973 (ActiveMQ-client-global-threads)) [Child workflow execution]   Command failed for Workflow '<workFolw_Name>' with error : Failed to create the Active Directory machine account "<CIFS_Server_Name>". Reason: SecD Error: no server available Details: Error: Machine account creation procedure failed   [  0 ms] Trying to re-use machine account '<CIFS_Server_Name>' in '<AD_Server_Namde>' for Vserver'<SVM_Name>' **[    11] FAILURE: Unable to contact DNS to discover domain ** controllers.   [    11] Unable to connect to any (0) domain controllers.   [    17] Unable to contact DNS to discover domain controllers.   [    23] No servers available for MS_LDAP_AD, vserver: 648,            domain: <AD_Server_Name>. .

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.