Anonymous_User Absent Member.
Absent Member.
3938 views

SP6 and iPrint problems!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

What the hell has Novell done to iPrint in SP6 for NW6.5?!

Ever since I installed SP6 on my file/print server I have been having
nothing but problems with my printers. I keep getting random printers that
stop printing and when I check the iPrint Manager health it says LPR
Communications Failure.

I did some searching in the knowledge base and found IPRNTNW65SP6C.EXE but
that hasn't helped either.

You would think that something this disruptive would have come out in beta.

0 Likes
36 Replies
Anonymous_User Absent Member.
Absent Member.

Re: SP6 and iPrint problems!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

It seems that Novell has a new NDPSGW.NLM that is suppose to once again
fix the communication issues, but that fix is not available for download
yet. I will ask about the status of it.
In any case, I would suggest you watch the following space as I will
update it if there is any news:

http://wiki.novell.com/index.php/Nw65sp6#NDPS.2FiPrint_updates

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

Re: SP6 and iPrint problems!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

I just got the reply back that the new gateway still does not work for the
customers with communication problems. So stick with the SP5 version of
NDPSGW for now!

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

Re: SP6 and iPrint problems!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

I went back to the ndpsgw.nlm from sp5. It worked for awhile but then
started abending the server. The Jan 2 ndpsgw.nlm is worthless. I don't
like the choice I am making between a stable server environment or people
printing.

>>> On 1/30/2007 at 10:28 AM, in message

<gfLvh.11130$Sz4.2754@prv-forum2.provo.novell.com>, Marcel
Cox<cimetmc@myrealbox.com> wrote:
> It seems that Novell has a new NDPSGW.NLM that is suppose to once again
> fix the communication issues, but that fix is not available for download
>
> yet. I will ask about the status of it.
> In any case, I would suggest you watch the following space as I will
> update it if there is any news:
>
> http://wiki.novell.com/index.php/Nw65sp6#NDPS.2FiPrint_updates

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: SP6 and iPrint problems!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Doyle collings wrote:

>It worked for awhile but then
>started abending the server.


You have an abend.log file for that problem?

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

Re: SP6 and iPrint problems!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Yes, a sample follows:
Novell Open Enterprise Server, NetWare 6.5
PVER: 6.50.06

Server NW1 halted Tuesday, January 30, 2007 9:08:31.415 am
Abend 1 on P00: Server-5.70.06: Page Fault Processor Exception (Error code
00000000)

Registers:
CS = 0060 DS = 0068 ES = 0068 FS = 007B GS = 007B SS = 0068
EAX = B9675F00 EBX = FFFFFFFF ECX = 001E1FAC EDX = FFFFFFFF
ESI = FFFFFFFF EDI = FFFFFFFF EBP = 35239EFF ESP = B9EEE3AC
EIP = 00209E10 FLAGS = 00010286
00209E10 8B5310 MOV EDX, [EBX+10]=?
EIP in SERVER.NLM at code start +00007990h
Access Location: 0x0000000F

The violation occurred while processing the following instruction:
00209E10 8B5310 MOV EDX, [EBX+10]
00209E13 89DE MOV ESI, EBX
00209E15 81FA121F041E CMP EDX, 1E041F12
00209E1B 7549 JNZ 00209E66
00209E1D 53 PUSH EBX
00209E1E E83DDAEFFF CALL LOADER.NLM|kSpinLockDisable
00209E23 8B4B14 MOV ECX, [EBX+14]
00209E26 83C404 ADD ESP, 00000004
00209E29 49 DEC ECX
00209E2A 89C7 MOV EDI, EAX



Running process: GW_TaskThrd_3 Process
Thread Owned by NLM: NDPSGW.NLM
Stack pointer: B9EEE378
OS Stack limit: B9EEA480
Scheduling priority: 67371008
Wait state: 3030070 Yielded CPU
Stack: --35239EFF ?
--FFFFFFFF ?
--FFFFFFFF ?
--B7FCE700 ?
8CD80C22 (THREADS.NLM|_WaitOnSemaphore+26)
--FFFFFFFF ?
--FFFFFFFF ?
--B7FCE700 ?
8CD80F53 (THREADS.NLM|WaitOnLocalSemaphore+57)
--FFFFFFFF ?
--B198A290 ?
--B198A290 ?
B10E30D5 (NDPSGW.NLM|(Code Start)+80D5)
--FFFFFFFF ?
--00000032 (LOADER.NLM|KernelAddressSpace+32)
--35239EFF ?
--00000032 (LOADER.NLM|KernelAddressSpace+32)
--B1A05F50 ?
B10E5DA0 (NDPSGW.NLM|(Code Start)+ADA0)
--00000032 (LOADER.NLM|KernelAddressSpace+32)
--B1134080 ?
--35239EFF ?
--00000011 (LOADER.NLM|KernelAddressSpace+11)
--B2638950 ?
B10E62E4 (NDPSGW.NLM|(Code Start)+B2E4)
--B10A5890 ?
--B1A05F50 ?
B10E6282 (NDPSGW.NLM|(Code Start)+B282)
--B7FCE700 ?
--B8CF0B60 ?
8CD6D356 (THREADS.NLM|getcmd+21E)
--B1A05F50 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000246 (LOADER.NLM|KernelAddressSpace+246)
--B2A510A0 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
8CD6D194 (THREADS.NLM|getcmd+5C)
--B0FB4A40 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
8CD6D18C (THREADS.NLM|getcmd+54)
--B0FB4A40 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--B2A510A0 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--B2A510A0 ?
-8CD88730 (THREADS.NLM|(Data Start)+2730)
0021F0F8 (SERVER.NLM|TcoNewSystemThreadEntryPoint+40)
--B2A510A0 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--34343434 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)

Additional Information:
The CPU encountered a problem executing code in SERVER.NLM. The problem
may be in that module or in data passed to that module by a process owned by
NDPSGW.NLM.

>>> On 1/30/2007 at 11:09 AM, in message

<KRLvh.11164$Sz4.7950@prv-forum2.provo.novell.com>, Marcel
Cox<cimetmc@myrealbox.com> wrote:
> I just got the reply back that the new gateway still does not work for
> the
> customers with communication problems. So stick with the SP5 version of
> NDPSGW for now!

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: SP6 and iPrint problems!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

There are a couple of people reporting an abend like this but I cannot see
a pattern in it. Probably the only way to solve it is to open an incident.
However could you also post the remainder of the abend.log file?

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

Re: SP6 and iPrint problems!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Is there any way to be emailed when the new Gateway is ready AND working?

> There are a couple of people reporting an abend like this but I cannot see
> a pattern in it. Probably the only way to solve it is to open an incident.
> However could you also post the remainder of the abend.log file?
>
> --
> Marcel Cox (using XanaNews 1.18.1.6)


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: SP6 and iPrint problems!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

terry@nomail.com wrote:

>Is there any way to be emailed when the new Gateway is ready AND working?


Well, what you can do is the following:

Add the following wiki page on your watch list (you need to login with a
Novell web account to put the article on your watch list):

http://wiki.novell.com/index.php/Nw65sp6

Then configure your user to be sent an email when the article changes.

I will promise I will do my best to update the page as soon as there is
new information.
Of course, you will also get emails for other updates on that page not
related to iPrint.

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

Re: SP6 and iPrint problems!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

In jest,

Meanwhile, whilst we wait for the fix, what do I do with the 40 pairs of shoes stuck up in my nether regions put there by my end users? 🙂 I have been going home with icepacks tied around my bum. 🙂

Seriously though, it has been painful through this. I built a completely new server and installed iPrint on it, sp5, to handle the printers that do not work. I have only 6 of them, but they were our high duty Canon and newer HP printers.

Sincerely,

Tom


>>> Marcel Cox<cimetmc@myrealbox.com> 1/30/2007 2:31 PM >>>

terry@nomail.com wrote:

>Is there any way to be emailed when the new Gateway is ready AND working?


Well, what you can do is the following:

Add the following wiki page on your watch list (you need to login with a
Novell web account to put the article on your watch list):

http://wiki.novell.com/index.php/Nw65sp6

Then configure your user to be sent an email when the article changes.

I will promise I will do my best to update the page as soon as there is
new information.
Of course, you will also get emails for other updates on that page not
related to iPrint.

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

Re: SP6 and iPrint problems!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

I just tried going back to the SP5 NDPSGW.NLM and I still have the LPR comm
problems with all the same printers! Doesn't anybody beta test anything any
more?

> I just got the reply back that the new gateway still does not work for the
> customers with communication problems. So stick with the SP5 version of
> NDPSGW for now!
>
> --
> Marcel Cox (using XanaNews 1.18.1.6)


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: SP6 and iPrint problems!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Open an incident with Novell. That's really the only way to get more
movement on the issue.

--
Marcel Cox
http://support.novell.com/forums
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: SP6 and iPrint problems!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

It's interesting that you have this problem with heavy duty Canon
printers. Out of the 50 printers that our manager services, the 2 that
don't work are Canon (iR500 & 2800). Should we be trying to compile a
list of printers that don't work to see if there is any pattern? Would
this be helpfull for Novell?

I'm unable to go back to the SP5 module as our iPrint is clustered. I've
service packed 2 of our 4 nodes and if I try and run iPrint on an SP5 node
now, it won't load. I presume the upgrade has modified the ndps database
in some way and there is no going back.

For the time being, I thinnk I'll create another manager on a SP5 server
to service these two broken printers. I have an SR open with Novell and
our PSE is doing all he can to find any internal updates.


> In jest,
>
> Meanwhile, whilst we wait for the fix, what do I do with the 40 pairs of

=
> shoes stuck up in my nether regions put there by my end users? 🙂 I

have =
> been going home with icepacks tied around my bum. 🙂
>
> Seriously though, it has been painful through this. I built a

completely =
> new server and installed iPrint on it, sp5, to handle the printers that

do =
> not work. I have only 6 of them, but they were our high duty Canon and =
> newer HP printers.
>
> Sincerely,
>
> Tom
>
>
> >>> Marcel Cox<cimetmc@myrealbox.com> 1/30/2007 2:31 PM >>>

> terry@nomail.com wrote:
>
> >Is there any way to be emailed when the new Gateway is ready AND

working?
>
> Well, what you can do is the following:
>
> Add the following wiki page on your watch list (you need to login with =
> a=20
> Novell web account to put the article on your watch list):
>
> http://wiki.novell.com/index.php/Nw65sp6
>
> Then configure your user to be sent an email when the article changes.
>
> I will promise I will do my best to update the page as soon as there

is=20
> new information.
> Of course, you will also get emails for other updates on that page not=20
> related to iPrint.
>
> --=20
> Marcel Cox (using XanaNews 1.18.1.6)
>


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: SP6 and iPrint problems!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

So, help me understand this. I have to open a $650 incident to tell Novell that printing doesn't work?

Why does this happen in the tech world. If I buy a car, boat, or even a computer, and the silly thing doesn't work because of a 'defect', it is taken care of as a defect. If I get defective software, I have to pay for the fix.

It is beginning to sound like the Novell Mob. "You want software, we got software.... You want software to work, you have to purchase 'protection'.... You don't want protection, maybe Guido and Mickey can convince you that you need 'protection' "

🙂

Tom

>>> Marcel Cox<cimetmc@myrealbox.com> 1/31/2007 1:15 AM >>>

Open an incident with Novell. That's really the only way to get more
movement on the issue.

--
Marcel Cox
http://support.novell.com/forums
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: SP6 and iPrint problems!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Hey Terry,

I am a part of the Public beta for OES2. I can tell you that I am going to BETA the (&^& out of it as much as I can. I don't know if Novell realizes it but OES2 will either be the beginning or the end of many peoples following of Novell. Some have already jumped off the wagon, fearing the cliff ahead.

OES2 will either be a cliff or a bridge. If OES2 doesn't grab the Netware people, Novell will be a Linux OS company and the OES vision will die.

Tom


>>> <terry@nomail.com> 1/30/2007 11:22 PM >>>

I just tried going back to the SP5 NDPSGW.NLM and I still have the LPR comm
problems with all the same printers! Doesn't anybody beta test anything any
more?

> I just got the reply back that the new gateway still does not work for the
> customers with communication problems. So stick with the SP5 version of
> NDPSGW for now!
>
> --
> Marcel Cox (using XanaNews 1.18.1.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.