Ms sql server ошибка 1326

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.

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;

Scenario :

• The error occurs when trying to connect to a database from a website. 

Cannot connect to Database Server.

Fix 1 :

Basic checks to be done for this error :

• Named pipe/TCP is enabled.

• Remote connections are allowed.

• Windows Firewall is off.

Go to Control Panel -> Click on Windows Firewall -> Go to exception tab as shown below. 

    4.     Click on Add Port… and enter the port number and name.

    5.     Click on Add Program -> Add C:\Program Files\Microsoft SQL Server\90\Shared location\SQLBrowser.exe in exception list.

    6.     Click ok and save the changes. 

Fix 2 :

Go to control panel -> Open Local services window -> select MSSQLSERVER service and restart.

( Or )

Go to run -> services.msc -> right click on SQL Server name and select “Restart” as shown below :

Fixes are applicable to the following versions of SQL Server:

• SQL Server 1.1 (16 bit)

• SQL Server 4.2A (16 bit)

• SQL Server 4.2B (16 bit)

• SQL Server 4.21a

• SQL Server 6.0

• SQL Server 6.5

• SQL Server 7.0

• SQL Server 7.0 OLAP Tools

• SQL Server 2000

• SQL Server 2000 64-bit Edition

• SQL Server 2005

• SQL Server 2008

• Azure SQL DB

• SQL Server 2008 R2

• SQL Server 2012

• SQL Server 2014

• SQL Server 2016

Related Error Tags :

• i get sql error 1326 when connect to other computer

• SQL Server 2008 R2 — Cannot Connect Remotely (Error 1326)

• Resolving could not open a connection to SQL Server errors

• Error (1326) in SQL Server 2008 R2

• How do I get this SQL Server ODBC Connection working?

• SQL Server 2008 — Connection Error 1326

• Sql Error 1326 : Cannot connect to Database server

Problem Description:

Microsoft SQL database: [][State =01000][Error=1326][Microsoft][ODBC SQL Server Driver] [SQL Server]”Logon failure: unknown user name or bad password.

sql server error 1326 windows 10
sql server error 17
named pipes provider: could not open a connection to sql server (53)

Cause of the issue

Error 1326 means “Logon failure: unknown user name or bad password.” This error is raised because the IIS Service does not have any rights to use the named pipe.

Or It’s possible, even likely, that SQL Express is not listening on port 1433. By default, we use dynamic TCP ports, which is why you need SQL Browser to be running in the first place. Check out http://support.microsoft.com/kb/914277 which it a different take on enabling remote connections through the firewall.

Explanation:

A client must be validated by the Windows NT server before being granted access to a Windows NT named pipe. This is usually performed through a

1.Workgroups-style validation in which the client and server produce identical identities and passwords

2. the domain method in which both the client and server are domain members.

IIS produces a Windows NT ID named IUSR machine-name (where machine name is the name of the Windows NT server) and adds that user to the Guest local group during the setup process. This Windows NT account is used to execute the IIS service.

IIS employs the Windows NT account IUSR machine-name if the connection to IIS is anonymous, and any network activity performed by IIS is done under this account ID.

Named pipes connections work and validation is successful if the SQL server and IIS are on the same server.
If SQL is installed on a different server than IIS, the IUSR machine name account must be confirmed on the Windows NT server where SQL is installed.

Solution for Resolving The Problem

This account must be verified by the server hosting Microsoft SQL Server in order for the connection to occur properly. If this account is not verified, then the connection fails and provides only the line number in the script file of the attempted connection opening.

To resolve this problem, you can use one of the following options:

1. Enable the Windows NT ID Guest.
2. Make the Windows NT user, IUSR_Machine-Name, a member of the domain where SQL server resides.
3. Use the account information from Internet Service Manager to set up a local user account on the Windows NT Server that hosts SQL Server.
4. Make sure named pipes provider is enabled for error relating to “named pipes provider: could not open a connection to sql server”
5. Make sure firewall exceptions are added for sql server for remote access if ” a network-related or instance-specific error in sql server 2014 error 26 ” or ” microsoft sql server error 53 “

Try below if above does not resolve if 2005 version

1. Using the SQL Server 2005 Surface Area Configuration tool, enable remote connections to accept both local and remote connections.
2. Using SQL Server Configuration Manager, configure the same TCP for both SQLSERVER(EXPRESS) and SQL Native Client port protocols. Use the default port (1433) if possible, but it must be the same for both the Server and Client components. Remember to re-initialize both the SQL Server and SQL Browser services.
3. Add sqlservr.exe and sqlbrowser.exe as exceptions to your firewall (which was the source of the problem). In SQL Server 2005, you don’t need to use the netsh command.

Before installing the SQL Native Client, I was able to login remotely using the SQL Compact Edition that came with the LAP. The only thing I didn’t like about it was that I couldn’t utilize a Trusted Connection and had to rely on the SQL sa user and password instead.