connect to sql server 2005 problem

I tried to run MS SQL server management studio with sa login. But it gives
an error as following:
Cannot connect to the server:
Additional information:
A connection waas successfully established with the server, but then an
error occured during the
login process. (provider: Shared Memory Provider, error:0 - No process is on
other end of the
pipe.) (Microsoft SQL Server, error:233)
Does anyone know what is the problem and how to fix it? THanks
Hi
"00MichaelJordan" wrote:

> I tried to run MS SQL server management studio with sa login. But it gives
> an error as following:
> Cannot connect to the server:
> Additional information:
> A connection waas successfully established with the server, but then an
> error occured during the
> login process. (provider: Shared Memory Provider, error:0 - No process is on
> other end of the
> pipe.) (Microsoft SQL Server, error:233)
I assume you are on the server itself when you try and connect? Can you
sucessfully connect using windows authentication?
Checking Google for your error message came up with:
http://msdn2.microsoft.com/en-us/library/ms175496.aspx
http://blogs.msdn.com/sql_protocols/archive/2005/10/22/483684.aspx
Check the client and server protocols installed. Check any antivirus or
intrusion detection systems installed on the server is not interferring.

> Does anyone know what is the problem and how to fix it? THanks
>
John
|||Yes, I can login with window authentication.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:2DDB7F0E-DE41-467C-8A7E-1BAF6EBBEDF1@.microsoft.com...
> Hi
> "00MichaelJordan" wrote:
>
> I assume you are on the server itself when you try and connect? Can you
> sucessfully connect using windows authentication?
> Checking Google for your error message came up with:
> http://msdn2.microsoft.com/en-us/library/ms175496.aspx
> http://blogs.msdn.com/sql_protocols/archive/2005/10/22/483684.aspx
> Check the client and server protocols installed. Check any antivirus or
> intrusion detection systems installed on the server is not interferring.
>
> John
|||Hi
On Feb 2, 12:09 am, "00MichaelJordan" <M...@.yahoo.com> wrote:
> Yes, I can login with window authentication.
>
You don't say if this is a local or remote connection!
Have you tried creating a new SQL Server Login and tried to use that?
Have you set the default database for sa?
Has this databases been moved from a different machine?
John
|||John,
This is a local connection. The default database for sa is
master and I have created a new sql server account and I cannot login with
the new account as well and this database is moved from a SQL 2000 server.
Please help. Thanks.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:1170405046.429970.295550@.s48g2000cws.googlegr oups.com...
> Hi
> On Feb 2, 12:09 am, "00MichaelJordan" <M...@.yahoo.com> wrote:
> You don't say if this is a local or remote connection!
> Have you tried creating a new SQL Server Login and tried to use that?
> Have you set the default database for sa?
> Has this databases been moved from a different machine?
> John
>
>
|||Hi
On Feb 6, 3:08 am, " 00EricClapton" <E...@.yahoo.com> wrote:
> John,
> This is a local connection. The default database for sa is
> master and I have created a new sql server account and I cannot login with
> the new account as well and this database is moved from a SQL 2000 server.
> Please help. Thanks.
>
As you can log in with windows authentication then make sure that the
server is set to used mixed mode. Are you using Query Analyser to log
in? Try using the server's IP address instead of the server name,
'(local)' or '.'. You could also try removing the shared memory
setting on the protocol.
John