SQL Server cannot connect itself

Dear all,

The current config is SQL2000 + SP4 with Windows 2003.

Our SQL server suddenly cannot connect to itself. SQL server agent also fail
to start.

However, all other clients can connect to the SQL Server and work properly.

We found that in client connectivity tools, when trying to add the alias,
the TCP/IP option is disable.

Does anyone encounter similar problem?

Ivan

We suspect it may related to the Windows 2003 update on 16/12. After the
system auto install the Windows 2003 update and reboot, the SQL server agent
cannot connect to the SQL server.

Does anyone encounter this problem?

Ivan

"Ivan" <ivan@microsoft.com>  级糶秎ン穝籇:exr%2
3y0GBGHA.208@tk2msftngp13.phx.gbl...
> Dear all,
>
> The current config is SQL2000 + SP4 with Windows 2003.
>
> Our SQL server suddenly cannot connect to itself. SQL server agent also
> fail to start.
>
> However, all other clients can connect to the SQL Server and work
> properly.
>
> We found that in client connectivity tools, when trying to add the alias,
> the TCP/IP option is disable.
>
> Does anyone encounter similar problem?
>
> Ivan
>

Hi

Are there any messages in the SQL Server System Log or the Windows Event
Log?

John
"Ivan" <ivan@microsoft.com> wrote in message
news:uyJYH6GBGHA.3760@tk2msftngp13.phx.gbl...
> We suspect it may related to the Windows 2003 update on 16/12. After the
> system auto install the Windows 2003 update and reboot, the SQL server
> agent cannot connect to the SQL server.
>
> Does anyone encounter this problem?
>
> Ivan
>
> "Ivan" <ivan@microsoft.com>
>  级糶秎ン穝籇:exr%2
3y0GBGHA.208@tk2msftngp13.phx.gbl... 
>
>

No... Nothing special is log....

"John Bell" < jbellnewsposts@hotma
il.com>  级糶秎ン穝籇:uFGyX
zHBGHA.1252@TK2MSFTNGP09.phx.g
bl...
> Hi
>
> Are there any messages in the SQL Server System Log or the Windows Event
> Log?
>
> John
> "Ivan" <ivan@microsoft.com> wrote in message
> news:uyJYH6GBGHA.3760@tk2msftngp13.phx.gbl... 
>
>

When I try to start the SQL Server agent, it shows:
SQLServerAgent could not be started (reason: Unable to connect to server
'(local)'; SQLServerAgent cannot start).

However, the SQL server is well started and other users can connect to the
sql server without any problem.

It seems that the SQL server itself cannot connect to itself through TCP/IP.
It cannot act as a SQL client.

Ivan

"John Bell" < jbellnewsposts@hotma
il.com>  级糶秎ン穝籇:uFGyX
zHBGHA.1252@TK2MSFTNGP09.phx.g
bl...
> Hi
>
> Are there any messages in the SQL Server System Log or the Windows Event
> Log?
>
> John
> "Ivan" <ivan@microsoft.com> wrote in message
> news:uyJYH6GBGHA.3760@tk2msftngp13.phx.gbl... 
>
>

Hi Ivan

Have you checked out
http://support.microsoft.com/defaul...kb;en-us;237604

John

"Ivan" wrote:

> When I try to start the SQL Server agent, it shows:
> SQLServerAgent could not be started (reason: Unable to connect to server
> '(local)'; SQLServerAgent cannot start).
>
> However, the SQL server is well started and other users can connect to the
> sql server without any problem.
>
> It seems that the SQL server itself cannot connect to itself through TCP/I
P.
> It cannot act as a SQL client.
>
> Ivan
>
> "John Bell" < jbellnewsposts@hotma
il.com>  录露录g漏贸露l楼贸路
s禄D:uFGyXzHB
GHA.1252@TK2MSFTNGP09.phx.gbl... 
>
>
>

Dear John,

The situation is, my sql server cannot use Query Analyser to connect to
itself.

When checking the client connectivity tools, the TCP/IP option is disable.

I think that's the main reason why the SQL Server Agent cannot be start.

How can I resume the TCP/IP option? I have tried install the client tools
but fail to resume it.

However, all other clients can connect to this sql server without any proble
m.

Ivan

"John Bell" wrote:

> Hi Ivan
>
> Have you checked out
> http://support.microsoft.com/defaul...kb;en-us;237604
>
> John
>
> "Ivan" wrote:
> 

Hi

It is not clear what you mean by disabled. On the General Tab of the Client
Network Utitity, can you highlight TCP/IP in the 'disabled' list and then
click the enable button? You may then want to move TCP/IP to the top of the
list.

If you can't do this then check the network libraries tab to see if TCP/IP
is there. If not run the MDAC component checker http://tinyurl.com/6gsv to
see if your installation of MDAC is correct.

I assume that TCP/IP is enables in the Server Network Utility as well if
other clients can connect using it?

John

"Ivan" wrote:

> Dear John,
>
> The situation is, my sql server cannot use Query Analyser to connect to
> itself.
>
> When checking the client connectivity tools, the TCP/IP option is disable.
>
> I think that's the main reason why the SQL Server Agent cannot be start.
>
> How can I resume the TCP/IP option? I have tried install the client tools
> but fail to resume it.
>
> However, all other clients can connect to this sql server without any prob
lem.
>
> Ivan
>
> "John Bell" wrote:
> 

Well, having checked the Network Libraries, we found that the TCP/IP Library
file is missed.

However, the TCP/IP Library is found in Server Network Utility.

What can we do to this case?

Re-install the SQL Client or Re-install MDAC 2.8 sp1?

Best Regards,
Ivan

"John Bell" < jbellnewsposts@hotma
il.com>  级糶秎ン穝籇:824C8
3AA-07D5-4E54-82B4-ADC253FB4DC
0@microsoft.com...
> Hi
>
> It is not clear what you mean by disabled. On the General Tab of the
> Client
> Network Utitity, can you highlight TCP/IP in the 'disabled' list and then
> click the enable button? You may then want to move TCP/IP to the top of
> the
> list.
>
> If you can't do this then check the network libraries tab to see if TCP/IP
> is there. If not run the MDAC component checker http://tinyurl.com/6gsv to
> see if your installation of MDAC is correct.
>
> I assume that TCP/IP is enables in the Server Network Utility as well if
> other clients can connect using it?
>
> John
>
> "Ivan" wrote:
> 

Hi Ivan

I assume it is missing on the client?

If you run the MDAC component checker that will tell you the version of MDAC
and if it is complete. If it is not complete you can then re-install it.

John

"Ivan" wrote:

> Well, having checked the Network Libraries, we found that the TCP/IP Libra
ry
> file is missed.
>
> However, the TCP/IP Library is found in Server Network Utility.
>
> What can we do to this case?
>
> Re-install the SQL Client or Re-install MDAC 2.8 sp1?
>
> Best Regards,
> Ivan
>
> "John Bell" < jbellnewsposts@hotma
il.com>  录露录g漏贸露l楼贸路
s禄D:824C83AA
-07D5-4E54-82B4- ADC253FB4DC0@microso
ft.com... 
>
>
>