Many organizations still have servers running Windows 2003. The default number of sessions for Terminal Server, Remote Desktop Protocol (RDP), is two without add more licenses. If an administrators disconnects from the server instead of logs out, there will be open RDP sessions. If you need to login for some DBA task you are performing, you might get the following screen which states all connections are full.
How do over come this situation?
There are two solutions that you can try:
1 – Use the admin console option of the terminal services program (mstsc).
2 – Use system internals light weight execution program (psexec)
We currently have a problem on machine name satpdb01. The syntax to log onto the machine using a administrator console is the following. It will prompt your for an admin account and password.
mstsc /v:satpdb01 /f /admin
The system internals program is more powerful since it will work when the RDP service is having issues. The syntax to log onto the machine in a command shell is the following. It will prompt you for a password.
psexec \\satpdb01 -u
If you are using the first solution, open a command shell from the run or search prompt.
In summary, administrators should log off the server when they are done their work. Following the instructions in this article will help you regain a server that has no more terminal sessions. However, being polite to other administrators is a life style choice. Point out the error of their ways and share this article with them.
Cloud TagsAFTER ALTER TABLE ALTER TRIGGER CPAN perl modules CREATE DATABASE create function CREATE FUNTION create procedure CREATE TABLE create trigger create view database administrator database developer DATA TYPES DDL DECLARE DELETE DROP DATABASE DROP TRIGGER DROP VIEW execute EXISTS FORMAT free code INSERT ISNULL John F. Miner III perl script REPLACE SELECT sp_help sp_helptext SQL Server SQL Server Management Studio SSMS. string function sys.databases sys.objects sys.schemas TRIGGERS TRUNCATE TABLE TSQL UPDATE USER DEFINED VIEW vb script