${resource:CF_GenericContent}test

If an answer to your question is correct, click on "Verify Answer" under the "More" button.  The answer will now appear with a checkmark.  Please be sure to always mark answers that resolve your issue as verified.  Your fellow Community members will appreciate it!  Learn more.

  • State Suggested Answer
  • Replies replies
    2
  • Answers answer
    1
  • Subscribers subscribers
    30
  • Views views
    185
  • Users 0 members are here

novell.jclient.JCException: getEffectivePrivileges -626 ERR_ALL_REFERRALS_FAILED

Naveen Kumar

Hi ,

Some of the drivers are senidng below error message and events failed to process. Kindly assist on the case and let me know if you need more information. It is null driver.

Error:  (edited by geoffc to make it more readable)

 

[01/02/25 11:49:36.196]:LIFY-FTP-export ST: Query from policy 
01/02/25 11:49:36.196]:LIFY-FTP-export ST: 
<?xml version="1.0" encoding="UTF-8"?>
<nds dtdversion="4.0" ndsversion="8.x">
   <source>
      <product edition="Advanced" version="4.8.7.0100">DirXML</product>
      <contact>NetIQ Corporation</contact>
   </source>
   <input>
      <query-ex>
         <query-token>rO0ABXNyACxjb20ubm92ZWxsLm5kcy5kaXJ4bWwuZW5naW5lLk5EU1JlYWRlciRUb2tlbuWeJE0ga5xBAgACSgAFc3RhbXBJAAlzdGF0ZUhhc2h4cAAAAZQmofwzK0ilGQ==</query-token>
      </query-ex>
   </input>
</nds>
[01/02/25 11:49:36.197]:LIFY-FTP-export ST: Pumping XDS to eDirectory. 
[01/02/25 11:49:36.197]:LIFY-FTP-export ST: Performing operation query-ex for . 
[01/02/25 11:49:36.197]:LIFY-FTP-export ST: --JCLNT-- \VCC-CDS\VCC\System\DriverSet\LIFY-FTP-export : Duplicating : context = 1695744204, tempContext = 1695744239 
[01/02/25 11:49:36.410]:LIFY-FTP-export ST: --JCLNT-- \VCC-CDS\VCC\System\DriverSet\LIFY-FTP-export : Calling free on tempContext = 1695744239 
[01/02/25 11:49:36.417]:LIFY-FTP-export ST: Query from policy result 
[01/02/25 11:49:36.417]:LIFY-FTP-export ST: 
<?xml version="1.0" encoding="UTF-8"?>
<nds dtdversion="4.0" ndsversion="8.x">
   <source>
      <product edition="Advanced" version="4.8.7.0100">DirXML</product>
      <contact>NetIQ Corporation</contact>
   </source>
   <output>
      <status level="retry">Code(-9011) eDirectory returned an error indicating that the operation should be retried later: novell.jclient.JCException: getEffectivePrivileges -626 ERR_ALL_REFERRALS_FAILED</status>
   </output>
</nds>
[01/02/25 11:49:36.417]:LIFY-FTP-export ST: Query from policy

Parents
  • 0  

    Generally a 625 and 626 error are communication related errors.

    But this is the second or Nth (greater than first anyway) query in a query-ex, since it has a query-token cookie.  This should be honoured by eDir/IDM to finish the query. Complaining on the first one, would make sense, with a 626, cannot communicate in some fashion.  But one worked, returned the Query token.  Now it is not.

    Are you using a load balancer for eDir/LDAP that is not set to sticky connections?  Actually, no that can;t be it, since IDM runs inside eDir's local instance and talks to that all the time.

    PErhaps some more information about how you got this error would enlighten us?

Reply
  • 0  

    Generally a 625 and 626 error are communication related errors.

    But this is the second or Nth (greater than first anyway) query in a query-ex, since it has a query-token cookie.  This should be honoured by eDir/IDM to finish the query. Complaining on the first one, would make sense, with a 626, cannot communicate in some fashion.  But one worked, returned the Query token.  Now it is not.

    Are you using a load balancer for eDir/LDAP that is not set to sticky connections?  Actually, no that can;t be it, since IDM runs inside eDir's local instance and talks to that all the time.

    PErhaps some more information about how you got this error would enlighten us?

Children
No Data

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.