locked
Print Spooler Stops Several Times Per Day RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    We have 4 RD Session Hosts which are managed by a Connection Broker.  The Print Spooler service randomly stops on each of the hosts.  It seems to happen more on 2 of the servers.  I'm having trouble finding the cause.  This went from never happening, to happening about once a week, to now happening 5-6 times per day.

    Event Log - General tab

    Faulting application name: spoolsv.exe, version: 10.0.14393.3085, time stamp: 0x5d1d7cc8

    Faulting module name: jscript.dll, version: 5.812.10240.16384, time stamp: 0x5d804423

    Exception code: 0xc0000005

    Fault offset: 0x0000000000005223

    Faulting process id: 0x5948

    Faulting application start time: 0x01d57a032a3f18ac

    Faulting application path: C:\Windows\System32\spoolsv.exe

    Faulting module path: C:\Windows\System32\jscript.dll

    Report Id: 34267c01-cc0a-41ef-9c82-066a33f4e406

    Faulting package full name: 

    Faulting package-relative application ID: 

    XML:

    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="Application Error" />
      <EventID Qualifiers="0">1000</EventID>
      <Level>2</Level>
      <Task>100</Task>
      <Keywords>0x80000000000000</Keywords>
      <TimeCreated SystemTime="2019-10-03T16:01:48.552416900Z" />
      <EventRecordID>470280</EventRecordID>
      <Channel>Application</Channel>
      <Computer>sRSHdlfna202.i.dlfna.com</Computer>
      <Security />
      </System>
    - <EventData>
      <Data>spoolsv.exe</Data>
      <Data>10.0.14393.3085</Data>
      <Data>5d1d7cc8</Data>
      <Data>jscript.dll</Data>
      <Data>5.812.10240.16384</Data>
      <Data>5d804423</Data>
      <Data>c0000005</Data>
      <Data>0000000000005223</Data>
      <Data>5948</Data>
      <Data>01d57a032a3f18ac</Data>
      <Data>C:\Windows\System32\spoolsv.exe</Data>
      <Data>C:\Windows\System32\jscript.dll</Data>
      <Data>34267c01-cc0a-41ef-9c82-066a33f4e406</Data>
      <Data />
      <Data />
      </EventData>
      </Event>


    Thursday, October 3, 2019 5:55 PM

Answers

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    there is a known issue with printing in KB4522016,
    but thats supposedly fixed in the latest update:
    October 3, 2019—KB4524147 (OS Build 18362.388)

    "Addresses an intermittent issue with the print spooler service that may cause print jobs to fail."


    • Edited by EckiS Thursday, October 3, 2019 6:25 PM
    Thursday, October 3, 2019 6:24 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I tried the update on Windows 10 1809 (775) and it didn't fix the issue for me.  Same error appears for me.
    • Edited by Alex Klaman Thursday, October 3, 2019 8:46 PM Clarified Version
    Thursday, October 3, 2019 8:45 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Please update system to latest build 18362.388 and test result, which fix the known issue about print spooler service in KB4517211.

    Regards


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, October 4, 2019 9:27 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    We're on Version 1607, Build 14393.3242.  Trying to schedule the update now.  I'll post an update after we do it.
    Friday, October 4, 2019 6:09 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I did find a solution to this.  But it's a little bit of a mess as I had to delete quite a few Keys from the Registry.

    You should look at:
    Event Viewer Applications and Services Microsoft\Windows\PrintService

    I found the Solution.
    There are WARNINGS to this.
    One, you WILL need to Delete Things from the System's Registry. Two, you WILL need to reinstall all printers after this is done.
    Three, this may only apply if you are using a Print Server.

    Four, MAKE a BACKUP before you delete things. Just in case.

    With that being said, here's what I did and how I fixed it. I got the above message on Windows 10 1809 Version 775 from the Event Viewer under Windows Logs, Application. You should see a Red Error Icon with a message like I got. If you do, then check Event viewer, windows logs, applications and services logs, microsoft, windows, printservice

    You are looking for an error message like: Printer {ED766806-D1CC-463F-951D-25647A0CF513} failed to initialize because a suitable HP Universal Printing PCL 6 (v5.8.0) driver could not be found. The new printer settings that you specified have not taken effect. Install or reinstall the printer driver. You might need to contact the vendor for an updated driver.

    Or another message starting with Printer {UID}

    Note each {UID} that has a problem.

    Open RegEdit as Administrator. You will need to Edit/Delete HKLM values.
    Go to:

    Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Providers\Client Side Rendering Print Provider

    You should see various SIDs listed for each user that has logged into the System. For each SID, go to Printers\Connections. You should see your Network printers listed. Delete them all. Repeat for each SID.

    Go to: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Providers\Client Side Rendering Print Provider\Servers

    Expand out the Key for each of the listed servers. Under each Server key, go to Printers. You should see the {UID} that was giving you trouble. Delete that Key Under the Server's Printers Key.

    Also under Each Server key, go to:
    Monitors\Client Side Port

    and delete the {UID} Key there as well. DO NOT delete Monitors\Client Side Port

    Go to:

    Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Printers

    Delete your Network Printers. Do NOT delete the Microsoft Printers.

    Restart the Printer Spooler Service if is running or start the Print Spooler Service if isn't not running. Check the Event Viewer and see if you missed anything.
    After that is done, reinstall your Printers and you should be good after that.


    Friday, October 4, 2019 6:11 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    We're also seeing a lot of these:

    1. The print spooler failed to import the printer driver that was downloaded from \\TANSVR1\print$\x64\PCC\datamax.inf_amd64_9f994d3949313e39.cab into the driver store for driver Datamax I-4208. Error code= 800f0242. This can occur if there is a problem with the driver or the digital signature of the driver.
    2. The print spooler failed to download and import the printer driver from \\TANSVR1 into the driver store for driver Datamax I-4208. Error code= 800f0242.

    We have many Zebra and Datamax printers on \\tansvr1, which is the print server.  I see 9 errors like these all happening within seconds of each other.  I only see these errors in reference to drivers coming from Seagull Scientific.

    Friday, October 4, 2019 8:06 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    We're having similar issues on server 2019 (v 1809, build 17763.775), with the added bonus of massive duplication of printers. We have ~63 printers in the company but two of our servers (again, 2019 v1809, build 17763.775) duplicated most if not all of the printers until there was about 300 printers on each server. We cleaned this up by ensuring the spooler was stopped (which isn't hard when it crashes every few minutes) and then removing the following registry keys:

    Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Connections
    Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Printers
    Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Providers
    Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\V4 Connections

    Then starting the spooler and manually deleting each duplicate printer from within Devices and Printers. This was the only way we were able to remove the dupes.  Even after all that, the spooler continues to crash every so often with the following error:


    Faulting application name: spoolsv.exe, version: 10.0.17763.615, time stamp: 0x24910946
    Faulting module name: jscript.dll, version: 5.812.10240.16384, time stamp: 0xbd259d2a
    Exception code: 0xc0000005
    Fault offset: 0x000000000001e0fb
    Faulting process id: 0xfb8
    Faulting application start time: 0x01d57af3dc792392
    Faulting application path: C:\Windows\System32\spoolsv.exe
    Faulting module path: C:\Windows\System32\jscript.dll
    Report Id: fe5785ee-90bc-433a-af79-c4ffb28db154
    Faulting package full name: 
    Faulting package-relative application ID: 

    Note: We never install printers locally. They're always deployed "per machine" via Group Policy. We never install printers "per user" either. The PrintService log is also full of entries like this:


    Group Policy was unable to add per computer connection \\PRINTSERVER\TOSHIBA e-STUDIO7516AC (SomeOffice). Error code 0xBC4. This can occur if the name of the printer connection is incorrect, or if the print spooler cannot contact the print server. 

    Group Policy was unable to add per computer connection \\PRINTSERVER\HP LaserJet P2035n (SomeOtherOffice). Error code 0xA. This can occur if the name of the printer connection is incorrect, or if the print spooler cannot contact the print server. 

    Group Policy was unable to add per computer connection \\PRINTSERVER\Samsung X7500GX (SomeOtherOtherOffice). Error code 0x5. This can occur if the name of the printer connection is incorrect, or if the print spooler cannot contact the print server. 

    We've applied the latest available updates through Windows Update yet the problem persists.

    EDIT: I was able to resolve the issue by uninstalling the following updates: 

    1. KB4524148 (October 3, 2019)
    2. KB4516077 (September 24, 2019)
    3. KB4522015 (September 23, 2019)
    4. KB4512578 (September 10, 2019)
    5. KB4512534 (August 17, 2019)

    Start with the first one in the list and work your way down to the last. You'll be prompted to reboot after every uninstall. The forum won't allow me to post a link but just google Microsoft releases even more patches for the CVE-2019-1367 IE zero-day, and the bugs are having a field day ... Read the article on computerworld by Woody Leonhard.


    Friday, October 4, 2019 9:20 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Microsoft posted a fix in latest 10/8/19 update: KB4519338 (OS Build 17763.806).

    Addresses an issue with applications and printer drivers that utilize the Windows JavaScript engine (jscript.dll) for processing print jobs.

    https://support.microsoft.com/en-us/help/4519338/windows-10-update-kb4519338

    Install these in order:

    http://www.catalog.update.microsoft.com/Search.aspx?q=KB4521862

    http://www.catalog.update.microsoft.com/Search.aspx?q=KB4519338

    Tuesday, October 8, 2019 9:34 PM