2009년 10월 30일 금요일 오전 10:45Hi.
Suddenly all my windows froze. I locked the computer (Windows-L) and went for a cup of coffee hoping it'd "blow over". When I got back, trying to unlock gives me a black screen before the monitor turns into power saving mode. After a while, the monitor turns back on, greeting me with the logon screen.
Logging on another user in a parallel session works.
All the processes in the "locked" session seem to be running; music is playing, tasklist from another computer gives the impression that everything's good.
While browsing through the eventlog, I saw the following event in Microsoft -> Windows -> TerminalServices-LocalSessionManager/Operational:
Error, Event ID 20: Attempt to send connect message to Windows video subsystem failed. The relevant status code was 0x80070102.
The message gives 0 hits on google and repeats for every connection attempt, be from the console or via remote desktop from another computer.
OS: Windows 7 Enterprise x64, fully patched
Is there any hope for the locked session?
Are there tools, logs, etc. that can assist in solving the problem?
2009년 12월 30일 수요일 오전 1:15I'm having the same issue sporadically when trying to connect remotely to my Windows 7 Ultimate x64 machine. Every time, I'm able to get to the login screen remotely, and after logging in, the screen changes to the "Welcome" screen with a wait cursor. A few seconds into that screen, the cursor freezes and about a minute later, I get this error:
"This computer can't connect to the remote computer. The two computers couldn't connect in the amount of time allotted. Try connecting again. If the problem continues, contact your network administrator or technical support."
I've had to reboot the computer to get the error to go away. Poking through the event log yielded the same error reported by Magnus Holm above.
2010년 1월 26일 화요일 오전 10:09Here we go again.
Same issue, same data in the event log.
When locking the console, trying to get back in, I got:
"The task you are trying to do can't be completed because Remote Desktop Services is currently busy.
Please try again in a few minutes. Other users should still be able to log on."
Pressing OK and retrying gives a black screen after l/p is entered, it stays black for a while, then returns to the "Press CTRL + ALT + DELETE to log on" screen.
2010년 4월 19일 월요일 오전 6:37
Same issue here- it happened to me today on a fully patched Win7 x64 system. I was working away, and while using Aero flip3d to cycle thru some windows, the animation "froze" but the mouse was still moving, music was playing etc. I was able to even CTRL+ALT+DELETE and "switch user" and log in under another account, same as the original poster, but I could not recover into my original session. Just a perpetual black screen, and no RDP access either. I had a lot of unsaved work in that session unfortunately. :-(
Would love to know the cause and more importantly, if there is some sort of solution the next time it happens. I was messing around with SysInternals "PSTools" suite thinking I could execute some kind of kill signal with pskill from my other machine, but all attempts to connect to the main computer even as an Admin were rejected with things like "could not access $ADMIN share" or "remote registry service not running", etc.
Anyone got some more info on this or ideas? I do have a tendency to install hotfixes beyond what is available in Windows Update- maybe I got trigger happy and installed a hotfix that I shouldn't have but seeing as how this issue dates back to Oct '09 that seems unlikely.
2011년 5월 27일 금요일 오후 2:57
I think it's a problem with users try running video over RDP.
Check your configuration, Open Remote Desktop Session host Configuration, right click on "RDP-Tcp" "Properties" , verify TAB "Client Settings".
On "Redirection" check if "Audio and video playback" is select for disable the following (probably set i on).
If you wish all user play video/audio over RDP uncheck that.
2011년 7월 10일 일요일 오후 5:05
My users (myself included) are also experiencing the problem. I haven't been able to determine what the status code (0x80080102) means, maybe it has a clue into why it's failing.
Is there a hot fix for this, or at least something in the works? If we understood what was happening and/or why it would help but at the moment we're in the dark and I'm unable to answer questions as to why. Anyone?
Ok, just found out that the code means WAIT_TIMEOUT (from here: http://blogs.msdn.com/b/joshpoley/archive/2008/01/04/errors-007-facility-win32.aspx), now the reason is why is it timing out? What is hanging that is causing the connect call to time out, more importantly _why_ is it hanging?
2012년 5월 19일 토요일 오후 6:05The problem is still occuring on server 2008R2 sp1 with all updates. Can someone from Microsoft respond in this thread?
2012년 8월 27일 월요일 오후 5:51
I am also having that same issue with Remote Desktop on a Server 2008 system.
Attempt to send disconnect message to Window video subsystem failed. The relevant status code was 0x80070102
Event ID 20
Did anyone ever find a solution?