Re: Spoolsv.exe & CPU Since Update
- From: "Don Miller" <nospam@xxxxxxxxxx>
- Date: Wed, 7 Sep 2005 09:53:10 -0500
OK. I tried the workaround. Deleted two BUD files and then went to regedit
and never found a subkey PostSPUpgrade. I deleted by old printer and added a
new printer using the generic Brother drivers as provided on the link you
left. I could even see the printer "opening" and the BUD file appearing and
then tried to print a test page when it was ready. The test page error
message popped up immediately. Then, my printer was no longer recognized on
the network and I had to unplug and plug in again the router to be able to
see the printer on the network. Then I tried printing a test page again
without success. And now my printer is off the network again.
I tried the workaround on my other computer and also did not find the subkey
PostSPUpgrade.
And here is the properties from the error event:
Event Type: Error
Event Source: Print
Event Category: None
Event ID: 6161
Date: 9/7/05
Time: 9:42:20 AM
User: xxxxx/xxxxx
Computer: xxxxx
Description:
The document Test Page owned by xxxxxx failed to print on printer
\\BRN_327B00\BINARY_P1. Data type: NT EMF 1.008. Size of the spool file in
bytes: 0. Number of bytes printed: 0. Total number of pages in the document:
0. Number of pages printed: 0. Client machine: \\xxxxx Win32 error code
returned by the print processor: 259.
"Tom Che [MSFT]" <v-tomche@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:tAqouL3sFHA.456@xxxxxxxxxxxxxxxxxxxxxxxx
> Hi Don,
>
> Thanks for your update.
>
> Yes, it is possible. Based on my research, the Brother HL-1650/1670 is
> using Unidrv-based Printer Control Language (PCL) printer driver. So, I
> suggest that you may refer to the workaround of KB832219 for a test:
>
> WORKAROUND
> Warning If you use Registry Editor incorrectly, you may cause serious
> problems that may require you to reinstall your operating system.
Microsoft
> cannot guarantee that you can solve problems that result from using
> Registry Editor incorrectly. Use Registry Editor at your own risk.
>
> If you cannot wait for the server to complete the parsing of all the
> Unidrv-based printer drivers, manually remove all cached binary printer
> description files (.bud files), and then let them be automatically
> re-created. Depending on the speed of your server, this automatic
> re-creation may be completed in a shorter time. Typically, this operation
> is completed within 30 minutes.
>
> Note When Print Spooler starts, it installs a newer version of Unidrv.dll.
> As a result, the .bud files are out of date. The .bud files are the
> compiled versions of .ppd files and can be completely regenerated from
> those .ppd files. Because of this, you can remove the .bud files. To do
> this, follow these steps:
>
> 1. Stop the Print Spooler service. To do this, run the following command
> from a command prompt:
> net stop spooler
> 2. Search for all .bud files, and then make sure that they are stamped
with
> the current time and date. The files appear with today's date.
> 3. Remove all .bud files that have a date and time stamp that is before
> today's date. These files are located in the following folder:
> %SYSTEMROOT%\System32\Spool\Drivers\w32x86\3
> 4. Remove the following registry key if it exists:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\PostSPUpgrade
> To do this, follow these steps:a. Click Start, click Run, type regedit in
> the Open box, and then click OK.
> b. Locate, and then click the following registry subkey:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print
> c. On the Registry menu, click Export Registry File.
> d. In the File name box, type printkey, and then click Save.
>
> Note If you later have to restore the Print registry key, you can do so by
> double-clicking the Printkey.reg file that you saved.
> e. Locate, and then click the following registry subkey if it exists:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\PostSPUpgrade
> f. On the Edit menu, click Delete, and then click Yes to confirm the
> removal of the PostSPUpgrade registry key.
>
> Note The PostSPUpgrade registry key may reappear after you restart the
> computer. This behavior occurs if other .bud files exist that have not yet
> been parsed. After these files have been parsed, this registry key is
> automatically removed.
>
> 5. Restart the server.
> After you restart the server, printing functionality is available to users
> after about 30 minutes.
>
>
> If the issue persists after above steps, you may uninstall the current
> driver and try to download and install the following driver:
>
> <http://solutions.brother.com/hl1650/download/dl-generic2kxp.html>
>
> Hope this helps!
>
> Have a nice day!
>
> Sincerely,
> Tom Che
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
>
> =====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> --------------------
> >From: "Don Miller" <nospam@xxxxxxxxxx>
> >References: <#i4TmDosFHA.4036@xxxxxxxxxxxxxxxxxxxx>
> <R6yJSdrsFHA.2956@xxxxxxxxxxxxxxxxxxxxx>
> >Subject: Re: Spoolsv.exe & CPU Since Update
> >Date: Tue, 6 Sep 2005 08:56:00 -0500
> >Lines: 101
> >X-Priority: 3
> >X-MSMail-Priority: Normal
> >X-Newsreader: Microsoft Outlook Express 6.00.2800.1506
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
> >Message-ID: <#4hLCpusFHA.596@xxxxxxxxxxxxxxxxxxxx>
> >Newsgroups: microsoft.public.win2000.general
> >NNTP-Posting-Host: adsl-65-66-153-119.dsl.kscymo.swbell.net 65.66.153.119
> >Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
> >Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.win2000.general:62652
> >X-Tomcat-NG: microsoft.public.win2000.general
> >
> >Yes, I checked the system log and the printing errors (copied below)
began
> >immediately after my update on 8/13/05. I think I can find the name of
the
> >updates listed in the system log as well.
> >
> >I've read the link but I do not receive error messages as stated in the
> >Article. The print job seems to start, the printer icon appears in the
> >system tray and then goes away without any data sent to the printer. When
I
> >try to print a test page, nothing happens, no error messages, it just
> hangs.
> >Then I found, after any attempt to print, my LAN is shut down until I
> unplug
> >the router and plug it back in.
> >
> >Does this sound like the same problem to you? Thanks.
> >
> >
> >The document XXX owned by XXX failed to print on printer Brother
> >HL-1650/1670N-USB. Data type: NT EMF 1.008. Size of the spool file in
> bytes:
> >0. Number of bytes printed: 0. Total number of pages in the document: 0.
> >Number of pages printed: 0. Client machine: XXX. Win32 error code
returned
> >by the print processor: 259.
> >
> >The document XXX owned by XXX failed to print on printer Brother
> >HL-1650/1670N series. Data type: NT EMF 1.008. Size of the spool file in
> >bytes: 0. Number of bytes printed: 0. Total number of pages in the
> document:
> >0. Number of pages printed: 0. Client machine: XXX. Win32 error code
> >returned by the print processor: 1801.
> >
> >
> >
> >"Tom Che [MSFT]" <v-tomche@xxxxxxxxxxxxxxxxxxxx> wrote in message
> >news:R6yJSdrsFHA.2956@xxxxxxxxxxxxxxxxxxxxxxxx
> >> Hi Don,
> >>
> >> Thanks for posting here. Also thanks for our MVP Dave's advice.
> >>
> >> Actually, there were some similar printing issues with latest updates
for
> >> Windows 2000. Don, you may refer to the following KB article for
> >> troubleshooting first:
> >>
> >> Users cannot print after you install a service pack, update rollup, or
> >> printer hotfix on a server in Windows 2000
> >> http://support.microsoft.com/kb/832219
> >>
> >> If above KB article cannot help on your issue, you may attempt to
> >uninstall
> >> the latest updates one by one for a test. If the issue disappears
after
> >> the removal of certain update, you may try to install this update again
> to
> >> reproduce this issue. If you can reproduce this issue as expected,
> please
> >> let us know which update is the root cause.
> >>
> >> Hope this helps!
> >>
> >> Have a nice day!
> >>
> >> Sincerely,
> >> Tom Che
> >> Microsoft Online Partner Support
> >> Get Secure! - www.microsoft.com/security
> >>
> >> =====================================================
> >> When responding to posts, please "Reply to Group" via your newsreader
so
> >> that others may learn and benefit from your issue.
> >> =====================================================
> >> This posting is provided "AS IS" with no warranties, and confers no
> >rights.
> >>
> >> --------------------
> >> >From: "Don Miller" <nospam@xxxxxxxxxx>
> >> >Subject: Spoolsv.exe & CPU Since Update
> >> >Date: Mon, 5 Sep 2005 20:21:47 -0500
> >> >Lines: 12
> >> >X-Priority: 3
> >> >X-MSMail-Priority: Normal
> >> >X-Newsreader: Microsoft Outlook Express 6.00.2800.1506
> >> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
> >> >Message-ID: <#i4TmDosFHA.4036@xxxxxxxxxxxxxxxxxxxx>
> >> >Newsgroups: microsoft.public.win2000.general
> >> >NNTP-Posting-Host: adsl-65-66-153-119.dsl.kscymo.swbell.net
> 65.66.153.119
> >> >Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
> >> >Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.win2000.general:62628
> >> >X-Tomcat-NG: microsoft.public.win2000.general
> >> >
> >> >Since my last automatic August update for my W2KSP4 machine, I have
not
> >> been
> >> >able to print anything from MS products. I find that process
spoolsv.exe
> >is
> >> >using close to 100% CPU. I've seen that there were problems with the
SP4
> >> >Rollup with this regard, and noticed that the update MS05-043 had
> >something
> >> >to do with the spool server. I'm guessing that MS's "fix" does not
play
> >> well
> >> >with others.
> >> >
> >> >The same thing happened on another W2K machine of mine.
> >> >
> >> >Does anyone know what is going on, and how I can print again?
> >> >
> >> >
> >> >
> >>
> >
> >
> >
>
.
- Follow-Ups:
- Re: Spoolsv.exe & CPU Since Update
- From: Dave Patrick
- Re: Spoolsv.exe & CPU Since Update
- References:
- Spoolsv.exe & CPU Since Update
- From: Don Miller
- RE: Spoolsv.exe & CPU Since Update
- From: Tom Che [MSFT]
- Re: Spoolsv.exe & CPU Since Update
- From: Don Miller
- Re: Spoolsv.exe & CPU Since Update
- From: Tom Che [MSFT]
- Spoolsv.exe & CPU Since Update
- Prev by Date: installing Win 2000 Pro.
- Next by Date: OT: where are the Microsoft Antispyware newsgroups?
- Previous by thread: Re: Spoolsv.exe & CPU Since Update
- Next by thread: Re: Spoolsv.exe & CPU Since Update
- Index(es):
Loading