UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21. Read more.
UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21.Read more.
Absent Member.
Absent Member.
3153 views

iPrint Manager error -631

I am having trouble keeping the iPrint Print Manager service running. I was first seeing -601 Cannot bind to eDir. eDirectory is working fine and time and replication reports are clean. I now get the following error trying to get the print manager service to run:

FATAL The iPrint Manager was unable to set the generation number. Error Code: -631
INFO The iPrint Manager has unloaded successfully
WARNING A child process has gone or the iPrint Manager has just experienced a fatal error. It will be restarted by it's monitoring process


I have already attempted to update any of the iPrint modules. I have also reconfigured the iPrint through OES install and configuration.

I have also reset Default Certificates and also ran namconfig -k and then ndsconfig upgrade, to no avail.

Any help in advance will be greatly appreciated.
0 Likes
6 Replies
Absent Member.
Absent Member.

I assume this is iPrint running on an OES2/Linux server, but please
confirm the exact OS version and SP level you are using.
The error "-601" for the iPrint login means "object name not found". This
could point to a mismatch between the iPrint configuration files on the
server and the iPrint objects in eDirectory. This could for exemple occur
if you configure iPrint multiple times on the same server using different
names and options each time.
To further investigate your problem, I suggest you go into the
/etc/opt/novell/iprint/conf directory of your server and you look at the 2
main configuration files ipsmd.conf (for the manager) and ipsd.conf (for
the driver store).
For both files, make sure that the parameter DSServer1 points to a valid
eDirectory server with a replica holding the manager and driver store
objects. Also verify that the PSMObjectDN and IDSObjectDN options point to
existing eDirectory objects that represent the iPrint Manager and the
Driver Store.

--
Marcel Cox
http://support.novell.com/forums
------------------------------------------------------------------------
Marcel Cox's Profile: http://forums.novell.com/member.php?userid=8
0 Likes
Absent Member.
Absent Member.

Marcel_Cox;1976665 wrote:
I assume this is iPrint running on an OES2/Linux server, but please
confirm the exact OS version and SP level you are using.
The error "-601" for the iPrint login means "object name not found". This
could point to a mismatch between the iPrint configuration files on the
server and the iPrint objects in eDirectory. This could for exemple occur
if you configure iPrint multiple times on the same server using different
names and options each time.
To further investigate your problem, I suggest you go into the
/etc/opt/novell/iprint/conf directory of your server and you look at the 2
main configuration files ipsmd.conf (for the manager) and ipsd.conf (for
the driver store).
For both files, make sure that the parameter DSServer1 points to a valid
eDirectory server with a replica holding the manager and driver store
objects. Also verify that the PSMObjectDN and IDSObjectDN options point to
existing eDirectory objects that represent the iPrint Manager and the
Driver Store.

--
Marcel Cox
http://support.novell.com/forums
------------------------------------------------------------------------
Marcel Cox's Profile: NOVELL FORUMS - View Profile: Marcel_Cox



I was able to verify that the files contain the correct information. The DSServer1 points to the server itself, which it should correct? All other options appear to point to the correct information. Also I am not receiving the -601 error I am getting the error that is in my original post.

Also I am using SLES 10 SP3 with OES SP2 and all of the latest updates.
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

dshofkom33;1976739 wrote:
I was able to verify that the files contain the correct information. The DSServer1 points to the server itself, which it should correct? All other options appear to point to the correct information. Also I am not receiving the -601 error I am getting the error that is in my original post.

Also I am using SLES 10 SP3 with OES SP2 and all of the latest updates.


And you have made sure that cups is disabled in the runlevel editor?

Thomas
0 Likes
Absent Member.
Absent Member.

Was your iPrint manager ever working or is this still your attempt to get
it working in first place? If it was working before, what made it stop
working?

--
Marcel Cox
http://support.novell.com/forums
------------------------------------------------------------------------
Marcel Cox's Profile: http://forums.novell.com/member.php?userid=8
0 Likes
Absent Member.
Absent Member.

Marcel_Cox;1976773 wrote:
Was your iPrint manager ever working or is this still your attempt to get
it working in first place? If it was working before, what made it stop
working?

--
Marcel Cox
http://support.novell.com/forums
------------------------------------------------------------------------
Marcel Cox's Profile: NOVELL FORUMS - View Profile: Marcel_Cox


I had iPrint running briefly on another server with the same build, but it was upgraded to OES 2 SP2 from the inception of SLES and OES. I then decided I wanted to build a new "Print" server only. So this new build does not work.
0 Likes
Absent Member.
Absent Member.

thsundel;1976771 wrote:
And you have made sure that cups is disabled in the runlevel editor?

Thomas


Yes CUPS is disabled in RUNLEVEL
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.