Anonymous_User Absent Member.
Absent Member.
899 views

SP4a driver uploads look ok, but are not

I'm having a strange issue, and after looking around in this forum for a
little, it seems my issue is a little different. We have approx 30+
NW65SP4a, that were all recently updated from either NW6.5SP2 or SP3, in
or headquarters we have two iPrint servers (dont' ask why two, it's a long
story) that are identically configured with the exception of the domain
suffix, both were upgraded from NW6.5SP2 about a week ago. Since updating
to SP4a, I can not seem to upload drivers to the broker, but I can upload
drivers to other NW6.5SP4a servers in our tree that were recently updated.

The problem that I'm seening is that when I run iManage from one of our
remote servers (ServerQ) and attempt to upload drivers to BrokerB running
on ServerB, while running iManage from ServerQ it looks as though the
drivers actually make it to the broker, I just don't see the Yellow
exclamation point telling me to hit apply or OK to save my changes, but if
I do it anyway, the drivers are not there. I've checked the drvers folder,
not there, drivers do zip up in to a folder on c:\ndps\drvr_tmp, and then
disappear as if they've made it up sucessfully. I've updated to iPrint
client 4.12Beta, but this hasn't helped. I know it's not the driver,
because it uploads to other Brokers/Server, I don't think it's the UserID,
because the same ID does work to other servers. Apache is running on the
two servers, NLDAP is running on both servers, these two server do not
have replica's on them, but they never did have, since their creation. Any
ideas where to start?

../chris
0 Likes
3 Replies
Anonymous_User Absent Member.
Absent Member.

SP4a driver uploads look ok, but are not

There is 2 methods of uploading drivers, and you identified the
critical "visual" sign of the method of upload. If you do get the "Yellow
exclamation point telling hit apply or OK to save changes", this would
indicate that the HTTPSTK method was used. THis indicates that the
driver was uploaded to the server you are running iManager on. iManager
then informs the Broker that it has a driver on the iManager server in the
sys:\ndps\xfer directory that it needs to upload... If you don't get
the exclamation point, the driver should have been loaded directly to the
server where the broker is running via apache.

You can quickly eliminate uid problems by simply typing a secure URL to
the server running the broker as follows: "https://server address and/or
dns name/ipps". Try doing this 2 times, once with the address and once
with the dns name. You should be prompted for authentication. PRovide
the same credentials you did when logging into iManager... If this works
okay, you don't have uid or cert problems (the dreaded 401 issues)...

I would look at the apache log file on the server where the broker is
running. What does it indicate??? You could also try setting the iprint
client trace up on the workstation you are running iManager on. Do a
search for "iprint client troubleshoot" on support.novell.com. This
logging trace file might give you more information...


> I'm having a strange issue, and after looking around in this forum for a
> little, it seems my issue is a little different. We have approx 30+
> NW65SP4a, that were all recently updated from either NW6.5SP2 or SP3, in
> or headquarters we have two iPrint servers (dont' ask why two, it's a

long
> story) that are identically configured with the exception of the domain
> suffix, both were upgraded from NW6.5SP2 about a week ago. Since updating
> to SP4a, I can not seem to upload drivers to the broker, but I can upload
> drivers to other NW6.5SP4a servers in our tree that were recently

updated.
>
> The problem that I'm seening is that when I run iManage from one of our
> remote servers (ServerQ) and attempt to upload drivers to BrokerB running
> on ServerB, while running iManage from ServerQ it looks as though the
> drivers actually make it to the broker, I just don't see the Yellow
> exclamation point telling me to hit apply or OK to save my changes, but

if
> I do it anyway, the drivers are not there. I've checked the drvers

folder,
> not there, drivers do zip up in to a folder on c:\ndps\drvr_tmp, and then
> disappear as if they've made it up sucessfully. I've updated to iPrint
> client 4.12Beta, but this hasn't helped. I know it's not the driver,
> because it uploads to other Brokers/Server, I don't think it's the

UserID,
> because the same ID does work to other servers. Apache is running on the
> two servers, NLDAP is running on both servers, these two server do not
> have replica's on them, but they never did have, since their creation.

Any
> ideas where to start?
>
> ../chris


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: SP4a driver uploads look ok, but are not

On Wed, 02 Nov 2005 05:27:55 +0000, iprintrox wrote: Well, I've deleted my
alias for my ID (which was named the same as my user ID, just in the tree
root) and it looks like that corrected my issue, which doesn't make senss
why I couldn't upload only to two different servers only, all other
servers that I've tried have worked. Thanks for the suggestions.


> There is 2 methods of uploading drivers, and you identified the critical
> "visual" sign of the method of upload. If you do get the "Yellow
> exclamation point telling hit apply or OK to save changes", this would
> indicate that the HTTPSTK method was used. THis indicates that the
> driver was uploaded to the server you are running iManager on.
> iManager then informs the Broker that it has a driver on the iManager
> server in the sys:\ndps\xfer directory that it needs to upload... If
> you don't get the exclamation point, the driver should have been loaded
> directly to the server where the broker is running via apache.
>
> You can quickly eliminate uid problems by simply typing a secure URL to
> the server running the broker as follows: "https://server address
> and/or dns name/ipps". Try doing this 2 times, once with the address
> and once with the dns name. You should be prompted for authentication.
> PRovide the same credentials you did when logging into iManager... If
> this works okay, you don't have uid or cert problems (the dreaded 401
> issues)...
>
> I would look at the apache log file on the server where the broker is
> running. What does it indicate??? You could also try setting the
> iprint client trace up on the workstation you are running iManager on.
> Do a search for "iprint client troubleshoot" on support.novell.com.
> This logging trace file might give you more information...
>
>
>> I'm having a strange issue, and after looking around in this forum for
>> a little, it seems my issue is a little different. We have approx 30+
>> NW65SP4a, that were all recently updated from either NW6.5SP2 or SP3,
>> in or headquarters we have two iPrint servers (dont' ask why two, it's
>> a

> long
>> story) that are identically configured with the exception of the domain
>> suffix, both were upgraded from NW6.5SP2 about a week ago. Since
>> updating to SP4a, I can not seem to upload drivers to the broker, but I
>> can upload drivers to other NW6.5SP4a servers in our tree that were
>> recently

> updated.
>>
>> The problem that I'm seening is that when I run iManage from one of our
>> remote servers (ServerQ) and attempt to upload drivers to BrokerB
>> running on ServerB, while running iManage from ServerQ it looks as
>> though the drivers actually make it to the broker, I just don't see the
>> Yellow exclamation point telling me to hit apply or OK to save my
>> changes, but

> if
>> I do it anyway, the drivers are not there. I've checked the drvers

> folder,
>> not there, drivers do zip up in to a folder on c:\ndps\drvr_tmp, and
>> then disappear as if they've made it up sucessfully. I've updated to
>> iPrint client 4.12Beta, but this hasn't helped. I know it's not the
>> driver, because it uploads to other Brokers/Server, I don't think it's
>> the

> UserID,
>> because the same ID does work to other servers. Apache is running on
>> the two servers, NLDAP is running on both servers, these two server do
>> not have replica's on them, but they never did have, since their
>> creation.

> Any
>> ideas where to start?
>>
>> ../chris

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: SP4a driver uploads look ok, but are not

It's a long story detailed in another thread somewhere in this forum, but
update the iPrint client on the PC you are accessing iManager from to the
latest 4.12. I think that will allow you to upload drivers even with
your alias user ID there.

I don't remember the details but something changed in how drivers are
uploaded through iManager in SP3 and SP4 and it would no longer work if
the same user ID existed in more than one place in the tree. Your alias
entry might be causing the same thing. The iPrint client 4.12 allows it
to work even with an ID that exist in multiple places in the tree.


> On Wed, 02 Nov 2005 05:27:55 +0000, iprintrox wrote: Well, I've deleted

my
> alias for my ID (which was named the same as my user ID, just in the

tree
> root) and it looks like that corrected my issue, which doesn't make

senss
> why I couldn't upload only to two different servers only, all other
> servers that I've tried have worked. Thanks for the suggestions.
>
>
> > There is 2 methods of uploading drivers, and you identified the

critical
> > "visual" sign of the method of upload. If you do get the "Yellow
> > exclamation point telling hit apply or OK to save changes", this would
> > indicate that the HTTPSTK method was used. THis indicates that the
> > driver was uploaded to the server you are running iManager on.
> > iManager then informs the Broker that it has a driver on the iManager
> > server in the sys:\ndps\xfer directory that it needs to upload...

If
> > you don't get the exclamation point, the driver should have been

loaded
> > directly to the server where the broker is running via apache.
> >
> > You can quickly eliminate uid problems by simply typing a secure URL

to
> > the server running the broker as follows: "https://server address
> > and/or dns name/ipps". Try doing this 2 times, once with the address
> > and once with the dns name. You should be prompted for

authentication.
> > PRovide the same credentials you did when logging into iManager...

If
> > this works okay, you don't have uid or cert problems (the dreaded 401
> > issues)...
> >
> > I would look at the apache log file on the server where the broker is
> > running. What does it indicate??? You could also try setting the
> > iprint client trace up on the workstation you are running iManager

on.
> > Do a search for "iprint client troubleshoot" on support.novell.com.
> > This logging trace file might give you more information...
> >
> >
> >> I'm having a strange issue, and after looking around in this forum

for
> >> a little, it seems my issue is a little different. We have approx

30+
> >> NW65SP4a, that were all recently updated from either NW6.5SP2 or SP3,
> >> in or headquarters we have two iPrint servers (dont' ask why two,

it's
> >> a

> > long
> >> story) that are identically configured with the exception of the

domain
> >> suffix, both were upgraded from NW6.5SP2 about a week ago. Since
> >> updating to SP4a, I can not seem to upload drivers to the broker,

but I
> >> can upload drivers to other NW6.5SP4a servers in our tree that were
> >> recently

> > updated.
> >>
> >> The problem that I'm seening is that when I run iManage from one of

our
> >> remote servers (ServerQ) and attempt to upload drivers to BrokerB
> >> running on ServerB, while running iManage from ServerQ it looks as
> >> though the drivers actually make it to the broker, I just don't see

the
> >> Yellow exclamation point telling me to hit apply or OK to save my
> >> changes, but

> > if
> >> I do it anyway, the drivers are not there. I've checked the drvers

> > folder,
> >> not there, drivers do zip up in to a folder on c:\ndps\drvr_tmp, and
> >> then disappear as if they've made it up sucessfully. I've updated to
> >> iPrint client 4.12Beta, but this hasn't helped. I know it's not the
> >> driver, because it uploads to other Brokers/Server, I don't think

it's
> >> the

> > UserID,
> >> because the same ID does work to other servers. Apache is running on
> >> the two servers, NLDAP is running on both servers, these two server

do
> >> not have replica's on them, but they never did have, since their
> >> creation.

> > Any
> >> ideas where to start?
> >>
> >> ../chris


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.