Microsoft sql server error 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»;

[{«Product»:{«code»:»SSSH5A»,»label»:»Rational ClearQuest»},»Business Unit»:{«code»:»BU053″,»label»:»Cloud & Data Platform»},»Component»:»Database Configuration/Connectivity — SQL Server»,»Platform»:[{«code»:»PF033″,»label»:»Windows»}],»Version»:»2002.05.00;2002.05.20;2003.06.00;2003.06.01;2003.06.10;2003.06.12″,»Edition»:»»,»Line of Business»:{«code»:»LOB45″,»label»:»Automation»}}]

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 FilesMicrosoft SQL Server90Shared locationSQLBrowser.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

---

---

There might be various reasons for above error, but this case is very specific to a situation where SQL Server was installed on a machine which was in Workgroup whereas the backup destination was the server located in the domain.  Here is the error message seen in SQL Agent job history. Let us learn about how to fix Operating system error 1326.

Executed as user: NT ServiceSQLSERVERAGENT. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60
 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved.
 Started: 12:23:24 PM Progress: 2016-12-27 12:23:25.00 Source: {229AB1E3-E7E5-4185-B305-BF0F7657122A}
 Executing query “DECLARE @Guid UNIQUEIDENTIFIER EXECUTE msdb..sp…”.: 100% complete End Progress Error:
 2016-12-27 12:23:25.35 Code: 0xC002F210 Source: Back Up Database Task Execute SQL Task
 Description: Executing the query “BACKUP DATABASE [master] TO DISK = N’192.168.3….” failed with the following error:
 “Cannot open backup device ‘192.168.3.55backupSharemaster_backup_2016_12_27_122325_2407734.bak’.
 Operating system error 1326(Logon failure: unknown user name or bad password.).
 BACKUP DATABASE is terminating abnormally.”. Possible failure reasons:
 Problems with the query, “ResultSet” property not set correctly, parameters not set correctly, or connection
 not established correctly.
 End Error

Generally, when the backup is taken SQL Agent Service account is used to take backup. In this case since SQL was on Workgroup, it was NT ServiceSQLSERVERAGENT. This account is not a valid account to validate for a domain.

VERIFICAITON

First, let’s verify that we are hitting the same issue which I experienced. From Workgroup machine, we would try to query remote share using xp_cmdshell. Here is the command.

xp_cmdshell 'dir 192.168.3.55backupShare'

This command should fail with below error.

Logon failure: unknown user name or bad password.

SOLUTION

Since we are talking about authentication issue. So, we need to make sure that we map a drive to SQL Server (not windows). As per SQL Server Books-On-Line:

“For a network share to be visible to SQL Server, the share must be mapped as a network drive in the session in which SQL Server is running”

Here is the command to map the drive.

EXEC XP_CMDSHELL 'net use Z: 192.168.3.55backupShare password@123 /User:domainuser'

Once the above is completely successful, we should be able to see content on the Z drive by running below command.

EXEC XP_CMDSHELL 'dir Z:'

After this we should be able to take backup on the Z drive as its mapped within SQL Server as a drive.

Backup database master to disk = 'Z:master.bak'

The above command should work and create the backup file in 192.168.3.55backupShare

Have you encountered this error earlier? Did you find this solution interesting? Please comment and let me know.

Reference: Pinal Dave (https://blog.sqlauthority.com)

First appeared on SQL SERVER – Cannot open backup device. Operating system error 1326 (Logon failure: unknown user name or bad password.)

Tags:

SQL Server

Written by Pinal Dave

Pinal Dave is a Microsoft Technology Evangelist (Database and BI). He has written over 1700 articles on the subject on his blog at http://blog.sqlauthority.com. He is a dynamic and proficient Principal Database Architect who specializes in SQL Server Performance Tuning and has 7+ years of hands-on experience. He holds a Masters of Science degree and a number of certifications, including MCTS, MCDBA and MCAD (.NET). He is also Regional Mentor for PASS Asia. Prior to joining Microsoft he was awarded Microsoft MVP award for three continuous years for his contribution in community.

Home > SQL Server 2008 > SQL Server 2008 to Windows Server 2008 Connection Error 1326

SQL Server 2008 to Windows Server 2008 Connection Error 1326

SQL Server 2008 to Windows Server 2008 Connection Error 1326 Having installed SQL Server 2008 on a Windows Server 2008 with a firewall, all along I thought it’s just a matter of allowing SQL Server’s port 1433 in the Windows Firewall to accept incoming connections and everything should be just fine.  But unfortunately, this was not the case because I was not able to connect to SQL Server. Windows Firewall on Windows Server 2008 helps prevent unauthorized access to computer resources.  However, if the firewall is configured incorrectly, which is the case I am in, attempts to connect to an instance of SQL Server may be blocked.  To access an instance of SQL Server that is behind the firewall, the firewall must be configured on the computer that is running SQL Server. After adding SQL Server’s port 1433 to my firewall to accept incoming network connections, I get the following error message: Cannot connect to 10.10.10.1 Additional Information A network-related or instance-specific error occurred while establishing a connection to SQL Server.  The server was not found or was not accessible.  Verify that the instance name is correct and that SQL Server is configured to allow remote connections.  (provider: Named Pipes Provider, error:40 — Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 1326). Automatically Opening the Firewall Port for SQL Server on Windows Server 2008 To fix the problem automatically, download the fix from the following link: Microsoft Fix it 50169.  Click Run in the File Download dialog box, and then follow the steps in the wizard.  Alternatively, instead of clicking on Run, you may opt to click on Save to save the file locally before running it.  This may be useful so that you can simply copy the file to all your servers that you want to open the firewall port for SQL Server. The wizard may be in English only; however, the automatic fix also works for other language versions of Windows. Reference: How do I open the firewall port for SQL Server on Windows Server 2008? Manually Opening the Firewall Port for SQL Server on Windows Server 2008 The following script and the procedure in executing the script opens the firewall ports for SQL Server. To create the script, follow these steps: Start Notepad. Copy and paste the following code into Notepad: @echo ========= SQL Server Ports =================== @echo Enabling SQLServer default instance port 1433 netsh firewall set portopening TCP 1433 "SQLServer" @echo Enabling Dedicated Admin Connection port 1434 netsh firewall set portopening TCP 1434 "SQL Admin Connection" @echo Enabling conventional SQL Server Service Broker port 4022 netsh firewall set portopening TCP 4022 "SQL Service Broker" @echo Enabling Transact-SQL Debugger/RPC port 135 netsh firewall set portopening TCP 135 "SQL Debugger/RPC" @echo ========= Analysis Services Ports ============== @echo Enabling SSAS Default Instance port 2383 netsh firewall set portopening TCP 2383 "Analysis Services" @echo Enabling SQL Server Browser Service port 2382 netsh firewall set portopening TCP 2382 "SQL Browser" @echo ========= Misc Applications ============== @echo Enabling HTTP port 80 netsh firewall set portopening TCP 80 "HTTP" @echo Enabling SSL port 443 netsh firewall set portopening TCP 443 "SSL" @echo Enabling port for SQL Server Browser Service's 'Browse' Button netsh firewall set portopening UDP 1434 "SQL Browser" @echo Allowing multicast broadcast response on UDP (Browser Service Enumerations OK) netsh firewall set multicastbroadcastresponse ENABLE Save the file as a .txt file by using the following name: OpenSqlServerPort.txt Rename the OpenSqlServerPort.txt file to the following: OpenSqlServerPort.bat Copy the OpenSqlServerPort.bat file to the computer which has the firewall that has the SQL Server 2008 installed and run the script on that computer.  To run the script, follow these steps: Click Start, click Run, type cmd, and then click OK. At the command prompt, use the cd command to navigate to the folder in which you saved the OpenSqlServerPort.bat file. To run the script, type OpenSqlServerPort.bat at the command prompt, and then press ENTER. Reference: How do I open the firewall port for SQL Server on Windows Server 2008?

Related Articles :

What’s New in SQL Server 2008

Ошибка. Сервер базы данных не обнаружен

Я

   Kongo2019

31.01.22 — 08:24

Пытаюсь создать новую базу получаю ошибку «Сервер базы данных не обнаружен Microsoft SQL Server Native Client 11.0: Поставщик именованных каналов: Не удалось открыть соединение с SQL Server [1326].

HRESULT=80004005, HRESULT=80004005, HRESULT=80004005, SQLSrvr: SQLSTATE=08001, state=1, Severity=10, native=1326, line=0″,

попытался создать новую базу через консоль 1с сервера тот же самый результат.

Брадмаузер выключен, другие базы работают, все перегрузил, в Студию захожу, базу создать могу. Указываю везде IP.

1С:Предприятие 8.3 (8.3.19.1150), MS SQL sql 13.0.4001.0(2016)

   Фрэнки

1 — 31.01.22 — 08:34

т.е. все базы уже были созданы под мсскл и после установки обновленной платформы создание новой базы оказалось сломано?

   Kongo2019

2 — 31.01.22 — 08:35

(1) Не обновлял платформу на этом сервере

   ads55

3 — 31.01.22 — 09:13

(2) Логин пароль у сервера 1с правильные?

   Ёпрст

4 — 31.01.22 — 09:57

   Kongo2019

5 — 31.01.22 — 09:57

(3) Студию захожу, базу создать могу.

   Aleksey

6 — 31.01.22 — 10:05

   Ёпрст

7 — 31.01.22 — 10:05

(5) какая авторизация стоит в скуле ? Какой логин пароль прописываешь в кластере 1с ? Какой адрес сервера скуля прописан в кластере 1с ?

   Kongo2019

8 — 31.01.22 — 10:08

(4)А это мысль, включены оба. Глянул через профайлер, 1с сервер работает со скулем через сеть.

   Kongo2019

9 — 31.01.22 — 10:10

(6) Однозначно нет. Брамаузер вырублен. Старые базы работают, как сервере так и по сети.

   Kongo2019

10 — 31.01.22 — 10:12

(7)Естественно локальный SQL. И все конечно же под sa.

   Kongo2019

11 — 31.01.22 — 10:13

Ладно, это тестовый. Пойду 1С сервер грохну и переставлю заново.

   Kongo2019

12 — 31.01.22 — 10:42

А вот фиг, не помогло.

Скуль еще что ли переставить?

   Aleksey

13 — 31.01.22 — 10:46

и все таки проверь порты, может они заняты.

У меня на домашнем компе стоит windows 10, и после очередного обновления системные службы винды стали занимать порт 1540 и 1541, т.е. сервер 1с при установки из коробки не стартует, приходиться его на другие порты перенастраивать

   Kongo2019

14 — 31.01.22 — 11:24

   Ёпрст

15 — 31.01.22 — 11:40

(14) не верный логин/пароль в свойствах базы указан.

   Biker

16 — 31.01.22 — 11:41

попробуй отключи ipv6

   Kongo2019

17 — 31.01.22 — 12:04

(15) И фигли он тогда работает при выключенной сети? Гномик бегает паролю меняет? Типа как лампочку в холодильнике выключает?

   Kongo2019

18 — 31.01.22 — 12:04

(16) Выключено, я эту фигню сразу выключаю.

   ads55

19 — 31.01.22 — 12:35

(17) Второй сервак с таким же именем (при выключенной сети)

   Kongo2019

20 — 31.01.22 — 12:40

(19) Точно нет.

Я задрался, тупо снес нафуй, поднял бекап виртуалки, предновогодний. Все заработало.

Админа поймаю надеру задницу. Что он там накрутил зараза такая.

   Dmitrii

21 — 31.01.22 — 15:37

Возможно, пользователь, под которым 1С подключается к СУБД не имеет прав на создание баз.

Тогда создай базу на сервере БД средствами СУБД. Например, в MS-SQL Server Management Studio (MS-SMS).

Укажи пользователя, под которым подключается сервер 1С к СУБД, владельцем (owner) этой базы.

Создай базу в кластере серверов 1С с указанием параметров базы, созданной вручную на предыдущих шагах.

(21) Делал. Сервер 1С при включенной сети не видит новые базы. При выключенной сети все ок. Так что админу ухи надеру когда поймаю. Явно что с сетевым стеком накрутил.

SQL SERVER – FIX : ERROR : (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server) (Microsoft SQL Server, Error: )

Regular readers of my blog are aware of the fact that I have written about this subject umpteen times earlier, and every time I have spoken about a new issue related to it. Few days ago, I had redone my local home network. I have LAN setup with wireless router connected with my four computers, two mobile devices, one printer and one VOIP solution. I had also formatted my primary computer and clean installed SQL Server 2008 into it. Yesterday, incidentally, I was sitting in my yard trying to connect SQL Server located in home office and suddenly I stumbled upon the following error. Finding the solution was the most infuriating part as it consumed my precious 10 minutes.

Let us look at few of the common errors received:

An error has occurred while establishing a connection to the server.

(provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 5)

An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 1326)

I eventually found the resolution to this error on this blog itself; so I was saved from hunting for the solution. I am sure there are a number of developers who had previously fixed this error while installing SQL Server 2008 or SQL Server 2005 but in due course forgot the right solution to this error. This is just a quick refresher. Make sure to bookmark this as you never know when you would need this solution.

Let us check into the steps to resolve this error.

      1)    SQL Server should be up and running.

Go to All Programs >> Microsoft SQL Server 2008 >> Configuration Tools >> SQL Server Configuration Manager >> SQL Server Services, and check if SQL Server service status is “Running”.

I have confronted numerous situations when these nerve-wracking errors crop up, and most of the time when I try to troubleshoot I notice that SQL Server services are neither running nor installed. If SQL Server is not installed as default instance SQL Server Browser should be running together with it; we will explore this further in Topic 5.

      2)    Enable TCP/IP in SQL Server Configuration

When two or more SQL Servers are connected across network they do all communication using TCP/IP. The default port of SQL Server installation is 1433. This port can be changed through SQL Server Configuration Manager. TCP/IP should be enabled for SQL Server to be connected.

Go to All Programs >> Microsoft SQL Server 2008 >> Configuration Tools >> SQL Server Configuration Manager >> Select TCP/IP

Right Click on TCP/IP >> Click on Enable

You must restart SQL Server Services for all the changes to take effect. Right click and go to menu properties to select location where default port of SQL Server can be changed.

       3)    Open Port in Windows Firewall

Windows Firewall is very efficacious in protecting the Operating system from all sorts of malicious attacks. By default, many of the ports and services are refrained from running byfirewall. Time and again, SQL Server ports are not open in firewall as well. All the ports on which SQL Server is running should be added to exception and firewall should filter all the traffic from those ports. As described, by default SQL Server runs on port 1433, but ifdefault port is changed then the new port should be added to exception. If SQL Server has named instance (another instance besides default instance) is installed, SQL Server browsershould also be added to the exception, as described in Step 7.

Go to Control Panel >> Windows Firewall >> Change Settings >> Exceptions  >> Add Port

Make the following entries in popup “Add a Port” and click OK.

Name:Sql
PortNumber:1433
Protocol:  Select TCP

       4)    Enable Remote Connection

Enabling remote connection is another important, yet oft-neglected step that is frequently missed by database administrators while setting up SQL Server. If this feature is turned off SQL Server will function smoothly on local machine, but it will let another server connect to it remotely. By default this feature is ON in SQL Server 2008.

Right click on the server node and select Properties.

Go to Left Tab of Connections and check “Allow remote connections to this server”

5) Enable SQL Server Browser Service

If SQL Server is not installed as default instance but instead installed as named instance and also if there is no specific TCP/IP port configured, it will give rise to the error that is being discussed in this article. If SQL Server Browser service is enabled, it will allow the server to be connected through dynamic TCP/IP port. Enabling this service is a one-time process, as on enabling it once it will apply to all the instances installed on the same server.

Go to All Programs >> Microsoft SQL Server 2008 >> Configuration Tools >> SQL Server Configuration Manager >> SQL Server Browser

Right Click on SQL Server Browser >> Click on Enable

If Click on Enable (Start) is Not allowing to click, then click on Properties >>Service>>

Start-Mode change it to Automatic /Manual >> Apply>>Ok >> Right Click on SQL Server Browser >> Click on Enable.

6) Create exception of sqlbrowser.exe in Firewall

As elucidated in Step 6, sqlbrowser service needs to be enabled for named instance. Windows Firewall may prevent sqlbrowser.exe to execute. So, it is imperative to addexception for the same in windows firewall.

Search for sqlbrowser.exe on your local drive where SQL Server is installed. Copy the path of the sqlbrowser.exe like C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe and create the exception of the file in Firewall, as delineated in Step 3.

7) Recreate Alias

It is getting quite common to create alias of SQL Server and use it in application. This will ensure that in future if any physical SQL Server has to be moved, it will not be required to change any code or connection string. You can simply create alias with the same name pointing to different SQL Server and it will start working instantaneously. I have observed that a couple of times due to internal error while recreating alias this error was fixed.

Go to All Programs >> Microsoft SQL Server 2008 >> Configuration Tools >> SQL Native Client 10.0 Configuration >> Aliases

Delete the alias that is giving problem and recreate it with identical parameters.

I have tried my best to include all the methods of fixing this error and if I have missed any, please leave a comment and I will be very glad to include them here. I have put in my effort to encompass this issue in one article that needs to be refereed when any connection error comes up.