After DISM upgrade from Standard to Enterprise, clients can no longer print RRS feed

  • Question

  • After upgrading our terminal server from 2008 R2 standard to 2008 R2 Enterprise using DISM, our users are now no longer able to print. The version upgrade seems successful on the surface (the version shows as 2008 R2 Enterprise, and Windows is activated), but now clients can't print to printers on our print server, printers directly configured on the terminal server, or redirected printers through the clients.

    PrintService shows error 602:

    "The print spooler failed to reopen an existing printer connection because it could not read the configuration information from the registry key $SID\Printers\Connections\,,$SERVER,$PRINTER. This can occur if the key name or values are malformed or missing."

    Is it possible that something went awry with the DISM process? I may attempt a downgrade from Enteprise to Standard in an attempt to see if the problem is rectified - having no printing available from our terminal server is obviously quite disruptive (particularly since I lobbied to put all of our resource-heavy software on the TS to save on hardware costs and so forth).

    Any help, advice, or information would be greatly appreciated.



    EDIT: I should mention that we have printers from three different manufacturers - HP, Konica Minolta, and Brother. All have the same error. Additionally, the problems with printing began the morning after I performed the DISM upgrade.
    • Edited by Gaz.S Tuesday, December 13, 2011 2:40 AM Additional information
    Tuesday, December 13, 2011 2:13 AM


  • Hi,


    You can restart the spooler service on both the client and Server.


    Restart the print spooler, using the following procedure.

    Warning: Restarting the print spooler causes all print jobs to be restarted. Additionally, you might need to reset or turn off and then back on some printers after restarting the print spooler. On an active print server, perform this procedure outside of normal business hours or during scheduled maintenance time, if possible. Before performing this procedure, take all printers offline and wait for all print jobs to be completed, or pause all printers and wait for all Active print jobs to be completed.

    1. In the Administrative Tools folder, open the Services snap-in.
    2. Locate the Print Spooler service in the list of services, and confirm that its status is Started. If its status is not Started, select the service and then click Start on the Action menu.

    Note: You can also do this from an elevated Command Prompt window by typing the following command: net stop spooler && net start spooler

    In some instances, you might receive Error 1068  "The dependency service or group failed to start"  when attempting to start the Print Spooler service. This can happen if the Print Spooler service relies on other services that are not running. To resolve this issue, use the following procedure:

    1. In the Services snap-in, right-click Print Spooler and then click Properties.
    2. Click the Dependencies tab. The first box lists all of the system services that must be running for Print Spooler service to start. These are the dependencies.
    3. Make a note of each service, click OK, and then start each service that the Print Spooler service depends on, if the service is not already started. If a particular service is not already started, right-click it, click Properties, and then confirm that the Startup type is Automatic.


    Please also refer to the following thread.

    Printer Errors on new Server 2008 R2 Remote Desktop Server






    Dollar Wang

    Forum Support

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


    Technology changes life……

    Wednesday, December 14, 2011 8:35 AM