Error Connecting To Existing Session For Administrator
Contents |
article provides information on a condition that may prevent Remote Desktop connections to the local console session of a server running Windows Server 2003. You may find that you are unable to remotely connect to the console session error connecting to existing session for user of a server running Windows Server 2003 using the mstsc /admin command. When you windows xp error connecting to existing session attempt to do so, you receive the following error: Error connecting to existing session for
Error Connecting To Existing Session The Operation Completed Successfully
The connection may succeed on the first attempt after a reboot but fail on subsequent attempts. There is more than one possible reason for this error. It can be caused by non-Windows services interfering with the connection attempt. To rule this out, use the following procedure: Type msconfig at a command prompt to open the System Configuration utility. In the Services tab, check the Hide all Microsoft services box and click the Disable all button. Click OK to close the System Configuration utility, then reboot the server. When the server reboots, use mstsc /admin to attempt to connect to the console session again. If the connection succeeds, it may be a good idea to attempt another connection to make sure you can connect consistently. If you are able to connect consistently, re-enable the disabled services one by one until the problem returns. The last service enabled is the one causing the problem. Contact the appropriate software vendor for further assistance. The problem can also be caused by existing remote sessions that are failing to close properly. In order to force all existing sessions to close, you can reset the server's RDP listener. To do so, perform the following steps: Open Terminal Services Manager from the Administrative Tools menu. Expand the server in the left pane. Right-click the RDP-Tcp listener object beneath the server and select Reset.Note: The next step will abruptly disconnect any users currently connected to the server via RDP. All legitimate RDP sessions should be logged off prior to completing this step. Click OK to confirm.The listener will be reset, and all existing sessions will close. You should now be able to connect with no errors. Quick Tips content is self-published by the Dell Support Professionals who resolve issues daily. In order to achieve a speedy publication, Quick Tips may represent only partial solutions or work-arounds that are still in development or pending further proof of successfully resolv
Technical Consultant/SI GROUP SPONSORED BY MICROSOFT See more RELATED PROJECTS eClinicalWorks V10 Full implementation of eClinicalWorks V10 Cloud. 19 Providers, 2 sites. Business Continuity Plan Replicate all environment in a Data Center located into a partner and enable users + SPB operators to keep all things running in case of a disaster. Workstation Replacement We are replacing any XP machines with Windows 7 PCs so that we wont have any issues with XP not having support. TECHNOLOGY IN THIS DISCUSSION Join the Community! Creating your account only takes a few minutes. Join Now Anyone encountered this problem? FROM USER: Any work I have open in an existing session is being lost. I typically log in and then will perform some work. When I get home http://www.dell.com/support/article/us/en/04/SLN249309/en?c=us&l=en&s=bsd&cs=04 I typically reconnect and then continue my work. I was able to log in after the error. But if I had disconnected and tried to re-login, it would give me the error and bring up a new session. I would lose any open files I had. Reply Subscribe View Best Answer RELATED TOPICS: Error connecting to computers Error connecting to desktops Unable to connect MKS:Error connecting to /bin/vmx process   3 Replies Serrano OP Zach333 Sep 13, 2011 at 1:47 UTC https://community.spiceworks.com/topic/155844-error-connecting-to-existing-session-in-rdp Tell the user to save their work and log off before they leave( it takes all of 30 secs). Then they can log back in at home. No need to keep the session active IMO. It seems poor practice to leave unsaved work on a RDP session anyway. Unless you like doing the same work again and again. 0 Mace OP Denis Kelley Sep 13, 2011 at 1:53 UTC Any errors generated on the server that might shine some light? 0 Poblano OP Best Answer erikbrandvig Sep 13, 2011 at 3:57 UTC i believe you may want to check your remote user settings in AD. obviously this user is a remote user and able to initiate remote sessions. but there is a switch in AD that allows the user to connect from anywhere back into his current session. it's in the "sessions" tab (in 2003), called "allow reconnection: from any client" i can't guarantee that's your issue, and "from any client" is the default behavior, but it may have been changed in group policy. edit: and what client is he using? mstsc? citrix? edit: http://www.pcreview.co.uk/forums/error-connecting-existing-session-solved-t649045.html and maybe he has an nvidia video card at home? hahahh 1 This discussion has been inactive for over a year. You may get a better answer to your question by starting a new discussion. Text Quote Post |Replace Attachment Add link Text to display: Where should this link go? Add Cancel × Insert code Language Apache A
Experts-Exchange. I just paste a screen shot to show that you need to remove the additional Display Adapters if https://woodaway.wordpress.com/2010/07/07/error-connecting-to-existing-session-for-id-0-the-operation-completed-successfully/ you get this error message when RDP to a server. Like this:Like Loading... Related from → Windows Server ← Install Certificates http://www.pcreview.co.uk/threads/fix-error-connecting-to-existing-session.648233/ on ApacheOpenSSL 欧游杂记(七) → No comments yet Leave a Reply Cancel reply Enter your comment here... Fill in your details below or click error connecting an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your WordPress.com account. (LogOut/Change) You are commenting using your Twitter account. (LogOut/Change) You are commenting using your Facebook account. (LogOut/Change) You are commenting using your Google+ account. (LogOut/Change) Cancel error connecting to Connecting to %s Notify me of new comments via email. CategoriesCategories Select Category Career Log(16) Computers and Internet(76) English(16) Entertainment(2) Exchange Server(12) Hobbies 爱好(92) ISA Server(30) Microsoft General(32) News and politics(40) Photography 摄影(8) Shanghai 上海(4) SharePoint(2) Travel 旅游(48) Uncategorized(12) Virtual Server(8) Windows Server(28) 中文(35) Azure BlackBerry browser bug Caribbean Celebrity Summit Cloud Cruise drive letters English Facebook Forefront Google Google Map Google Map API Halloween Hawaii HDR high dynamic range HP iLO Internet ISA Japan Java JDK Live Office LOMO lomography Microsoft moon Muskoka Office Live Photography 摄影 ProLiant proxy Shanghai snow solar sun supermoon TMG VCAgent Version Control Agent Windows Knowledgebase xd_proxy[1].css Yahoo 万圣节 上海 世博 东欧 中欧 云计算 光影魔术手 加勒比群岛 匈牙利 奥地利 布拉格 布达佩斯 微软 意大利 捷克 摄影 斯洛伐克 旅游 日本 欧洲 洋泾浜 海德堡 游记 游轮 维也纳 茵斯布鲁克 萨尔斯堡 萨尔茨堡Photo - Budapest Photo - Prag
the record as I've had this issue for a while and noticed that a number of others also have, but no-one ever posted a solution. I've recently had a new HP computer at work and after I'd got all of my applications ported across from my old machine to the new one and enabled remote desktop I started to have problems connecting to an existing session. This occurred regardless of whether the original login session was created from the console or remotely, and it happened for all accounts on the machine that had remote logins enabled. The error message I was getting was Logon Connect Failed Error connecting to existing session for XXX (Id n) The Specified session cannot be found. A new session will be created. No new session was ever created and the only course of action was to login under an alternative admin account and kill the initial session (this had an obvious down-side in that any unsaved work was lost). After a couple of calls to the HP product support number here in the UK they eventually came up with a simple solution that worked for me. The solution was simply to create a new user with full admin rights, login as that user. Then login as that user again via remote desktop. At this point I was then able to disconnect and reconnect. This seems to also have fixed the problem with all of the other accounts at the same time. I've no idea why it fixed it or indeed what had broken in the first place. However the fact it was fixed was good enough for me. I just hope that this post helps someone else out in the future. Regards Ian Ian, Mar 11, 2004 #1 Advertisements Huei Wang [MSFT] Guest Re: Error connecting to existing session Is this on Windows 2000 server or Windows 2003? -- This posting is provided "AS IS" with no warranties, and confers no rights. "Ian" <> wrote in message news:... > I thought I'd post this for the record as I've had this issue for a > while and noticed that a number of others also have, but no-one ever > posted a solution. > > I've recently had a new HP computer at work and after I'd got all of > m