Looking for tips to stabilize my print server

  • Thread starter Bruce Lautenschlager
  • Start date

B

Bruce Lautenschlager

I'm looking to increase the reliability of my print server. I have 287 HP
printers installed on my Windows Server 2003 R2 Standard, SP2 (fully
patched), print server. It has 4 GB of RAM, a single 3.2 Ghz Xeon CPU (it's
an IBM 8843/HS20 Blade server), with a single 36 GB mirrored volume. The
only 3rd party software installed on it is VNC and Network Associates Virus
Scan 8.5i (the corporate version, not the craptacular retail client). I have
24 of these blades in that same config, and I find them VERY stable,
typically.

The print servers connected to the physical printers are all Intel (various
models) or HP JetDirects (none internal to the printers). The workstations
are 95% Windows 2000 SP4, the remaining are a mix of XP SP2, or printing
from my Citrix Farm (CPS 4.0, using WI).

All the printer drivers are either the canned print drivers for Windows
(usually in the case of the older HP LaserJet 4's and 5's), or the driver
available from the HP site sometime between January and March of this year.

The models of HP B&W laser printer drivers installed are 4, 5, 5si, 1200,
1320, P2015, 4000, 4050, 4100, 4200, 4250, 8100, 8150, 9050.

The models of HP color laser printer drivers installed are 2550, 2800, 3800,
4005, 4650.

The models of HP DeskJet printer drivers installed are 1600, 6122, and a
DesignJet 650c.

The realtime virus scanning excludes the spool folder, but I've turned it
off entirely, and it doesn't seem to make a difference. I've set the spooler
service to recover if it fails, and lately, it would seem to go into
recovery once a week or so (Event ID 7031 - The Print Spooler servuce
terminated unexpectedly). It usually recovers, but sometimes it doesn't, and
I have to reboot the whole server.

I don't have the worst print server in the world, but I'm looking to make it
more stable. Any tips would be greatly appreciated. I have one enterprise
application (for surgical suites) that gets really hosed if it can't print,
so any downtime can make it dicey.

I thought about setting this up on a cluster, like my file server, but I
thought splitting off all printing on a dedicated print server would be
reliable enough, plus some people indicate print server clusters aren't the
greatest, either. But now I'm wondering.

In my smaller facilities, I combine the printing on my file servers and have
zero issues, but those are hosting 10-12 printers and 50 users, not 287
printer and 1000 users.

Thanks in advance,
Bruce Lautenschlager
 
Ad

Advertisements

D

Danny Sanders

I would split the printers off into probably a total of 3 print servers. Put
the high priority printers on one, less priority on the second and the least
important on the existing server.

If you continue to have the problems at least a reboot won't take out all
the printers.

hth
DDS
 
B

Bruce Lautenschlager

That's a good thought - if I had it to do over again, I'd install VMWare
ESXi 3.5 on the blade and split it up into at least two...

But it reality, that won't help me entirely, either. Of the 287 printers,
probably 50-75 get a lot of printing, from our surgical suite package (we
are a hospital). It comes from a print server" (one of 9 Window Server 2003
boxes) belonging to the surgical suite package. If it tries to print to any
printer that isn't immediately available, it seems to send that package into
a tizzy, and we start having to dork with it.

It's crappy, and it's wrong, but it's also not great that my print server's
spooler service hoses once a week or so lately, either.

Every other app in the hospital could care less for the most part - it
prints when it's available, queues up when it's not, and spits it out when
it's ready. Just like God intended printing to work.

This surgical package is a lot like some of my old AIX stuff, though, in
that if the server doesn't say "I got it! I printed it!", bad stuff starts
happening (in the case of AIX, it'll mark the print queue as unavailable
until you turn it on....).
 
A

Alan Morris [MSFT]

Since you have R2, have you configured the machine with the print server
role?

That's not going to help with the stability, but you will get the Print
Management Console added where you can check some of the driver versions.

Do you publish the printers into an Active Directory?

Make sure you have the latest driver for the HP 9050.
Microsoft is currently using version 61.71.698.21 which fixed a failure when
publishing the printer to the AD.

Are there any event 6161s around the time the service terminates. Most
failures in the spooler are caused by print drivers corrupting memory within
the process.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1

This posting is provided "AS IS" with no warranties, and confers no rights.
 
B

Bruce Lautenschlager

Alan -

Yes, I configured it in the print server role. The Print Management Console
is the best thing since sliced bread, my network admin loves it (and I do,
too). The printers are published in AD, too. Most of the time we add them to
PCs via ADDPRINTER.CMD (rundll32 printui.dll,PrintUIEntry /ga /c\\%1
/n\\%2).

My 9050 driver is older than the one you mentioned, I will have to update
it. Fortunately, I think those aren't used for AD printing (I put all my
printers in AD, but the reality is, some 50% are only used for host based
printing from our mainframe or similar systems). But I will update that.

I do get 6161 errors. A few days I see I've gotten 15 or 20 a day. But
typically I'll go 2 to 5 days without any 6161 errors, and only get about 3
a day when I do. They don't seem to immediately precede any spooler crashes
(4 or 5 hours is the closest I see them occuring together), and they appear
on so many different printers (and different types of documents) that it
will take some time to determine if there's a common thread (same driver or
model, etc.). But I will examine that.

I really appreciate all your efforts.

Thanks,
Bruce
 
A

Alan Morris [MSFT]

You will get 6161 when someone cancels the job while printing. The main
error I look for within the 6161 event is Error 5 (access denied) and Error
8 (out of some resource). Error 259 is normally the job canceled and there
are a could of error codes when the physical printer can not be reached on
the network.


Do you have any watson or Windows Error Report crashes? If you do, you can
attach the NT Source Debugger and dump the stack to locate the offending
binary that caused the problem.

look for user.dmp or watson.log files around the time that the spooler
service failed.



--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1

This posting is provided "AS IS" with no warranties, and confers no rights.
 
B

Bruce Lautenschlager

FWIW, I upgraded my 9000 and 9050 drivers to the latest HP drivers
61.74.561.43.

The only error code I see within my 6161 Events is Win error code 0 - they
all look like this:

The document Crystal Reports ActiveX Designer - Patient Itinerary owned by
TAB failed to print on printer ADMIT_LASER3. Data type: NT EMF 1.008. Size
of the spool file in bytes: 31512. Number of bytes printed: 0. Total number
of pages in the document: 1. Number of pages printed: 0. Client machine:
\\10.108.42.77. Win32 error code returned by the print processor: 0. The
operation completed successfully.

No total crashes, so I don't have any .DMP files or WATSON.LOG files.
Something interesting I see today after sifting through all the errors in
Event Viewer - nothing new in System, but in Application, I see quite a few
Event ID 1000, Source Application error, and they all read like this:

Faulting application spoolsv.exe, version 5.2.3790.3959, faulting module
hpmdp5r1.dll, version 0.3.1537.66, fault address 0x00004193.

I'm not sure it's a one to one relationship with the Print Spooler crashes,
but it's pretty close. I don't know if that's just a symptom of the spooler
service crashing, or a cause, though.

While I'm picking your (considerable brain), looking at the drivers on this
server, the HP 4, 4+, 4000, 4050, 4100 drivers I'm using are all Microsoft,
which I assume are stable and don't need to be touched.

But my 4200 drivers are HP - 61.63.461.42. My 4250 drivers are HP also -
61.74.561.43 (hey, the same as 90x0!). Any suspicions with those (I would
guess not the 4250 ones)....?

Bruce
 
A

Alan Morris [MSFT]

The error 0 is typically returned on a GDI rendering issue when GDI clears
the last error. Due to application compatibility issues, they are never
going to change this.

watson logs are actually in \windows and named drwtsn32.log

HP has a post on one of their forums regarding the hpmdp5r1.dll driver file

http://forums11.itrc.hp.com/service/forums/bizsupport/questionanswer.do?admit=109447626+1219849865198+28353475&threadId=1245060

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1

This posting is provided "AS IS" with no warranties, and confers no rights.
 
B

Bruce Lautenschlager

watson logs are actually in \windows and named drwtsn32.log
Doh! Yeah, I have that - 24 MB chock full of info about my spoolsv.exe
crashes. Not sure how to read it, though - I have WinDbg 6.7 installed on my
PC - but not sure exactly what to do with the drwtsn32.log file (I mean, I
searched around and saw the breakdown of the subsections - it's only
spoolsv.exe crashing - but I'm not sure how to take that log file and
interpret exactly what's crashing it, although I'm assuming it's related to
hpmdp5r1.dll based on what I see).

HP has a post on one of their forums regarding the hpmdp5r1.dll driver file
http://forums11.itrc.hp.com/service/forums/bizsupport/questionanswer.do?admit=109447626+1219849865198+28353475&threadId=1245060

Thanks for the tip - I've taken my problem over there, too - but I'm not
sure that some of the suggestions (remove all printers, create with new
share names, etc) are practical for 287 printers and over 1000 workstations.

Bruce
 
Ad

Advertisements

B

Bruce Lautenschlager

I did, but I'm not sure what:

FAULT ->02d04193 668b516c mov dx,[ecx+0x6c]
ds:0023:0000006c=????

Will tell me...

Bruce
 
A

Alan Morris [MSFT]

you need to look at the stack trace information under the FAULT. The top of
the stack is unidrv but this was a failure in the HP print processor that's
been fixed for over a year. I had to go back to a retired Win2k3 print
server to find a drwatson log file.

*** ERROR: Symbol file could not be found. Defaulted to export symbols for
C:\WINNT\system32\spool\DRIVERS\W32X86\3\UNIDRV.DLL -
function: UNIDRV!DrvEnableDriver
767f4427 5d pop ebp
767f4428 0803 or [ebx],al
767f442a da03 fiadd dword ptr [ebx]
767f442c c23bc3 ret 0xc33b
767f442f 895d08 mov [ebp+0x8],ebx
767f4432 0f8778310000 jnbe UNIDRV!DrvEnableDriver+0xfa0b
(767f75b0)
767f4438 8b5dfc mov ebx,[ebp-0x4]
767f443b 66837b1600 cmp word ptr [ebx+0x16],0x0
767f4440 0f8516310000 jne UNIDRV!DrvEnableDriver+0xf9b7
(767f755c)
767f4446 8d0448 lea eax,[eax+ecx*2]
FAULT ->767f4449 668b08 mov cx,[eax]
ds:0023:02f7e2a6=????
767f444c 668b4002 mov ax,[eax+0x2]
767f4450 660fb6dd movzx bx,ch
767f4454 8af9 mov bh,cl
767f4456 660fb6cc movzx cx,ah
767f445a 8ae8 mov ch,al
767f445c 0fb7c3 movzx eax,bx
767f445f 8d0447 lea eax,[edi+eax*2]
767f4462 2bcb sub ecx,ebx
767f4464 d1e1 shl ecx,1
767f4466 66890e mov [esi],cx

*----> Stack Back Trace <----*
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
C:\WINNT\system32\GDI32.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
C:\WINNT\system32\spool\PRTPROCS\W32X86\hpzpp41w.DLL -
ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be
wrong.
026fcf70 767f48eb 02f71784 02f40010 0000ffe5 UNIDRV!DrvEnableDriver+0xc8a4
026fcfa8 76809653 02807290 027d4268 0000ffe5 UNIDRV!DrvEnableDriver+0xcd46
026fcfcc 767fdf7b 02807290 027d4268 0000ffe5
UNIDRV!DrvQueryDriverInfo+0x7d8d
026fcff8 767f40af 02807290 020c4268 0000001d UNIDRV!DrvEnableDriver+0x163d6
026fd058 767f3ecf 03bb0238 02fc0068 03bb036c UNIDRV!DrvEnableDriver+0xc50a
026fd088 767ee8c4 026fd104 02fc0068 026fd164 UNIDRV!DrvEnableDriver+0xc32a
026fd1a4 767ee140 02fc0000 02fc0068 02fc008c UNIDRV!DrvEnableDriver+0x6d1f
026fd1dc 77c1b7a5 02fc0000 02fc0068 02fc008c UNIDRV!DrvEnableDriver+0x659b
026fd230 773aa2cc 026fda98 026fd248 00000004 GDI32!StartPage+0x2bc
026fda80 7c82ec9e 026fda98 0000003c 026fdd18 USER32!EmptyClipboard+0x11f
026fdaf4 77c13452 440a025e 051f3fe0 000b03b0
ntdll!KiUserCallbackDispatcher+0x2e
026fdb08 77c120bf 8c210307 027d0f20 00000006 GDI32!ExtCreatePen+0x900
026fdb80 77c1b88f 8c210307 027d0f20 051f45a0
GDI32!PlayEnhMetaFileRecord+0x37
026fdbfc 77c1b8dc 8c210307 41bd5f3a 00000000 GDI32!StartPage+0x3a6
026fdc18 77c35817 8c210307 2c46030a 03b97a10 GDI32!StartPage+0x3f3
026fdcd0 77c35aad 03b94048 00000000 00000000
GDI32!GdiPlayPrivatePageEMF+0x3e7
026fdd28 77c35b0e 03b94048 00000000 00000000 GDI32!GdiEndPageEMF+0x13c
026fdd5c 01d92abb 03b94048 00000000 00000000 GDI32!GdiEndDocEMF+0x2c
026fddac 01d932b0 00000001 00000001 00000000
hpzpp41w!EnumPrintProcessorDatatypesW+0x28b
026fee90 01d9d2d6 04f60020 026ff304 00836760
hpzpp41w!EnumPrintProcessorDatatypesW+0xa80
026feeb0 76143faf 04f60020 026ff304 00000000
hpzpp41w!PrintDocumentOnPrintProcessor+0x4b
026ff948 76143b04 0083edc0 026ff970 00000000
localspl!SplSetPrinterDataEx+0x1a6e
026fffb8 77e6608b 0083edc0 00000000 00000000
localspl!SplSetPrinterDataEx+0x15c3
026fffec 00000000 76143c60 0083edc0 00000000
kernel32!GetModuleFileNameA+0xeb

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1

This posting is provided "AS IS" with no warranties, and confers no rights.

Bruce Lautenschlager said:
I did, but I'm not sure what:

FAULT ->02d04193 668b516c mov dx,[ecx+0x6c]
ds:0023:0000006c=????

Will tell me...

Bruce


Alan Morris said:
I search on FAULT to locate the failure point.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1
 
B

Bruce Lautenschlager

Mine all look a lot like this:

*** ERROR: Symbol file could not be found. Defaulted to export symbols for
C:\WINDOWS\system32\spool\DRIVERS\W32X86\3\hpmdp5r1.dll -
function: hpmdp5r1
02d04178 c9 leave
02d04179 7542 jnz hpmdp5r1+0x41bd (02d041bd)
02d0417b 8b55f0 mov edx,[ebp-0x10]
02d0417e 8b420c mov eax,[edx+0xc]
02d04181 0fbf484e movsx ecx,word ptr [eax+0x4e]
02d04185 83f901 cmp ecx,0x1
02d04188 7533 jnz hpmdp5r1+0x41bd (02d041bd)
02d0418a 8b55f0 mov edx,[ebp-0x10]
02d0418d 8b4210 mov eax,[edx+0x10]
02d04190 8b4de8 mov ecx,[ebp-0x18]
FAULT ->02d04193 668b516c mov dx,[ecx+0x6c]
ds:0023:0000006c=????
02d04197 6689504e mov [eax+0x4e],dx
02d0419b 8b45f0 mov eax,[ebp-0x10]
02d0419e 8b4810 mov ecx,[eax+0x10]
02d041a1 8b55e8 mov edx,[ebp-0x18]
02d041a4 668b426e mov ax,[edx+0x6e]
02d041a8 66894150 mov [ecx+0x50],ax
02d041ac 8b4df0 mov ecx,[ebp-0x10]
02d041af 8b5110 mov edx,[ecx+0x10]
02d041b2 8b45e8 mov eax,[ebp-0x18]
02d041b5 668b4870 mov cx,[eax+0x70]

*----> Stack Back Trace <----*
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
C:\WINDOWS\system32\winspool.drv -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
C:\WINDOWS\system32\GDI32.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
C:\WINDOWS\system32\spool\PRTPROCS\W32X86\hpzpp4wm.DLL -
ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be
wrong.
01d3b3a4 02d078f9 00000000 01d3b944 01d3b6ec hpmdp5r1+0x4193
01d3b910 73076633 00000000 01d3b944 00000000
hpmdp5r1!DrvDocumentPropertySheets+0x5f9
01d3b930 730765a8 00000000 01d3b944 000f9fa0
winspool!DocumentPropertySheets+0x56
01d3b968 77c131ba 00000000 00126144 00161a78
winspool!DocumentPropertiesW+0x9f
01d3b9d0 77c0b923 01d3b9f4 01d3b9ec 00161a78 GDI32!EngDeletePalette+0xe0
01d3ba08 77c0b944 77c0156c 000d3d70 77c0156c GDI32!EnumFontFamiliesExW+0x18b
01d3ba24 77c3406e 77c0156c 000d3d70 77c0156c GDI32!CreateDCW+0x18
01d3ba48 01937073 000d3d70 00161a78 01d3f304
GDI32!GdiGetSpoolFileHandle+0xad
01d3ee80 0195484d 00100390 01d3f304 00000006
hpzpp4wm!EnumPrintProcessorDatatypesW+0xfb3
01d3eeb0 7615a229 00100390 01d3f304 00000000
hpzpp4wm!PrintDocumentOnPrintProcessor+0x6d
01d3f948 7615aadd 009375b8 01d3f970 00000000 localspl!SplDeleteSpooler+0xbd0
01d3ffb8 77e64829 009375b8 00000000 00000000
localspl!SplDeleteSpooler+0x1484
01d3ffec 00000000 7615a83a 009375b8 00000000 kernel32!GetModuleHandleA+0xdf


Bruce
 
A

Alan Morris [MSFT]

find out which printer uses the hpzpp4wm print processor and check if HP has
an updated driver for the device

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1

This posting is provided "AS IS" with no warranties, and confers no rights.

Bruce Lautenschlager said:
Mine all look a lot like this:

*** ERROR: Symbol file could not be found. Defaulted to export symbols
for C:\WINDOWS\system32\spool\DRIVERS\W32X86\3\hpmdp5r1.dll -
function: hpmdp5r1
02d04178 c9 leave
02d04179 7542 jnz hpmdp5r1+0x41bd (02d041bd)
02d0417b 8b55f0 mov edx,[ebp-0x10]
02d0417e 8b420c mov eax,[edx+0xc]
02d04181 0fbf484e movsx ecx,word ptr [eax+0x4e]
02d04185 83f901 cmp ecx,0x1
02d04188 7533 jnz hpmdp5r1+0x41bd (02d041bd)
02d0418a 8b55f0 mov edx,[ebp-0x10]
02d0418d 8b4210 mov eax,[edx+0x10]
02d04190 8b4de8 mov ecx,[ebp-0x18]
FAULT ->02d04193 668b516c mov dx,[ecx+0x6c]
ds:0023:0000006c=????
02d04197 6689504e mov [eax+0x4e],dx
02d0419b 8b45f0 mov eax,[ebp-0x10]
02d0419e 8b4810 mov ecx,[eax+0x10]
02d041a1 8b55e8 mov edx,[ebp-0x18]
02d041a4 668b426e mov ax,[edx+0x6e]
02d041a8 66894150 mov [ecx+0x50],ax
02d041ac 8b4df0 mov ecx,[ebp-0x10]
02d041af 8b5110 mov edx,[ecx+0x10]
02d041b2 8b45e8 mov eax,[ebp-0x18]
02d041b5 668b4870 mov cx,[eax+0x70]

*----> Stack Back Trace <----*
*** ERROR: Symbol file could not be found. Defaulted to export symbols
for C:\WINDOWS\system32\winspool.drv -
*** ERROR: Symbol file could not be found. Defaulted to export symbols
for C:\WINDOWS\system32\GDI32.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols
for C:\WINDOWS\system32\spool\PRTPROCS\W32X86\hpzpp4wm.DLL -
ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be
wrong.
01d3b3a4 02d078f9 00000000 01d3b944 01d3b6ec hpmdp5r1+0x4193
01d3b910 73076633 00000000 01d3b944 00000000
hpmdp5r1!DrvDocumentPropertySheets+0x5f9
01d3b930 730765a8 00000000 01d3b944 000f9fa0
winspool!DocumentPropertySheets+0x56
01d3b968 77c131ba 00000000 00126144 00161a78
winspool!DocumentPropertiesW+0x9f
01d3b9d0 77c0b923 01d3b9f4 01d3b9ec 00161a78 GDI32!EngDeletePalette+0xe0
01d3ba08 77c0b944 77c0156c 000d3d70 77c0156c
GDI32!EnumFontFamiliesExW+0x18b
01d3ba24 77c3406e 77c0156c 000d3d70 77c0156c GDI32!CreateDCW+0x18
01d3ba48 01937073 000d3d70 00161a78 01d3f304
GDI32!GdiGetSpoolFileHandle+0xad
01d3ee80 0195484d 00100390 01d3f304 00000006
hpzpp4wm!EnumPrintProcessorDatatypesW+0xfb3
01d3eeb0 7615a229 00100390 01d3f304 00000000
hpzpp4wm!PrintDocumentOnPrintProcessor+0x6d
01d3f948 7615aadd 009375b8 01d3f970 00000000
localspl!SplDeleteSpooler+0xbd0
01d3ffb8 77e64829 009375b8 00000000 00000000
localspl!SplDeleteSpooler+0x1484
01d3ffec 00000000 7615a83a 009375b8 00000000
kernel32!GetModuleHandleA+0xdf


Bruce
 
B

Bruce Lautenschlager

I'm pretty sure that's the 4200/4250 drivers, which are the latest, but I'll
see if anyone at HP can agree. That being the case, I'm thinking about
trying this workaround:

http://support.microsoft.com/kb/947477


Alan Morris said:
find out which printer uses the hpzpp4wm print processor and check if HP
has an updated driver for the device

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1

This posting is provided "AS IS" with no warranties, and confers no
rights.

Bruce Lautenschlager said:
Mine all look a lot like this:

*** ERROR: Symbol file could not be found. Defaulted to export symbols
for C:\WINDOWS\system32\spool\DRIVERS\W32X86\3\hpmdp5r1.dll -
function: hpmdp5r1
02d04178 c9 leave
02d04179 7542 jnz hpmdp5r1+0x41bd (02d041bd)
02d0417b 8b55f0 mov edx,[ebp-0x10]
02d0417e 8b420c mov eax,[edx+0xc]
02d04181 0fbf484e movsx ecx,word ptr [eax+0x4e]
02d04185 83f901 cmp ecx,0x1
02d04188 7533 jnz hpmdp5r1+0x41bd (02d041bd)
02d0418a 8b55f0 mov edx,[ebp-0x10]
02d0418d 8b4210 mov eax,[edx+0x10]
02d04190 8b4de8 mov ecx,[ebp-0x18]
FAULT ->02d04193 668b516c mov dx,[ecx+0x6c]
ds:0023:0000006c=????
02d04197 6689504e mov [eax+0x4e],dx
02d0419b 8b45f0 mov eax,[ebp-0x10]
02d0419e 8b4810 mov ecx,[eax+0x10]
02d041a1 8b55e8 mov edx,[ebp-0x18]
02d041a4 668b426e mov ax,[edx+0x6e]
02d041a8 66894150 mov [ecx+0x50],ax
02d041ac 8b4df0 mov ecx,[ebp-0x10]
02d041af 8b5110 mov edx,[ecx+0x10]
02d041b2 8b45e8 mov eax,[ebp-0x18]
02d041b5 668b4870 mov cx,[eax+0x70]

*----> Stack Back Trace <----*
*** ERROR: Symbol file could not be found. Defaulted to export symbols
for C:\WINDOWS\system32\winspool.drv -
*** ERROR: Symbol file could not be found. Defaulted to export symbols
for C:\WINDOWS\system32\GDI32.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols
for C:\WINDOWS\system32\spool\PRTPROCS\W32X86\hpzpp4wm.DLL -
ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be
wrong.
01d3b3a4 02d078f9 00000000 01d3b944 01d3b6ec hpmdp5r1+0x4193
01d3b910 73076633 00000000 01d3b944 00000000
hpmdp5r1!DrvDocumentPropertySheets+0x5f9
01d3b930 730765a8 00000000 01d3b944 000f9fa0
winspool!DocumentPropertySheets+0x56
01d3b968 77c131ba 00000000 00126144 00161a78
winspool!DocumentPropertiesW+0x9f
01d3b9d0 77c0b923 01d3b9f4 01d3b9ec 00161a78 GDI32!EngDeletePalette+0xe0
01d3ba08 77c0b944 77c0156c 000d3d70 77c0156c
GDI32!EnumFontFamiliesExW+0x18b
01d3ba24 77c3406e 77c0156c 000d3d70 77c0156c GDI32!CreateDCW+0x18
01d3ba48 01937073 000d3d70 00161a78 01d3f304
GDI32!GdiGetSpoolFileHandle+0xad
01d3ee80 0195484d 00100390 01d3f304 00000006
hpzpp4wm!EnumPrintProcessorDatatypesW+0xfb3
01d3eeb0 7615a229 00100390 01d3f304 00000000
hpzpp4wm!PrintDocumentOnPrintProcessor+0x6d
01d3f948 7615aadd 009375b8 01d3f970 00000000
localspl!SplDeleteSpooler+0xbd0
01d3ffb8 77e64829 009375b8 00000000 00000000
localspl!SplDeleteSpooler+0x1484
01d3ffec 00000000 7615a83a 009375b8 00000000
kernel32!GetModuleHandleA+0xdf


Bruce
 
A

Alan Morris [MSFT]

sounds like a good way to get the print server stabilized.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1

This posting is provided "AS IS" with no warranties, and confers no rights.

Bruce Lautenschlager said:
I'm pretty sure that's the 4200/4250 drivers, which are the latest, but
I'll see if anyone at HP can agree. That being the case, I'm thinking
about trying this workaround:

http://support.microsoft.com/kb/947477


Alan Morris said:
find out which printer uses the hpzpp4wm print processor and check if HP
has an updated driver for the device

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1

This posting is provided "AS IS" with no warranties, and confers no
rights.

Bruce Lautenschlager said:
Mine all look a lot like this:

*** ERROR: Symbol file could not be found. Defaulted to export symbols
for C:\WINDOWS\system32\spool\DRIVERS\W32X86\3\hpmdp5r1.dll -
function: hpmdp5r1
02d04178 c9 leave
02d04179 7542 jnz hpmdp5r1+0x41bd (02d041bd)
02d0417b 8b55f0 mov edx,[ebp-0x10]
02d0417e 8b420c mov eax,[edx+0xc]
02d04181 0fbf484e movsx ecx,word ptr [eax+0x4e]
02d04185 83f901 cmp ecx,0x1
02d04188 7533 jnz hpmdp5r1+0x41bd (02d041bd)
02d0418a 8b55f0 mov edx,[ebp-0x10]
02d0418d 8b4210 mov eax,[edx+0x10]
02d04190 8b4de8 mov ecx,[ebp-0x18]
FAULT ->02d04193 668b516c mov dx,[ecx+0x6c]
ds:0023:0000006c=????
02d04197 6689504e mov [eax+0x4e],dx
02d0419b 8b45f0 mov eax,[ebp-0x10]
02d0419e 8b4810 mov ecx,[eax+0x10]
02d041a1 8b55e8 mov edx,[ebp-0x18]
02d041a4 668b426e mov ax,[edx+0x6e]
02d041a8 66894150 mov [ecx+0x50],ax
02d041ac 8b4df0 mov ecx,[ebp-0x10]
02d041af 8b5110 mov edx,[ecx+0x10]
02d041b2 8b45e8 mov eax,[ebp-0x18]
02d041b5 668b4870 mov cx,[eax+0x70]

*----> Stack Back Trace <----*
*** ERROR: Symbol file could not be found. Defaulted to export symbols
for C:\WINDOWS\system32\winspool.drv -
*** ERROR: Symbol file could not be found. Defaulted to export symbols
for C:\WINDOWS\system32\GDI32.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols
for C:\WINDOWS\system32\spool\PRTPROCS\W32X86\hpzpp4wm.DLL -
ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be
wrong.
01d3b3a4 02d078f9 00000000 01d3b944 01d3b6ec hpmdp5r1+0x4193
01d3b910 73076633 00000000 01d3b944 00000000
hpmdp5r1!DrvDocumentPropertySheets+0x5f9
01d3b930 730765a8 00000000 01d3b944 000f9fa0
winspool!DocumentPropertySheets+0x56
01d3b968 77c131ba 00000000 00126144 00161a78
winspool!DocumentPropertiesW+0x9f
01d3b9d0 77c0b923 01d3b9f4 01d3b9ec 00161a78 GDI32!EngDeletePalette+0xe0
01d3ba08 77c0b944 77c0156c 000d3d70 77c0156c
GDI32!EnumFontFamiliesExW+0x18b
01d3ba24 77c3406e 77c0156c 000d3d70 77c0156c GDI32!CreateDCW+0x18
01d3ba48 01937073 000d3d70 00161a78 01d3f304
GDI32!GdiGetSpoolFileHandle+0xad
01d3ee80 0195484d 00100390 01d3f304 00000006
hpzpp4wm!EnumPrintProcessorDatatypesW+0xfb3
01d3eeb0 7615a229 00100390 01d3f304 00000000
hpzpp4wm!PrintDocumentOnPrintProcessor+0x6d
01d3f948 7615aadd 009375b8 01d3f970 00000000
localspl!SplDeleteSpooler+0xbd0
01d3ffb8 77e64829 009375b8 00000000 00000000
localspl!SplDeleteSpooler+0x1484
01d3ffec 00000000 7615a83a 009375b8 00000000
kernel32!GetModuleHandleA+0xdf


Bruce
 
J

JoShmo

Im getting very similar issues on a few win2k3 print servers, its looking
like the 1320 driver is the one cause our faults.. 6161 errors with a 0 They
have been ongoing for a couple of years now... HP released a new driver in
May 08 (for a printer that has been discontinued hmmm..) but we are still
getting issues.

Have you managed to get to the bottom of your issue, we have already tried
the points in KB947477
 
Ad

Advertisements

B

Bruce Lautenschlager

I haven't sorted it out yet, and I haven't tried the suggestions in KB947477
yet (somehow I don't think they apply to me - just a hunch). I have two
other smaller sites that I keep domain controllers at (they use a single
2003 R2 server) and also as their print server, with a similar mix of
printers (just much smaller proportions, about 22 instead of 287). I'm
trying to compare them, to see why the spooler service doesn't crash at
those two sites like it does here. One site has the latest 4250 driver, and
one doesn't. Other than that, they're pretty similar. And pretty reliable.
Although I did notice when I updated the 4250 driver at one of the remote
sites (trying to fix a random printing issue), when the server started
pushing out the updated druver to the client PCs, often the spooler on the
PCs would crash and not restart. Related, ironic, or both?

I'm also trying to relate the 6161 errors (or any printing errors) with when
the spooler crashes. I think I might see a pattern with an Excel spreadsheet
that gets printed frequently to a LJ4200, but I'm not sure.

I haven't given up, and will post the changes/results here.

Bruce
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top