Sei sulla pagina 1di 2

ERRMSG: "A network-related or instance-specific error occurred while establishin

g a connection to SQL Server ..."


Modified on: Tue, 23 Feb, 2016 at 9:13 PM
Product:
EzParts Electronic Parts Catalog Software.
Problem:
When you try to connect to EzParts electronic parts catalog software client to M
SSQL Server, the following error message appears: "A network-related or instance
-specific error occurred while establishing a connection to SQL Server. The serv
er was not found or was not accessible. Verify that the instance name is correct
and that SQL Server is configured to allow remote connections."
Solution:
This error message informs you that it is not possible to connect to MSSQL Serve
r and EzParts electronic parts catalog software will not connect to the EzParts
database. The possible reasons and the step for elimination are described below:
1) MSSQL Server is not started. Starting of it will allow you to see your MSSQL
Server/instance in the drop-down list of available MSSQL Servers.
a) Go to the Start menu -> Control Panel -> Administration Tools -> Services.
b) In the list of services find SQL Server (instance name, by default it is EZPA
RTS5) and check its status, it must be Started (if it is not started, then right
click on SQL Server and select Start from the context menu).
2) Firewall is blocking port 1433 (MSSQL standard port for connections). It can
be disabled following the steps below:
a) Go to the Start menu -> Control Panel -> Administration Tools -> Services.
b) Find Firewall service, it must be disabled (if it is not, then right click th
e service and select Stop from the context menu).
Note: More information on this can be found on the official Microsoft site: http
://msdn.microsoft.com/en-us/library/cc646023.aspx
3) TCP/IP protocol is disabled for MSSQL protocols. To enable it, see the steps
below:
a) Navigate to SQL Server Configuration Manager in the Start menu.
b) Specify settings for TCP/IP protocol in SQL Server Configuration Manager.
c) Restart the computer.
Note: More information on this can be found on the official Microsoft site: http
://msdn.microsoft.com/en-us/library/bb909712%28v=vs.90%29.aspx
4) Make sure your database engine is configured to accept remote connections (If
you are using centralized database):
a) Open SQL Server Management Studio.
b) Right click SQL Server instance -> Properties -> Connections -> Check the Al
low remote connections to this server box.
c) Go to the General section and check name of SQL Server specified in the Name
field.
5) If you are using a named SQL Server instance, make sure you are using that in
stance name in your connection strings. Usually the format needed to specify the
database server is machinename\instancename.
6) Make sure your login account has access permission on the database you used d
uring login.
Alternative:
If you still can t get any connection, you may want to create a SQL account on the
server, a corresponding SQL user on the database in question, and just use this
username/password login data to connect to SQL Server.

Potrebbero piacerti anche