none
Error: Remote Desktop Connection has stopped working

    Question

  • Remote Desktop Connection on a HP dv9000 Vista Ultimate 64 bit w SP3 laptop keeps crashing 10-15 seconds after logging into a Windows Terminal Server 2008 w SP1 with the above message.  The entry in the laptop's Application Log is:

    Event 1000: Faulting application mstsc.exe, version 6.0.6002.18005, time stamp 0x49e02f4f, faulting module ntdll.dll, version 6.0.6002.18005, time stamp 0x49e0421d, exception code 0xc0000374, fault offset 0x00000000000aef37, process id 0xccc, application start time 0x01ca03157ecc6e59.

    Troubleshooting steps already taken:
    1.  When I uncheck 'Printers' under Local Devices and Resources no error occurs and I can log in normally.  This is a terrible work around since I need to be able to print remotely.
    2.  I tried using msconfig to disable all non-microsoft services and all startup programs.  No change.
    3.  The error occurs whether I try Remote Desktop Connection or TS Web Access, with 'Printers' checked.
    4.  I can connect to a Windows Terminal Server 2003 with no problem, even with 'Printers' checked.

    Anyone have a clue what's going on and how to troubleshoot and/or fix the issue?

    Monday, July 13, 2009 2:18 AM

All replies

  • Monday, July 13, 2009 8:56 AM
    Moderator
  • I looked in Control Panel / Programs and Features, and found that .NET 3.5 SP1 was installed back in December 2008.

    Any other ideas?
    Tuesday, July 14, 2009 7:29 AM
  • is it the session crashing out or is the computer itself crashing?  Have you tried using a native print driver to see if the error stops?
    Tuesday, July 14, 2009 11:44 AM
    Moderator
  • Remote Desktop Connection on a HP dv9000 Vista Ultimate 64 bit w SP3 laptop keeps crashing 10-15 seconds after logging into a Windows Terminal Server 2008 w SP1 with the above message.  The entry in the laptop's Application Log is:

    Event 1000: Faulting application mstsc.exe, version 6.0.6002.18005, time stamp 0x49e02f4f, faulting module ntdll.dll, version 6.0.6002.18005, time stamp 0x49e0421d, exception code 0xc0000374, fault offset 0x00000000000aef37, process id 0xccc, application start time 0x01ca03157ecc6e59.

    Troubleshooting steps already taken:
    1.  When I uncheck 'Printers' under Local Devices and Resources no error occurs and I can log in normally.  This is a terrible work around since I need to be able to print remotely.
    2.  I tried using msconfig to disable all non-microsoft services and all startup programs.  No change.
    3.  The error occurs whether I try Remote Desktop Connection or TS Web Access, with 'Printers' checked.
    4.  I can connect to a Windows Terminal Server 2003 with no problem, even with 'Printers' checked.

    Anyone have a clue what's going on and how to troubleshoot and/or fix the issue?


    Any fancy printing stuff or Printer drivers you have installed on TS Server?
    Does the users have permissions for the printers he is getting connected to?
    Have you enabled or disabled Easy Print.
    Also You mean Vista SP2 correct?
    Citrix Technology Professional, PubForum.net Founder, LinkedIn, Free TS Training in Europe! Love Microsoft &its people to bits!
    Tuesday, July 14, 2009 12:00 PM
    Moderator
  • I just ran into this issue on HP Elitebook 8530p with Windows 7 64 bit fully updated.

    I followed your troubleshooting tips and sure enough it was a bad printer driver I installed last week (HP Laserjet 1022N). After removing the printer, the Remote Desktop Connection immediately began functioning normally.

    If anyone else runs into this issue I would suggest the following steps:
    1. Disable the "printers" check box on your Remote Desktop Connection by navigating to Options>Local Resources>Local Devices and resources. Then try to connect.
    2. If connection is successful with the printers disable, start removing printers on your local machine one by one in order to figure out which printer is causing the problem.
    3. Once you have figured out the problem printer driver, reinstall with a different driver.

    • Proposed as answer by RDP-9th Monday, October 25, 2010 10:21 PM
    Monday, May 10, 2010 2:50 PM
  • I try to follow the last step to remove my printer driver, then my remote desktop connection begin to work.

    Thursday, May 26, 2016 6:58 AM