Windows Server - Can't login to server - The requested operation cannot be completed because the terminal connection is currently busy processing a connection operation

Asked By K C on 22-Jul-08 05:04 AM

Hello,

I have 2 dell poweredge 2003 R2 (DC, DNS, DHCP) servers causing me this problem.

I seem to get this error when trying to login (locally or remotely) after having used an mmc with remote desktops to access the server from my XP machine earlier in the day, but not everytime, has been every couple months but seems to be getting more frequent and actually occured for the first time yesterday on the second machine.

 "The requested operation cannot be completed because the terminal connection is currently busy processing a connection operation".

Nothing in the event logs... I have to do a hard reboot to gain access again.  I am the only person accessing these machines remotely  and sometimes I do several times a day and I always "logoff "and I don't "disconnect".

Users see no difference as mapped drives continue to function and I can connect to the event logs just fine.

Any ideas would be appreciated, I haven't found anything thus far,

KC

Try this one

Sagar P replied to K C on 22-Jul-08 05:03 AM

Open

Start -> Programes -> Administrative Tools -> Terminal Services ->

Open Terminal services on server Pc & then End one of the Remote connection.

Refresh it and then try to connect it.

Actually this error comes when there are more connection or users are connceted at a time to server. So you just have to remove connection by disconnecting it.

Best Luck!!!!!!!!!!!!!!!!!!
Sujit.

What do you think about this

K C replied to Sagar P on 22-Jul-08 05:12 AM

Yesterday I changed my GPO on the domain controller group for terminal services to do the following, do you think this will help? (hope this makes sense I am translating from French!).  I did connect pretty frequently to both of the servers yesterday.  I will try what you said if I get the error again.

Terminal Server/Sessions

-Define expiration delay for disconnected - 3 hrs

-Define expiration delay for active - 2 days

-Define expiration dealy for inactive - 2 days

Close session when delay expires- Active

Thanks,

KC