Cannot not connect to SQL Server instance.

Hello,
I have SQL Server 2012 installed and when I run this command:
sc query mssql$MSSQLSERVER
I get this error:
[SC] EnumQueryServicesStatus:OpenService FAILED 1060:
The specified service does not exist as an installed service.
I run this command on the same server where SQL Server is installed. Databases are on the same server too. TCP/IP is enabled for the instance and port 1433 is open on the server's firewall. SQL Server Browser is running.
Many errors in the SQL Server error logs like:
SQLServer Error: 11001, A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct.
SQLServer Error: 11001, TCP Provider: No such host is known. [SQLSTATE 08001]
Any ideas what could have gone wrong?
Thanks,
Paul
Paul

Hi Paul,
According to your description, you fail to connect to SQL Server 2012 instance. According to the SQL Server error log, based on my research, your issue could be due to that
the client cannot resolve the name of the SQL Server instance.
Are the errors from the SQL Server error log solved? If the errors are not solved, please follow the steps below to troubleshoot the issue.
1. Make sure you are able to ping the physical server where SQL Server is installed from the client machine. If not, you can try to connect to the SQL Server using an IP Address (for default instance) or IP Address\Instance Name
for a named instance.
2. Make sure you are using the correct instance name. When you connect to a default instance, machine name is the best representative for the instance name and when you connect to a named instance such as sqlexpress, you should
specify machinename\instancename according to
Niting123’s post. And you could verify if you use the right instance name in SQL Server configuration manager according to
Niting123’s post.
3. Check that SQL Server is in the network. You can use the SQLCMD -L command to retrieve the list of SQL Server installed in the network. Note that this will only return SQL Servers if the SQL Server Browser service is running.
4. Make sure that you enable Named Pipes besides TCP/IP protocol.
5. Check to see if remote connections is enabled. Right click on the server name in SSMS and select Properties. Go to the Connections tab and make sure Allow remote connection to this server is checked.
6. Locally connect to SQL Server and check the error log for the port entry.
7. To connect to SQL Server instance using TCP/IP from another computer, on the SQL Server computer, you must configure the firewall to allow connections to the TCP port used by the Database Engine. If you are connecting to a named
instance or a port other than TCP port 1433, you must also open the UDP port 1434 for the SQL Server Browser service according to pasquale’s post.
For step by step instruction on opening a port in the Windows firewall, see
How to: Configure a Windows Firewall for Database Engine Access
For more information about the process, please refer to the article:
http://www.mssqltips.com/sqlservertip/2340/resolving-could-not-open-a-connection-to-sql-server-errors/
In addition, you mention that there are many other errors, so please provide the SQL Server error log for analysis.
Regards,
Michelle Li

Similar Messages

Could not connect to SQL Server 2012 Remotely

Hello,
I have a situation as follows:
The Server
SQL Server 2012 Standard Edition installed on Windows Server 2012 Standard Edition
Active Directory is installed on the same server as well
Remote Access Role added and configured to connect VPN
DNS Role added
Windows Firewall is disabled
The Server is connected to the internet
SQL Server Service & SQL Browser both are running under domain accounts
SQL Server allows remote connections
The Router
The router that connects the server to the Internet is configured to:
Enable VPN Tunnels Protocols (PPTP, L2TP and IPSec)
Forwarding > Virtual Servers (all requests on TCP and UDP on all ports to the server local IP)
The Client
PC running Windows 7 SP1 with SQL Server 2012 Express
Joined AD on the server
Connected to the internet
VPN Connected to the Server
Can Remote Desktop the Server
Can ping the server host name
Can nslookup the server host name
The Problem
If Both the Server and the Client are connected in the same Local Area Network, Client can connect to the SQL Serve
Once the Client is placed in different location connected to the Interent, VPN connected as described above, I could not connect to the Server using:
Windows Authentication Domain Users or
SQL Server users
and the error message is:
Cannot connect to SERVER\SQLINSTANCE.
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:
SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476
Any thoughts
Thanks in advance

Hello Hilary,
I have been working on a small replication test.
On the Publisher, things went smooth and the Snapshot Agent was able to work and produce a snapshot written in a shared folder located on the Publisher
On the Subscriber, as I am testing from SQL Server Express, I had run the following command:
replmerg.exe -Publisher [SERVER\SQLInstance] -PublisherDB [dbRepl] -PublisherSecurityMode 0 -PublisherLogin rplMergeAgent -PublisherPassword p@ssw0rd -Publication [TEST Publication] -Distributor [SERVER\SQLInstance] -DistributorSecurityMode 0 -DistributorLogin
rplMergeAgent -DistributorPassword p@ssw0rd -Subscriber [SUBSCRIBER\SQLInstance] -SubscriberSecurityMode 0 -SubscriberLogin rplMergeAgent -SubscriberPassword p@ssw0rd -SubscriberDB [dbRepl] -SubscriptionType 1 -OutputVerboseLevel 2 -Output C:\TEMP\mergeagent.log
Where
SERVER
Publisher and Distributor
dbRepl
Database to replicate
Merge Agent
rplMergeAgent
Subscriber
SUBSCRIBER
dbRepl
Subscriber Database
Merge Agent
rplMergeAgent
Password
p@ssw0rd
rplMergeAgent
SQL Login defined in both Publisher and Subscriber with same password
Granted the following at Publisher:
Login to Publication Database (dbRepl)
Login to Distribution Database (distribution)
Member of PAL
Granted the following at Subscriber:
db_owner fixed database role in Subscription database (dbRepl)
I couldn't grant rplMergeAgent Read Permission on SnapshotFolder as it is only a SQL Login.
When I ran the above command line, I received the following error:
Message: The schema script 'Person_2.sch' could not be propagated to the subscriber.
I am pasting below the whole log file written by the above command:
2014-04-11 15:38:07.205 Microsoft SQL Server Merge Agent 11.0.2218.0
2014-04-11 15:38:07.342 Copyright (c) 2008 Microsoft Corporation
2014-04-11 15:38:07.389
2014-04-11 15:38:07.406 The timestamps prepended to the output lines are expressed in terms of UTC time.
2014-04-11 15:38:07.433 User-specified agent parameter values:
-Publisher SERVER\SQLInstance
-PublisherDB dbRepl
-PublisherSecurityMode 0
-PublisherLogin rplMergeAgent
-PublisherPassword **********
-Publication TEST Publication
-Distributor SERVER\SQLInstance
-DistributorSecurityMode 0
-DistributorLogin rplMergeAgent
-DistributorPassword **********
-Subscriber SUBSCRIBER\SQLInstance
-SubscriberSecurityMode 0
-SubscriberLogin rplMergeAgent
-SubscriberPassword **********
-SubscriberDB dbRepl
-SubscriptionType 1
-OutputVerboseLevel 2
-Output C:\TEMP\mergeagent.log
2014-04-11 15:38:07.497 Percent Complete: 0
2014-04-11 15:38:07.517 Connecting to Subscriber 'SUBSCRIBER\SQLInstance'
2014-04-11 15:38:07.518 Connecting to OLE DB Subscriber at datasource: 'SUBSCRIBER\SQLInstance', location: '', catalog: 'dbRepl', providerstring: '' using provider 'SQLNCLI11'
2014-04-11 15:38:07.608 OLE DB Subscriber: SUBSCRIBER\SQLInstance
DBMS: Microsoft SQL Server
Version: 10.50.4000
catalog name: dbRepl
user name: rplMergeAgent
API conformance: 0
SQL conformance: 0
transaction capable: 1
read only: F
identifier quote char: "
non_nullable_columns: 0
owner usage: 15
max table name len: 128
max column name len: 128
need long data len:
max columns in table: 1000
max columns in index: 16
max char literal len: 131072
max statement len: 131072
max row size: 131072
2014-04-11 15:38:07.613 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': select SERVERPROPERTY ('ProductVersion')
2014-04-11 15:38:07.617 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': set nocount on declare @dbname sysname select @dbname = db_name() declare @collation nvarchar(255) select @collation = convert(nvarchar(255), databasepropertyex(@dbname, N'COLLATION')) select
collationproperty(@collation, N'CODEPAGE') as 'CodePage', collationproperty(@collation, N'LCID') as 'LCID', collationproperty(@collation, N'COMPARISONSTYLE') as 'ComparisonStyle',cast(case when convert (int,databasepropertyex (@dbname,'comparisonstyle')) &
0x1 = 0x1 then 0 else 1 end as bit) as DB_CaseSensitive,cast(case when convert (int,serverproperty ('comparisonstyle')) & 0x1 = 0x1 then 0 else 1 end as bit) as Server_CaseSensitive set nocount off
2014-04-11 15:38:07.637 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': {?=call sp_helpsubscription_properties (N'SERVER\SQLInstance', N'dbRepl', N'TEST Publication')}
2014-04-11 15:38:07.681 Distributor security mode: 0, login name: rplMergeAgent, password: ********.
2014-04-11 15:38:07.682 Percent Complete: 0
2014-04-11 15:38:07.683 Connecting to Distributor 'SERVER\SQLInstance'
2014-04-11 15:38:07.684 Connecting to OLE DB Distributor at datasource: 'SERVER\SQLInstance', location: '', catalog: '', providerstring: '' using provider 'SQLNCLI11'
2014-04-11 15:38:25.062 OLE DB Distributor: SERVER\SQLInstance
DBMS: Microsoft SQL Server
Version: 11.00.2100
catalog name:
user name: guest
API conformance: 0
SQL conformance: 0
transaction capable: 1
read only: F
identifier quote char: "
non_nullable_columns: 0
owner usage: 15
max table name len: 128
max column name len: 128
need long data len:
max columns in table: 1000
max columns in index: 16
max char literal len: 131072
max statement len: 131072
max row size: 131072
2014-04-11 15:38:28.887 OLE DB Distributor 'SERVER\SQLInstance': select SERVERPROPERTY ('ProductVersion')
2014-04-11 15:38:29.842 OLE DB Distributor 'SERVER\SQLInstance': {call sp_helpdistpublisher (N'SERVER\SQLInstance') }
2014-04-11 15:38:32.198 OLE DB Distributor 'SERVER\SQLInstance': select datasource, srvid from master..sysservers where upper(srvname) = upper(N'SERVER\SQLInstance')
2014-04-11 15:38:33.199 OLE DB Distributor 'SERVER\SQLInstance': {call sp_MShelp_merge_agentid (0,N'dbRepl',N'TEST Publication',null,N'dbRepl',100,N'SUBSCRIBER\SQLInstance')}
2014-04-11 15:38:34.451 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:38:34.560 OLE DB Distributor 'SERVER\SQLInstance': {call sp_MShelp_profile (23, 4, N'')}
2014-04-11 15:38:36.189 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:38:36.499 OLE DB Distributor 'SERVER\SQLInstance': {call sys.sp_get_redirected_publisher(N'SERVER\SQLInstance',N'dbRepl',0)}
2014-04-11 15:38:37.396 Percent Complete: 0
2014-04-11 15:38:37.396 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:38:37.399 Initializing
2014-04-11 15:38:37.401 OLE DB Distributor 'SERVER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:38:37.403 Connecting to OLE DB Publisher at datasource: 'SERVER\SQLInstance', location: '', catalog: 'dbRepl', providerstring: '' using provider 'SQLNCLI11'
2014-04-11 15:38:38.427 Percent Complete: 0
2014-04-11 15:38:38.428 Validating publisher
2014-04-11 15:38:38.429 OLE DB Distributor 'SERVER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:38:39.455 Percent Complete: 0
2014-04-11 15:38:39.456 Connecting to Publisher 'SERVER\SQLInstance'
2014-04-11 15:38:39.457 OLE DB Distributor 'SERVER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:38:46.548 OLE DB Publisher: SERVER\SQLInstance
DBMS: Microsoft SQL Server
Version: 11.00.2100
catalog name: dbRepl
user name: rplMergeAgent
API conformance: 0
SQL conformance: 0
transaction capable: 1
read only: F
identifier quote char: "
non_nullable_columns: 0
owner usage: 15
max table name len: 128
max column name len: 128
need long data len:
max columns in table: 1000
max columns in index: 16
max char literal len: 131072
max statement len: 131072
max row size: 131072
2014-04-11 15:38:50.282 OLE DB Publisher 'SERVER\SQLInstance': set nocount on declare @dbname sysname select @dbname = db_name() declare @collation nvarchar(255) select @collation = convert(nvarchar(255), databasepropertyex(@dbname, N'COLLATION')) select collationproperty(@collation,
N'CODEPAGE') as 'CodePage', collationproperty(@collation, N'LCID') as 'LCID', collationproperty(@collation, N'COMPARISONSTYLE') as 'ComparisonStyle',cast(case when convert (int,databasepropertyex (@dbname,'comparisonstyle')) & 0x1 = 0x1 then 0 else 1 end
as bit) as DB_CaseSensitive,cast(case when convert (int,serverproperty ('comparisonstyle')) & 0x1 = 0x1 then 0 else 1 end as bit) as Server_CaseSensitive set nocount off
2014-04-11 15:38:57.393 OLE DB Publisher 'SERVER\SQLInstance': select SERVERPROPERTY ('ProductVersion')
2014-04-11 15:38:59.236 Connecting to OLE DB Publisher at datasource: 'SERVER\SQLInstance', location: '', catalog: 'dbRepl', providerstring: '' using provider 'SQLNCLI11'
2014-04-11 15:39:07.271 OLE DB Publisher: SERVER\SQLInstance
DBMS: Microsoft SQL Server
Version: 11.00.2100
catalog name: dbRepl
user name: rplMergeAgent
API conformance: 0
SQL conformance: 0
transaction capable: 1
read only: F
identifier quote char: "
non_nullable_columns: 0
owner usage: 15
max table name len: 128
max column name len: 128
need long data len:
max columns in table: 1000
max columns in index: 16
max char literal len: 131072
max statement len: 131072
max row size: 131072
2014-04-11 15:39:45.229 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:39:45.234 Percent Complete: 0
2014-04-11 15:39:45.235 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:39:45.236 Retrieving publication information
2014-04-11 15:39:45.238 OLE DB Distributor 'SERVER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:39:46.287 Percent Complete: 0
2014-04-11 15:39:46.288 Retrieving subscription information.
2014-04-11 15:39:46.290 OLE DB Distributor 'SERVER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:40:00.472 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:40:00.478 Percent Complete: 0
2014-04-11 15:40:00.479 Applying the snapshot to the Subscriber
2014-04-11 15:40:00.480 OLE DB Distributor 'SERVER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:40:02.535 OLE DB Distributor 'SERVER\SQLInstance': select datasource, srvid from master..sysservers where upper(srvname) = upper(N'SERVER\SQLInstance')
2014-04-11 15:40:03.559 OLE DB Distributor 'SERVER\SQLInstance': {call sys.sp_MSadd_mergesubentry_indistdb (0,N'SERVER\SQLInstance',N'dbRepl',N'TEST Publication',N'SUBSCRIBER\SQLInstance',N'dbRepl',1,1,0,N'',?,90)}
2014-04-11 15:40:04.600 Connecting to OLE DB Subscriber at datasource: 'SUBSCRIBER\SQLInstance', location: '', catalog: 'dbRepl', providerstring: '' using provider 'SQLNCLI11'
2014-04-11 15:40:04.609 OLE DB Subscriber: SUBSCRIBER\SQLInstance
DBMS: Microsoft SQL Server
Version: 10.50.4000
catalog name: dbRepl
user name: rplMergeAgent
API conformance: 0
SQL conformance: 0
transaction capable: 1
read only: F
identifier quote char: "
non_nullable_columns: 0
owner usage: 15
max table name len: 128
max column name len: 128
need long data len:
max columns in table: 1000
max columns in index: 16
max char literal len: 131072
max statement len: 131072
max row size: 131072
2014-04-11 15:40:04.611 OLE DB Subscriber: SUBSCRIBER\SQLInstance
DBMS: Microsoft SQL Server
Version: 10.50.4000
catalog name: dbRepl
user name: rplMergeAgent
API conformance: 0
SQL conformance: 0
transaction capable: 1
read only: F
identifier quote char: "
non_nullable_columns: 0
owner usage: 15
max table name len: 128
max column name len: 128
need long data len:
max columns in table: 1000
max columns in index: 16
max char literal len: 131072
max statement len: 131072
max row size: 131072
2014-04-11 15:40:07.454 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': sp_MSacquiresnapshotdeliverysessionlock
2014-04-11 15:40:07.526 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': sp_MStrypurgingoldsnapshotdeliveryprogress
2014-04-11 15:40:07.530 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': sp_MSissnapshotitemapplied @snapshot_session_token = N'\\SERVER\Snapshot\unc\SERVER$SQLInstance_DBREPL_TEST PUBLICATION\20140411082109\', @snapshot_progress_token = N'\\SERVER\Snapshot\unc\SERVER$SQLInstance_DBREPL_TEST
PUBLICATION\20140411082109\Person_2.sch'
2014-04-11 15:40:24.659 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': sp_MSreleasesnapshotdeliverysessionlock
2014-04-11 15:40:24.663 The schema script 'Person_2.sch' could not be propagated to the subscriber.
2014-04-11 15:40:24.665 OLE DB Subscriber 'SUBSCRIBER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:40:24.690 Percent Complete: 18
2014-04-11 15:40:24.692 The schema script 'Person_2.sch' could not be propagated to the subscriber.
2014-04-11 15:40:24.693 OLE DB Distributor 'SERVER\SQLInstance': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2014-04-11 15:40:27.541 Percent Complete: 0
2014-04-11 15:40:27.542 Category:NULL
Source: Merge Replication Provider
Number: -2147201001
Message: The schema script 'Person_2.sch' could not be propagated to the subscriber.
2014-04-11 15:40:28.563 Percent Complete: 0
2014-04-11 15:40:28.565 Category:AGENT
Source: SUBSCRIBER\SQLInstance
Number: 0
Message: The process could not read file '\\SERVER\Snapshot\unc\SERVER$SQLInstance_DBREPL_TEST PUBLICATION\20140411082109\Person_2.sch' due to OS error 1326.
2014-04-11 15:40:28.566 Disconnecting from OLE DB Subscriber 'SUBSCRIBER\SQLInstance'
2014-04-11 15:40:28.568 Disconnecting from OLE DB Subscriber 'SUBSCRIBER\SQLInstance'
2014-04-11 15:40:28.569 Disconnecting from OLE DB Subscriber 'SUBSCRIBER\SQLInstance'
2014-04-11 15:40:28.570 Disconnecting from OLE DB Subscriber 'SUBSCRIBER\SQLInstance'
2014-04-11 15:40:28.571 Disconnecting from OLE DB Publisher 'SERVER\SQLInstance'
2014-04-11 15:40:28.573 Disconnecting from OLE DB Publisher 'SERVER\SQLInstance'
2014-04-11 15:40:28.575 Disconnecting from OLE DB Publisher 'SERVER\SQLInstance'
2014-04-11 15:40:28.577 Disconnecting from OLE DB Publisher 'SERVER\SQLInstance'
2014-04-11 15:40:28.578 Disconnecting from OLE DB Distributor 'SERVER\SQLInstance'
2014-04-11 15:40:28.579 Disconnecting from OLE DB Distributor 'SERVER\SQLInstance'
I can say it is about how can the rplMergeAgent read the Shared folder.
What do you think?

Could not connect to sql server 2008 R2

TITLE: Connect to Server
Cannot connect to SURENDRA-PC\MSSQLSERVER.
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:
SQL Network Interfaces, error: 25 - Connection string is not valid) (Microsoft SQL Server, Error: 87)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=87&LinkId=20476
BUTTONS:
OK

Hi Shravan,
According to my research, besides the causes from SQL Server services, firewall, protocol according to other people’s posts, the issue could also be due to the wrong server name, or the remote connections are not allowed. To work around your issue, please
pay attention to the points below.
Firstly, for the local connection to SQL Server default instance, please just type [.] dot or 'localhost','(local)' in server name field according to Shashikant’s post.
Secondly, for the remote connection to SQL Server default instance, please make sure that 'Allow remote connections to this server' is checked in Server Connections properties in SQL Server Management Studio referring to the
article. And just type the computer name in server name field, like SURENDRA-PC.
Regards,
Michelle Li

SCOM 2012 Installation does not show the SQL Server Instance for reporting services

I have an issue when I try to install SCOM 2012 with the Reporting Server feature, so in the step that I have to select a SQL Server Instance I cannot do that, because as you can see in the picture no one option appears.
In my scenario I have a DCSERVER, SQLSERVER2008 R2, SCCMSERVER 2012 and in other server I are trying to install SCOM 2012. I are trying to use the same SQLSERVER to SCOM 2012.
Should I do other procedure on SQL Server before to continue? I will apreciate someone could say me what I need to do to resolve this issue.
Regards,
Paul Mendoza.

Hi Paul
Can you confirm that SQL Reporting Services is installed on the server that you are doing the install.
For a lab environment where you have SCOM Management Server, Web Server on one server and SQL Server on another you need to:
- run setup on the SCOM Server and choose NOT to install reporting. The install here will create the OperationsManager database and OperationsManagerDW (reporting) database.
- run setup on the SQL Server where SQL Reporting Services is installed. Then choose to install reporting. You should then see the SQL Reporting Services instance on the above window which is blank in your screenshot.
Take note of the warning in that window - SCOM uses its own role based security within SQL Reporting Services and this can break other reporting. E.g. you can't install SCOM and SCSM reporting (SQL RS component) together.
Cheers
Graham
New SCOM 2012 Blog! - http://www.systemcentersolutions.com/blog/
View OpsMgr tips and tricks at
http://systemcentersolutions.wordpress.com/

Certificate empty in registry. No IP connected to SQL Server instance

Hello,
I have a SQL Server 2008r2 instance running on Windows 2008 clustered physical server. The instance starts, then fails with the following:
2014-01-02 08:41:28.82 Server      Error: 26054, Severity: 16, State: 1.
2014-01-02 08:41:28.82 Server      Could not find any IP address that this SQL Server instance depends upon. Make sure that the cluster service is running, that the dependency relationship between SQL Server and Network Name resources
is correct, and that the IP addresses on which this SQL Server instance depends are available. Error code: 0x103.
2014-01-02 08:41:28.82 Server      Error: 17182, Severity: 16, State: 1.
2014-01-02 08:41:28.82 Server      TDSSNIClient initialization failed with error 0x103, status code 0xa. Reason: Unable to initialize the TCP/IP listener. No more data is available.
2014-01-02 08:41:28.82 Server      Error: 17182, Severity: 16, State: 1.
2014-01-02 08:41:28.82 Server      TDSSNIClient initialization failed with error 0x103, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. No more data is available.
2014-01-02 08:41:28.82 Server      Error: 17826, Severity: 18, State: 3.
2014-01-02 08:41:28.82 Server      Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2014-01-02 08:41:28.82 Server      Error: 17120, Severity: 16, State: 1.
2014-01-02 08:41:28.82 Server      SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
I found: http://support.microsoft.com/kb/2023869. I believe this will resolve my issue, however the command is not quite right. I cannot execute as in the article, but I can run certutil
-store.   There are 4 certificates in the file. Which do I use? Excerpt of file below - there are 0-3 Certificates in the file.
CA
================ Certificate 0 ================
Serial Number: 06376c00aa00648a11cfb8d4aa5c53f4 (numbers changed to protect the innocent)
Issuer: CN=Root Agency
NotBefore: 5/28/1996 4:02 PM
NotAfter: 12/31/2039 5:59 PM
Subject: CN=Root Agency
Signature matches Public Key
Root Certificate: Subject matches Issuer
Template:
Cert Hash(sha1): fe e4 49 ee 0e 39 65 a5 24 6f 00 0e 87 fd e2 a0 65 fd 98 d4 ((numbers changed to protect the innocent)
No key provider information
Cannot find the certificate and private key for decryption.
My certificate value under this registry key is empty.
Any help appreciated,
Dianne
Dianne

Hello ,
Please check below link
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/cc39d8cb-bc64-48e6-8368-24886481dd4f/sql-server-cluster-sql-server-resource-not-coming-online?forum=sqlsetupandupgrade
http://blogs.technet.com/b/taraj/archive/2009/01/07/could-not-find-any-ip-address-that-this-sql-server-instance-depends-upon.aspx
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Addon in Client is not connecting to SQL Server 2005

Hi, we have an add-on, which is working in SBO 2005 with SQL Server 2000.
When the addon tries to connect to the same DB, restored on a SQL Server 2005, the addon is hanging up on the oCompany.Connect method. But this only happens when we try a remote connection from a SBO client.
If we run the addon from the SBO server, where the SQL Server is running too, the addon completes the connection in the expected way.
The SBO Client is connecting to the server, and works fine, but the addon is not connecting to the server.
We try to connect to the server from the client, using SQL Query Analizer from SQL Server 2000, and it works fine too.
Does anyone knows how to fix this issue?
Thanks

Hi Alejandro, thanks for your response.
After installing SBO Patch 20 the add-on is now connecting fine, so I think it must be an upgrade on the new DI API. I noticed the version changes from 6.80.318 to 6.80.319
I had checked the SQL to confirm is was allowing remote connections.
Thank you guys.

Cannot establish connection with SQL server from SQL developer

Hi, I recently downloaded SQL Developer version 3.0.04 and am trying to establish a connection to a remote SQL server. The database was created on this server by someone who is no longer working on the project. I have been given the username, password and server name. Is there another piece of information I am missing? I keep receiving the error:
Status: Failure-Test failed: IO Error: The Network Adapter could not establish the connection.

Check out the SQL Server network configuration. When instances are used the port on which the SQL Server is listening on might be different. Use the networking utility from the SQL Server and check out the SQL Server network details.

Windows 7 64-bit Pro not connecting to SQL Server on domain Windows Server 2008 R2 Standard

I am upgrading computers from Windows XP Professional to Windows 7 Professional but I have a problem getting one of the stock control software programs we use to connect to our SQL Windows Server 2008 R2 Standard from the new Windows 7 computers.
Our computers are connected to a domain and so is the SQL Server. The Windows XP computers allows each standard domain user to log on and connect to the SQL Server via the stock control software program.
But on the Windows 7 Pro computers standard domain users can't connect to the SQL Server but the domain administrator accounts on the same Windows 7 Pro computers can connect to the SQL Server via the stock control program.
I have setup the server alias, server name and port number via the SQL Server Client Network Utility (cliconfg.exe) so I know this isn't the problem as it works when I am logged on as domain administrator.
It seems to be something to do with domain user permissions and Windows 7 Pro. There seems to be a change from Windows XP Pro to Windows 7 Pro that doesn't allow standard domain users to connect to an SQL Server. But I can't find anything about this and
can't workout how to fix it except to make all the users domain administrators which is obviously not a good thing to do. So basically I I think I need to create a group policy that allows the users to connect to the SQL Server but I have no experience doing
this and don't know where to begin.
Thanks for all you guys help and I hope someone can provide me with the solution to this problem.

Hi,
Was there any message?
Please run the stock control software as Administrator to check if it was caused by UAC.
If it could run as administrator, please add the standard domain user to local administrator.
Karen Hu
TechNet Community Support

JTDS not connecting with SQL Server 2008 R2 SP2 + SSL with Java 6 U34-35

Environment:
Windows 7 Pro 32-bit
SQL Server 2008 R2 SP2 (Forced Encryption = Yes, No Certificate provided to server)
Java 6 Update 27-35 and Java 7 Update 2-7
jTDS 1.2.2 and 1.2.6
Under the following setup, our Java application is able to connect to the SQL Server database:
- SQL Server 2008 R2 SP2
- Java 6 Update 27-33 or Java 7 Update 2-5
just switching the JVM to the following would cause the application to be unable to connect to the database:
- Java 6 Update 34 or 35, or Java 7 Update 6 or 7
Browsing through the Java 6 Update 34 release notes, it looks like nothing big was changed, so I'm wondering what has changed with Java 6 U34 and Java 7 U6. I was also looking through a packet sniffer, and indeed the behavior of Java 6 Update 33 and lower was different from Java 6 Update 34 (although I couldn't understand the messages being passed, the number of connections and messages were different).
* This is different from the issue with Java 6 Update 29-30 and Java 7 wherein they were patched for the BEAST SSL vulnerability. That was fixed with the SP2 patch for SQL Server 2008 R2, and for SQL Server 2008 you'd need a hotfix aside from SP3. After patching the server with those updates, Java 6 Update 29-33 and Java 7 U1-5 should be able to connect to the database.
* If I do switch off Force Encryption, all Java versions are able to connect to the database.
Edited by: user1357749 on Oct 12, 2012 1:20 AM

Hi,
It's four months later, but my colleague and I have reproduced the same behavior in both our commercial product, and a very simple example class. It's exactly as you describe it, where the latest versions of both Java 6 and 7 (and several previous versions) hang during the first jTDS SQL query to the DB (immediately after the SSL and handshake). It also happens with the Microsoft JDBC driver.
If you disable the BEAST SSL fix (-Djsse.enableCBCProtection=false), then the connections work without any problems. So, while this is different from the original BEAST SSL problem and subsequent fix, it really seems like some additional changes were made to the fix in a later Java release that broke things.
My colleague has filed a bug with Oracle, and is awaiting a response. We also filed a bug at the jTDS project (#690 - http://sourceforge.net/p/jtds/bugs/690/) that has simple reproduction steps. A contributer at the jTDS project agrees that this seems to be a problem with the JRE, and is not specific to jTDS.
I hope that Oracle will address this issue soon. We need to periodically update the JRE due to vulnerabilities, and we need to have SSL for our JDBC connections for security reasons. This bug puts us and others in a difficult position.

Cannot connect to the specified SQL Server instance

I am trying to install Microsoft System Center 2012 R2 Virtual Machine Management.
I am getting the following error:
Setup cannot connect to the specified SQL Server instance.
Ensure that the server name, isntance name, and, if speceified, port number are correct. If you are installing VMM remotely, ensure that remote connections are set up correctly, and then try Setup again.
I have installed the
Microsoft® SQL Server® 2008 R2 Command Line Utilities
but have not set up any SQL Server instances.
how should i proceed?
Edit:
The followign fields are configured:
Server Name: The name of the machine i am using
Port: <empty>
Use the following credentials <NOT ticked>
Instance name <empty> (the drop down is empty)
New Database <Ticked> : VirtualManagerDB

Is SQL server is properly installed on the system?
Are you able to connect with SQL server instance?
As per the given details looks, only client utilities installed and trying to create the database which needs SQL server.
Make sure you are able to connect with the "ServerName\InstanceName,PortNumber" and hope installing the system as per below article:
http://technet.microsoft.com/en-us/library/gg610656.aspx
Hope it help!
Please click the Mark as answer button and vote as helpful if this reply solves your problem

I want make use of SQL Server Instance, while connecting

hi,
i have developed Code using normal conditions,Like i have not checked for SQL Server Instances, my client need to b use Instances of the SQL Server, so i need to change the code.
can any one help Regarding SQL Server Instances Connection coding.
Ex: jdbc:JSQLConnect://servername\Instance_Name
can any one help out me, it would be grate help for me,
thanks.

Read the JDBC tutorial and read the SQL Server JDBC driver documentation.
http://www.google.com/search?q=jdbc+tutorial+site:sun.com
http://www.google.com/search?q=sql+server+jdbc+driver+site:microsoft.com

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. (p

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: 2)
The system cannot find the file specified
Cannot connect to COWBOYS.
Here are the technical details===================================
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) (.Net SqlClient Data Provider)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476
Error Number: 2
Severity: 20
State: 0
Program Location:
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, Boolean withFailover)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer
timeout)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance,
SqlConnectionString userConnectionOptions, SessionData reconnectSessionData)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.SqlServer.Management.SqlStudio.Explorer.ObjectExplorerService.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
===================================
The system cannot find the file specified
I have tried from so many forms. This is so frustrating. Thank for everyone/anyone who wants to help. So this is what happened: I had to uninstall my previous sqlserver 2012(which worked great) for some reason, and I uninstalled everything from that download.
Then I installed the trial edition of sql server 2012 (64 Bit) and It wouldn't connect to the database. (Error mentioned above.) My local DB is COWBOYS. (COWBOYS is also my computer name.) After this, I have tried downloading sqlexpress and sqlserver 64bit
many times and cannot connect to my local DB.
How do I connect to my Local DB?
Also, I think this might help: (When I run sqlserve.exe, which I was able to find in C:\Program Files\Microsoft SQL Server\110\LocalDB\Binn, I get an error: Your SQL server installation is either corrupt or has been tampered with(Error getting
instance ID from name). Please uninstall then re-run setup to correct this problem.
I would happily re install it, if it wasn't my 20th time.
I don't have any remote connections, I don't use username/password, only window authentication. I work mostly on visual studio, but without able to store /retrieve data, I don't know how to survive.
May be the solution is very simple, but I am too frustrated.
Some of the things I have tried:
From a command prompt, enter one of the following commands:
net start "SQL Server Agent (MSSQLSERVER)" OR
net start "SQL Server Agent(instancename)"(for instance)
on my sql configuration, I cannot start anything because there is nothing there to start. I can post more details, if that would help. Also, some more details about the error:
Details
Product:
SQL Server
ID:
2
Source:
MSSQLServer
Version:
10.0
Component:
SQLEngine
Message:
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: Named Pipes Provider, error:
40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)
Explanation
SQL Server did not respond to the client request because the server is probably not started.
User Action
Make sure that the server is started.
Version:
9.0
Component:
SQLEngine
Message:
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) (.Net SqlClient Data Provider)
Explanation
SQL Server did not respond to the client request because the server is probably not started.
User Action
Make sure that the server is started.
Any one that can help me, I will be greatful. Thank you so much. p.s. please ask me anything if you have any questions.

It sounds like there are a couple things going on here. First check if you have a successful install of SQL Server, then we'll figure out the connection issues.
Can you launch SQL Server Configuration Manager and check for SQL Server (MSSQLSERVER) if default instance or SQL Server (other name) if you've configured your instance as a named instance. Once you find this, make sure the service is started.
If not started, try to start it and see if it throws an error. If you get an error, post the error message your hitting. If the service starts, you can then launch SSMS and try to connect. If you have a default instance, you can use the machine
name in the connection dialog. Ex: "COWBOYS" where Cowboys is the machine name. However, if you named the SQL Server instance during install, you'll need to connect using the machine\instance format. Ex: COWBOYS\Romo (where Romo
is the instance name you set during install).
You can also look at the summary.txt file in the SQL Server setup error logs to see what happened on the most recent install. Past install history is archived in the log folder if you need to dig those up to help troubleshoot, but the most
recent one may help get to the bottom of it if there is an issue with setup detecting a prior instance that needs to be repaired.
Thanks,
Sam Lester (MSFT)
http://blogs.msdn.com/b/samlester
This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click
"Mark as Answer" and
"Vote as Helpful" on posts that help you. This can be beneficial to other community members reading the thread.

Data modeler cannot connect to non-default sql server instance

I've just started using DM, it installed and loaded fine, I got the jdbc drivers v2.0 from MS so that I can reverse engineer a couple of SQL-Server 2005 DB's.
All worked just fine until I tried to connect to a machine with a named-sql-server instance.
Normal way of doing this for sql-server is to add instance name to end of hostname in the hostname field, like this: "server10\inst01"
but this gives me a cannot-connect-to-server10 error.
I copied database over to a different server that has just a default sql-server instance and it worked fine. (both sql-server2005 and 2000!)
I also tried the older 1.2 jdbc driver from MS against the sql-server 2005 named instance, no luck!
I tried putting the instance name in front of the port number, that didn't work either.
Am I just doing something wrong? or does DM need a special way of specifying the instance name on the sql-server host?

Hello,
you don't need instance name in order to connect. It's only host and port - probably named instance is not listening on default port. It'll be unfortunate if dynamic port assignment is used - but probably that won't be the case.
I hope someone can tell you the port number.
Philip

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible.

Server Error in '/' Application.
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)
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: 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)
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[SqlException (0x80131904): 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)]
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +4846887
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +194
System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject) +4860189
System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject) +90
System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart) +342
System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +221
System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +189
System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +185
System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +31
System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +433
System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +66
System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +499
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +65
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +117
System.Data.SqlClient.SqlConnection.Open() +122
System.Data.Common.DbDataAdapter.QuietOpen(IDbConnection connection, ConnectionState& originalState) +31
System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +112
System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +287
System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, String srcTable) +92
System.Web.UI.WebControls.SqlDataSourceView.ExecuteSelect(DataSourceSelectArguments arguments) +1297
System.Web.UI.DataSourceView.Select(DataSourceSelectArguments arguments, DataSourceViewSelectCallback callback) +19
System.Web.UI.WebControls.DataBoundControl.PerformSelect() +142
System.Web.UI.WebControls.BaseDataBoundControl.DataBind() +73
System.Web.UI.WebControls.GridView.DataBind() +4
System.Web.UI.WebControls.BaseDataBoundControl.EnsureDataBound() +82
System.Web.UI.WebControls.CompositeDataBoundControl.CreateChildControls() +72
System.Web.UI.Control.EnsureChildControls() +87
System.Web.UI.Control.PreRenderRecursiveInternal() +44
System.Web.UI.Control.PreRenderRecursiveInternal() +171
System.Web.UI.Control.PreRenderRecursiveInternal() +171
System.Web.UI.Control.PreRenderRecursiveInternal() +171
System.Web.UI.Control.PreRenderRecursiveInternal() +171
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +842
Version Information: Microsoft .NET Framework Version:2.0.50727.3082; ASP.NET Version:2.0.50727.3082

On what website/link did you received this error message ??

SQL Server Agent Log showing errors [298] SQLServer Error: 10061, A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL

Hi All,
I have started receiving this error in the logs for the last 10 days and the Schedules Jobs for the database have stopped running. My MS CRM application is working fine.
Can anyone guide me what could be the problem.
Date                      17/4/2014 2:04:20 PM
Log                         SQL Server Agent (Current - 17/4/2014 2:01:00 PM)
Message
[298] SQLServer Error: 10061,
A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct
and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. [SQLSTATE 08001]
Date                      17/4/2014 2:11:55 PM
Log                         SQL Server Agent (Current - 17/4/2014 2:01:00 PM)
Message
[298] SQLServer Error: 10061,
A network-related or instance-specific error
has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information
see SQL Server Books Online. [SQLSTATE 08001]
Date                      7/4/2014 11:00:31 AM
Log                         SQL Server Agent (Current - 17/4/2014 2:01:00 PM)
Message
[298] SQLServer Error: 10061,
A network-related or instance-specific error
has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information
see SQL Server Books Online. [SQLSTATE 08001]

Check this link
http://social.msdn.microsoft.com/Forums/en-US/906da9b5-2482-468c-a424-ae099da2d96b/sql-server-agent-service-account-error?forum=sqlsetupandupgrade
Regards, RSingh

Cannot not connect to SQL Server instance.

Similar Messages

Maybe you are looking for