Error Connecting To Existing Session For Username Id 0
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 (id 0). the operation completed successfully of a server running Windows Server 2003 using the mstsc /admin command. When you error connecting to existing session for administrator (id 0) attempt to do so, you receive the following error: Error connecting to existing session for (ID 0). 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 resolving an issue
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Error connecting to existing session for (Id 0) Want to Advertise Here? Solved Error connecting to existing session for (Id 0) Posted on 2006-12-15 Windows Server 2003 1 Verified Solution 13 Comments 18,625 Views Last Modified: 2010-10-29 http://www.dell.com/support/article/us/en/04/SLN249309/en?c=us&l=en&s=bsd&cs=04 I have a Windows 2003 SP1 Standard edition and installed the Terminal Service. I can connect myself using the RDP. When i try to use mstsc /console i put the ipaddress of the server it arrive to ask the username and the password and after popup a window with "Error connecting to existing session for (Id 0). The operation completed successfully." and doesn't allow me to connect https://www.experts-exchange.com/questions/22094822/Error-connecting-to-existing-session-for-username-Id-0.html on the console of the server.On other servers works fine, same updates same model, same group policy settings. I wonder what is stopping me to access the console session on the server ? Thank you 0 Question by:djmagicb Facebook Twitter LinkedIn Google Best Solution bydjmagicb Found the solution. I had installed an application which installed another video adapter driver that could be visible under "Display adapters". Removing the application resolved the issue. Thanks everybody Go to Solution 12 Comments LVL 18 Overall: Level 18 Windows Server 2003 11 Message Active today Expert Comment by:Andrew Davis2006-12-17 Check is there allready a user logged on to the console? is that the same user that you are trying to log on remotely? 0 Message Author Comment by:djmagicb2006-12-18 Hi, there is no user logged on the server. If i use the command "mstsc -v:servername /F -console" i am able to connect on the server's console. But there shoud be a problem because on the other 2 servers "mstsc /console" works file. I don't know what's the difference and how to fix this error. Thanks 0 LVL 18 Overall: Level 18 Windows Server 2003 11 Message Active today Expert Comment by:Andrew Davis2006-12-18 Sounds lik
session.." Here you will find help for frequently asked questions as well as for your specific question. Post a reply 5 posts • Page 1 of 1 Remote Desktop: "Error connecting to existing session.. http://forum.ultravnc.info/viewtopic.php?t=3431 by gp » 2005-07-08 14:45 Hi Folks, Don't know whether this is a bug http://www.tomshardware.com/forum/143924-45-error-connecting-existing-session-solved in installer/unintaller/UVNC or simply a wrong handling.... I had UltraVNC-100-RC203 installed on a Win2003 server. It worked fine but there were some probs with Remote Desktop as already described in this forum. Now I downloaded "UltraVNC-1.0-Setup.exe" from www.uvnc.com, uninstalled the RC203 (reboot) and installed the 1.0 version (reboot). Note: I did not uninstall the error connecting hook driver seperately I simply used the Uninstall option of UVNC with following reboot. There is/was no additional Remove option for the hook driver. New version of Ultra VNC is working fine but unfortunately now Remote Desktop fails permanently. On the RD session I get the Login prompt. I enter name and password. Screen becomes dark-grey and it takes much longer as usual before something happenes. What error connecting to will happen then is that the screen is still dark gray but I get an error message: Logon Connection Failed Error connecting to existing session for (ID 0). The operation completed successfully. This applies to any username and there is no difference whether there is an active VNC session on the machine or not. Server is a Dell, dual Xeon 2.8 GHz, Win2k3 SP1, 2 GB RAM, ATI Radeon 7000 On the Device Manager I can see: [-] Display Adapters ....+ Radeon 7000 Series ....+ WinVNC video hook driver ....+ WinVNC video hook driver 2 drivers ?! Both are version 1.19.0.0 Hook driver's properties are: - vncdrv.dll version 1.00.19 - vnccom.sys version 1.0.0.17 - vncdrv.sys version 1.00.17 - The driver is present - The communication service is present - The driver is currently active I already tried to uncheck the "Video Hook Driver" checkbox without any change. How to proceed? Regards GP gp Posts: 4Joined: 2005-07-08 14:11 Top by redge » 2005-07-08 23:50 there a new post fix for your issue with win2003 Terminal Service (need some tests of end user like you for validate some fix please try it and come back with your feedback Pre-release 1.0.1( fixes)
Gaming Smartphones Tablets Windows 8 PSUs Android Your question Get the answer Tom's Hardware>Forum>Windows XP>Error connecting to existing session (solved)> Error connecting to existing session (solved) Tags: Nvidia Windows XP Last response: 28 May 2004 05:51 in Windows XP Share Ian 27 May 2004 01:51:42 Archived from groups: microsoft.public.windowsxp.work_remotely (More info?) A few months ago I started a thread about a problem I was having when trying to reconnect to an existing remote desktop session. http://groups.google.com/groups?threadm=%238gRyGtEEHA.1... At the time the suspicion was pointing towards the NVIDIA display drivers, but nothing i tried ever seemed to fully solve the problem. A few weeks ago I came across a number of other posts in this group regarding problems with the NVIDIA drivers and the solution there seemed to be to disable the NVIDIA Display Driver Service. At the time I thought what the hell, and decided to give it a try. Since then I have not had a repeat of the reconnection problem, so I am confidently able to say that disabling the service fixed it. FWIW, I also disabled this service on my computer at home and I've since been able to remotely connect to my home machine from work. I have also noticed that I haven't had any crashes whilst playing DirectX games either. In particular I was finding that my computer at home would crash at least 2/3 of the times I played FarCry, which is very graphics intensive. Since disabling the display driver service two weeks ago, no crashes. Regards Ian More about : error connecting existing session solved Anonymous 27 May 2004 06:27:15 Archived from groups: microsoft.public.windowsxp.work_remotely (More info?) Thanks! So if I'm remembering correctly--there were a number of similar machines and only yours exhibited the problem--any idea why that was? Any idea what this service is supposed to do for you? "Ian" wrote in message news1e22473.0405261251.3c4c0b6b@posting.google.com... >A few months ago I started a thread about a problem I was having when > trying to reconnect to an existing remote desktop session. > > http://groups.google.com/groups?threadm=%238gRyGtEEHA.1... > > At the time the suspicion was pointing