August 12, 2007 at 6:46 pm
I have just installed Sql server 2005 on my Win XP Pro machine.
When I go into the sql server management studio, there is only
one entry under the "database engine" entry in the registered servers'
panel on the left. It is MyServerName\SQLEXPRESS.
When I click on it and then select connect, either new query
or object explorer, I get one of the following errors.
An error has occurred while establishing a connection to there server.
When connecting to SQL Server 2005, the 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 )
An error has occurred while establishing a connection to there server.
When connecting to SQL Server 2005, the 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.
I have looked all over the internet, but couldn't find anything that would help.
I went into the sql server configuration manger, and enabled the name pipes and rebooted.
I didn't work. In the sql service configuration manager I have five services that are status of
running and startup mode of automatic. However they are not for the SQLExpress server.
They are for another sql server name, that I put in for the server name when I installed
sql server 2005. I thought that would be the server name.
There are two entries under sql server 2005 network configuration
Protocals for SQLEXPRESS and
Protocals for Myotherservername
MyOtheservername is not the same name that I
gave to the server when I installed it.
Not sure which is which.
How can I connect.
Why do I have two instances are those instances of servers,
I thought that there was only server.
What do I do?
Thanks in Advance,
Laurence
August 13, 2007 at 8:59 am
I'm not 100% sure what is wrong, but when you first install SSMS or SQL Server, there are not connections under Registered Servers. You need to add them yourself.
I'd create a new one, use the name you put in for the server instance and leave the defaults. It should connect. Also be sure that your service is actually running.
December 13, 2007 at 5:31 pm
I'm having the same issue. I can't seem to connect to my SQL Server using SSMS. I'm even running SSMS on the same server that SQL Server is running. Why wouldn't I be able to connect. I have enabled the remote connection options, but it still fails. It won't connect to the database engine.
There is only one database engine to select from, so that can't be the problem. This is very frustrating and there doesn't seem to be a lot of help on the Net about it.
Can anyone shed some light?
December 13, 2007 at 11:04 pm
silly question but is the sql server service running?
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply