Microsoft KB Archive/268065

= Terminal Services event messages 1100 or 1114 in Windows 2000 Server or Windows Server 2003 =

Article ID: 268065

Article Last Modified on 7/23/2007

-

APPLIES TO


 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Datacenter Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)

-



This article was previously published under Q268065



Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry



SYMPTOMS
An event ID 1100 message is logged in the Event Viewer on a Microsoft Windows 2000 Server-based computer, or an event ID 1114 message is logged in the Event Viewer on a Microsoft Windows Server 2003-based computer. The event ID messages may be similar to the following messages: Event Type: Error

Event Source: TermServDevices

Event Category: None

Event ID: 1100

Description: Initialization of Notify Failed.

Event Type: Error

Event Source: TermServDevices

Event Category: None

Event ID: 1114

Description: Error communicating with the Spooler system service. Open the Services snap-in and confirm that the Print Spooler service is running.



CAUSE
This behavior occurs because the spooler service on the server has stopped.



RESOLUTION
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To resolve this issue, try the following methods until the issue is resolved:
 * Start the spooler service on the server.


 * Turn off Windows printer mapping and LPT port mapping for Terminal Services connections. To do this, follow these steps:
 * Click Start, click Run, type TSCC.MSC, and then click OK.
 * Click Connections, and then double-click RDP-Tcp.
 * Click the Client Settings tab.
 * Click to clear the Windows printer mapping check box, click to clear the LPT port mapping check box, and then click OK.

 As a last resort, you can add the fEnablePrintRDR registry entry to delete the error message. To do this, follow these steps:  Click Start, click Run, type regedit, and then click OK. Locate the following registry subkey:

 On the Edit menu, point to New, and then click DWORD value. Type fEnablePrintRDR, and then press ENTER. Double-click fEnablePrintRDR, in the Value data box, type 0, and then click OK.

Note Setting fEnablePrintRDR to 0 (disabled) will also disable client drive mappings.</li></ol> </li></ul>

<div class="moreinformation_section">

MORE INFORMATION
If the registry value is set to 0, Printer Redirection will fail even if the Print Spooler is started on the Terminal Server. In this scenario, no Event IDs are logged to indicate why no printers are being redirected. To enable print redirection, check (or create) the registry value and set the value to 1.

Keywords: kberrmsg kbprb KB268065

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.