The requested operation cannot be completed because the Terminal connection is currently busy processing a connect operation

Great, isn’t it?  you get a computer, and operating system (windows 2003 server in this case), and then you can’t login via a terminal server window, because someone didn’t logoff a previous one!

What can you do? Reboot? Well, you could.. but what if it’s a production server that you can’t reboot easily?

you could try this…    (But don’t sue us if it all goes horribly wrong! You’re responsible for your own servers, and of course, you have valid backups? Don’t you??)

Anyway, If you have access to another windows server, try this on the command line:


C:\Documents and Settings\Administrator>sc \\servername query TermService

        TYPE               : 20  WIN32_SHARE_PROCESS
        STATE              : 4  RUNNING
                                (NOT_STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN))

        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0


Marvellous! we can see Terminal Services running on the remote server.


C:\Documents and Settings\Administrator>tasklist /s servername /u username
 /p password

Image Name                     PID Session Name        Session#    Mem Usage
========================= ======== ================ =========== ============

csrss.exe                     5864 RDP-Tcp#499                1      3,064 K
winlogon.exe                  7484 RDP-Tcp#499                1      4,776 K
rdpclip.exe                   7084 RDP-Tcp#499                1      1,404 K
ctfmon.exe                    2288 RDP-Tcp#499                1        724 K
explorer.exe                  4236 RDP-Tcp#499                1      7,716 K
cpqteam.exe                   5228 RDP-Tcp#499                1        260 K
ccApp.exe                     6364 RDP-Tcp#499                1      5,812 K
jusched.exe                   6236 RDP-Tcp#499                1        176 K
WindowsSearch.exe             1712 RDP-Tcp#499                1      1,236 K
jucheck.exe                   4372 RDP-Tcp#499                1        892 K
Manager.exe                   4572 RDP-Tcp#499                1     20,344 K
scrnsave.scr                   960 RDP-Tcp#499                1      1,376 K
wuauclt.exe                   6996 RDP-Tcp#499                1      4,044 K

(partial listing, this could be very long!)


It is quite possible that the .scr process is the one that you could kill off, and enable you log logon again via terminal Services. You can do this with:


C:\Documents and Settings\Administrator>taskkill /s servername /u username
/p password /PID 960

SUCCESS: The process with PID 960 has been terminated.


As stated, you follow these guidelines at your own risk, we accept no liability for any data, or any other loss that may happen!