Sign in
 
Home200820032000LibraryForums
Windows Server TechCenter > Windows Server Forums > Print/Fax > Client Side Rendering Spooler Warning Event 4
Ask a questionAsk a question
Search Forums:
 

AnswerClient Side Rendering Spooler Warning Event 4

  • Tuesday, May 05, 2009 10:22 PMSandy Wood Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    I've noticed a slew of events on a few of my Windows 2008 Servers that look just like this:

    Type: Warning
    Source: Client Side Rendering Spooler
    Event ID: 4
    Event Time: 5/5/2009 1:18:55 PM
    User: n/a
    Computer: mycomputer.domain.com
    Description:
    The print spooler failed to reopen an existing printer connection because it could not read the configuration information from the registry key S-1-5-18\Printers\Connections. The print spooler could not open the registry key. This can occur if the registry key is corrupt or missing, or if the registry recently became unavailable.

    They show up in small amounts on our Windows 2008 print server but in larger amounts on our main file server that hosts our user's home drives. We redirect user's folders to their home drives also.

    In reading about Client Side Rendering Spooler technology, it appears that this renders the print job on the client-side which sounds like it may use a user's redirected profile folders. Could this be what's giving this Warning?

    Orange County District Attorney
     

Answers

  • Monday, May 11, 2009 7:31 AMDavid Shen Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote

    Hi Sandy,

     

    Thanks for your reply.

     

    Based on my research, another possible reason of this event could be that the registry key HKEY_USERS\S-1-5-18\Printers\Connections was missing or corrupted on the problematic server. Thus, the print spooler could not open the registry key on the problematic server, therefore the system logged these events several times with Event ID 4.

     

    To resolve this issue, we will modify or create the necessary registry values.

     

    Please refer to the following action plan.

     

    Action Plan:

     

    1. Logon to the problematic server with Administrator credentials.

     

    2. Launch the Registry Editor by running "regedit" (without quotation marks)

     

    3. Expand and locate the node HKEY_USERS\S-1-5-18\Printers

     

    4. Right click and create a new key named "Connections"(without quotation marks)

     

    5. Right click on the newly-created "Connections" key and select "Permissions…"

     

    6. Verify that the SYSTEM account has full control permissions.

     

    7. Then restart the problematic server.

     

    8. Please monitor the problematic server with the event viewer to see if the event ID 4 is resolved.

     

    Please let us know the result at your earliest convenience.

     

    This posting is provided "AS IS" with no warranties, and confers no rights.
    • Proposed As Answer byDavid Shen Thursday, May 14, 2009 2:19 AM
    • Marked As Answer byDavid Shen Friday, May 15, 2009 10:15 AM
    • Edited byDavid Shen Monday, May 11, 2009 8:57 AMedit
    •  
     
  • Monday, May 18, 2009 3:17 AMDavid Shen Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote

    Hello Sandy,

     

    Thanks for your response.

     

    I'm glad to hear that you have resolved the issue. You are welcome to TechNet forum for further questions.

    This posting is provided "AS IS" with no warranties, and confers no rights.
    • Marked As Answer byDavid Shen Monday, May 18, 2009 3:17 AM
    •  
     

All Replies

  • Wednesday, May 06, 2009 10:18 AMDavid Shen Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Hello Sandy,

     

    Thank you for posting here.

     

    Based on my research, the Event ID 4 can be occur when we have changed Group Policy object to enable the following setting on Print Server and Domain controller.

     

    Computer Configuration/Administrative Templates/Printers/Allow Print Spooler to accept client connections

     

    Action plan:

     

    1. Please check if you have link any GPO to the problematic printer server and the main file server, which configured with the above Group Policy Settings.

     

    2. To resolve this issue, you may have an administrator to add the user in the Local Users and Groups snap-in by using the same username and password that you use on the server. And then please disable the GPO settings.

     

    Please note: the spooler service need to be restarted for changes to this policy to take effect.

     

    Hope the information will be helpful.

    This posting is provided "AS IS" with no warranties, and confers no rights.
     
  • Friday, May 08, 2009 10:39 AMDavid Shen Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Hello Sandy,


    I want to see if the information provided was helpful. Please keep us posted on your progress and let us know if you have any additional questions or concerns.

     

    We are looking forward to your response. 

    This posting is provided "AS IS" with no warranties, and confers no rights.
     
  • Friday, May 08, 2009 2:21 PMSandy Wood Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hello David,

    Thanks for your response to my issue. I checked our GPOs for my servers and found that we are not pushing any of the changes you mentioned to any of our servers. The only setting that comes close is a setting to Pre-populate printer search location text.

    Can you think of any other reason we might be seeing these events?
    Orange County District Attorney
     
  • Monday, May 11, 2009 7:31 AMDavid Shen Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote

    Hi Sandy,

     

    Thanks for your reply.

     

    Based on my research, another possible reason of this event could be that the registry key HKEY_USERS\S-1-5-18\Printers\Connections was missing or corrupted on the problematic server. Thus, the print spooler could not open the registry key on the problematic server, therefore the system logged these events several times with Event ID 4.

     

    To resolve this issue, we will modify or create the necessary registry values.

     

    Please refer to the following action plan.

     

    Action Plan:

     

    1. Logon to the problematic server with Administrator credentials.

     

    2. Launch the Registry Editor by running "regedit" (without quotation marks)

     

    3. Expand and locate the node HKEY_USERS\S-1-5-18\Printers

     

    4. Right click and create a new key named "Connections"(without quotation marks)

     

    5. Right click on the newly-created "Connections" key and select "Permissions…"

     

    6. Verify that the SYSTEM account has full control permissions.

     

    7. Then restart the problematic server.

     

    8. Please monitor the problematic server with the event viewer to see if the event ID 4 is resolved.

     

    Please let us know the result at your earliest convenience.

     

    This posting is provided "AS IS" with no warranties, and confers no rights.
    • Proposed As Answer byDavid Shen Thursday, May 14, 2009 2:19 AM
    • Marked As Answer byDavid Shen Friday, May 15, 2009 10:15 AM
    • Edited byDavid Shen Monday, May 11, 2009 8:57 AMedit
    •  
     
  • Wednesday, May 13, 2009 11:07 AMDavid Shen Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Hi Sandy,

    I haven't heard back from you yet. I am writing to see how everything is going. I would appreciate if you could get back to me at your earliest convenience.

     

    If you have any questions or concerns related to this issue, please drop me a note. I look forward to hearing from you.

     

    This posting is provided "AS IS" with no warranties, and confers no rights.
     
  • Wednesday, May 13, 2009 2:40 PMSandy Wood Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Sorry for the delay in getting back - I haven't been getting the alerts. Let me try your registry fix and I'll post right back.
    Orange County District Attorney
     
  • Wednesday, May 13, 2009 2:48 PMSandy Wood Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Just added the Connections key (it wasn't there) and rebooted the system. So far no errors! This might be the fix! I'll keep my eye on it and see how we do.

    Thanks again.
    Orange County District Attorney
     
  • Thursday, May 14, 2009 3:50 AMDavid Shen Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Hi Sandy,

     

    Thanks for the reply.

     

    I'm glad that the suggestion was helpful for you.

     

    I believe that it is beneficial to monitor this issue for one or two more days. If the original symptoms occur again or you require further assistance during this period of time, please let me know.

     

    I appreciate your time and effort.

     

    Thank you.

    This posting is provided "AS IS" with no warranties, and confers no rights.
     
  • Friday, May 15, 2009 3:23 PMSandy Wood Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Hello David,

    Just a note that I checked my test server and your suggestion fixed my issue. Adding the key was the answer. Thanks again.

    Orange County District Attorney
     
  • Monday, May 18, 2009 3:17 AMDavid Shen Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote

    Hello Sandy,

     

    Thanks for your response.

     

    I'm glad to hear that you have resolved the issue. You are welcome to TechNet forum for further questions.

    This posting is provided "AS IS" with no warranties, and confers no rights.
    • Marked As Answer byDavid Shen Monday, May 18, 2009 3:17 AM
    •