Iprint Issues; Driver Store Fails To Create - Novell OPEN ENTERPRISE SERVER 2.0 SP2 - DOMAIN SERVICE FOR WINDOWS Manual

nldap -u
nldap -l

19.3 iPrint Issues

Section 19.3.1, "Driver Store Fails to Create," on page 212

19.3.1 Driver Store Fails to Create

Problem: Creation of driver store (or any other print object) fails with following error:
Internal Server Error
IPP Error: 0xF01F4
HTTP Error: 500
This occurs when a user tries to create a print object that does not exist in the base context set for the
LDAP search in the iPrint configuration file.
Assume that two or more peer containers exist at the top, such as, and , and the tree
o=abc o=xyz
admin exists in the as shown below:
o=abc
TREE
|__ o=abc
|__cn=admin,o=abc
|__ o=xyz
When you setup a DSfW name-mapped forest root domain in by using the tree admin
o=xyz
) and try configuring iPrint by using the domain administrator ( , you get
(cn=admin,o=abc o=xyz)
this error while creating the driver store in .
o=xyz
Why It Happens: The iPrint installer takes the root context of the user installing iPrint ( ) and
o=abc
sets it as default base context for the LDAP search. When you try to create a driver store as a domain
administrator of the container, the LDAP search fails to find the user creating the driver store.
o=xyz
Creating the drive store with the tree admin succeeds.
cn=admin,o=abc
Solution: The base context for LDAP search is stored in the
/etc/opt/novell/iprint/httpd/
as mentioned below:
conf/iprint_ssl.conf
AuthLDAPDNURL "ldaps://frd.xyz.com:1636/o=abc???(objectClass=user)"
The above configuration limits the LDAP search to . Removing the base context completely
o=abc
allows the LDAP search to start from the tree root, as shown below:
AuthLDAPDNURL "ldaps://frd.xyz.com:1636/???(objectClass=user)
212 OES 2 SP2: Domain Services for Windows Administration Guide