Bobcares

WeSupport

Call Us! 1-800-383-5193
Call Us! 1-800-383-5193
Call Us! 1-800-383-5193

Need Help?

Emergency Response Time custom

Our experts have had an average response time of 11.55 minutes in January 2021 to fix urgent issues.

We will keep your servers stable, secure and fast at all times for one fixed price.

SQL server error 1326 – How to fix

by | Feb 8, 2021

Stuck with SQL server error 1326? We can help you.

Often SQL server error 1326 pops up when we connect to the SQL server.

Usually, this happens when the IIS Service does not have any rights to use the named pipe.

Here at Bobcares, we often receive requests to solve such SQL errors as part of our Server Management Services.

Today let’s see how our Support Engineers fix this error for our customers.

How to fix SQL server error 1326 on Windows 10?

In order to gain access to Windows NT named pipe, the client must be validated by the Windows NT server

Before going to the steps to fix this error, we will do the basic troubleshooting steps given below:

  • Checking whether named pipe/TCP enabled or not.
  • Remote connections allowed or not.
  • Checking if Windows Firewall is off.
  • Ensuring that there is ping the SQL Server box.
  • Verifying that the SQL Services are running.
  • Checking the port number which the SQL Server is using.

Now let’s see some of the methods that are used by our Support Engineers to fix this:

1. Creating an exception for port 1433 in Windows firewall.

The steps to follow are given below:

1. First, go to Control Panel and click on Windows Firewall

2. From there go to the exception tab.

2. Then we click on Add Port and enter the port number and name.

3. Here we can see the SQL name in the exception tab list.

4. Finally click on the OK button.

2. Enabling mixed authentication.

If we are using the SQL Server Authentication we can enable the mixed authentication for fixing this error.

The steps to follow are given below:

1. First, go to the Properties, then take the Security page under the Server authentication section.

2. Then we will choose the SQL Server and Windows Authentication mode radio button.

3. Finally, we will restart the service.

This will fix the error being faced.

[Still, stuck with the error? We are happy to help you.]

 

3. Restart MSSQL service.

Sometimes SQL server error 1326 can be fixed by restarting the service.

To restart the service we can do the following steps:

1. First, go to the control panel and open the Local services window.

2. After that we can select the MSSQLSERVER service and restart.

( Or )

1. First, go to Run and give services.msc

2. Then right-click on SQL Server name and select Restart

 

 

Conclusion

In short, the SQL server error 1326 has raised because the IIS Service does not have any rights to use the named pipe. Today, we saw the main reason for the SQL error and how our Support Engineers fix it.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

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

server management

Spend time on your business, not on your servers.

TALK TO US

Or click here to learn more.

Categories:

Tags: