Anonymous_User Absent Member.
Absent Member.
1645 views

Error adding Win 2000 or XP drivers

This is an issue that I have encountered in two separate installations. In
both I started with NW 6.5 SP3 and encountered this error when I tried
adding a WIN 2000 or XP printer driver using iManager - Exception saving
resource print drivers configuration
NDPS Library Error Category: 1060004h
Other Error: FFFFFC50h

Tried and XP SP2 workstation and a WIN2000 workstation. Novell Client 4.91
and 4.91 SP1. It copies the diver and the printer show up in the list, when
you click apply the error pops up.(Browser - IE version 6.0.2800.1106)

Tried iprint client 4.06 on the workstation. Did not fix the problem.
Applied SP4a and iprint client 4.12. This did not fixed the problem.

Looked at TID 10090590 and 10094013. These talk about the same issue but
the fix do not seem to apply here. (NDPSM.NLM in SP4a is dated Aug 25, 2005).

I have been able to use NWADMN to add 2000 drivers. Seems like this is a
bug. Is there is another workaround?
0 Likes
4 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Error adding Win 2000 or XP drivers

lalls@valcom-m.com wrote:

>Other Error: FFFFFC50h


I found the following description for this error code:

<<<<<<<<<<<<<<
-944 0xFFFFFC50 NWDP OE RM NOT ADMIN SESSION>
NDPS, Resource Manager NLM program
Explain: The RMS bind attempted an operation that requires Admin rights.

Possible Cause: The user is not an Admin of the Broker object.

Action: Log in as the user Admin or as a user with equivalent rights.
>>>>>>>>>>>>>>>>>


This seems to indicate that this is a rights issue.
Maybe you should double check what user has manager rights to the Broker.

--
Marcel Cox (using XanaNews 1.17.6.6)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Error adding Win 2000 or XP drivers

We have recently discovered an issue with both IP and IPX being bound on
the server. Do you have both??? If so, this could be an issue with
the library DPLSV386.nlm..

If this is the case, email probello@novell.com and say to send to
iprintrox..

> lalls@valcom-m.com wrote:
>
> >Other Error: FFFFFC50h

>
> I found the following description for this error code:
>
> <<<<<<<<<<<<<<
> -944 0xFFFFFC50 NWDP OE RM NOT ADMIN SESSION>
> NDPS, Resource Manager NLM program
> Explain: The RMS bind attempted an operation that requires Admin

rights.
>
> Possible Cause: The user is not an Admin of the Broker object.
>
> Action: Log in as the user Admin or as a user with equivalent rights.
> >>>>>>>>>>>>>>>>>

>
> This seems to indicate that this is a rights issue.
> Maybe you should double check what user has manager rights to the

Broker.
>
> --
> Marcel Cox (using XanaNews 1.17.6.6)


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Error adding Win 2000 or XP drivers

I am logging in as admin. Created the broker as admin.

Yes I do have both IP and IPX bound to the server. I still have some queue
based printing.
> We have recently discovered an issue with both IP and IPX being bound on
> the server. Do you have both??? If so, this could be an issue with
> the library DPLSV386.nlm..
>
> If this is the case, email probello@novell.com and say to send to
> iprintrox..
>
> > lalls@valcom-m.com wrote:
> >
> > >Other Error: FFFFFC50h

> >
> > I found the following description for this error code:
> >
> > <<<<<<<<<<<<<<
> > -944 0xFFFFFC50 NWDP OE RM NOT ADMIN SESSION>
> > NDPS, Resource Manager NLM program
> > Explain: The RMS bind attempted an operation that requires Admin

> rights.
> >
> > Possible Cause: The user is not an Admin of the Broker object.
> >
> > Action: Log in as the user Admin or as a user with equivalent rights.
> > >>>>>>>>>>>>>>>>>

> >
> > This seems to indicate that this is a rights issue.
> > Maybe you should double check what user has manager rights to the

> Broker.
> >
> > --
> > Marcel Cox (using XanaNews 1.17.6.6)

>


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Error adding Win 2000 or XP drivers

lalls@valcom-m.com wrote:

>Yes I do have both IP and IPX bound to the server. I still have some queue
>based printing.


Note that you don't need IPX to print to print queues. You may only need
IPX if you have IPX based print servers on the backend. Generally, you can
easily reply the PSERVER backend with NDPS while keeping the queues on the
client side.

--
Marcel Cox (using XanaNews 1.17.6.6)
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.