Learn about Edgartown's quest to ensure the safety and security of the entire town's employee and citizen data. Read the case study!
Course Of The Month
8 days, 6 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
SERVER 2008 small business
Posted on 2016-07-14
I recently started working on an old and scary server. Today I tried to log off the administrator from Remote Desktop. It took a long time to complete so I ended the remote session. Now when I try to log in again with Remote Desktop, I get the following error from the server after entering my password.
"The requested operation cannot be completed because the terminal connection ... busy processing a connect, disconnect, reset, or delete operation"
Can I force a power down of the server and hope or expect that it will come back up??
Right now I am dead in the water. Oddly the server is hosting emails on Exchange 2007 and the email is still working!
"The requested operation cannot be completed because the terminal connection ... busy processing a connect, disconnect, reset, or delete operation"
Can I force a power down of the server and hope or expect that it will come back up??
Right now I am dead in the water. Oddly the server is hosting emails on Exchange 2007 and the email is still working!
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
5
4-
4
- +2
20 Comments
If this server is hosting email, then definitely do not power down (yet).
Do you have another account with administrative rights that you can use to log in?
And if so, do you still get the same error?
If you are able to log in, open Remote Desktop Services Manager and see if you can logoff/reset the account in question.
Do you have another account with administrative rights that you can use to log in?
And if so, do you still get the same error?
If you are able to log in, open Remote Desktop Services Manager and see if you can logoff/reset the account in question.
Try connecting to the console session instead. Use /admin after the IP address or FQDN in the computer name field of the RDP client.
You may be able to access other workstations in the network via Remote Web Workplace if that was set up. https://FQDN/remote will get you in.
You may be able to access other workstations in the network via Remote Web Workplace if that was set up. https://FQDN/remote will get you in.
Active 1 day ago
Thanks Jeffrey, but that gives me an error 'The computer name is blank or it contains invalid characters...'
I am typing XXX.XXX.XX.XXX/admin
I am typing XXX.XXX.XX.XXX/admin
Active 1 day ago
I have another admin account. So far, when I log in with it it goes to the 'Welcome' screen, then it goes to 'Applying user settings', and seems to be stuck there. So, I ended the session, now back to the same error for both accounts.
I did have someone onsite look at the server screen and it shows the same as mine, so we cannot log in locally either. So this is a server issue, not an RDC issue??
I did have someone onsite look at the server screen and it shows the same as mine, so we cannot log in locally either. So this is a server issue, not an RDC issue??
Try this locally (it will only be for about a minute or two).
Pull the network plug on the server.
Now have the onsite tech attempt to log in.
If he is able to log in, then reattach the network cable.
Pull the network plug on the server.
Now have the onsite tech attempt to log in.
If he is able to log in, then reattach the network cable.
Active today
You need to be typing from a command line:
MSTSC /V:xx.xxx.x.xxx /ADMIN
You can't use the console session from the gui - you must start the client from the command line that way.
You can also try forcing a proper reboot by using shutdown.
shutdown /m \\servernameOrIP /r /t 1
To break that down - the /m means machine to shutdown follows, the /r is a reboot instead of an outright shutdown, and the /t 1 is the delay before rebooting in seconds. By specifying a delay greater than zero you are telling windows to "force" running applications to shutdown and allow the restart in the event some have unsaved data (like an open notepad that hasn't been saved).
MSTSC /V:xx.xxx.x.xxx /ADMIN
You can't use the console session from the gui - you must start the client from the command line that way.
You can also try forcing a proper reboot by using shutdown.
shutdown /m \\servernameOrIP /r /t 1
To break that down - the /m means machine to shutdown follows, the /r is a reboot instead of an outright shutdown, and the /t 1 is the delay before rebooting in seconds. By specifying a delay greater than zero you are telling windows to "force" running applications to shutdown and allow the restart in the event some have unsaved data (like an open notepad that hasn't been saved).
Active today
I've seen accounts freeze during logon and doing what @efrimpol recommends worked for me. I believe it has something to do with the profile trying to connect to a domain controller. When you disconnect the network cable it reverts to the local saved credentials and often logs in normal speed.
Have you tried this?
Have you tried this?
I believe that I provided a proper method to access the server. And I'm sure that once he put the space in between the server IP Address and /admin it worked as expected.
Active 1 day ago
Hi Folks,
I never did get my client to try the login (without the Cat 5 attached) as recommended. by Jeffrey.
Sorry that I did not resolve the question here.
The server is in the same state it was in several months ago.
Wondering what will happen I if I force a reboot by powering the server down manually.
Thanks for your help and consideration!
I never did get my client to try the login (without the Cat 5 attached) as recommended. by Jeffrey.
Sorry that I did not resolve the question here.
The server is in the same state it was in several months ago.
Wondering what will happen I if I force a reboot by powering the server down manually.
Thanks for your help and consideration!
Lee and Kane were the ones who suggested logging via admin console or command line.
I suggested pulling the network plug on the unit and logging directly via the console.
You really don't want to do an improper shut down of the server since you stated it is running Exchange services.
Are you able to get in contact with the client and try to direct log in?
I suggested pulling the network plug on the unit and logging directly via the console.
You really don't want to do an improper shut down of the server since you stated it is running Exchange services.
Are you able to get in contact with the client and try to direct log in?
Active 1 day ago
Also just tried to login with the Cat 5 cable disconnected as recommended by efrimpol - sorry it was not Jeffrey). Same results as before.
Still wondering about a hard reboot in this situation.
Still wondering about a hard reboot in this situation.
If you MUST shut the server down, then end the services for Exchange Remotely.
Try this on your computer (you must be a member of Admin Group for this to work):
Start, Control Panel Administrative Tools Services.
You will see the services running on your computer. Now select Action Connect to another computer.
Type in the FQDN or IP address of the server.
It may take a while but hopefully it will list the services running on the remote server.
Now you safely end services relating to Exchange (this will probably start with MS Exchange).
This link talks about creating a script to do this:
http://exchange.sembee.info/2007/shutdown-script.asp
but I would just look at the services being listed so you can see what order to shut the services down.
If you succeed in doing this, then yes, you can safely reboot the server.
Try this on your computer (you must be a member of Admin Group for this to work):
Start, Control Panel Administrative Tools Services.
You will see the services running on your computer. Now select Action Connect to another computer.
Type in the FQDN or IP address of the server.
It may take a while but hopefully it will list the services running on the remote server.
Now you safely end services relating to Exchange (this will probably start with MS Exchange).
This link talks about creating a script to do this:
http://exchange.sembee.info/2007/shutdown-script.asp
but I would just look at the services being listed so you can see what order to shut the services down.
If you succeed in doing this, then yes, you can safely reboot the server.
Featured Post
Ransomware – malware that gets on your customers’ computers, encrypts their data, and extorts a hefty ransom for the decryption keys – is a surging new threat. The purpose of this eBook is to educate the reader about ransomware attacks.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
A safe way to clean winsxs folder from your windows server 2008 R2 editions
I was prompted to write this article after the recent World-Wide Ransomware outbreak. For years now, System Administrators around the world have used the excuse of "Waiting a Bit" before applying Security Patch Updates. This type of reasoning to me …
This tutorial will give a short introduction and overview of Backup Exec 2012 and how to navigate and perform basic functions.
Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as conne…
This tutorial will show how to configure a single USB drive with a separate folder for each day of the week. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten.
The USB drive must be s…
Suggested Courses
Course of the Month8 days, 6 hours left to enroll
Earn Certification
MCSA Configuring Windows 7 Exam 70-680
$49.00$44.10
729 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.