Event ID 215 PrintService - Installing printer driver - failed, error code 0x5b3,

Answered Event ID 215 PrintService - Installing printer driver - failed, error code 0x5b3,

  • Thursday, May 05, 2011 2:36 PM
     
     

    Windows 2008 R2 SP1 x64 Terminal Server - Hyper-V with Citrix XenApp6

    Unable to install printer.  Event ID 215 - 0x5b3 error code.

    Log Name:      Microsoft-Windows-PrintService/Admin
    Source:        Microsoft-Windows-PrintService

    Event ID:      215
    Task Category: Installing a printer driver
    Level:         Error
    Keywords:      Printer Setup,Printer

    Description:
    Installing printer driver - failed, error code 0x5b3, HRESULT 0x800705b3. See the event user data for context information.

     

    Prior to that Event ID 215

    Description:
    Installing printer driver HP Universal Printing PCL 5 (v5.2) failed, error code 0x0, HRESULT 0x800705b3.

     

    I was able to remove the driver but cannot add it back.

    This keeps happening on various servers.  In the past week I have had to rebuild 4 servers out of 11.

     

    The only reference to the error code 0x5b3 I have found is for Vista and I have tried those suggestions.

    I have ruled out the problem being a Virus.   I have cleaned out the registry settings as per various posts from Technet.  Which allowed me to remove the driver only. Not add it back.

    This is the latest version of the HP UPD PCL5 driver.  It seems to have started after installing SP1 for W2k8 R2 in February.

    The problem seems to happening more frequent now.

     

    Are there other suggestions?

    Would appreciate any help.

     

    Thanks,

    Denise


    Denise Child

All Replies

  • Thursday, May 05, 2011 4:45 PM
    Answerer
     
     

    HP driver throws a session 0 UI.  Is there anything in your configuration that would remove the Interactive Windows security?

    C:\>winerror 0x5b3
      1459 ERROR_REQUIRES_INTERACTIVE_WINDOWSTATION


    Alan Morris Windows Printing Team
  • Thursday, May 05, 2011 5:04 PM
     
     

    Hi Alan,

    I see the Interactive Services Detection service set to manual - same as the other servers.  It was not running, so I started it, but I see it running on the other servers. 

    Is there something else I need to do once this is running.  Tried to install the driver and it gave the same 0x5b3 error.

     

    Thanks,

    Denise

     


    Denise Child
  • Thursday, May 05, 2011 8:13 PM
    Answerer
     
     Answered

    Not sure if this is the same.  I assume you can install a printer using one of the drivers HP included in Windows.  Session 0 UI is not allowed for any of the vendor print drivers included in Windows so the HP driver do not perform those functions.  I stay clear of the Universal drivers unless asked to verify some enhancements or fixes to the driver. 

    It sounds more like there is some setting on your system blocking the session 0 UI.  I have installed printer using the HP Universal PCL6 driver on 2008 R2 SP1 and got the session 0 dialogs and the device installed.

    I recall there was an issue when an older version of a HP file existed on the machine that blocked the printer install.  I'll check with the HP driver developer who works out of Redmond. 


    Alan Morris Windows Printing Team
  • Thursday, May 05, 2011 8:41 PM
     
     

    Yes, I am able to install other drivers, including HP drivers, on the server when this happens.  Only the HP UPD PCL5 gives the problem.

    There are 3 other HP drivers -

    HP Color LaserJet 2800 Series PS

    HP Color Laser Jet 4730mfp pcl5c

    HP Color Laser Jet 3500

     

    The majority of the printers use the UPD driver.

    I can print to the other printers and add/remove drivers for those. 

     


    Denise Child
  • Monday, May 09, 2011 5:01 PM
     
     

    I have 2 more servers down this morning due to this error.  Any word from HP developer?

    Do you have any suggestions on how to repair vs. rebuild? 

    I was only able to follow tips from Vista machine in past.  Not sure if this would be different for a W2k8 R2 server.

     

    Thanks,

    Denise


    Denise Child
  • Thursday, June 09, 2011 2:03 PM
     
     

    Is there any update on this issue?

    We have a similar problem on a Remote Desktop Services Server. Error is "There is not enough disk space to complete this operation", but we are sure we have disk space about 20GB free.

    Logs are showing Error id 215 Installing printer driver - failed, error code 0x70, HRESULT 0x80070070. See the event user data for context information.

  • Thursday, June 09, 2011 3:15 PM
    Answerer
     
     

    The errors are stating you are out of disk space.  Have you set up disk quotas?  You should start a new post, this is a different issue.

    C:\>winerror 0x70
       112 ERROR_DISK_FULL <--> 0xc000007f STATUS_DISK_FULL


    Alan Morris Windows Printing Team
  • Monday, June 13, 2011 2:50 PM
     
     

    Like i said, there was 20gb free space. And now we extended there is 120gb free space.

    We have disk quotas but Administrator , system, network service accounts dont have any restriction. Quotas are just for RDS users.

  • Thursday, October 13, 2011 2:50 PM
     
     
    I am having same errors did we ever found the solutions
    • Edited by Yi Ping Thursday, October 13, 2011 2:51 PM
    •  
  • Friday, August 31, 2012 1:55 AM
     
     
    I am having the same issue as well.
  • Monday, January 14, 2013 11:28 AM
     
     

    Same issue here. Also same error, same driver:

    "Installing printer driver HP Universal Printing PCL 5 (v5.2) failed, error code 0x0, HRESULT 0x800705b3."

    Workstations randomly report this error, even freshly installed machines.

  • Thursday, April 25, 2013 3:19 PM
     
     

    You may want to check the %SYSTEMROOT%\System32\Spool\prtprocs\x64 folder contents out.

    Our 2008 R2 RDSH server environment was suddenly running into Event ID 215 PrintService issues and it ended up we hit this "499" folder limit.  We have been having a fair number of Print Spooler crashes and our theory is that when Print Spooler crashes due to drivers & print processors the temporary copy process that generates these folders is killed before it can remove the folder.

    See this Technet Discussion: http://social.technet.microsoft.com/Forums/en-US/winserverprint/thread/111c5a7e-14f5-42a8-9a89-789a8f2e54cb/

    I'm still searching on Technet to see if any Microsoft HotFix exists that would handle this supposed "499" folder limit automatically.  We already had to generate a custom script to delete Print Spool temp files in %SYSTEMROOT%\System32\Spool\PRINTERS\ whenever the Print Spool crashes before it restarts the service.  Now I'm going to add to the script to clear out these prtprocs\x64 folders to see if this helps.


    "Those who fear the darkness have never seen what the light can do." Magic: The Gathering