Logo Background

Oracle LDAP Error

  • By on May 30, 2009 | No Comments

    LDAP_WRAPPER_UPDATE_USER_FAIL (USER_NAME=USER) (REASON=ORA-20001: Unabled to call fnd_ldap_wrapper.update_user due to following reason: An unexpected error occured. Please contact System Administrator.)

    Afrer you have run the script as written in Oracle E-Business Suite and SSO/OID Integration, where we register the OID/SSO using txkrun.pl -script=SetSSOReg -registeroid=Yes and txkrun.pl -script=SetSSOReg -registersso=Yes, by default the provisioning template that will be deployed was the bi-directional provisioning template.

    Which means now when we update the user in Oracle Applications 11i E-Business Suite, by right it will automatically update the attribute of the user in OID.

    Make sure you have run the bulk load script to migrate the existing user from Oracle Applications 11i E-Business Suite to the new OID platform.

    If you still having the error LDAP_WRAPPER_UPDATE_USER_FAIL (USER_NAME=USER) (REASON=ORA-20001: Unabled to call fnd_ldap_wrapper.update_user due to following reason: An unexpected error occured. Please contact System Administrator.), use the steps below to get the details log files from Oracle Applications 11i E-Business Suite to troubleshoot further.

    ldap-error

    Troubleshoot & Fix LDAP Error From Log Generation

    1.Enable Apps debug by turn on logging at the statement level by setting these profile options at Site level. Go to System Administrator – Profile – System
    – FND: Debug Level to “Statement”
    – FND: Debug Module to “fnd.plsql.oid%”
    – FND: Debug Log Enabled to “Yes”

    2. Reproduce the problem where you get the error message LDAP_WRAPPER_UPDATE_USER_FAIL (USER_NAME=USER) (REASON=ORA-20001: Unabled to call fnd_ldap_wrapper.update_user due to following reason: An unexpected error occured. Please contact System Administrator.)
    3. Revert the profile options back to originial value.
    4. Run the following script against the Oracle Applications 11i database logged as APPS user

    REM
    REM  START OF SQL
    REM
    REM List any messages logged relating TO AS10g  integration
    REM Run this script against the Apps 11i DATABASE
    REM Logged  IN AS APPS USER
    REM
    -- set up SQLPLUS environment
    SET serveroutput  ON
    SET echo ON
    SET feedback ON
    SET long 10000
    SET pagesize  132
    SET linesize 100
    col user_name form a15
    col node form a15
    col  module form a50 wrap
    col message_text form a80 wrap
    col time_stamp form  a17
    col session_id form 999999999999
    spool AS10g_log_messages.txt
    --  Run the SQL to find any messages in the last 30 days
    -- relating to AS10g  integration
    SELECT
    to_char(TIMESTAMP, 'DD-MM-RR HH24:MI:SS')  time_stamp,
    user_name,
    node,
    module,
    message_text
    FROM  fnd_log_messages m, fnd_user u
    WHERE m.user_id = u.user_id
    AND  trunc(TIMESTAMP) >= sysdate -1
    AND
    (LOWER(module) LIKE  'fnd.wf.bes%'
    OR LOWER(module) LIKE 'fnd.plsql.oid%'
    OR LOWER(module) LIKE  'fnd.sso%'
    OR LOWER(module) LIKE 'oracle.apps.fnd.oid%'
    OR LOWER(module)  LIKE 'oracle.apps.fnd.sso%'
    )
    ORDER BY time_stamp,  log_sequence
    /
    spool off
    REM
    REM END OF  SQL
    REM
    Previous
    Next
    » Oracle APPS.FND_FILE Error
Leave a Comment