I cannot connect to my local SQL Server Express (2012, but the version shouldn’t matter) from my server (Windows 2008 R2) to use a tool on it (APEX SQL Data Diff if you are wondering). I can browse the network servers fine, and select my local instance from the dropdown of available servers, but when I go to search tables on the server, it times out with this error message (same is true of SSMS).
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: SQL
Network Interfaces, error: 28 — Server doesn’t support strong text
requested protocol) (Microsoft SQL Server, Error: -1)
I have enabled the firewall — that’s not it.
I have allowed remote connections — that’s not it.
SQL Server Browser service is on and passed through the firewall — that’s not it.
I can connect fine with the same tools TO the server, but FROM the server it fails.
Any ideas?
Usually, the error ‘SQL Network Interfaces error 28’ occurs while trying to connect to SQL Server instance either using SQL Server Management Studio or using any other way.
Here at Bobcares, we have seen several such SQL related issues as part of our Server Management Services for web hosts and online service providers.
Today we’ll take a look at the cause for this error and see how to fix it.
What causes ‘SQL Network Interfaces error 28’ error to occur
Before we get into the solution part, let’s first discuss the causes for this error to occur. Here are the different reasons for this error to occur.
- Invalid SQL Server instance name.
- Disabling of Remote access for your SQL Server instance name
- The ports used by SQLBROWSER.EXE and SQLSERVR.EXE is blocked. As a result, the firewall on the server refuses to connect.
- The SQL Server Browser service (sqlbrowser) is not started.
For instance, the error appears as below.
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: SQL Network Interfaces, error: 28 – Server doesn’t support requested protocol)How we fix the error ‘SQL Network Interfaces error 28’
Here are the suggestions our Support Engineers provide to our customers to resolve this error.
Validate that the Server on which the SQL server is hosted is reachable by the client machine. For that, you can run ping and telnet to check the connectivity.
Ensure that the SQL server is running well on your server. For that, make sure to check SQL Server services.
The firewall ports like 1433 for SQL Server and 1434 for SQL Server Browser must be open.
Verify that the SQL Server Instance name is correct. Also, check the spelling of the SQL Server Instance name that is mentioned in the connection string.
In case you have named instance like SERVERNAMESQL2017, then make sure to enter the full SQL Server Instance name.
Make sure to start the SQL Server Browser service on the server.
Enable Remote connection for your SQL Server Instance. You can enable SQL Server to accept remote connections over the TCP or named pipes protocols by using the SQL Server Configuration Manager tool. Here are the steps to enable remote connections.
- First, launch SQL Server Configuration Manager. Then from the left side pane expand SQL Server Network Configuration and then click Protocols for InstanceName. If your server has a default instance then it will look like “Protocols for MSSQLSERVER”
- Now, you must be able to see all three protocols in the right-side panel. They are Shared Memory, Named Pipes, and TCP/IP.
- Enable Named Pipes and TCP/IP. For that, right-click at the protocol name and then click Enable. Now, the icon for the protocol will change to show that the protocol is enabled.
- Finally, restart the SQL Server services to bring the changes into effect.
[Need any further assistance in fixing SQL errors? – We’re available 24*7]
Conclusion
In short, this error occurs while trying to connect to SQL Server instance either using SQL Server Management Studio or using any other way. Today, we saw how to fix this SQL error.
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»;
I cannot connect to my local SQL Server Express (2012, but the version shouldn’t matter) from my server (Windows 2008 R2) to use a tool on it (APEX SQL Data Diff if you are wondering). I can browse the network servers fine, and select my local instance from the dropdown of available servers, but when I go to search tables on the server, it times out with this error message (same is true of SSMS).
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: SQL
Network Interfaces, error: 28 — Server doesn’t support strong text
requested protocol) (Microsoft SQL Server, Error: -1)
I have enabled the firewall — that’s not it.
I have allowed remote connections — that’s not it.
SQL Server Browser service is on and passed through the firewall — that’s not it.
I can connect fine with the same tools TO the server, but FROM the server it fails.
Any ideas?
Symptoms
ERROR: S0022:[Microsoft][ODBC SQL Server Driver][SQL Server] Invalid column name ‘reference_code’This error occurs when generating a report to the transaction level and using reference codes in the Row Format.
Status
Due to the introduction of Budget Reference codes within Epicor’s eBackOffice 7.3.5, a new column of data was introduced in the glbuddet table.
This SMR has been fixed in R06670 Service Pack, please check our website (www.FRxSoftware.com) for availability of Service Packs for your General Ledger. You may also sign up for automatic notification of Services on our website .
Workaround
Resolution:There are two options available to workaround this issue: Upgrade Epicor eBackOffice to v7.3.5 Roll back the latest FRx Service Pack to R04670 (v6.7.4031)
References
Need more help?
I cannot connect to my local SQL Server Express (2012, but the version shouldn’t matter) from my server (Windows 2008 R2) to use a tool on it (APEX SQL Data Diff if you are wondering). I can browse the network servers fine, and select my local instance from the dropdown of available servers, but when I go to search tables on the server, it times out with this error message (same is true of SSMS).
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: SQL
Network Interfaces, error: 28 — Server doesn’t support strong text
requested protocol) (Microsoft SQL Server, Error: -1)
I have enabled the firewall — that’s not it.
I have allowed remote connections — that’s not it.
SQL Server Browser service is on and passed through the firewall — that’s not it.
I can connect fine with the same tools TO the server, but FROM the server it fails.
Any ideas?
I cannot connect to my local SQL Server Express (2012, but the version shouldn’t matter) from my server (Windows 2008 R2) to use a tool on it (APEX SQL Data Diff if you are wondering). I can browse the network servers fine, and select my local instance from the dropdown of available servers, but when I go to search tables on the server, it times out with this error message (same is true of SSMS).
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: SQL
Network Interfaces, error: 28 — Server doesn’t support strong text
requested protocol) (Microsoft SQL Server, Error: -1)
I have enabled the firewall — that’s not it.
I have allowed remote connections — that’s not it.
SQL Server Browser service is on and passed through the firewall — that’s not it.
I can connect fine with the same tools TO the server, but FROM the server it fails.
Any ideas?
Я не могу подключиться к локальному SQL Server Express (2012, но версия не должна иметь значения) с моего сервера (Windows 2008 R2), чтобы использовать на нем инструмент (APEX SQL Data Diff, если вам интересно). Я могу просматривать сетевые серверы нормально, и выбрать мой локальный экземпляр из выпадающего списка доступных серверов, но когда я иду искать таблицы на сервере, он истекает с этим сообщением об ошибке (то же самое верно для SSMS).
ошибка, связанная с сетью или экземпляром произошло при установлении соединения с SQL Server. Сервер не найден или
был недоступен. Убедитесь, что имя экземпляра правильно и что
SQL Server настроен на разрешение удаленных подключений. (поставщик: службы SQL
Сетевые интерфейсы, ошибка: 28-сервер не поддерживает сильный текст
запрошенный протокол) (Microsoft SQL Server, ошибка: -1)
Я включил брандмауэр-это не так.
Я разрешил удаленные подключения — это не так он.
служба браузера SQL Server включена и проходит через брандмауэр — это не так.
Я могу подключиться нормально с теми же инструментами до сервер, но С сервер не удается.
какие идеи?
3 ответов
там, кажется, нет другой записи Stack Exchange на этом, и никто не фиксирует проблему полностью, так что здесь он идет.
спасибо в этой статье для меня где-то с сообщением об ошибке.
Проблема в том, что необходимые сетевые протоколы по умолчанию отключены в SQL Server Express. Мне пришлось локально перейти в Диспетчер конфигурации Sql Server и включить «именованные каналы»и» TCP/IP».
После этого необходимо перезапустить браузер SQL Server и SQL Службы сервера (экземпляра).
хотя мне это не нужно, вам также может потребоваться проверить «сетевую конфигурацию SQL Server» в разделе «протоколы» для параметров, которые необходимо настроить там.
надеюсь, это поможет кому-то еще!
диспетчер конфигурации SQL:
на картинке выбрана неправильная группа на панели ссылок: это должна быть конфигурация сети SQL Server → протоколы для SQLEXPRESS.
Не забудьте также проверить в разделе «Конфигурация сети SQL Server» — > протоколы для YourInstance. Я был болваном и тоже забыл туда заглянуть.
Today I am going to discuss about Microsoft SQL Server Error 28 that most of the SQL Server users might have faced at least once in their career. It belongs to SQL Server connectivity issue SQL Network Interfaces Error 28.
Microsoft SQL Server Error 28
This is very common error that most of the people have gone through. Microsoft SQL Server Error 28 details are given below:
An error has occurred while establishing a connection to the server. When connecting to SQL Server, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 28 – Server doesn’t support requested protocol) (Microsoft SQL Server, Error: -1)
Sometime you might get same error as below description.
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: SQL Network Interfaces, error: 28 – Server doesn’t support requested protocol)
Root Cause
Generally, we get SQL Network Interfaces Error 28 while connecting to SQL Server instance either using SQL Server Management studio or using any other way. There might be several reasons behind generating Microsoft SQL Server Error 28. I have tried to capture all such reasons in below points..
- A specified SQL Server instance name is not valid. Wrong SQL Server Instance Name can lead to generate Microsoft SQL Server Error 28.
- Remote access is not enabled for your SQL Server instance.
- The firewall on the server has refused the connection because ports used by SQLBROWSER.EXE and SQLSERVR.EXE is still blocked.
- The SQL Server Browser service (sqlbrowser) is not started.
Solution
We need to check and validate multiple factors to fix Microsoft SQL Server error 28. Check all factors given in below step by step points to fix all possibilities for this SQL error 28.
- Validate whether server on which SQL Server is hosted is reachable from your client machine or not. Run ping and telnet to make sure server connectivity.
- Make sure SQL Server is running fine on your server. Check SQL Server services.
- Firewall ports 1433 for SQL Server and 1434 for SQL Server Browser services should be opened.
- Verify correct SQL Server Instance name. Check the spelling of the SQL Server instance name that is specified in the connection string.
- Make sure to enter full SQL Server Instance name in case you have named instance like SERVERNAMESQL2017.
- Make sure that the SQL Server Browser service is started on the server.
- Enable Remote connection for your SQL Server Instance. Most of the people face Microsoft SQL Server error 28 because remote connection was disabled on the SQL Server Instance. Use the SQL Server Configuration Manager tool to enable SQL Server to accept remote connections over the TCP or named pipes protocols. Below steps you can follow to enable remote connections.
- Launch SQL Server Configuration Manager. Expand SQL Server Network Configuration from left side pane and then click Protocols for InstanceName. If your server has default instance then it will look like “Protocols for MSSQLSERVER”
- You can see all three protocols in right side pane. Shared Memory, Named Pipes and TCP/IP.
- Make sure to enable Named Pipes and TCP/IP. Right-click at the protocol name and then click Enable. The icon for the protocol will change to show that the protocol is enabled.
- You need to restart the SQL Server services to bring the changes into effect so restart your SQL Server services.
Related Articles
- Fix SQL Server Error 40: A Network related or Instance specific Error Occurred while establishing a connection to SQL Server
- How to Fix SQL Server Error 53: Could Not Open a Connection on SQL Server?
- Fix Error 4064: Cannot open user default database
- SAP Connectivity Issue After AlwaysON Automatic failover
- Fix Error 976: Cannot connect to Secondary Replica of AOAG
Here, i have shown you how to fix sql error 28. I hope you like this article. Please follow our Facebook page and Twitter handle to get latest updates.
- Author
- Recent Posts
I am working as a Technical Architect in one of the top IT consulting firm. I have expertise on all versions of SQL Server since SQL Server 2000. I have lead multiple SQL Server projects like consolidation, upgrades, migrations, HA & DR. I love to share my knowledge. You can contact me on my social accounts for any consulting work.
Summary
Article Name
Fix: SQL Network Interfaces Error 28 – Server doesn’t support requested protocol
Description
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: SQL Network Interfaces, error: 28 – Server doesn’t support requested
Author
Manvendra Deo Singh
Publisher Name
www.techyaz.com
- Remove From My Forums
-
Question
-
Hello room,
I have 3 window servers 2003 running in window virtual server 2005.
Server1 has 3 instances of sql 2005
— SQLDev01
— SQLDev02
— SQLDev03Server2 has 3 instance of sql 2005
— SQLDev01
— SQLDev02
— SQLDev03Serve3 has 3 instance of sql 2005
— SQLDev01
— SQLDev02
— SQLDev03The servers are running in DC.
The sql server was setup with Window authentication mode only.I was unable to add the server 2 or 3 sql instances into my register server1sqldev01.
steps:
1. Right click the database engine
2. Select New and Server Registration
3 Select the sql server name. eg: Server2sqldev01.Error msg: An error has occurred while establishing a connection to the server.
When connection to SQL Server 2005, this failure may be caused by the fact that under
the default setting SQL Server does not allow remote connections. (provider: SQL Network
Interfaces, error: 28 — Server doesn’t support request protocol)All the sql instances’services are running under single domain user account.
e.g: sqladmin.Thanks for the help.
When I initially downloaded SQL Server Express the System tables were visible using SQL Server Management Studio Express. I was able to create a new database and define and populate a couple of small tables. I then attempted to set up an ODBC SQL Natvie Client connection so that I could print the table contents using Crystal Reports. That failed with the following error message:
«An error 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 setting SQL Server does not allow remote connections.»
I subsequently uninstalled and reinstalled SQL Server Express. Now, I get the following error message whenever I try to connect to the database using SQL Server Management Studio Express. Additionally, the System tables are no longer visible. However, I can access my database via the Server Explorer in VS2005.
TITLE: Connect to Server
——————————
Cannot connect to STAN-DELLSQLEXPRESS.
——————————
ADDITIONAL INFORMATION:
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: SQL Network Interfaces, error: 28 — Server doesn’t support requested protocol) (Microsoft SQL Server, Error: -1)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476
February 28, 2008 at 6:10 pm
#120048
Hello room,
I have 3 window servers 2003 running in window virtual server 2005.
Server1 has 3 instances of sql 2005
— SQLDev01
— SQLDev02
— SQLDev03
Server2 has 3 instance of sql 2005
— SQLDev01
— SQLDev02
— SQLDev03
Serve3 has 3 instance of sql 2005
— SQLDev01
— SQLDev02
— SQLDev03
The servers are running in DC.
The sql server was setup with Window authentication mode only.
I was unable to add the server 2 or 3 sql instances into my register server1sqldev01.
steps:
1. Right click the database engine
2. Select New and Server Registration
3 Select the sql server name. eg: Server2sqldev01.
Error msg: An error has occurred while establishing a connection to the server.
When connection to SQL Server 2005, this failure may be caused by the fact that under
the default setting SQL Server does not allow remote connections. (provider: SQL Network
Interfaces, error: 28 — Server doesn’t support request protocol)
All the sql instances’services are running under domain user name.
e.g: sqladmin.
Thanks for the help.
February 28, 2008 at 6:38 pm
#783556
Can your virtual machines actually see each other at all? Simple ping test will verify that in short order.
What ports are the various instances listening on? You will probably need to specify the port in the connection details or ensure that SQL Browser is running on the server you are trying to connect to.
Scott Duncan
MARCUS. Why dost thou laugh? It fits not with this hour.
TITUS. Why, I have not another tear to shed;
—Titus Andronicus, William Shakespeare
Vivien Xing
SSChampion
Points: 12297
February 28, 2008 at 8:23 pm
#783568
Ed7
SSCrazy Eights
Points: 8516
February 28, 2008 at 8:41 pm
#783573
The 3 servers can ping each other via ip address and computer names.
Ed7
SSCrazy Eights
Points: 8516
February 28, 2008 at 8:42 pm
#783574
I was trying to setup database mirroring and run into this issue 🙂
Sugesh Kumar
One Orange Chip
Points: 27311
February 29, 2008 at 9:05 am
#783870
Do you have remote connection set to on on your server?
Big Data Man
SSCrazy Eights
Points: 8536
February 29, 2008 at 9:17 am
#783887
Hi,
Have you enabled remote connections using the Surface Area Configuration tool? Also, check what ports your named instances are listening on using SQL Server Configuration Manager tool.
Thanks,
Phillip Cox
MCITP — DB Admin
Ed7
SSCrazy Eights
Points: 8516
February 29, 2008 at 1:24 pm
#784029
Sugesh,
Can you more specifics and give the steps on setup remote connection.?
Thank you.
TJ
Adam Bean
One Orange Chip
Points: 26631
February 29, 2008 at 1:41 pm
#784038
Is TCP/IP enabled in SQL Server Configuration Manager per instance?
Ed7
SSCrazy Eights
Points: 8516
February 29, 2008 at 2:00 pm
#784041
Phillip,
Ops!! I have not enabled the remote connection on Surface Area Configuration tool.
Thank you for your valuable advice.
Regards,
TJ 🙂
Big Data Man
SSCrazy Eights
Points: 8536
Hi Edwin,
Excellent result and appreciate update!
Thanks,
Phillip Cox
MCITP — DBAdmin
I cannot connect to my local SQL Server Express (2012, but the version shouldn’t matter) from my server (Windows 2008 R2) to use a tool on it (APEX SQL Data Diff if you are wondering). I can browse the network servers fine, and select my local instance from the dropdown of available servers, but when I go to search tables on the server, it times out with this error message (same is true of SSMS).
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: SQL
Network Interfaces, error: 28 — Server doesn’t support strong text
requested protocol) (Microsoft SQL Server, Error: -1)
I have enabled the firewall — that’s not it.
I have allowed remote connections — that’s not it.
SQL Server Browser service is on and passed through the firewall — that’s not it.
I can connect fine with the same tools TO the server, but FROM the server it fails.
Any ideas?
Usually, the error ‘SQL Network Interfaces error 28’ occurs while trying to connect to SQL Server instance either using SQL Server Management Studio or using any other way.
Here at Bobcares, we have seen several such SQL related issues as part of our Server Management Services for web hosts and online service providers.
Today we’ll take a look at the cause for this error and see how to fix it.
What causes ‘SQL Network Interfaces error 28’ error to occur
Before we get into the solution part, let’s first discuss the causes for this error to occur. Here are the different reasons for this error to occur.
- Invalid SQL Server instance name.
- Disabling of Remote access for your SQL Server instance name
- The ports used by SQLBROWSER.EXE and SQLSERVR.EXE is blocked. As a result, the firewall on the server refuses to connect.
- The SQL Server Browser service (sqlbrowser) is not started.
For instance, the error appears as below.
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: SQL Network Interfaces, error: 28 – Server doesn’t support requested protocol)How we fix the error ‘SQL Network Interfaces error 28’
Here are the suggestions our Support Engineers provide to our customers to resolve this error.
Validate that the Server on which the SQL server is hosted is reachable by the client machine. For that, you can run ping and telnet to check the connectivity.
Ensure that the SQL server is running well on your server. For that, make sure to check SQL Server services.
The firewall ports like 1433 for SQL Server and 1434 for SQL Server Browser must be open.
Verify that the SQL Server Instance name is correct. Also, check the spelling of the SQL Server Instance name that is mentioned in the connection string.
In case you have named instance like SERVERNAMESQL2017, then make sure to enter the full SQL Server Instance name.
Make sure to start the SQL Server Browser service on the server.
Enable Remote connection for your SQL Server Instance. You can enable SQL Server to accept remote connections over the TCP or named pipes protocols by using the SQL Server Configuration Manager tool. Here are the steps to enable remote connections.
- First, launch SQL Server Configuration Manager. Then from the left side pane expand SQL Server Network Configuration and then click Protocols for InstanceName. If your server has a default instance then it will look like “Protocols for MSSQLSERVER”
- Now, you must be able to see all three protocols in the right-side panel. They are Shared Memory, Named Pipes, and TCP/IP.
- Enable Named Pipes and TCP/IP. For that, right-click at the protocol name and then click Enable. Now, the icon for the protocol will change to show that the protocol is enabled.
- Finally, restart the SQL Server services to bring the changes into effect.
[Need any further assistance in fixing SQL errors? – We’re available 24*7]
Conclusion
In short, this error occurs while trying to connect to SQL Server instance either using SQL Server Management Studio or using any other way. Today, we saw how to fix this SQL error.
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»;
Symptoms
ERROR: S0022:[Microsoft][ODBC SQL Server Driver][SQL Server] Invalid column name ‘reference_code’This error occurs when generating a report to the transaction level and using reference codes in the Row Format.
Status
Due to the introduction of Budget Reference codes within Epicor’s eBackOffice 7.3.5, a new column of data was introduced in the glbuddet table.
This SMR has been fixed in R06670 Service Pack, please check our website (www.FRxSoftware.com) for availability of Service Packs for your General Ledger. You may also sign up for automatic notification of Services on our website .
Workaround
Resolution:There are two options available to workaround this issue: Upgrade Epicor eBackOffice to v7.3.5 Roll back the latest FRx Service Pack to R04670 (v6.7.4031)
References
Need more help?
Want more options?
Explore subscription benefits, browse training courses, learn how to secure your device, and more.
Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.