Home » SQL Server Error : 10026, Severity: 16. No command text was set.

SQL Server Error : 10026, Severity: 16. No command text was set.

sql server DBA 999

SQL Server Error : 10026 Details

SQL Server Error: 10026
Severity: 16
Event Logged or not: No
No command text was set.
Severity 16 Description:
Indicates general errors that can be corrected by the user.

Reading sql server error log location from SQL Query

Identifying SQL Server Error Log File used by SQL Server Database Engine can be done by reading SQL Server Error Logs. DBA can execute the XP_READERRORLOG extended stored procedure to read the SQL Server Error Log and search for its location used by the instance of SQL Server.

USE master
xp_readerrorlog 0, 1, N'Logging SQL Server messages in file', NULL, NULL, N'asc'

For other ways to read and find error log location please our artcile https://sqlserver-dba.co.uk/error-log/sql-server-identify-location-of-the-sql-server-error-log-file.html

Solution for Resolving the Error

There are various possible causes for these error messages. 
To check whether you can fix the problem, follow the instructions below.
Check that you can ping the SQL Server box
Ensure that the client machine can ping the physical server/VM where SQL Server is installed. 
If it doesn’t work, try connecting to SQL Server with an IP Address (for default instance) or an IP Address
Check if Instance Name is working with odbc (for named instance).
fixing SQL server connection problems
You can add the SQL Server machine to the /etc/host file if it resolves using an IP address. 
To add the entry to the /host file, open the host file with Notepad and type percent SystemRoot percent system32driversetc in the run window.
Now we be able to connect to the SQL Server using the machine name rather than the IP address.
Use an IP address to connect to the SQL server.
Step 2: Verify that the SQL Services are operational.
Ensure that the SQL services are up and operating. 
SQL Server services can be checked with the SC command or SQL Server Configuration Manager. 
The SQL Server instance may not be running on several occasions.

Alternate Solutions

  1. Restarting SQL Server Service(non production instances only)

  • To Restart, Start or Stop the SQL Server instance by right click on sql server instance in SSMS or in SQL. You may need to open SSMS as administrator to start, stop the instance.


  • Other ways for restarting SQL server Service

  1. From SQL Configuration manager from Start menu
  2. From Services in Windows server
  3. From Cmd using net start and net stop

2.Checking SQL Performance metrics like CPU, Memory

Check SQL Server CPU, Memory usage, longest running queries, deadlocks etc.. using activity monitor or sp_who2.

To view Activity Monitor in SQL Server 2005 and in SQL Server 2008, a user must have VIEW SERVER STATE permission.

2 Different Ways to Open up Activity Monitor in SQL Server 2008 are mentioned below:

Open up Activity Monitor Using Object Explorer

In Object Explorer, right click the SQL Server 2008 Instance and click on Activity Monitor.

Also can be opened from SQL Server 2008 Management Studio’s toolbar, by clicking Activity Monitor

Opening SQL Server Activity Monitor method2

SSMS Activity Monitor by Method2

It shows the graphical display of Processor Time (%), Number of Waiting Tasks, Database I/O (MB/Sec) and the Number of Batch Requests/second.

For information on SQL Server Activity monitor go to https://sqlserver-dba.co.uk/sql-server-administration-basics/activity-monitor

Or using SQL Query analyzer window to run sp_who2 command which is less resource intensive and gives same information as activity monitor.

2.Checking Windows Performance metrics like CPU, Memory, Disk Space etc.

  1. Open task manager to check CPU, Memory usage etc.
  2. Open file explorer to check Disk space on each drive.


SQL Server Error Code and solution summary

SQL Server Error: 10026
Severity: 16
Event Logged or not: No
No command text was set.

Leave a Reply

Your email address will not be published. Required fields are marked *