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

View products that this article applies to.

This article was previously published under Q268065

Expand all | Collapse all

Problem description

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 resemble 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.

To have us fix this problem for you, go to the "Fix it for me" section. To fix this problem yourself, go to the "Let me fix it myself" section.

Back to the top

Fix it for me

To fix this problem automatically, click the Fix it button or link. Click Run in the File Download dialog box, and then follow the steps in the Fix it wizard.

Fix this problem

Collapse this tableExpand this table

Note

This automatic fix works for all languages. However, for some languages, the wizard text may be in English.

Collapse this tableExpand this table

Note

If you are not on the computer that has the problem, save the automatic fix to a flash drive or to a CD, and then run it on the computer that has the problem.

Next, go to the "Did this fix the problem?" section.

Back to the top

Let me fix it myself

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 (http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in Windows

To resolve this issue yourself, 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:
1. Click Start, click Run, type TSCC.MSC, and then click OK.
2. Click Connections, and then double-click RDP-Tcp.
3. Click the Client Settings tab.
4. 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:
1. Click Start, click Run, type regedit, and then click OK.
2. Locate the following registry subkey:
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\Wds\rdpwd
3. On the Edit menu, point to New, and then click DWORD value.
4. Type fEnablePrintRDR, and then press ENTER.
5. Double-click fEnablePrintRDR, in the Value data box, type 1, and then click OK.
  
  Note Setting fEnablePrintRDR to 0 (disabled) will also disable client drive mappings.

Back to the top

Did this fix the problem?

Check whether the problem is fixed. If the problem is fixed, you are finished with this article. If the problem is not fixed, you can contact support (http://support.microsoft.com/contactus) .
We would appreciate your feedback. To provide feedback or to report any issues with this solution, please leave a comment on the "Fix it for me (http://blogs.technet.com/fixit4me/) " blog or send us an e-mail (mailto:fixit4me@microsoft.com?Subject=KB268065 - Printer redirection for RDP 2003 Terminal Server side) message.

Back to the top

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.

Back to the top