Re: Print Spool / Pipes not released
- From: "Alan Morris [MSFT]" <alanmo@xxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 1 Nov 2005 14:42:54 -0800
The clients will keep 1 session open for every application that has called
into the remote spooler. When you say logon is this from a logoff of just
locking the machine? If users lock and leave the application running (which
is very normal) I would expect 3 or 4 open sessions to the print server.
The biggest problems I have had are mobile computers as they move from one
network segment to another and the server attempts to find them at the old
address when sending notification information to the client. But with
service pack 2 rollout the looping client calls has not been an issue.
The next step would be to get a network capture of the packet exchange
between the client and server. Filter for MSRPC packets . Opnum 13 is
RPCwriteprinter so you would see this when the client is printing.
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
This posting is provided "AS IS" with no warranties, and confers no rights.
"Adrian" <Adrian@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2DF84365-5E94-4693-B268-3EB3238788FD@xxxxxxxxxxxxxxxx
> We have about 10 machines on the network with local printers. Some of
> these
> PC's are seeing the problem, but as far as I can tell no more than any
> other
> PC. We are running SP2 on our XP machines (SP1 on the 2003 Printserver).
> On
> all our machines we have the following local printer drivers installed:
> Microsoft Office Document Image Writer
> PDF995
> Xerox Phaser 5400 PCL 5e.
>
> As well as this we have on the Printserver the following drivers:
> HP Business Inkjet 2230/2280
> HP LaserJet 2100
> HP LaserJet III
> OKI B6300(PCL6)
> OKI C5400(PCL)
> Tektronix Phaser 860N by Xerox
> Xerox Phaser 5400 PCL 5e
> Xerox Phaser 5500N PCL 5e
> Xerox Phaser 7300N
> Xerox Phaser 8200N
>
> These drivers are used for 18 networked printers.
>
> On top of this the drivers from the local printers have found their way
> onto
> all the PC's on the network (about 500). If these drivers are not being
> used
> by the printers, can they still have an adverse affect.
>
> The following are the extra drivers found on the workstations:
>
> Brother HL-1230
> Brother HL-2460
> HP Color LaserJet 2500 PCL 6
> HP LaserJet 4000 Series PCL6
> HP LaserJet 6L
> HP LaserJet 6P
> HP LaserJet Series II
> Kyocera FS-1550 / FS-1550A
> Kyocera Mita FS-1020D
> Kyocera Mita FS-1020D KX
> OKI C5200n
> Samsung ML-1450 Series PCL 6
> Xerox Phaser 5400 PS.
>
> As you can see there are one or two. Whether these drivers came from when
> users logged and they 'Automatically search for network folders and
> printers'
> (which is now unticked) I don't know.
>
> I have a machine next to me that the spool is running at about 90% with 20
> threads open and 7 pipes open to the Printserver. All I did was logon.
>
> So what do you suggest? Do I delete the unwanted printer drivers (if that
> solves it how do I stop them coming back?).
> Can I try a pre-SP2 spoolsv.exe to see how that performs.
>
> Thanks for your help
>
> Adrian Passey
>
>
> "Alan Morris [MSFT]" wrote:
>
>> There was a fix in XP SP2 that limits the number of client spooler
>> asynchronous OpenPrinter calls to the server.
>>
>> We found in cases for mobile users and slow networks that the client
>> spooler
>> would retry the connection before the transport layer could fail or
>> succeed
>> and thus wind up looping and piling up a series of these calls to the
>> server.
>>
>> You will see an increased # of connections on the server for a specific
>> client.
>>
>> On the client, the spooler is looping causing excessive CPU utilization.
>> Check the client using task manager to verify the number of spooler
>> threads
>> running on the client spoolsv.exe process. Normal for none printing
>> system
>> with a couple of connected printers will be less than 20 threads.
>>
>> Are there any local printers defined on the clients? There was also an
>> issue with some Vendor drivers that caused the spooler to start looping
>> in
>> this function.
>>
>> If you are running SP2 and have some clients with local printers, what
>> are
>> the drivers used?
>>
>> --
>> Alan Morris
>> Windows Printing Team
>> Search the Microsoft Knowledge Base here:
>> http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Adrian" <Adrian@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:B7FB051C-1CBF-4CD0-AC86-7CF23EFFE566@xxxxxxxxxxxxxxxx
>> > Hello there,
>> > Since we upgraded our system to XP from 2000 in the summer we have
>> > noticed
>> > that the print spool on some of the workstations (no particular
>> > pattern)
>> > runs
>> > at about 50 - 60%. This activity remains even after the user has
>> > logged
>> > off.
>> > This also affects the Print Server as the \pipe\spoolss does not get
>> > released and therefore over the course of a day the CPU on the server
>> > runs
>> > at
>> > 100%. Generally one thing happens before this arises on the
>> > workstations.
>> > Print drivers get downloaded from the server. It doesn't seem to
>> > matter
>> > which drivers are downloaded, but this problem is always preceded by a
>> > printer driver coming from the Print server. Also on occasion if an
>> > application crashes such as word then the pipes are not released
>> > between
>> > the
>> > workstation and server.
>> > Rebooting of the workstation or the restarting of the print spool on
>> > the
>> > workstation resolves this but that doesn't help the user on the very
>> > slow
>> > workstation.
>> > Any ideas? I've tried changing the profiles, changing the print
>> > server,
>> > trying to prevent null connections. None of this has identified the
>> > cause.
>> >
>> > Thanks
>>
>>
>>
.
- Follow-Ups:
- Re: Print Spool / Pipes not released
- From: Adrian
- Re: Print Spool / Pipes not released
- Prev by Date: Re: Can't send fax
- Next by Date: Re: Pausing documents by default
- Previous by thread: Re: Can't send fax
- Next by thread: Re: Print Spool / Pipes not released
- Index(es):
Relevant Pages
|
Loading
