LDAP Error Causes workflow fail | Community
Skip to main content
R
Ramprakash_T
November 10, 2021
Solved

LDAP Error Causes workflow fail

  • November 10, 2021
  • 3 replies
  • 1824 views

Hi,

We are getting the strange error with LDAP. "operationMgt" workflow continuously getting failed daily.
Below is the error code.

 

11/09/2021 3:12:02 PM Unable to connect with login 'abc123'. Make sure that the login is correct and that the account is not disabled. If you wish to stop the workflow, use the unconditional stop.
11/09/2021 3:12:02 PM LDA-340002 [ldap_start_tls_s] LDAP error with server abc.abnet.ae:389 (err=82, Local Error) (Local Error)


We tried unconditional stop and started again. Again the workflow is getting failed after few hours or the next day. There is no changes done for the login abc123 in LDAP directory. The user is active in both LDAP directory and Adobe campaign client console.

 

Thanks,
Ram

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by david--garcia

    This option was introduced in the build below, you have to create it and set it to 1, after that you will see debug messages on the workflow, after you are done, set it back to 0

    Release 19.1 - Build 9026{#release-19-1-build-9026}

    3 replies

    Jyoti_Yadav
    Jyoti_Yadav
    Level 8
    November 10, 2021

    Hi @ramprakash_t ,

     

    Someone might have changed user 'abc123' password. Try to change password and update the same and then try to connect.

    Error is related to "Not able to login".

     

    Thanks,

    Jyoti

      R
      Ramprakash_TAuthor
      November 25, 2021

      Hi @jyoti_yadav,

       

      We confirmed there is no changes done for the user in LDAP Directory. We tried restarting the workflow with multiple operators. Also tried with the "Admin" operator, still the workflows failing randomly.

      Initially it was only OperationMgt workflow failing. Now other workflows also start getting failed due to the LDAP error.

       

      Thanks,

      Ram.

      david--garcia
      david--garcia
      Level 10
      November 10, 2021

      operationMgt throws inconsistent auth error sometimes and have nothing to do with credential changes, it literally happened to me today.

       

      1. Go to platform options and set value to 1 for the following option NmsOperation_OperationMgtDebug
      2. Re-execute the workflow

      You will notice a couple of workflows mentioned in the audit tab, those are usually the culprit, try to start the workflow outside of the campaign context (try stopping them or starting them by finding them in the workflow view folder)

       

      In my case the workflows that were stopped and had to be restarted first were mentioned in the log. The credential error is very misleading indeed.

       

      10/11/2021 15:15:49 scheduler Starting targeting workflow 'WKF1193' for campaign 'UK > Private Clients > Content > Newsletter (OP370)'

       

        david--garcia
        david--garcia
        Level 10
        November 15, 2021

        @ramprakash_tis the issue resolved ? or is it still happening.

        R
        Ramprakash_TAuthor
        November 25, 2021

        @david--garcia , The issue is still not resolved. I checked for the option NmsOperation_OperationMgtDebug. But it is not available in both stage and prod environment. We are using the version v7 9032. 

         

        The operationMgt workflow  failing 1or 2 times a day due to LDAP error. There are some other workflows also randomly failing due to LDAP error. We confirmed there is no changes done in LDAP directory.

         

        Thanks,

        Ram

        david--garcia
        david--garciaAccepted solution
        Level 10
        November 26, 2021

        This option was introduced in the build below, you have to create it and set it to 1, after that you will see debug messages on the workflow, after you are done, set it back to 0

        Release 19.1 - Build 9026{#release-19-1-build-9026}

          Terms & ConditionsAccessibility statement

          Loading footer...