Environment
iPrint on OES2 Linux
Situation
New manager will not load.
New driver store will not load.
Log files show eDir authentication errors.
Error messages from manager log:
The iPrint Manager can not bind to eDir. Error FFFFFD8E .
WARNING The iPrint Manager was unable to update its status in eDir, Error: -626 .
Error messages from driver store log:
WARNING directoryLogin(): Unable to bind to directory server as object
New driver store will not load.
Log files show eDir authentication errors.
Error messages from manager log:
The iPrint Manager can not bind to eDir. Error FFFFFD8E .
WARNING The iPrint Manager was unable to update its status in eDir, Error: -626 .
Error messages from driver store log:
WARNING directoryLogin(): Unable to bind to directory server
Resolution
Edit the "DSServer1" entry in the ipsmd.conf file to point to a server that holds a replica of the print objects. ipsmd.conf is found in the etc/opt/novell/iPrint/conf directory.
Additional Information
The -626 error means that the eDirectory server could either not find or could not connect to a server holding a suitable replica. From the error code documentation:
-626 FFFFFD8E ALL REFERRALS FAILED
Source: eDirectory or NDS
Explanation: All attempts to connect to the available server while walking the eDirectory or NDS tree or resolving name requests have failed.
Possible Cause: An attempt to walk the eDirectory or NDS tree or resolve an object name failed because
* The source server was unable to connect to any of the available referrals (eDirectory or NDS servers).
* The referrals had no instance of the object in question while they held replicas of the target partition.
Possible Cause: An occurrence of this error during an attempt to connect to the target server could indicate LAN/WAN issues such as SAP/RIP filtering. It also could mean that discrepancies exist in the connectivity between partition boundaries.
Possible Cause: An occurrence of this error during an eDirectory or NDS background process could indicate that discrepancies exist in the connectivity between partition boundaries.
Action: Perform all or some of the following actions until the error disappears:
* On the source and target server, verify all network addresses and remote server IDs using the advanced menu options in DSREPAIR.
* Verify partition connectivity by doing the following:
o Start at the [Root] partition and ensure consistency between the replica rings of the servers that hold a replica of the partition.
o Continue this process downward through the eDirectory or NDS tree, examining each partition root, until the targeted partition is reached.
o Ensure that each replica ring has a master replica and that any required subordinate reference replicas are in place.
* From the Partition Continuity screen in NDS manager, run the Repair Network Addresses or Verify Remote Server IDs option. If you prefer to work from the server console, run the Repair Network Addresses option and Verify Remote Server ID Numbers option in DSREPAIR.
* From the Partition Continuity screen in NDS manager, verify that there is one master replica (in each row) for the partition in question.
* Check the replica states and make sure they are all "ON."
* Resolve whatever problems you find in the dsrepair.log file.
* Run the display servers command and see whether the tree name is present. If not, check issues related to the -625 errors (including SAP filtering).
* If creation time stamps are invalid, eliminate the problem by selecting the Advanced Option > Check External References in DSREPAIR (NetWare 4.1 or later version).
-626 FFFFFD8E ALL REFERRALS FAILED
Source: eDirectory or NDS
Explanation: All attempts to connect to the available server while walking the eDirectory or NDS tree or resolving name requests have failed.
Possible Cause: An attempt to walk the eDirectory or NDS tree or resolve an object name failed because
* The source server was unable to connect to any of the available referrals (eDirectory or NDS servers).
* The referrals had no instance of the object in question while they held replicas of the target partition.
Possible Cause: An occurrence of this error during an attempt to connect to the target server could indicate LAN/WAN issues such as SAP/RIP filtering. It also could mean that discrepancies exist in the connectivity between partition boundaries.
Possible Cause: An occurrence of this error during an eDirectory or NDS background process could indicate that discrepancies exist in the connectivity between partition boundaries.
Action: Perform all or some of the following actions until the error disappears:
* On the source and target server, verify all network addresses and remote server IDs using the advanced menu options in DSREPAIR.
* Verify partition connectivity by doing the following:
o Start at the [Root] partition and ensure consistency between the replica rings of the servers that hold a replica of the partition.
o Continue this process downward through the eDirectory or NDS tree, examining each partition root, until the targeted partition is reached.
o Ensure that each replica ring has a master replica and that any required subordinate reference replicas are in place.
* From the Partition Continuity screen in NDS manager, run the Repair Network Addresses or Verify Remote Server IDs option. If you prefer to work from the server console, run the Repair Network Addresses option and Verify Remote Server ID Numbers option in DSREPAIR.
* From the Partition Continuity screen in NDS manager, verify that there is one master replica (in each row) for the partition in question.
* Check the replica states and make sure they are all "ON."
* Resolve whatever problems you find in the dsrepair.log file.
* Run the display servers command and see whether the tree name is present. If not, check issues related to the -625 errors (including SAP filtering).
* If creation time stamps are invalid, eliminate the problem by selecting the Advanced Option > Check External References in DSREPAIR (NetWare 4.1 or later version).