SQL Server 2005 - "server not found or not accessible" error message
Hello All,
I am new to SQL Server. I just installed SQL Server 2005 on a new server, and am trying to access it for the first time so I can attach a database to it.
I'm pretty sure I missed something in the installation because when I bring up Management Studio and try to connect as follows:
Server Type: Database Engine
Server Name: (this is blank so I type in the server's IP address)
Authentication: Windows Authentication
Username: (my credentials)
results in this error message:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server as not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remove connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 51)
I've also tried logging on with SQL Server authentication and the sa password but get a similar error message.
Do I need to run the install again and create a named instance?
Any thoughts appreciated.
brl8
I am new to SQL Server. I just installed SQL Server 2005 on a new server, and am trying to access it for the first time so I can attach a database to it.
I'm pretty sure I missed something in the installation because when I bring up Management Studio and try to connect as follows:
Server Type: Database Engine
Server Name: (this is blank so I type in the server's IP address)
Authentication: Windows Authentication
Username: (my credentials)
results in this error message:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server as not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remove connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 51)
I've also tried logging on with SQL Server authentication and the sa password but get a similar error message.
Do I need to run the install again and create a named instance?
Any thoughts appreciated.
brl8
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi Carlos,
Thanks for that link. I began following the steps in the section "Enable remote connections for SQL Server 2005 Express or SQL Server 2005 Developer Edition", but when I click Surface Area Configuration for Services and Connections I get this error message: "No SQL Server 2005 components were found on the specified computer. Either no components are installed, or you are not an administrator on this computer. (SQLSAC)"
I'm thinking that something went wrong in the install and I may just start over with a new virtual server.
Thoughts?
Thanks for that link. I began following the steps in the section "Enable remote connections for SQL Server 2005 Express or SQL Server 2005 Developer Edition", but when I click Surface Area Configuration for Services and Connections I get this error message: "No SQL Server 2005 components were found on the specified computer. Either no components are installed, or you are not an administrator on this computer. (SQLSAC)"
I'm thinking that something went wrong in the install and I may just start over with a new virtual server.
Thoughts?
So, are you connecting to SQL server with administrator account?
What computer are you trying to manage in Surface Area Configuration? localhost?
What computer are you trying to manage in Surface Area Configuration? localhost?
ASKER
I googled the error message I mentioned in my last post, which took me to this link: http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=71794.
I did not install the database engine...Doh!
Ran the installer again and selected database services, its all good now!
Thanks.
I did not install the database engine...Doh!
Ran the installer again and selected database services, its all good now!
Thanks.
Is this default instance or named instance? Named instance is listening on other port than default 1433. Do you connect over local network? Is firewall enabled on server? Does it allows SQL server? Did you try to connect by using network name instead of IP address?
You should log in to you SQL server and open SQL Server Configuration Manager. Check "SQL Server Network Configuration". You will see enabled protocols and IP addresses/ports that are used.