Is this the bug in SQL2000?

HI Group
I have shared memory enable on client network utility
on my sql2000 server but every time I restart the service
I will lost my setting even the box still check enable
shared memory but my sql only listen to TCP and Name pipe
Does any one have this same problem ? I must restart the
sql service 4 to 5 times before the sql server listen to
the share memory. Any clue ?
ThanksThe "Client Network Utility" is only used to configure how clients connect.
The "Server Network Utility" controls what connections SQL Server will
accept/listen on. It does not have an option for shared memory, that is
always on unless there is a failure at startup (which would be documented
in the SQL error log).
Which utility are you using? Where are you checking what SQL Server listens
on (check the SQL error log)? What is the actual failure you see?
Hint: To force a client to connect with a certain protocol, include it in
the connection string. If your instance name is MyServer\Inst1, you would
use:
for TCP/IP sockets: tcp:MyServer\Inst1
for shared memory: lcp:MyServer\Inst1
for named pipes: np:MyServer\Inst1
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.|||HI
I checked in the error log when SQL started
the only TCP and Namepipe is listen by server
then if I use query analyzer on the console
it will connect at TCP protocol
I wolud like to connect client from sql console
using LPC protocol not TCP. Again there is no error
indicated any thing failed on sql startup log but
it only listen to TCP and Name pipe even shared memory
have been checked.
Thanks
>--Original Message--
>The "Client Network Utility" is only used to configure
how clients connect.
>The "Server Network Utility" controls what connections
SQL Server will
>accept/listen on. It does not have an option for shared
memory, that is
>always on unless there is a failure at startup (which
would be documented
>in the SQL error log).
>Which utility are you using? Where are you checking what
SQL Server listens
>on (check the SQL error log)? What is the actual failure
you see?
>Hint: To force a client to connect with a certain
protocol, include it in
>the connection string. If your instance name is
MyServer\Inst1, you would
>use:
>for TCP/IP sockets: tcp:MyServer\Inst1
>for shared memory: lcp:MyServer\Inst1
>for named pipes: np:MyServer\Inst1
>Cindy Gross, MCDBA, MCSE
>http://cindygross.tripod.com
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>.
>|||There is no checkbox to make SQL Server listen on shared memory. I suspect
you're talking about the checkbox that allows a client to connect with
shared memory. Shared memory only works on the same box.
You mentioned that SQL Server is only listening on TCP and named pipes. If
the error log doesn't list shared memory as a protocol it is listening on
then you should check to see if there are other errors, particularly
related to ssnetlib.dll. Can you post your errorlog file?
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.sql