Verified Answers

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 Verified Answer
  • Replies replies
    7
  • Subscribers subscribers
    6
  • Views views
    859
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

iprnt 5.0.1 Appliance lose Groups and Identity Source

raffi321

Hello,

Our iPrint Server had in the last month two big problems:

1. Losed all Users and also the rights to the printers. A new synchronisation did not help.

2. Today the iPrint losed the Identity Sources.

How can we fix these big problems?

Regards,

Raffi

Parents
  • 0  

    What is(are) your Identity Source(s)?  And how is their health?

    ________________________

    Andy of KonecnyConsulting.ca in Toronto
    Please use the "Like" and/or "Verified Answers" as appropriate as that helps us all.

  • 0 in reply to   

    There are two eDir Servers connected with LDAPS. How should we verify their health?

  • 0   in reply to 

    On each of those eDir servers, run each of the below, stopping to fix any errors identified before bothering with the next step.   Essentially: Check that the servers are connecting well. Check they all partitions are synchronized within a reasonable time, usually minutes). And make sure there are no stuck obituaries on that server.

    ndsrepair -T

    ndsrepair -E
       (or alternatively for larger systems:  ndsrepair -E | egrep 'Partition|All'  )

    ndsrepair -C -Ad -A

    ________________________

    Andy of KonecnyConsulting.ca in Toronto
    Please use the "Like" and/or "Verified Answers" as appropriate as that helps us all.

Reply
  • 0   in reply to 

    On each of those eDir servers, run each of the below, stopping to fix any errors identified before bothering with the next step.   Essentially: Check that the servers are connecting well. Check they all partitions are synchronized within a reasonable time, usually minutes). And make sure there are no stuck obituaries on that server.

    ndsrepair -T

    ndsrepair -E
       (or alternatively for larger systems:  ndsrepair -E | egrep 'Partition|All'  )

    ndsrepair -C -Ad -A

    ________________________

    Andy of KonecnyConsulting.ca in Toronto
    Please use the "Like" and/or "Verified Answers" as appropriate as that helps us all.

Children

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.