| Author |
 Topic  |
|
|
rega83
Starting Member
Iraq
6 Posts |
 Posted - 03/04/2013 : 09:57:55
|
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: 121)
"
 |
|
|
James K
Flowing Fount of Yak Knowledge
1481 Posts |
Posted - 03/04/2013 : 10:04:00
|
| Is that servername "b" just an example that you are using, or is it the real server name you are using? Try (local) including the brackets if you are trying to connect from the same box where SQL Server is installed. |
 |
|
|
rega83
Starting Member
Iraq
6 Posts |
Posted - 03/04/2013 : 13:12:48
|
| i tried (local)but it took same problem,,please what can i do? |
|
|
|
James K
Flowing Fount of Yak Knowledge
1481 Posts |
Posted - 03/04/2013 : 13:42:23
|
| Go through this blog. Walks you step by step to figure out what you need to fix. |
|
|
|
rega83
Starting Member
Iraq
6 Posts |
Posted - 03/04/2013 : 14:05:40
|
| i read it but i didn't understand it,,please tell me by yourself |
|
|
|
James K
Flowing Fount of Yak Knowledge
1481 Posts |
Posted - 03/04/2013 : 14:47:06
|
I don't know if I can explain it better than they have done there.
I would suggest these initial steps though:
1. Log on the box on which the SQL Server is installed, start up SSMS and try to connect to the database engine using (local) for the servername. Depending on how the server was set up you may need to use Windows Authentication or SQL Authentication.
2. If that does not work, see if SQL Server is running. To do that, run services.msc and look for SQL Server. It should be running.
If you are able to connect locally (i.e., by logging in on the server box), but not able to connect from a remote workstation, then it is a connectivity problem that you have to figure out using the steps described in that article. |
|
|
|
rega83
Starting Member
Iraq
6 Posts |
Posted - 03/04/2013 : 14:56:37
|
| i opened services.msc but i didn't find sql server |
|
|
|
James K
Flowing Fount of Yak Knowledge
1481 Posts |
Posted - 03/04/2013 : 15:08:12
|
| That means you don't have SQL Server installed. What did you install? Did you install only the client tools? |
|
|
|
rega83
Starting Member
Iraq
6 Posts |
Posted - 03/04/2013 : 15:15:27
|
| i installed sql server perfectly,,it was same problem for sql server 2008 |
|
|
|
James K
Flowing Fount of Yak Knowledge
1481 Posts |
Posted - 03/04/2013 : 15:25:29
|
If you don't see SQL Server in Services.msc, that certainly means you don't have SQL Server installed. Do you see anything in services.msc that has a name that starts with SQL?
How did you install? Did you install from a DVD, or did you download it from Microsoft? If you downloaded it, what is the link you used? |
|
|
|
rega83
Starting Member
Iraq
6 Posts |
Posted - 03/04/2013 : 15:36:54
|
| i installed from dvd,,we use this version in office on windows server 2008 does not have problem ,but i use windows 7 i dont know what is problem with me |
|
|
| |
Topic |
|
when i want connect it ,it takes this error,,pleas
