Event ID - 1103

Event Id1103
SourceMicrosoft-Windows-TerminalServices-Printers
DescriptionAn internal communication error occurred. Redirected printing will no longer function for a single user session. Check the status of the Terminal Services Device Redirector in the System folder of Device Manager.
Event InformationAccording to Microsoft :
Cause :
This event is logged when an internal communication error occurred.
Resolution :
Enable the Terminal Server Device Redirector or fix Rdpdr issues
To resolve this issue, enable the Terminal Server Device Redirector. If you cannot enable the Terminal Server Device Redirector, replace the existing Rdpdr.sys file. If the problem persists, replace the RDPDR registry subkey.
To perform these tasks, refer to the following sections.
Enable the Terminal Server Device Redirector
To perform this procedure on the terminal server, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To enable the Terminal Server Device Redirector on the terminal server:
  1. On the terminal server, open Device Manager. To open Device Manager, click Start, click Run, type devmgmt.msc, and then click OK.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. Expand System devices.
  4. Right-click Terminal Server Device Redirector, and then click Properties.
  5. On the Driver tab, click Enable.
  6. Restart the computer so that the changes take effect.
  7. Start Device Manager, and then view the properties of the Terminal Server Device Redirector. In Device status, ensure that the message This device is working properly appears.
Replace the existing Rdpdr.sys fileIf the Rdpdr.sys file is missing or corrupted, copy the Rdpdr.sys file from the Windows Server 2008 installation media into the %systemroot%\system32\drivers folder on the terminal server (where %systemroot% is the folder in which the operating system is installed, which is, by default, c:\windows).
To perform this procedure on the terminal server, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To copy the Rdpdr.sys file:
  1. Insert the installation media.
  2. On the terminal server, click Start, click Run, type expand source destination, where source is the path to the file that you want to expand on the installation disk, and destination is the path to the location where you want to save the file, and then click OK.
  3. Restart the terminal server.
Replace the RDPDR registry subkey
If copying the Rdpdr.sys file does not resolve the problem, the RDPDR registry subkey may be corrupted.
To resolve this issue, use either of the following methods.
To perform these procedures, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
Method one
To replace the RDPDR registry subkey:
Caution : Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.
  1. On a working terminal server, open Registry Editor. To open Registry Editor, click Start, click Run, type regedit, and then click OK
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. Locate the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\RDPDR registry subkey.
  4. Right-click RDPDR, click Export, and then save the .reg file. Copy the .reg file to the terminal server that is having the problem.
  5. On the terminal server that is having the problem, double-click the .reg file that you created in the previous step.
  6. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  7. Click Yes, and then click OK.
  8. After the registry subkey is imported, start Device Manager, expand System devices, and then click Terminal Server Device Redirector.
  9. On the Action menu, click Scan for hardware changes.
  10. Right-click Terminal Server Device Redirector, and then click Properties. In Device status, make sure that the message This device is working properly appears.
    Note : You might have to restart the terminal server for the changes to take effect.
If this method does not work, uninstall and then reinstall the Terminal Server role service.
Method two
Uninstall and then reinstall the Terminal Server role service by using Server Manager.
Important : If you uninstall and then reinstall the Terminal Server role service, you may have to reinstall existing applications.
Verify :
To verify that printer redirection is working properly, establish a remote session with the terminal server and check that the redirected printer is available and is functioning as expected.
Reference LinksEvent ID 1103 from Source Microsoft-Windows-TerminalServices-Printers

Catch threats immediately

We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.

See what we caught

Did this information help you to resolve the problem?

Yes: My problem was resolved.
No: The information was not helpful / Partially helpful.
 Refresh