none
Event ID 4098 0x80070bc4 No printers were found

    Question

  • I'm deploying printers to Remote Desktop Services sessions using Group Policy Preferences. When a user logs in for the first time all printers are created correctly. Every subsequent login I get the follow event log error for each printer in the GPP.

    Log Name:      Application
    Source:        Group Policy Printers
    Event ID:      4098
    Task Category: (2)
    Level:         Warning
    Keywords:      Classic
    User:          SYSTEM
    Description:
    The user 'Printer-A' preference item in the 'RDS Printers {4B82A841-77B3-457A-87CE-87A73C04F63C}' Group Policy object did not apply because it failed with error code '0x80070bc4 No printers were found.' This error was suppressed.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Group Policy Printers" />
        <EventID Qualifiers="34305">4098</EventID>
        <Level>3</Level>
        <Task>2</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2013-02-14T02:31:14.000000000Z" />
        <EventRecordID>3395</EventRecordID>
        <Channel>Application</Channel>
        <Computer>RDS01.domain.com</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data>user</Data>
        <Data>Printer-A</Data>
        <Data>RDS Printers {4B82A841-77B3-457A-87CE-87A73C04F63C}</Data>
        <Data>0x80070bc4 No printers were found.</Data>
      </EventData>
    </Event>

    Printers still appear to work but I get TONS of these errors.

    DCs are Windows Server 2008 R2 SP1. RDS server is Windows Server 2008 R2 SP1.

    I have found lots of other posts of people having the same issue but never a solid resolution. Below are the various things I have tried.

    • Install KB2748246. Updates win32spl.dll (11/8/2012, v6.1.7601.17994) to (11/8/2012, v6.1.7601.22156). Still get the error.
    • Domain Admins get the error as well.
    • Restarting the spooler, log off, log on, same error.
    • Typing the printer name instead of browsing. Same error. http://www.eversity.nl/blog/2011/02/gpp-event-id-4098-warning-0x80070bc4-no-printers-were-found
    • Disabling Point & Print Restriction. Same error - http://support.microsoft.com/kb/2618460
    • Doesn't matter if the “Action” on the printer is set to Create or Update.
    • Doesn’t matter is there is any ILP or not.
    • Doesn’t matter if group in ILP is typed or browsed.
    • Doesn’t matter is its HP, Canon, or Sharp device.
    • Doesn’t matter if Print Processor is WinPrint/RAW or 3rd party.
    • Doesn’t matter if using FQDN or hostname to the print server.
    • “comp\admin\system\logon\Always wait for the network at computer startup and logon” in base policy. Same error.
    • If I add a new printer it appears to not give the error on any printers that follow it. Must have something to do with the fact that it is installing the new printer so subsequent printers are “refreshed” without issue.
    • Enabling CSE for Printers logging shows similar error.
      Initial Logon (Gets errors)
      2013-02-14 14:46:13.422 [pid=0x3e8,tid=0x14a4] {9A5E9697-9095-436d-A0EE-4D128FDFBCE5}
      2013-02-14 14:46:13.422 [pid=0x3e8,tid=0x14a4] Starting class <SharedPrinter> - Printer-A.
      2013-02-14 14:46:13.422 [pid=0x3e8,tid=0x14a4] Starting filter [AND FilterTerminal].
      2013-02-14 14:46:13.422 [pid=0x3e8,tid=0x14a4] Adding child elements to RSOP.
      2013-02-14 14:46:13.423 [pid=0x3e8,tid=0x14a4] Session: 3
      2013-02-14 14:46:13.423 [pid=0x3e8,tid=0x14a4] Protocol: 2
      2013-02-14 14:46:13.423 [pid=0x3e8,tid=0x14a4] Client Name: COMP1
      2013-02-14 14:46:13.424 [pid=0x3e8,tid=0x14a4] Passed filter [FilterTerminal].
      2013-02-14 14:46:13.424 [pid=0x3e8,tid=0x14a4] Starting filter [OR FilterTerminal].
      2013-02-14 14:46:13.424 [pid=0x3e8,tid=0x14a4] Adding child elements to RSOP.
      2013-02-14 14:46:13.424 [pid=0x3e8,tid=0x14a4] Session: 3
      2013-02-14 14:46:13.424 [pid=0x3e8,tid=0x14a4] Protocol: 2
      2013-02-14 14:46:13.425 [pid=0x3e8,tid=0x14a4] Client Name: COMP1
      2013-02-14 14:46:13.425 [pid=0x3e8,tid=0x14a4] Failed filter [FilterTerminal].
      2013-02-14 14:46:13.425 [pid=0x3e8,tid=0x14a4] Filters passed.
      2013-02-14 14:46:13.425 [pid=0x3e8,tid=0x14a4] Set user security context.
      2013-02-14 14:46:13.425 [pid=0x3e8,tid=0x14a4] Adding child elements to RSOP.
      2013-02-14 14:46:13.920 [pid=0x3e8,tid=0x14a4] Properties handled. [ hr = 0x80070bc4 "No printers were found." ]
      2013-02-14 14:46:13.921 [pid=0x3e8,tid=0x14a4] Set system security context.
      2013-02-14 14:46:13.929 [pid=0x3e8,tid=0x14a4] EVENT : The user 'Printer-A' preference item in the 'RDS Printers {4B82A841-77B3-457A-87CE-87A73C04F63C}' Group Policy object did not apply because it failed with error code '0x80070bc4 No printers were found.'%100790273
      2013-02-14 14:46:13.929 [pid=0x3e8,tid=0x14a4] Error suppressed. [ hr = 0x80070bc4 "No printers were found." ]
      2013-02-14 14:46:13.930 [pid=0x3e8,tid=0x14a4] Completed class <SharedPrinter> - Printer-A.

    • Gpupdate after 2 minutes (No errors)
      2013-02-14 14:47:39.015 [pid=0x3e8,tid=0x1730] {9A5E9697-9095-436d-A0EE-4D128FDFBCE5}
      2013-02-14 14:47:39.015 [pid=0x3e8,tid=0x1730] Starting class <SharedPrinter> - Printer-A.
      2013-02-14 14:47:39.015 [pid=0x3e8,tid=0x1730] Starting filter [AND FilterTerminal].
      2013-02-14 14:47:39.015 [pid=0x3e8,tid=0x1730] Adding child elements to RSOP.
      2013-02-14 14:47:39.015 [pid=0x3e8,tid=0x1730] Session: 3
      2013-02-14 14:47:39.016 [pid=0x3e8,tid=0x1730] Protocol: 2
      2013-02-14 14:47:39.017 [pid=0x3e8,tid=0x1730] Client Name: COMP1
      2013-02-14 14:47:39.017 [pid=0x3e8,tid=0x1730] Passed filter [FilterTerminal].
      2013-02-14 14:47:39.017 [pid=0x3e8,tid=0x1730] Starting filter [OR FilterTerminal].
      2013-02-14 14:47:39.017 [pid=0x3e8,tid=0x1730] Adding child elements to RSOP.
      2013-02-14 14:47:39.017 [pid=0x3e8,tid=0x1730] Session: 3
      2013-02-14 14:47:39.018 [pid=0x3e8,tid=0x1730] Protocol: 2
      2013-02-14 14:47:39.018 [pid=0x3e8,tid=0x1730] Client Name: COMP1
      2013-02-14 14:47:39.018 [pid=0x3e8,tid=0x1730] Failed filter [FilterTerminal].
      2013-02-14 14:47:39.018 [pid=0x3e8,tid=0x1730] Filters passed.
      2013-02-14 14:47:39.019 [pid=0x3e8,tid=0x1730] Set user security context.
      2013-02-14 14:47:39.019 [pid=0x3e8,tid=0x1730] Adding child elements to RSOP.
      2013-02-14 14:47:39.029 [pid=0x3e8,tid=0x1730] Properties handled.
      2013-02-14 14:47:39.029 [pid=0x3e8,tid=0x1730] RunOnce value created [SUCCEEDED(S_FALSE)]
      2013-02-14 14:47:39.029 [pid=0x3e8,tid=0x1730] Handle Children.
      2013-02-14 14:47:39.029 [pid=0x3e8,tid=0x1730] Set system security context.
      2013-02-14 14:47:39.037 [pid=0x3e8,tid=0x1730] EVENT : The user 'Printer-A' preference item in the 'RDS Printers {4B82A841-77B3-457A-87CE-87A73C04F63C}' Group Policy object applied successfully.
      2013-02-14 14:47:39.037 [pid=0x3e8,tid=0x1730] Completed class <SharedPrinter> - Printer-A.

    Any thoughts?


    Patrick Hoban
    http://patrickhoban.wordpress.com

    Thursday, February 14, 2013 10:34 PM

All replies

  • Hi Patrick,
     
    Thank you for your question.

    I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
     
    Thank you for your understanding and support.

    Regards,

    Cicely Feng

    ---------------------------------------------------

    TechNet Subscriber Support

    If you are TechNet Subscription  user and have any feedback on our support quality, please send your feedback here .

    Monday, February 18, 2013 2:34 AM
  • according to the CSE debug log, the issue caused by the client (TS server) cannot found the shared printer temporarily.

    Please check if the shared printer is always available.

    and then please try clean boot (Disable all 3rd party applications and services).

    if it still does not work, we may need to capture memory dump for analysis. if so, it is hard to troubleshoot by forum support, you need to open a case.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Tuesday, February 19, 2013 2:08 PM
  • one more thing, please try "Run in logged-in user security context"


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Thursday, February 21, 2013 11:02 AM
  • I do have all printers objects set "Run in logged-in user security context"

    Patrick Hoban
    http://patrickhoban.wordpress.com

    Friday, February 22, 2013 7:43 PM
  • i suggest you capture network trace when apply GP

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Saturday, February 23, 2013 8:48 AM
  • I am having this exact same issue on my Citrix server. Printers all work fine, but my event log is spammed with these errors. Did anyone ever find a resolution?
    Sunday, July 28, 2013 3:34 PM
  • I have the same issue as you on my Citrix servers. First logon with New profile has no errors, but after that.. every single time. I hope someone has any clever ideas :)

    .:TN

    Friday, August 30, 2013 6:37 AM
  • Toby N, did you ever find a solution for this issue? I've been experiencing the same problem in my Citrix VDI environment.
    Friday, October 18, 2013 10:40 PM
  • Hi,

    we have exactly the same Problems in our Citrix VDI in a box and physical Environment.
    The logon to the Domain takes so Long that you have to reenter the Password three or more times.
    When you look then to the enventlog you can find this Error.

    And by every logon it seams to be other Printers that make this error.

    Only by Windows XP Clients we do not have this Problem but by Windows 7 and Windows 8 Clients it is actually and we need a solution for the Problem.

    I also hat set the shareing of the Printers to no an after savint again to yes but it does not take Long time and i had again the Problem.



    Yours
    Stefan

    Friday, November 01, 2013 6:18 PM
  • Also experiencing this exact issue with a Windows Server 2008 R2 RDP environment. Any thoughts?
    Wednesday, November 20, 2013 4:17 PM