Fatal Error Errorcode 5 Seesion Will Be Disconected
Contents |
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting remote desktop connection low virtual memory error ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is
Remote Desktop Low Virtual Memory Windows 7
a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can your remote desktop session is about to end. this computer might be low on virtual memory ask a question Anybody can answer The best answers are voted up and rise to the top Windows Remote Desktop (RDP/MSTSC) fails with Error Code: 5 up vote 2 down vote favorite I have 2 Windows XP boxen: A (running XP SP3)
An Internal State Error Has Occurred. The Remote Session Will Be Disconnected
and B (running XP SP2). I'm using Remote Desktop to connect from A to B. When I connect, I get the login screen (which is slow to respond to keyboard/mouse input), and after logging in, I get the following: Fatal Error (Error Code: 5) Your Remote Desktop session is about to end. This computer might be low on virtual memory. Close your other programs, and then try connecting to the remote computer again. If the problem continues, contact your network administrator or technical support. I've seen one way to (sometimes) get in by opening a second RDP session to the same box [1], and if I wait long enough sometimes it will go ahead and log in anyway. Is there something broken/missing on the PC I'm trying to remote in to? Edited in reply to djangofan: There's nobody listed under "Lock pages in memory". When the double login trick works, a glance at Task Manager shows plenty of free memory, >800MB available out of 1.5 GB. (Performance tab, Physical memory) For what it's worth, this happens consistently after a reboot. What sort of exact info would be useful? There's very little remaining installed on that machine that's not Windows + Office... [1] found at http://www.fdcservers.net/vbulletin/archive/index.php/t-1580.html windows remote-desktop rdp mstsc share|improve this question edited Nov 17 '09 at 21:47 asked Nov 17 '09 at 13:24 BryCoBat 123117 add a comment| 4 Answers 4 active oldest votes up vote 1 down vote accepted I've seen this problem before, for me it was caused by a failing HDD. The virtual memory was set to a fixed size and part of the file was on some bad blocks. I temporarily corrected this by setting the virtual memory to system managed, running a scandisk, then a defrag, and then setting it back to a fixed size. After I got the system stable I imaged and replaced the failing drive about a week or so later. Since then its been running great, about 18 months.
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: BUG: Remote Desktop session is disconnected with protocol error if Remote Control is used on a Windows Server 2008-based computer Windows Server > Remote Desktop Services (Terminal Services) General discussion 11 Sign in to vote SYMPTOMS When a user remote controls another user's http://serverfault.com/questions/85501/windows-remote-desktop-rdp-mstsc-fails-with-error-code-5 session using Remote Desktop Services Manager or Terminal Services Manager on a Windows Server 2008-based computer, and then stops remote controlling, one or both sessions are disconnected with the following error: Remote Desktop Disconnected Because of a protocol error, this session will be disconnected. Please try connecting to the remote https://social.technet.microsoft.com/Forums/windowsserver/en-US/87fc497a-27fd-4a76-ab59-ea5fe01c9091/bug-remote-desktop-session-is-disconnected-with-protocol-error-if-remote-control-is-used-on-a?forum=winserverTS computer again. CAUSE This problem occurs if Remote Desktop Connection Client version 6.0.6001 or 6.0.6002 is used with the highest RDP Compression setting. Windows Server 2008 SP1/SP2 defaults to a lower RDP Compression setting, and thus will only exhibit the above symptoms if the setting has been changed to "Optimized to use less network bandwidth", which is the maximum. Windows Server 2008 R2 defaults to the maximum RDP Compression setting. WORKAROUND Change the RDP Compression setting on the server to "Balances memory and network bandwidth" (recommended) or "Optimized to use less memory" using Group Policy. If using Windows Server 2008 R2 you may also choose "Do not use an RDP compression algorithm". An alternative workaround is to use a different Remote Desktop Connection Client version than those mentioned above, however, this may not be practical. Below are instructions for making the change to the local group policy; if p
disconnected. Your computer may be low on memory. http://superuser.com/questions/176451/remote-desktop-closes-with-fatal-error-error-code-5 After closing some applications, try to reconnect the session" I had the user bring the remote desktop laptop in to the office, I tested the terminal server connecting usign remote desktop and it worked fine. I ran scans on the machine, clean. Made sure it was patched. The low virtual memory user still gets the same error when connecting to Terminal Server via Remote Desktop on his home DSL connection. This is an isolated issue. All the other users can connect without a problem. Thanks, scott . Follow-Ups: Re: Fatal Error Code 5 From: SJMP Prev by Date: Terminal server for POS Next by Date: Re: Terminal server for POS Previous by thread: Terminal server for POS Next by thread: Re: Fatal Error Code 5 Index(es): Date Thread Flag as inappropriate (AWS) Windows Science Usenet ArchiveAboutPrivacyImprint www.tech-archive.net >Archive >Windows >microsoft.public.windows.terminal_services >2007-03
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Super User Questions Tags Users Badges Unanswered Ask Question _ Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Remote Desktop closes with Fatal Error (Error Code: 5) up vote 1 down vote favorite We have one PC (Windows XP SP3) that we can not log onto using a Remote Desktop session. Logging on to the PC directly (sitting in front of it using the connected keyboard and monitor) work fine. From a second PC (tried a number of different ones but all Windows XP SP3) I run 'mstsc' and type in PC name to connect to. This shows the login box which we can enter the correct login details and click OK. Within a few second we get an error: Title: Fatal Error (Error Code:5) Error: Your Remote Desktop session is about to end. This computer might be low on virtual memory. Close your other programs, and then try connecting to the remote computer again. If the problem continues, contact your network administrator or technical support. None of the computers we are using are low on memory (2Gb+) and we let windows manage the virtual memory side of things. We do not see this with any other PC and do use Remote Desktop in meeting rooms to connect to user PCs with no problems. windows-xp remote-desktop share|improve this question asked Aug 16 '10 at 15:57 Swinders 2101714 add a comment| 1 Answer 1 active oldest votes up vote 0 down vote None of the computers we are using are low on memory (2Gb+) and we let windows manage the virtual memory side of things. I think you're talking about letting Windows control the size of the paging file. While I would consider that to be a good practice, it doesn't stop the computer from running out of virtual memory. At leas