September 26, 2006 at 10:26 am
Hi all,
I am having difficulties connecting to SQL 2005 standard edition from SQL 2005 express edition (Client connection).
Server: SQL 2005 Standard edition on Windows 2000 Server
Client: SQL 2005 Express on windows XP Firewall disabled
Below is the error:
Cannot connect to SPurina\SQLV1.
------------------------------
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: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476
I have tried all the solutions put in the following websites:
https://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx
http://www.datamasker.com/SSE2005_NetworkCfg.htm
I have changed the surface area configuration to accept both TCP/named pipes, as this was only configured for TCP/IP before, I have also checked the browser services, thats running, Windows XP firewall turned off.
Looking forward to your reply.
Thanks
John
September 26, 2006 at 10:55 am
Do you have installed the client access tools (did I name this right) on the pc you want to use to connect on the server?
Restart the sql server 2005 installation and in the list of componants it's like the first before the last one (client connectivity or something like that).
September 26, 2006 at 11:00 am
September 26, 2006 at 11:11 am
I don't have the install file here. Can you list me all the main componant options?
September 26, 2006 at 11:12 am
Hmmm yup that's it (confirmed by a coworker).
September 27, 2006 at 10:01 am
There is a good chance that this has *nothing* to do with any differences between SQL Server editions, but JIC I'm working from a SQL Express instance here...
So, under my Sql Server 2005 menu from Start->Programs, I have a Configuration Tools folder. From there, I can start SQL Server Configuration Manager.
In this tool, I see Sql Server Configuration (local), which when expanded shows me
... if you see this too, I think you can stop worrying about whether the native client is installed.
Now, as to what's happening: when you say that you are having trouble connecting to the instance, can you tell us more about exactly what you do to try to connect? Are you setting up a linked server, registering a server instance, or what? Are you doing this from a management tool, on the command line, etc? Windows auth or SQL auth?
The first thing I usually do when having trouble connecting to a server on a given box is to get out of the environment in which I'm connecting, and try a different method of connecting on the same box. This is what some of the examples in the URLs you cite are suggesting you do. For example, if you are using Management Studio Express, try the osql command line tool or try connecting from Visual Studio. (Some simple vb script in a vbs file would work too.)
The idea is to find out whether your issue is in how you are attempting to name/invoke the server, and whether the current box can see it, or something in particular about how you are trying to configure that connection in your chosen environment (SQL Server Express).
For example(s), it might be a domain issue, you might need to fully-qualify the name of the server, or it might be an authentication issue, if the identity you have chosen isn't recognized by the receiving server, or it might be an instance name issue. Trying a different environment helps take "SQL Server Express" out of the picture.
Hope this gives you some ideas.
>L<
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply