Problem: SQL Server does not accept TCP connections

Hi,
I have a W2k3 with SQL Server 2000 SP4. I have configured the server
to use named pipes and TCP on 1433 (at least that is what the registry
and server configuration tool say)
However the server does not accept tcp connections (i tried with
telnet, query analyzer, etc).
Log says the following:
2007-01-03 19:12:55.85 server SQL server listening on Shared Memory,
Named Pipes.
0
2007-01-03 19:12:55.85 server SQL Server is ready for client
connections
Is this a SQL Server BUG or i am doing something wrong?
Thanks,
Ezequiel Naftali
enaftali@.pisol.com.arIts not listening on TCP for some reason...verify that you have SQL Server
sp3 or higher (I know you say you have SP4) by looking at the file version
of sqlservr.exe on the server
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Ezequiel" <ezequiel.naftali@.gmail.com> wrote in message
news:1167922343.027575.146800@.6g2000cwy.googlegroups.com...
> Hi,
> I have a W2k3 with SQL Server 2000 SP4. I have configured the server
> to use named pipes and TCP on 1433 (at least that is what the registry
> and server configuration tool say)
> However the server does not accept tcp connections (i tried with
> telnet, query analyzer, etc).
> Log says the following:
> 2007-01-03 19:12:55.85 server SQL server listening on Shared Memory,
> Named Pipes.
> 0
> 2007-01-03 19:12:55.85 server SQL Server is ready for client
> connections
>
> Is this a SQL Server BUG or i am doing something wrong?
> Thanks,
> Ezequiel Naftali
> enaftali@.pisol.com.ar
>|||Hi Kevin,
The .exe version number is: 2000.080.0194.00
(8.0.0.194)
Is that what you were asking me?
Thanks for the answer.
Ezequiel
Kevin3NF ha escrito:
[vbcol=seagreen]
> Its not listening on TCP for some reason...verify that you have SQL Server
> sp3 or higher (I know you say you have SP4) by looking at the file version
> of sqlservr.exe on the server
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
> "Ezequiel" <ezequiel.naftali@.gmail.com> wrote in message
> news:1167922343.027575.146800@.6g2000cwy.googlegroups.com...|||Yes...that is the RTM version number, not sp4. Re-apply sp4 on the server.
If you are sure you already did it, look for a file in C:\windows\sqlsp.log
which is the sp4 install log
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Ezequiel" <ezequiel.naftali@.gmail.com> wrote in message
news:1167924459.305986.118040@.q40g2000cwq.googlegroups.com...
> Hi Kevin,
> The .exe version number is: 2000.080.0194.00
> (8.0.0.194)
> Is that what you were asking me?
> Thanks for the answer.
> Ezequiel
>
> Kevin3NF ha escrito:
>
>|||Kevin
You are right, I installed again SP4 and everything is working right.
Thank you very much.
Ezequiel
Kevin3NF ha escrito:
[vbcol=seagreen]
> Yes...that is the RTM version number, not sp4. Re-apply sp4 on the server
.
> If you are sure you already did it, look for a file in C:\windows\sqlsp.lo
g
> which is the sp4 install log
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
> "Ezequiel" <ezequiel.naftali@.gmail.com> wrote in message
> news:1167924459.305986.118040@.q40g2000cwq.googlegroups.com...

Problem: SQL Server does not accept TCP connections

Hi,
I have a W2k3 with SQL Server 2000 SP4. I have configured the server
to use named pipes and TCP on 1433 (at least that is what the registry
and server configuration tool say)
However the server does not accept tcp connections (i tried with
telnet, query analyzer, etc).
Log says the following:
2007-01-03 19:12:55.85 server SQL server listening on Shared Memory,
Named Pipes.
0
2007-01-03 19:12:55.85 server SQL Server is ready for client
connections
Is this a SQL Server BUG or i am doing something wrong?
Thanks,
Ezequiel Naftali
enaftali@.pisol.com.ar
Its not listening on TCP for some reason...verify that you have SQL Server
sp3 or higher (I know you say you have SP4) by looking at the file version
of sqlservr.exe on the server
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Ezequiel" <ezequiel.naftali@.gmail.com> wrote in message
news:1167922343.027575.146800@.6g2000cwy.googlegrou ps.com...
> Hi,
> I have a W2k3 with SQL Server 2000 SP4. I have configured the server
> to use named pipes and TCP on 1433 (at least that is what the registry
> and server configuration tool say)
> However the server does not accept tcp connections (i tried with
> telnet, query analyzer, etc).
> Log says the following:
> 2007-01-03 19:12:55.85 server SQL server listening on Shared Memory,
> Named Pipes.
> 0
> 2007-01-03 19:12:55.85 server SQL Server is ready for client
> connections
>
> Is this a SQL Server BUG or i am doing something wrong?
> Thanks,
> Ezequiel Naftali
> enaftali@.pisol.com.ar
>
|||Hi Kevin,
The .exe version number is: 2000.080.0194.00
(8.0.0.194)
Is that what you were asking me?
Thanks for the answer.
Ezequiel
Kevin3NF ha escrito:
[vbcol=seagreen]
> Its not listening on TCP for some reason...verify that you have SQL Server
> sp3 or higher (I know you say you have SP4) by looking at the file version
> of sqlservr.exe on the server
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
> "Ezequiel" <ezequiel.naftali@.gmail.com> wrote in message
> news:1167922343.027575.146800@.6g2000cwy.googlegrou ps.com...
|||Yes...that is the RTM version number, not sp4. Re-apply sp4 on the server.
If you are sure you already did it, look for a file in C:\windows\sqlsp.log
which is the sp4 install log
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Ezequiel" <ezequiel.naftali@.gmail.com> wrote in message
news:1167924459.305986.118040@.q40g2000cwq.googlegr oups.com...
> Hi Kevin,
> The .exe version number is: 2000.080.0194.00
> (8.0.0.194)
> Is that what you were asking me?
> Thanks for the answer.
> Ezequiel
>
> Kevin3NF ha escrito:
>
|||Kevin
You are right, I installed again SP4 and everything is working right.
Thank you very much.
Ezequiel
Kevin3NF ha escrito:
[vbcol=seagreen]
> Yes...that is the RTM version number, not sp4. Re-apply sp4 on the server.
> If you are sure you already did it, look for a file in C:\windows\sqlsp.log
> which is the sp4 install log
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
> "Ezequiel" <ezequiel.naftali@.gmail.com> wrote in message
> news:1167924459.305986.118040@.q40g2000cwq.googlegr oups.com...

PROBLEM: Grouping tasks: Connections disappear ?

Guys,

anyone seen this before?

I've just finished me lovely big package.. decided to tidy it up and make it look nice...
(when will I ever learn?)

So I selected a few tasks, right clicked and selected "group". Named the group.....

And now all the connectors between the tasks in the group have disappeared.... tried ungrouping.. still not there...

The package still runs fine... the tasks are executed in the right sequence and all that... but the connectors are jut not visible...

If I try to recreate the connector I get an error dialog saying "Cannot create connector. Only one workflow can exist between the same two executeables.". So they must still exist...

It'd be ok to leave it as it is I suppose.. if I didn't now need to modify the precedence constraint on one of the connectors.... and I can't actually select the feckin connector..

Any suggestions? Any way to refresh the display? Have already exited the environment and come back in.. will try rebooting machine now anyway...

PJ

I've seen problems like this before. Sometimes moving the tasks about makes them reappear. If not, you might be stuck.

In my opinion its a bug.

-Jamie

|||

They're back!

Phew..

I started copying and pasting new versions of the tasks... thinking I could delete the old ones and reconnect the new ones...

And after the first copy and paste... the connections reappeared...magic!

Suppose its good to have a note about this somewhere in the forums for anyone else that comes on this problem...

Now I'm off to get this thing into Sourcesafe (which I should have done from the start)

Thanks Jamie,

PJ