Can't RDP From Windows 7 to Server 2008 R2 SP1

Hello,
We have a server 2008 R2 SP1 with all the latest updates installed as of today (11/12/2014) that runs terminal services.
We started upgrading our office computers to windows 7 x64 and now unable to RDP into the server. They were able to RDP for a few days and now are unable. 
Once you hit connect, it asks for a username & password, and then it says configuring remote connection and after about 15-30 seconds it just says can not connect to remote computer. 
I am able to RDP from windows 7 into 2003 servers. 
Windows XP Computers can RDP just fine. 
I went through all the articles that had the updates that needed to be removed/reinstalled for RDP to work and none of them fixed the issue. 
This has been going on since Monday 11/10/2014 
Any advice or assistance is greatly appreciated.

SP1 Is installed. as well as updated as of 11/12/2104
Here is the only thing that shows up in the logs on the server side:
Attempt to send connect message to Windows video subsystem failed. The relevant status code was 0xd0000001.
System
Provider
[ Name]
Microsoft-Windows-TerminalServices-LocalSessionManager
[ Guid]
{5D896912-022D-40AA-A3A8-4FA5515C76D7}
EventID
20
Version
0
Level
2
Task
0
Opcode
0
Keywords
0x1000000000000000
TimeCreated
[ SystemTime]
2014-11-12T23:47:45.532187000Z
EventRecordID
19249
Correlation
Execution
[ ProcessID]
644
[ ThreadID]
1624
Channel
Microsoft-Windows-TerminalServices-LocalSessionManager/Operational
Computer
LAXCA-PD-TS01.XXXXXXXXXXXXXXX.local
Security
[ UserID]
S-1-5-18
UserData
EventXML
messageName
connect
errorCode
0xd0000001

Similar Messages

  • Move Virtual Machine from Hyper-V Server 2008 R2 SP1 to Hyper-V Server 2012 fails with Error 2901

    I have six Hyper-V 2008 R2 SP1 servers and two Hyper-V 2012 servers. I am running SCVMM 2012 SP1. I am trying to use "move virtual machine" from within SCVMM to move VMs from a 2008 host to a 2012 host. I have tried different VMs on different hosts
    and they all fail with this error:
    ==========
    Error (2901)
    The operation did not complete successfully because of a parameter or call sequence that is not valid.
    The parameter is incorrect (0x80070057)
    Recommended Action
    Ensure that the parameters are valid, and then try the operation again.
    ==========
    I have successfully created a VM on one of the 2012 hosts and moved it to the other 2012 hosts.  I can move VMs from 2008 host to 2008 host.  I just cannot move VMs from 2008 host to 2012 host.
    Does SCVMM 2012 SP1 not support moving VMs from Hyper-V 2008 to Hyper-V 2012?

    Hello Kevin,
    Have you got an resolution yet ? Do you have latest update roll up pack applied to SCVMM 2012 SP1?
    With SCVMM 2012 SP1  " Running VMs (Live Migartion) and VMs which are in Saved state or having checkpoints can not be migrated from 2008R2 host to 2012 Host " 
    above was fixed in SCVMM 2012 Update Roll up 1
    Apart this please check the approx. size of data (VHDs) which will get transferred over the network , If you have large files chances are more to get such errors.
    Thanks
    ~NY

  • Can't RDP to Windows Home Server 2011

    I saw a post from several years ago that said Verizon's TOS doesn't allow servers.  Couldn't find anything recent so was wondering if it still applies now that WHS 2011 and other NAS have come out targeted for home users (read...low bandwidth requirement).  I can access the server remotely via https:// to browse,upload, and stream content, but can't remotely login to administer.  Going crazy trying to set up port forwarding on my Actiontec MI424WR router for port 4125.  Any help/ideas?
    Solved!
    Go to Solution.

    Unless you changed it, RDP uses TCP port 3389. In the registry you can actually change the port if you want.  I have 2 machines, one uses 3389 while the other was set to 3390.  I can access either of them easily.
    In either scenario you need to make sure the Windows firewall is opened...

  • Upgrade from Windows Home Server 2011

    Even though Windows Server 2012 Essentials is being mentioned as a replacement for Windows Home Server 2011, there doesn't seem to be any documentation or mention of can you upgrade from Windows Home Server 2011 to Windows Server 2012 Essentials?
    Will this work with the beta download and will we then be able to upgrade this version to the RC and/or release version?
    As you may guess I have a Windows Home Server 2011 and am interested in looking at Windows Server 2012 Essentials to see what it offers me. The storage spaces sounds exactly what I want to replace the drive extender on the previous home server version. The
    problem is that I don't mind sacrificing my present server box by installing the beta but it would be nice if it actually retained what settings it could via an upgrade option, which I could then have a chance of using with a proper release version.
     

    Just clarifying about the 'upgrade path' and 32b vs 64b.
    Yes, no in-place upgrade. However, one could theorise about some form of 'migration' being possible, where the list of users, the content of your shares, the current backups, would be 'moved' from old box to new.
    I was in fact pretty sure no such process existed. (Wouldn't it be neat though? AND in future _at least theoretically_ possible, using processes similar to SBS AD migration.)
    From this perspective putting the new box onto the network is similar to replacing WHSv1 with WHS11, in that nothing is carried over. No gain, but no lesser. Working on currently available information.
    The later comment about the work laptop is, TTBOMK, a resounding 'NO'. When attempting to join a member of another AD the 'connect' process stated 'You must 1st remove the PC from the other AD'. I haven't tested this extensively but believe that PC's _capable_
    of operating in an AD (Pro, vs Home, versions) will be made members of the WS12E AD. It is only PC's that do not have 'domain join' capability that are left in workgroup mode.
    TTBOMK, AFAICS, so far, etc...

  • Retrieve SQL Agent Process ID via T-SQL below SQL Server 2008 R2 SP1.

    Dear Folks,
    I have to retrieve the process ID of SQL Agent (as shown in Configuration Manager) via T-SQL Script. It can be easily retrieved in SQL Server 2008 R2 SP1 or above using 'sys.dm_server_services'
    DMV. But I have to retrieve it in SQL Server 2008 R2 RTM and above DMV was not introduced in it. Using XP_cmdshell 'tasklist' is useless as well, as it doesn't reflect the instance specific details of SQLAgent process. Please Suggest the solution. Thanks in
    advance. :)   
    Pranshul Gupta

    Dear Folks,
    I have to retrieve the process ID of SQL Agent (as shown in Configuration Manager) via T-SQL Script. It can be easily retrieved in SQL Server 2008 R2 SP1 or above using 'sys.dm_exec_request' DMV.
    But I have to retrieve it in SQL Server 2008 R2 RTM and above DMV was not introduced in it.
    Using XP_cmdshell 'tasklist' is useless as well, as it doesn't reflect the instance specific details of SQLAgent process. Please Suggest the solution. Thanks in advance. :)   
    Pranshul Gupta
    Hello,
    Sys.dm_exec_requests DMV was introduced from sql server 2005.See this link
    http://technet.microsoft.com/en-us/library/ms177648(v=sql.90).aspx
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • Windows Server 2008 R2 SP1 RDS hang and stop responding new rdp session. Already connected session also hang as well

    We have a Windows Server 2008 R2 SP1 RDS supporting many ThinClients, mostly using a mandatory profile on a Windows 2003 R2 AD environment
    at the moment of the hang what we experienced was:
    New RDP sessions got stucked in the legend "Iniciando" (we have the spanish MUI).
    Systems Events shows a lot of Warnings:
    The Group Policy Client Side Extension Group Policy Shortcuts may have caused the Group Policy Service to terminate unexpectedly. To prevent further failures in the Group Policy
    Service, this extension has been temporarily disabled until after the next system restart. Group Policy settings managed by this extension may no longer be enforced until the system is restarted. The vendor of this extension should be contacted if this issue
    recurs.
    and after that a lot of this errors:
    A timeout (30000 milliseconds) was reached while waiting for a transaction response from the CryptSvc service.
    A timeout (30000 milliseconds) was reached while waiting for a transaction response from the NlaSvc service.
    The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client.
    timeout (30000 milliseconds) was reached while waiting for a transaction response from the Schedule service.
    A timeout (30000 milliseconds) was reached while waiting for a transaction response from the gpsvc service.
    A timeout (30000 milliseconds) was reached while waiting for a transaction response from the BITS service.
    A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SessionEnv service.
    A timeout (30000 milliseconds) was reached while waiting for a transaction response from the ShellHWDetection service.
    A timeout (30000 milliseconds) was reached while waiting for a transaction response from the CertPropSvc service.
    A timeout (30000 milliseconds) was reached while waiting for a transaction response from the IKEEXT service.
    A timeout (30000 milliseconds) was reached while waiting for a transaction response from the iphlpsvc service.
    A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SessionEnv service.
    A timeout (30000 milliseconds) was reached while waiting for a transaction response from the iphlpsvc service.
    During the problem we ping DC and Network Share where Profile and Document Redirection resides and they were working OK (we also did a
    \\server\HomeUsers and we reached it without problem)
    Only reseting the server worked, Any Ideas of what could be causing this ?? Best Regards
    Federico Giampietri Latamsupport IT Infrastructure Services

    Hi Clarence,
    Today we experienced the problem again,
    Users can’t login to RDS, but now they got stucked at “"Please wait for the Group Policy client”;
    System log events recorded the following errors again:
    timeout (30000 milliseconds) was reached while waiting for a transaction response from the Schedule service.
    timeout (30000 milliseconds) was reached while waiting for a transaction response from the sessionenv service.
    timeout (30000 milliseconds) was reached while waiting for a transaction response from the ShellHWDetection service.
    timeout (30000 milliseconds) was reached while waiting for a transaction response from the Wuauserv service.
    timeout (30000 milliseconds) was reached while waiting for a transaction response from the BITS service.
    timeout (30000 milliseconds) was reached while waiting for a transaction response from the CertPropSvc service.
    What path do you suggest to investigate further?
    Thanks a lot!
    Federico Giampietri Latamsupport IT Infrastructure Services

  • Can't browse anything in Windows Server 2008 R2 SP1

    Hi,
    Need your help and expertise. Suddenly, i can't browse anything in my Windows Server 2008 R2 SP1 with IIS7. I tried already three(3) different browsers (IE8, Firefox & Chrome). Before, i can browse (using IE8 & Firefox) both private (LAN) and public
    (Internet) websites be it via ip address or domain name without any issues whatsoever. In fact, i can't even access the local http website (status in IIS7 is Started) my server is hosting.
    The only problem occured just yesterday in my server was drive C: got disk full but i was still able to access via RDP the server and free up disk space of 80GB. I tried already to clear the browsser history,
    disable the add-ons of IE8 and turn-off the firewall. I have NOT tried to reset  IE8 settings, disable  third-party
    program or service and startup in msconfig as it require reboot of the server. I'm apprehensive
    to do things i mentioned i have not tried since the server is up and running for 919 days and 17hours. It is why i tried other browsers that i even installed Chrome just to test and troubleshoot the browsing problem.
    Thanks
    iootoo

    Maybe this one helps.
    https://social.technet.microsoft.com/Forums/scriptcenter/en-US/8ca76e02-c80c-4648-8983-33b5715adb41/no-microsoftcom-server-reachable-ie-address-is-not-valid-changes-to-http
    or possibly ask over here.
    https://social.technet.microsoft.com/Forums/scriptcenter/en-US/home?forum=ieitprocurrentver
     Also check IE|Tools|Internet Options|Connection|LAN  SETTINGS
    is correct and possibly Automatically Detect
    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]
    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

  • Upgrade from Windows Server 2008 R2 SP1 to Windows Server 2012 R2

    Hi, I was trying to setup a new DC for our company, originally it's DC is Windows Server 2003 SP2, we decided not tomigrate it and instead build a new one from scratch which is Windows Server 2008 R2 SP1. I was able to set it up, perform windows updates,
    added roles, perform Domains and Trusts, etc
    When suddenly our global standards shifted to Windows Server 2012 R2, so instead of creating another server from scratch, this is the time to upgrade from 2k8 to 2K12 R2, besides the MAPtool which I've downloaded to check for prerequisites, etc, are there
    other things I need to be aware of? backups? etc.
    Regards,
    Jeff
     

    Hi,
    You can
    insert Windows Server 2012 R2 DVD into the DVD-ROM and click onRun
    Setup.exe. You can refer to the link below:
    Windows Server 2008R2 in-place upgrade to Windows Server 2012/2012R2
    Note:
    Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure
    that you completely understand the risk before retrieving any suggestions from the above link.
    Best regards,
    Susie

  • Steps to move application DB( MSSql) from windows 2003 server to windows 2008 server.

    Hi All,
    I am new to DB. We need to move application's MSSQL DB(Currently used DB version is Microsoft SQL server 2008 R2)from windows server 2003 to windows
    2008. 
    Please advice steps to accomplish this task. How to make sure DB moved without any errors?
    Thanks in Advance.

    Hello,
    As mentioned by Visakh, a side-by-side upgrade can be performed by using backup/restore and detach/attach methods.
    Additionally, you can transfer logins from 
    one SQL Server instance to the other by using the following article:
    http://support.microsoft.com/en-us/kb/918992
    The following article may be useful about transferring not only the databases, but jobs, DTS, alerts, operators.
    Consider scripting any existing linked server.
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • Windows Storage Server 2008 - unzip with drag & drop from Windows 7 client fails

    Hello.
    As i asked this question in German and got no answer so i try it in English now.
    I have the following problem:
    We have a Windows SBS 2008, where we store our files. If somebody opens a ZIP-file on a network share from a Windows 7 Client (64 Bit) it is possible to drag & drop the content (multiple files) to a directory. So far everything works as expected.
    We now have an additional Windows Storage Server 2008 integrated in our domain (Buffalo Tera Station WS-QV8/R5), where we also store files. If somebody opens the same ZIP-file on a network share of this server from a Windows 7 Client and tries to drag &
    drop the content the following happens:
    1. only one file is extracted and to display the file a refresh of the explorer view is needed.
    2. when the drag & drop action is repeated a second file is extracted
    Not alle files are extracted and there is no error message or indication why this happens.
    The behaviour is reproducible from another Windows 7 Client (32 Bit).
    If we try to drag & drop the files from the ZIP-file on the Windows Storage Server network sahre to a directory on the SBS network share all files are extracted correctly.
    On the Windows Storage Server itself all files are extracted without problmems. Therefore it must be a problem with the combination of Windows Storage Server und Windows 7 Client accessing the files via network shares.
    Are there any ideas where this problem could be located? Has anybody the same phenomenon and maybe a solution for it?
    Thanks in advance
    Michael Pruss

    Hi Michael,
    Thank you for clarifying the issue for us.
    I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
    Thank you for your understanding and support.
    Regards
    Kevin
    TechNet Subscriber Support
    If you are
    TechNet Subscription user and have any feedback
    on our support quality, please send your feedback here.
     

  • How can i get a link to download windows storage server 2008 standard

    how can i get a link to download windows storage server 2008 standard

    Hi,
    Please find the below link for storage server and its resources.
    Windows storage server
    Regards, Ravikumar P

  • Post upgrade from Windows Server 2008 R2 SP1 to Windows Server 2012 R2

    Hi, I'm not sure if I've done something wrong or if i lack some steps.
    We have an existing server having Windows Server 2008 R2 SP1 as OS, DC, and DNS. I had to upgrade it based on global standards so I upgraded it into Windows Server 2012 R2.
    What I did was an online upgrade, insert the DVD installation disc and it asked for a adprep for forest and domain.
    I did both forest and domain adprep and installation continued. After reboot, it showed up errors on my local server. Please see image below:
    and when i clicked each roles under Manageability, it shows me
    Is there something I need to do to fix these red marks?
    Regards,
    Jeff

    These are the logs i've seen inside Custom Views>Server Roles>AD DS, DNS Server, and Administrative Events respectively.
    Regards,
    Jeff

  • Windows Server 2008 R2 SP1 - BSOD Stop Error 0x00000050 RDPWD.SYS

    Hi all,
    I have been struggling with a BSOD for the past 5 weeks and have scoured the web trying in vain to find someone else with the same issue.
    Environment:
    8 x 2008 R2 SP1 Windows Servers (8Gb RAM, 25Gb HDD) with Remote Desktop Services Roles installed, running as part of an RDS Farm.  All Servers are VM Guests (hardware version 7) running on VMware vSphere v4.1.0-260247 Hosts (Dell
    PowerEdge R710 - 128Gb RAM).  Our vSphere 'farm' has 5 Hosts that connect to our EMC SAN via iSCSI with multipath routes. 
    Each RDS Server is load balanced via a Connection Broker, and each server has the same set of software / vm hardware installed.  In a nutshell, each has Symantec Endpoint Protection v11.0.5002.333, Symantec Altiris v7.0, Microsoft Office 2007 as well as
    other various software essential to these servers.
    Symptoms:
    Randomly throughout the day, one (or more) of the RDS Servers will crash with a BSOD more often than not with "caused by driver ntoskrnl.exe" sometimes with "cng.sys" and once with "ksecpkg.sys".  So far in the 5 weeks I have had 90 crashes.  Yesterday
    all 8 of the RDS Servers crashed at some point throughout the day.
    On a typical BSOD, it says:
    The problem seems to be caused by the following file: ntoskrnl.exe
    PAGE_FAULT_IN_NONPAGED_AREA
    Technical Information:
    *** STOP: 0x00000050 (0xfffffa800c153284, 0x0000000000000001, 0xfffff880053dc0c9, 0x0000000000000000)
    *** ntoskrnl.exe - Address 0xfffff8000169ac40 base at 0xfffff8000161e000 DateStamp 0x4e02aaa3
    Using BlueScreenView it says "caused by address: ntoskrnl.exe+7cc40" nearly every time.
    I have analysed as best I could using Microsoft WinDbg, and this is the output of a typical mini-dump file:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [\\hqrds01\c$\Windows\Minidump\030112-19359-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    Symbol search path is: SRV*C:\Program Files\Debugging Tools for Windows (x64)\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
    Product: Server, suite: TerminalServer
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Machine Name:
    Kernel base = 0xfffff800`01609000 PsLoadedModuleList = 0xfffff800`0184e670
    Debug session time: Thu Mar  1 09:14:00.921 2012 (UTC + 0:00)
    System Uptime: 0 days 21:31:41.950
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    *                        Bugcheck Analysis                                   
    Use !analyze -v to get detailed debugging information.
    BugCheck 50, {fffffa800be83284, 1, fffff8800576f0c9, 0}
    Could not read faulting driver name
    Probably caused by : RDPWD.SYS ( RDPWD!memcpy+1d9 )
    Followup: MachineOwner
    1: kd> !analyze -v
    *                        Bugcheck Analysis                                   
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffffa800be83284, memory referenced.
    Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
    Arg3: fffff8800576f0c9, If non-zero, the instruction address which referenced the bad memory
     address.
    Arg4: 0000000000000000, (reserved)
    Debugging Details:
    Could not read faulting driver name
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800018b8100
     fffffa800be83284
    FAULTING_IP:
    RDPWD!memcpy+1d9
    fffff880`0576f0c9 668901          mov     word ptr [rcx],ax
    MM_INTERNAL_CODE:  0
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  svchost.exe
    CURRENT_IRQL:  0
    TRAP_FRAME:  fffff8800bf70a80 -- (.trap 0xfffff8800bf70a80)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=000000000000023d rbx=0000000000000000 rcx=fffffa800be83284
    rdx=ffffffffffe7e63b rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8800576f0c9 rsp=fffff8800bf70c18 rbp=0000000000000001
     r8=000000000000001c  r9=fffff8a0033401e8 r10=fffff8a0033401e8
    r11=fffffa800be83268 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    RDPWD!memcpy+0x1d9:
    fffff880`0576f0c9 668901          mov     word ptr [rcx],ax ds:0c40:fffffa80`0be83284=????
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff800016319fc to fffff80001685c40
    STACK_TEXT: 
    fffff880`0bf70918 fffff800`016319fc : 00000000`00000050 fffffa80`0be83284 00000000`00000001 fffff880`0bf70a80 : nt!KeBugCheckEx
    fffff880`0bf70920 fffff800`01683d6e : 00000000`00000001 fffffa80`0be83284 00000000`00000000 fffff8a0`0be85820 : nt! ?? ::FNODOBFM::`string'+0x4611f
    fffff880`0bf70a80 fffff880`0576f0c9 : fffff880`057547cf 00000000`00000000 00000000`00000022 00000000`00000002 : nt!KiPageFault+0x16e
    fffff880`0bf70c18 fffff880`057547cf : 00000000`00000000 00000000`00000022 00000000`00000002 fffff880`0576c99d : RDPWD!memcpy+0x1d9
    fffff880`0bf70c20 fffff880`0576c9fc : fffff8a0`0f938010 00000000`00000022 00000000`00000019 00000000`00000002 : RDPWD!SM_MCSSendDataCallback+0x303
    fffff880`0bf70c60 fffff880`0576b354 : fffff880`0bf70da0 fffff8a0`033401e8 00000000`00000000 fffff880`0576abfd : RDPWD!HandleAllSendDataPDUs+0x188
    fffff880`0bf70d10 fffff880`0576af64 : 00000000`00000031 fffffa80`0bd01895 00000006`0000001f fffff880`05739079 : RDPWD!RecognizeMCSFrame+0x28
    fffff880`0bf70d50 fffff880`029ba1f8 : fffff8a0`03345000 fffffa80`0bae6e80 fffffa80`0a5c0e60 fffff880`05737e00 : RDPWD!MCSIcaRawInputWorker+0x3d4
    fffff880`0bf70df0 fffff880`057378d0 : 00000000`00000000 fffff880`0bf70f10 fffff880`0bf70f08 00000000`00000000 : termdd!IcaRawInput+0x50
    fffff880`0bf70e20 fffff880`05736d85 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tssecsrv!CRawInputDM::PassDataToServer+0x2c
    fffff880`0bf70e50 fffff880`057367c2 : fffffa80`088e8a28 fffffa80`00000000 00000000`00000031 fffff800`00000000 : tssecsrv!CFilter::FilterIncomingData+0xc9
    fffff880`0bf70ef0 fffff880`029ba1f8 : fffff880`009b8180 00000000`00000001 00000000`00000000 00000000`00000000 : tssecsrv!ScrRawInput+0x82
    fffff880`0bf70f60 fffff880`0572c4c5 : fffffa80`088e8a10 fffffa80`0bd01658 00000000`00000000 fffffa80`088e8a10 : termdd!IcaRawInput+0x50
    fffff880`0bf70f90 fffff880`029baf3e : fffffa80`0bd01620 fffffa80`0c100420 fffffa80`0bd4b450 fffffa80`0973b9b0 : tdtcp!TdInputThread+0x465
    fffff880`0bf71810 fffff880`029b9ae3 : fffffa80`09d902b0 fffffa80`0973b9b0 fffffa80`093d8520 fffffa80`0bd4b450 : termdd!IcaDriverThread+0x5a
    fffff880`0bf71840 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : termdd!IcaDeviceControlStack+0x827
    STACK_COMMAND:  kb
    FOLLOWUP_IP:
    RDPWD!memcpy+1d9
    fffff880`0576f0c9 668901          mov     word ptr [rcx],ax
    SYMBOL_STACK_INDEX:  3
    SYMBOL_NAME:  RDPWD!memcpy+1d9
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: RDPWD
    IMAGE_NAME:  RDPWD.SYS
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7ab45
    FAILURE_BUCKET_ID:  X64_0x50_VRF_RDPWD!memcpy+1d9
    BUCKET_ID:  X64_0x50_VRF_RDPWD!memcpy+1d9
    Followup: MachineOwner
    The RDS servers are set to reboot automatically, and after a period of 5 minutes or so, the users can reconnect and log back in.  On a typical day each server will have around 10 people RDP'd in to them.
    The Users connecting to the RDS Servers included XP laptops/desktops and IGEL UD-120-LX Thin Terminals.  The XPs have SP3 installed and are fully patched via Symantec Altiris.
    Things I have tried:
    - Analyse the dump-files (as per above).
    - I have tracked each user logging on to the RDS Farm (via batch scripts) and tried to determine if this is caused by the same individual(s) but it appears random.
    - Check to see if the crashing Virtual Machine is running on a specific host, but it has happened on all Hosts.
    - Check to see if there was anything specific that happened on the day that the crashes started.  There were about 5 new poeple introduced to the RDS Farm at that time, but there were using (a) client machines that had been used previously elsewhere with
    no issues, (b) software that had been used previously, (c) in a remote location that had previous users using RDS, (d) have not been logged on to a RDS Server when it has crashed.
    - Updated Windows Server 2008 R2 SP1 to the latest patches (as of Feb 2012).
    - Turned on Verifier (using recommended settings), and then analysed dump-files with the same reference to rdpwd.sys.
    - Fixed the Memory Resource Reservation in vSphere to the full 8Gb for all these RDS Servers (so that the memory is not shared at all).
    - Ran MEMTEST on a VM Guest with the full 8Gb RAM, on a couple of the ESX Hosts.
    - Changed the VMTools Video Driver to the SVGA II driver from the Standard VGA Driver.
    - Ran a full AV Scan (using SEP).
    - Isolated the Printer Drivers using the Printer Management MMC.
    - Ran sfc /scannow of all RDS Servers and rebooted.
    The mini-dump file mentioned above is here:https://skydrive.live.com/redir.aspx?cid=48f471f287af2349&resid=48F471F287AF2349!105&parid=48F471F287AF2349!103
    I hope someone can help, as what hair I have left (from pulling it out) is turning grey!
    Andy

    *                        Bugcheck Analysis                                   
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffffa800c153284, memory referenced.
    Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
    Arg3: fffff880053dc0c9, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 0000000000000000, (reserved)
    Debugging Details:
    Could not read faulting driver name
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800018cd100
     fffffa800c153284
    FAULTING_IP:
    RDPWD!memcpy+1d9
    fffff880`053dc0c9 668901          mov     word ptr [rcx],ax
    MM_INTERNAL_CODE:  0
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  svchost.exe
    CURRENT_IRQL:  0
    TRAP_FRAME:  fffff8800aa48a80 -- (.trap 0xfffff8800aa48a80)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=00000000000001ff rbx=0000000000000000 rcx=fffffa800c153284
    rdx=ffffffffffee6b8b rsi=0000000000000000 rdi=0000000000000000
    rip=fffff880053dc0c9 rsp=fffff8800aa48c18 rbp=0000000000000001
     r8=000000000000001c  r9=fffff8a0123923a8 r10=fffff8a0123923a8
    r11=fffffa800c153268 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    RDPWD!memcpy+0x1d9:
    fffff880`053dc0c9 668901          mov     word ptr [rcx],ax ds:8c40:fffffa80`0c153284=????
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff800016469fc to fffff8000169ac40
    STACK_TEXT:  
    fffff880`0aa48918 fffff800`016469fc : 00000000`00000050 fffffa80`0c153284 00000000`00000001 fffff880`0aa48a80 : nt!KeBugCheckEx
    fffff880`0aa48920 fffff800`01698d6e : 00000000`00000001 fffffa80`0c153284 00000000`00000000 fffff8a0`10919830 : nt! ?? ::FNODOBFM::`string'+0x4611f
    fffff880`0aa48a80 fffff880`053dc0c9 : fffff880`053c17cf 00000000`00000000 00000000`00000022 00000000`00000002 : nt!KiPageFault+0x16e
    fffff880`0aa48c18 fffff880`053c17cf : 00000000`00000000 00000000`00000022 00000000`00000002 fffff880`053d999d : RDPWD!memcpy+0x1d9
    fffff880`0aa48c20 fffff880`053d99fc : fffff8a0`10cf30d0 00000000`00000022 00000000`00000019 00000000`00000002 : RDPWD!SM_MCSSendDataCallback+0x303
    fffff880`0aa48c60 fffff880`053d8354 : fffff880`0aa48da0 fffff8a0`123923a8 00000000`00000000 fffff880`053d7bfd : RDPWD!HandleAllSendDataPDUs+0x188
    fffff880`0aa48d10 fffff880`053d7f64 : 00000000`00000031 fffffa80`0c039de5 00000006`0000001f fffff880`053a6079 : RDPWD!RecognizeMCSFrame+0x28
    fffff880`0aa48d50 fffff880`012c01f8 : fffff8a0`12393000 fffffa80`0bb7aa60 fffffa80`0b81e9c0 fffff880`053a4e00 : RDPWD!MCSIcaRawInputWorker+0x3d4
    fffff880`0aa48df0 fffff880`053a48d0 : 00000000`00000000 fffff880`0aa48f10 fffff880`0aa48f08 fffffa80`0c039ba8 : termdd!IcaRawInput+0x50
    fffff880`0aa48e20 fffff880`053a3d85 : fffff880`01716890 fffffa80`0c0327e8 00000000`00000000 00000000`00000000 : tssecsrv!CRawInputDM::PassDataToServer+0x2c
    fffff880`0aa48e50 fffff880`053a37c2 : fffffa80`0c16e598 fffffa80`00000000 00000000`00000031 fffff800`00000000 : tssecsrv!CFilter::FilterIncomingData+0xc9
    fffff880`0aa48ef0 fffff880`012c01f8 : fffff880`009b8180 00000000`00000001 00000000`00000000 00000000`00000000 : tssecsrv!ScrRawInput+0x82
    fffff880`0aa48f60 fffff880`052994c5 : fffffa80`0c16e580 fffffa80`0c039ba8 00000000`00000000 fffffa80`0c16e580 : termdd!IcaRawInput+0x50
    fffff880`0aa48f90 fffff880`012c0f3e : fffffa80`0c039b70 fffffa80`0acccf20 fffffa80`0a95c450 fffffa80`0abf9620 : tdtcp!TdInputThread+0x465
    fffff880`0aa49810 fffff880`012bfae3 : fffffa80`0c0a6560 fffffa80`0abf9620 fffffa80`087eee80 fffffa80`0a95c450 : termdd!IcaDriverThread+0x5a
    fffff880`0aa49840 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : termdd!IcaDeviceControlStack+0x827
    STACK_COMMAND:  kb
    FOLLOWUP_IP:
    RDPWD!memcpy+1d9
    fffff880`053dc0c9 668901          mov     word ptr [rcx],ax
    SYMBOL_STACK_INDEX:  3
    SYMBOL_NAME:  RDPWD!memcpy+1d9
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: RDPWD
    IMAGE_NAME:  RDPWD.SYS
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7ab45
    FAILURE_BUCKET_ID:  X64_0x50_VRF_RDPWD!memcpy+1d9
    BUCKET_ID:  X64_0x50_VRF_RDPWD!memcpy+1d9
    Followup: MachineOwner
    Bug Check Code 0x50:http://msdn.microsoft.com/en-us/library/windows/hardware/ff559023%28v=vs.85%29.aspx
    Please start by that:
    Update all possible drivers
    Uninstall all unused programs
    Disable all security softwares you have
    Run chkdsk /r /f and sfc /scannow
    Run memtest86+ to check if all is okay with your RAM. If an error was detected then replace the faulty RAM or contact your manufacturer Technical Support
    If this does not help then upload MEMORY.DMP file (You can zip it and divide it using 7-ZIP) using Microsoft Skydrive and post a link here.
    You can also contact Microsoft CSS for assistance.
    This
    posting is provided "AS IS" with no warranties or guarantees , and confers no rights.   
    Microsoft
    Student Partner 2010 / 2011
    Microsoft
    Certified Professional
    Microsoft
    Certified Systems Administrator: Security
    Microsoft
    Certified Systems Engineer: Security
    Microsoft
    Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft
    Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft
    Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft
    Certified Technology Specialist: Windows 7, Configuring
    Microsoft
    Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft
    Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

  • How to install KB2950358 on Windows STORAGE Server 2008 R2?

    Hello
    I am experiencing the exact issue described
    here on my WD Sentinel DX4000 nas box which runs Windows Storage Server 2008 R2. This is causing regular crashes and reboots and general unreliability when the memory leak causes all ram to be used up and the CPU is constantly running at 100% which both
    increases electricity usage and shortens the lifespan of the system.
    I have downloaded the hotfix on that KB article but it refuses to install claiming that it is not compatible. When the underlying Windows Server 2008 R2 OS is the same how can it not be compatible? My theory is that the Storage server version is only used
    and available on a small handful of OEM devices and there's barely any information of it on the internet so I think Microsoft have forgotten to add it to the compatibility list for this particular hotfix.
    After weeks of searching, I cannot find a way to force install the update. It's not a business-critical system and I've got backups of it so I am happy to try manual or risky efforts to get it installed. I have tried extracting the MSU file but that doesn't
    give me any useful files to install it manually or skip the compatibility checks.
    I've also tried to contact Microsoft directly but they don't even have Storage Server listed as an option on their support contact page so I've given up there, as a last resort I am hoping someone here can point me in the right direction. Other online forums
    refuse to help saying it's too risky with a server but personally I want it installed and will try anything to do so because I've got a £1000 NAS sitting here that is unusable due to this issue. I'd rather not reinstall the OS as the problem reoccurs - I've
    tried it already before I found this KB article.
    Bottom line, Microsoft have identified the issue and released a hotfix, the server version IS supported, but was not added to the compatibility restrictions of the update so I cannot get the update installed.
    Any advice gladly received. Hopefully someone from MS will see this and be able to update the compatibility of the hotfix if nothing else is possible.

    I see SP1 is a prerequisite. Also the manufacturer may have specific patch procedures or recommendations so I'd probably contact them directly.
    http://support.wdc.com/product/install.asp?wdc_lang=en&fid=wdsfWDSentinel
    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]
    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

  • Unable to install SQL server 2008 r2 standard edition on windows server 2008 r2 sp1

    I am unable to install sql server 2008 r2 standard edition on windows server 2008 r2 sp1.
     On the Setup Support Files page, choose Install this step I don't get any other window i.e. nothing happens I waited for 5-10 min.  Then I checked the log file.
    Final result:                  Failed: see details below
      Exit code (Decimal):           -2068053929
      Exit facility code:            1212
      Exit error code:               87
      Exit message:                  Failed: see details below
      Start time:                    2014-03-18 14:59:31
      End time:                      2014-03-18 15:00:25
    === Verbose logging started: 3/19/2014  9:45:47  Build type: SHIP UNICODE 5.00.7601.00  Calling process: E:\SQL Server 2008 R2 Standard\x64\setup100.exe ===
    MSI (c) (10:34) [09:45:47:496]: Note: 1: 2203 2: E:\SQL Server 2008 R2 Standard\x64\redist\watson\dw20sharedamd64.msi 3: -2147287038
    MSI (c) (10:34) [09:45:47:496]: MsiOpenPackageEx is returning 2.
    === Verbose logging stopped: 3/19/2014  9:45:47 ===
    Please help As i am running out of time as i have to upgrade TFS for that first step is to install SQL server.

    Hello,
    The following are a few things you can try:
    Copy the media to the local disk drive, unzip it (in case you are installing from an ISO file, and run SQL Server setup from there.
    Try to unregister and register the Windows Installer with the following two commands:
    msiexec /unregister
    msiexec /regserver
    Try to use Process Monitor to log the detailed error produced when the installation of dw20sharedamd64.msi fails. You can download Process Monitor from the following link:
    http://technet.microsoft.com/en-us/sysinternals/bb896645
    Share with us the error captured by Process Monitor.
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

Maybe you are looking for