This is a bit of strange one.
My local version of SQL Server fails to start when I boot yet if I
start Enterprise Manager its started and working fine. ISQL or Query
Analyzer is also not working.
If I try and register the server by another SQL Server is not there. Me
thinks that the named pipes might be a bit broken but would appreciate
any advise from people.
Thanks
GintersCouple of thoughts. One the service is not starting until you start EM and
click on the server? By default when a server is registered in EM it sets
the checkbox for automatically start. Right click the server in EM, choose
Edit server registration and look at the bottom checkbox.
Another is only shared memory is working and you are trying to connect from
isql (osql) and QA remotely? In this case check the SQL server error log
for what protocols SQL started and verify that on the client that these
protocols are activated in the client network utility.
If this is a default installation then shared memory, named pipes, and tcp
are all active. Is the MSSQLServer service set to start automatically?
"Ginters" <jpmcginty@.talk21.com> wrote in message
news:1108124975.337210.24500@.f14g2000cwb.googlegro ups.com...
> Hello there,
> This is a bit of strange one.
> My local version of SQL Server fails to start when I boot yet if I
> start Enterprise Manager its started and working fine. ISQL or Query
> Analyzer is also not working.
> If I try and register the server by another SQL Server is not there. Me
> thinks that the named pipes might be a bit broken but would appreciate
> any advise from people.
> Thanks
> Ginters|||Ginters (jpmcginty@.talk21.com) writes:
> This is a bit of strange one.
> My local version of SQL Server fails to start when I boot yet
Do you get any error message?
Do you have the service set to start automatically?
> if I start Enterprise Manager its started and working fine. ISQL or Query
> Analyzer is also not working.
Even if SQL Server is running?
Which operating system and which version of SQL Server are you using?
> If I try and register the server by another SQL Server is not there. Me
> thinks that the named pipes might be a bit broken but would appreciate
> any advise from people.
Which protcols have you enabled in the Client Network Utility? Is
shared memory on?
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp
No comments:
Post a Comment