23
Jun

“under current configuration sql server studio express doesnot support remote connection”.

   Posted by: admin   in Window

Add Comment

If you are getting “under current configuration sql server studio express doesnot support remote connection”. error while conneting microsoft sql server 2005 please do following step

1)Please go to Start >> Programs >> Microsoft SQL Server 2005 >> Congfiguration Tools >> SQl Server Configuration manager then expand SQL server 2005 Network configuratiion >> Protocal for SQLEXPRESS and enable named pipes and TCP/IP protocal.

2)Make sure to restart the MSSQLSERVER service after enabling the TCP/IP and named pipes.

If you did so and its not still not working, try the following steps:

* Make sure your sql service is running, use either “net start” or “sc query <InstanceName>” or run services.msc, check status of the server; If server start fail, go to ERRORLOG to see what happened there, fix the problem and restart server.

* You might explicitly use “np:”prefix which ask for connect through named pipe. However, client can not connect to server through the pipe name that specified.Double check the server is started and listening on named pipe if you enabled Named Pipe. One way is that see the ERRORLOG of the server, search follow keywords:

Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ] or [\\.\pipe\mssql$<InstanceName>\sql\query]

Notice that “sql\query” is the default pipe name, so you need to know server is listening on which pipe name. eg: if you specify server pipe name is “sql\query1″, then you would see in the errorlog that server listening on [ \\.\pipe\sql\query1 ], and go to SQL Server Configuration Manager, click client Named Pipe properties, see whether the pipe name is same with the one server listening on.

*You might specify named pipe protocol in connection string, but did not enable named pipe on the server, check ERRORLOG.

* You might use FQDN/IPAddress/LoopbackIP to connect to the server when only shared memory was enabled, you can change to <machinename> to resolve this.

* You might explictly specify “lpc:” prefix in your connection string, but shared memory was not enabled. To resolve this, either remove the prefix as long as named pipe or tcp was enabled or enable shared memory.

Regard’s

Alex P

This entry was posted on Saturday, June 23rd, 2007 at 6:05 pm and is filed under Window. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

3 comments so far

Ron
 1 

Thank you for this post. This also worked for me in the Microsoft Client. In the ODBC, Client Configuration (Edit Network Library Configurations) I choose Named Pipes.
Server Alias, Server Name, & Pipe Name populated automatically.

For some reason Microsoft did not populate the Pipe Name correctly. I had manually enter the following as the Pipe Name:
[\\\pipe\mssql$\sql\query]

Again thanks for your post.

July 24th, 2007 at 7:06 pm
Ron
 2 

Thank you for this post. This also worked for me in the Microsoft Client. In the ODBC, Client Configuration (Edit Network Library Configurations) I choose Named Pipes.
Server Alias, Server Name, & Pipe Name populated automatically.

For some reason Microsoft did not populate the Pipe Name correctly. I had manually enter the following as the Pipe Name:
[\\>\pipe\mssql$>\sql\query]

Again thanks for your post.

For some reason the MachineName and InstanceName were not published in this reply.

July 24th, 2007 at 7:07 pm
Ron
 3 

Thank you for this post. This also worked for me in the Microsoft Client. In the ODBC, Client Configuration (Edit Network Library Configurations) I choose Named Pipes.
Server Alias, Server Name, & Pipe Name populated automatically.

For some reason Microsoft did not populate the Pipe Name correctly. I had manually enter the following as the Pipe Name:
[\\MachineName\pipe\mssql$InstanceName\sql\query]

Again thanks for your post.

For some reason the MachineName and InstanceName were not published in this reply.

July 24th, 2007 at 7:08 pm

Leave a reply

Name (*)
Mail (will not be published) (*)
URI
Comment
Back to top