Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
RDP not accessible after Service Pack upgrade - Windows Server 2008 R2 Enterprise

Answered RDP not accessible after Service Pack upgrade - Windows Server 2008 R2 Enterprise

  • Thursday, April 19, 2012 3:01 PM
     
     
    Sign In to Vote
    0

    Hi,

    I have a Windows Server 2008 R2 Enterprise. I just recently applied Service Pack 1 on this machine. After the upgrade, the Remote Desktop of the machine is not accessible. I would like to stress the point that, RDP was accessible after the upgrade, on the very same day. But, next day when I tried, the RDP request is getting crashed. I have checked that the Remote Desktop Services is Started. After that, when I tried to take the RDP of the machine, I could get to the machine initially. But, after I type the Username and password, the RDP literally crashes. Please note that I had entered the username and password inside the machine. Not in the first credential box which we get from the local machine.

    Also, after the crash, the service 'Remote Desktop Service' will be in stopped state. We need to manually restart the service from the machine. Kindly note that, this is a virtual machine in vmware ESX.

    The following entry is logged in the event viewer also.

    Log Name:      System
    Source:        Service Control Manager
    Date:          4/19/2012 5:49:11 PM
    Event ID:      7034
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      NOCMETPLSCE.forest.com
    Description:
    The Remote Desktop Services service terminated unexpectedly.  It has done this 11 time(s).
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
        <EventID Qualifiers="49152">7034</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8080000000000000</Keywords>
        <TimeCreated SystemTime="2012-04-19T12:19:11.499934800Z" />
        <EventRecordID>8005</EventRecordID>
        <Correlation />
        <Execution ProcessID="528" ThreadID="4872" />
        <Channel>System</Channel>
        <Computer>NOCMETPLSCE.forest.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="param1">Remote Desktop Services</Data>
        <Data Name="param2">11</Data>
      </EventData>
    </Event>

    I would really appreciate if someone can tell whether similar issues were faced before itself. Any help is really appreciated.

    Thanks,

    Tom

     

All Replies

  • Thursday, April 19, 2012 4:20 PM
    Moderator
     
     Answered
    Sign In to Vote
    3

    You cannot vote on your own postHi,

    I have seen this occur.  I recommend you open Control Panel -- Windows Update, click Check for updates, and then install all important updates.  After restarting please test to see if the issue has been solved.  If not, I recommend you first remove KB2667402 and KB2621440, restart, then check for updates again and re-install them (2621440 & 2667402).

    In the specific case I saw 2621440 was installed to a 2008 R2 RTM, then SP1, RDP crashing, then installing 2667402 fixed it.  In other reported cases 2621440 and 2667402 were already installed and installing additional updates and restarting fixed it.

    Please reply back with your results as well as details of which hotfixes/service pack 1 you had installed prior to breaking and then which hotfixes you installed to fix the issue.  This will help narrow down the problem.

    Thanks.

    -TP


     
  • Saturday, April 21, 2012 2:45 PM
     
     
    Sign In to Vote
    0

    Hi,

    Thanks for your reply. I checked and found that the mentioned two updates were installed in the server. I uninstalled the two updates KB2667402 and KB2621440 and restarted. After restart the RDP was working perfectly.

    I had checked and found that the mentioned two updates KB2667402 and KB2621440 were installed in the server. After uninstalling these two updates, I restarted and the issue was resolved. I was able to access the machine using RDP. I had again installed the two updates again and restarted the machine. Now also the machine is accessible remotely using RDP. Also, please note that the Service Pack which was installed in the server was Windows 7 and Windows Server 2008 R2 Service Pack 1 (KB976932).

    If you could please tell why this is acting wierly, it would be great. Anyways, I would like to really appreciate you for the help.

    Regards,

    Tom

     
  • Saturday, April 21, 2012 9:54 PM
     
     
    Sign In to Vote
    1

    Thanks for the information about uninstalling the two updates KB2667402 and KB2621440.

    I had a crazy situation where I switched Windows Server 2008 R2 Updates on, something I often don't bother with because of the potential to turn a working server to mush. After many updates I could log-on using RDP but after a log-off  the next log-on session would fail with a message about not being able to connect, maybe because of a network error. I knew this not to be true because I installed VNC when I started to get problems and that still connected.

    Using VNC after an RDP log-on failure I noticed that the Remote Desktop Service had stopped. I tried changing the log-on to Local System Account and then I tried the local administrator account. Neither worked because I got "Access Denied" for the remote log-in of the Adminsitrator. I went back to NETWORK SERVICE log-on credentials for Remote Desktop Service and that reverted me back to one log-on and then fail.

    So I followed the above advice about updates KB2667402 and KB2621440. I uninstalled KB2667402 first and that required a reboot. I decided to try try an RDP connection and that worked. I logged Off and tried again. It worked. The problem was fixed by the removal of KB2667402 alone.

    I can guess that there is something in the log-off sequence on the server that stops the Remote Desktop Service because if I simply closed the RDP session without logging-off then I could reconnect as many times as I wanted (as long as I didn't Log Off).

    It would be interesting to know why the KB and updates messed-up Remote Desktop.

    Thanks!

     
  • Monday, October 22, 2012 1:27 AM
     
     
    Sign In to Vote
    0

    I too installed sp1 on w2k8 r2 and it broke RDP.

    I simply removed just the one fix (KB2667402) and RDP came back to life.

    Lucky we had HPs iLO on the boxes!

    Cheers

    David Z