Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
mike8888
Starting Member
4 Posts |
 Posted - 2011-01-07 : 07:00:27
|
| Hi, I just installed the MS SQL Server 2008 Enterprise Edition Evaluation Version. I can connect to the SQL Server if I start the SQL Server Management Studio in the server. But then I go to my desktop PC and try to connect to the same SQL Server using SQL Server Management Studio, it give me the following message:The client was unable to establish a connection because of an error during connection initialization process before login. Possible causes include the following: the client tried to connect to an unsupported version of SQL Server; the server was too busy to accept new connections; or there was a resource limitation (insufficient memory or maximum allowed connections) on the server. (provider: Named Pipes Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 2333)My server is running Windows Server 2003 R2 Standard Edition and the Enterprise SQL Server Evaluation is 32bit version. Anybody knows why? Anything wrong with using Evaluation Version? The server is previously running SQL Server 2000 Standard Edition. It worked fine and I just uninstalled it to try 2008 version |
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2011-01-07 : 07:41:59
|
| Are you using Management Studio 2008? |
 |
|
|
mike8888
Starting Member
4 Posts |
Posted - 2011-01-07 : 15:26:50
|
quote:
Originally posted by russell
Are you using Management Studio 2008?
Yes I am! Also, on my desktop PC, I can't browse the SQL Server 2008 Enterprise Evaluation Edition on the network. The system error mentioned about Named Pipe, is that means the connection is not using TCP/IP like I always do in SQL Server 2000? |
|
|
|
mike8888
Starting Member
4 Posts |
Posted - 2011-01-07 : 16:11:35
|
| Problem solved. I am new to SQL Server 2008 so I thought Protocol like Named Pipes and TCP/IP were enabled by default after installation like in SQL Server 2000. Now I need to use SQL Configuration Manager to manually turn the Protocols on and everything is working fine. Probably I was in the wrong direction so I couldn't find any solution on Internet. |
|
|
|
|
|
|
Can't Login to SQL Server 2008 Evaluation Ed.