| Groups | Blog | Home |
sql server clustering : TCP connections suddenly failing.
I am running a large mission critical application on a cluster. This
is a 2003 server latest SP with SQL 2000 Enterprise latest SP also. This app has run for years with little change. Today at around 3:00 all connections stopped coming in. After some debugging, we found that we could connect with named pipes., but not TCP. TCP has been the default protocol for years. We have the server monitored and no changes occurred recently. The server has not been rebooted in months, and the last time the instance was restarted was two months ago. What can cause a server that has run reliably using TCP for years to stop accepting TCP connectionsl suddenly? The errors I am getting is a handshake error trying to connect locally using TCP, and I get a connection failed error remotely. Connections are instant and lovely using named pipes. Thanks for any help.
just a FYI. I can telnet to udp and Tcp port.
[quoted text, click to view] On Mon, 16 Apr 2007 19:25:00 -0400, ken.sumner@gmail.com wrote:
>I am running a large mission critical application on a cluster. This >is a 2003 server latest SP with SQL 2000 Enterprise latest SP also. > >This app has run for years with little change. Today at around 3:00 >all connections stopped coming in. > >After some debugging, we found that we could connect with named >pipes., but not TCP. TCP has been the default protocol for years. > >We have the server monitored and no changes occurred recently. The >server has not been rebooted in months, and the last time the instance >was restarted was two months ago. > >What can cause a server that has run reliably using TCP for years to >stop accepting TCP connectionsl suddenly? > >The errors I am getting is a handshake error trying to connect locally >using TCP, and I get a connection failed error remotely. > >Connections are instant and lovely using named pipes. >
Can you check
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Cluster and make sure the clusteripaddr is set to the virtual server ip? [quoted text, click to view] <ken.sumner@gmail.com> wrote in message news:8n0823tmas9r1tia19u6v6193fsl8glt3i@4ax.com... >I am running a large mission critical application on a cluster. This > is a 2003 server latest SP with SQL 2000 Enterprise latest SP also. > > This app has run for years with little change. Today at around 3:00 > all connections stopped coming in. > > After some debugging, we found that we could connect with named > pipes., but not TCP. TCP has been the default protocol for years. > > We have the server monitored and no changes occurred recently. The > server has not been rebooted in months, and the last time the instance > was restarted was two months ago. > > What can cause a server that has run reliably using TCP for years to > stop accepting TCP connectionsl suddenly? > > The errors I am getting is a handshake error trying to connect locally > using TCP, and I get a connection failed error remotely. > > Connections are instant and lovely using named pipes. > > Thanks for any help. >
The clusteipaddr was fine on both instances on both all servers within
the cluster. I want a root cause, but we took the cluster group offline and brought it back online and that resolved the TCP connect issue. On Apr 17, 5:51 am, "Gabe Matteson" <gmatteson.rounder.com.nospam> [quoted text, click to view] wrote: > Can you check > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Cluster > and make sure the clusteripaddr is set to the virtual server ip? > > <ken.sum...@gmail.com> wrote in message > > news:8n0823tmas9r1tia19u6v6193fsl8glt3i@4ax.com... > > > > >I am running a large mission critical application on a cluster. This > > is a 2003 server latest SP with SQL 2000 Enterprise latest SP also. > > > This app has run for years with little change. Today at around 3:00 > > all connections stopped coming in. > > > After some debugging, we found that we could connect with named > > pipes., but not TCP. TCP has been the default protocol for years. > > > We have the server monitored and no changes occurred recently. The > > server has not been rebooted in months, and the last time the instance > > was restarted was two months ago. > > > What can cause a server that has run reliably using TCP for years to > > stop accepting TCP connectionsl suddenly? > > > The errors I am getting is a handshake error trying to connect locally > > using TCP, and I get a connection failed error remotely. > > > Connections are instant and lovely using named pipes. > > > Thanks for any help.- Hide quoted text - > > - Show quoted text -
[quoted text, click to view]
On Apr 17, 9:35 am, ken.sum...@gmail.com wrote: > The clusteipaddr was fine on both instances on both all servers within > thecluster. > > I want a root cause, but we took theclustergroup offline and brought > it back online and that resolved the TCP connect issue. > > On Apr 17, 5:51 am, "Gabe Matteson" <gmatteson.rounder.com.nospam> > wrote: > > > > > Can you check > > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Cluster > > and make sure the clusteripaddr is set to the virtual server ip? > > > <ken.sum...@gmail.com> wrote in message > > >news:8n0823tmas9r1tia19u6v6193fsl8glt3i@4ax.com... > > > >I am running a large mission critical application on acluster. This > > > is a 2003 server latest SP with SQL 2000 Enterprise latest SP also. > > > > This app has run for years with little change. Today at around 3:00 > > > all connections stopped coming in. > > > > After some debugging, we found that we could connect with named > > > pipes., but not TCP. TCP has been the default protocol for years. > > > > We have the server monitored and no changes occurred recently. The > > > server has not been rebooted in months, and the last time the instance > > > was restarted was two months ago. > > > > What can cause a server that has run reliably using TCP for years to > > > stop accepting TCP connectionsl suddenly? > > > > The errors I am getting is a handshake error trying to connect locally > > > using TCP, and I get a connection failed error remotely. > > > > Connections are instant and lovely using named pipes. > > > > Thanks for any help.- Hide quoted text - > > > - Show quoted text -- Hide quoted text - > > - Show quoted text - Another issus that may have had an impact is that just before the problem started, we had a 2019 Srv error: Server was unable to allocate from the system nonpaged pool because pool was empty. Can this have an impact on SQL Server TCP connections only, but allow named pipes to connect?
We have a medium to high amount of .net connections Please explain
further... I am interested. [quoted text, click to view] On Apr 17, 11:17 am, "Geoff N. Hiten" <SQLCrafts...@gmail.com> wrote: > Yes. IIRC, that is where systmem network buffers come from. By chance, do > you have a lot of .Net client application connections? > > -- > Geoff N. Hiten > Senior Database Administrator > Microsoft SQL Server MVP > > <ken.sum...@gmail.com> wrote in message > > news:1176821541.594949.216660@q75g2000hsh.googlegroups.com... > > > > > On Apr 17, 9:35 am, ken.sum...@gmail.com wrote: > >> The clusteipaddr was fine on both instances on both all servers within > >> thecluster. > > >> I want a root cause, but we took theclustergroup offline and brought > >> it back online and that resolved theTCPconnect issue. > > >> On Apr 17, 5:51 am, "Gabe Matteson" <gmatteson.rounder.com.nospam> > >> wrote: > > >> > Can you check > >> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Cluster > >> > and make sure the clusteripaddr is set to the virtual server ip? > > >> > <ken.sum...@gmail.com> wrote in message > > >> >news:8n0823tmas9r1tia19u6v6193fsl8glt3i@4ax.com... > > >> > >I am running a large mission critical application on acluster. This > >> > > is a 2003 server latest SP with SQL 2000 Enterprise latest SP also. > > >> > > This app has run for years with little change. Today at around 3:00 > >> > > all connections stopped coming in. > > >> > > After some debugging, we found that we could connect with named > >> > > pipes., but notTCP. TCPhas been the default protocol for years. > > >> > > We have the server monitored and no changes occurred recently. The > >> > > server has not been rebooted in months, and the last time the > >> > > instance > >> > > was restarted was two months ago. > > >> > > What can cause a server that has run reliably usingTCPfor years to > >> > > stop acceptingTCPconnectionsl suddenly? > > >> > > The errors I am getting is a handshake error trying to connect > >> > > locally > >> > > usingTCP, and I get a connection failed error remotely. > > >> > > Connections are instant and lovely using named pipes. > > >> > > Thanks for any help.- Hide quoted text - > > >> > - Show quoted text -- Hide quoted text - > > >> - Show quoted text - > > > Another issus that may have had an impact is that just before the > > problem started, we had a 2019 Srv error: Server was unable to > > allocate from the system nonpaged pool because pool was empty. > > > Can this have an impact on SQL ServerTCPconnections only, but allow > > named pipes to connect?- Hide quoted text - > > - Show quoted text -
Yes. IIRC, that is where systmem network buffers come from. By chance, do
you have a lot of .Net client application connections? -- Geoff N. Hiten Senior Database Administrator Microsoft SQL Server MVP [quoted text, click to view] <ken.sumner@gmail.com> wrote in message
news:1176821541.594949.216660@q75g2000hsh.googlegroups.com... > On Apr 17, 9:35 am, ken.sum...@gmail.com wrote: >> The clusteipaddr was fine on both instances on both all servers within >> thecluster. >> >> I want a root cause, but we took theclustergroup offline and brought >> it back online and that resolved the TCP connect issue. >> >> On Apr 17, 5:51 am, "Gabe Matteson" <gmatteson.rounder.com.nospam> >> wrote: >> >> >> >> > Can you check >> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Cluster >> > and make sure the clusteripaddr is set to the virtual server ip? >> >> > <ken.sum...@gmail.com> wrote in message >> >> >news:8n0823tmas9r1tia19u6v6193fsl8glt3i@4ax.com... >> >> > >I am running a large mission critical application on acluster. This >> > > is a 2003 server latest SP with SQL 2000 Enterprise latest SP also. >> >> > > This app has run for years with little change. Today at around 3:00 >> > > all connections stopped coming in. >> >> > > After some debugging, we found that we could connect with named >> > > pipes., but not TCP. TCP has been the default protocol for years. >> >> > > We have the server monitored and no changes occurred recently. The >> > > server has not been rebooted in months, and the last time the >> > > instance >> > > was restarted was two months ago. >> >> > > What can cause a server that has run reliably using TCP for years to >> > > stop accepting TCP connectionsl suddenly? >> >> > > The errors I am getting is a handshake error trying to connect >> > > locally >> > > using TCP, and I get a connection failed error remotely. >> >> > > Connections are instant and lovely using named pipes. >> >> > > Thanks for any help.- Hide quoted text - >> >> > - Show quoted text -- Hide quoted text - >> >> - Show quoted text - > > Another issus that may have had an impact is that just before the > problem started, we had a 2019 Srv error: Server was unable to > allocate from the system nonpaged pool because pool was empty. > > Can this have an impact on SQL Server TCP connections only, but allow > named pipes to connect? >
..Net uses an 8k packet size by default. This is larger than the SQL 2000
default packet size and requests for allocations must be serviced from the system nonpaged memory pool rather than the internal network packet pool. The high use from this pool can cause severe fragmentation and memory starvation. You may want to lower the amount of physical memory allocated to SQL Server in this situation. -- Geoff N. Hiten Senior Database Administrator Microsoft SQL Server MVP [quoted text, click to view] <ken.sumner@gmail.com> wrote in message
news:1176830036.621596.271920@o5g2000hsb.googlegroups.com... > We have a medium to high amount of .net connections Please explain > further... I am interested. > > On Apr 17, 11:17 am, "Geoff N. Hiten" <SQLCrafts...@gmail.com> wrote: >> Yes. IIRC, that is where systmem network buffers come from. By chance, >> do >> you have a lot of .Net client application connections? >> >> -- >> Geoff N. Hiten >> Senior Database Administrator >> Microsoft SQL Server MVP >> >> <ken.sum...@gmail.com> wrote in message >> >> news:1176821541.594949.216660@q75g2000hsh.googlegroups.com... >> >> >> >> > On Apr 17, 9:35 am, ken.sum...@gmail.com wrote: >> >> The clusteipaddr was fine on both instances on both all servers within >> >> thecluster. >> >> >> I want a root cause, but we took theclustergroup offline and brought >> >> it back online and that resolved theTCPconnect issue. >> >> >> On Apr 17, 5:51 am, "Gabe Matteson" <gmatteson.rounder.com.nospam> >> >> wrote: >> >> >> > Can you check >> >> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Cluster >> >> > and make sure the clusteripaddr is set to the virtual server ip? >> >> >> > <ken.sum...@gmail.com> wrote in message >> >> >> >news:8n0823tmas9r1tia19u6v6193fsl8glt3i@4ax.com... >> >> >> > >I am running a large mission critical application on acluster. >> >> > >This >> >> > > is a 2003 server latest SP with SQL 2000 Enterprise latest SP >> >> > > also. >> >> >> > > This app has run for years with little change. Today at around >> >> > > 3:00 >> >> > > all connections stopped coming in. >> >> >> > > After some debugging, we found that we could connect with named >> >> > > pipes., but notTCP. TCPhas been the default protocol for years. >> >> >> > > We have the server monitored and no changes occurred recently. The >> >> > > server has not been rebooted in months, and the last time the >> >> > > instance >> >> > > was restarted was two months ago. >> >> >> > > What can cause a server that has run reliably usingTCPfor years to >> >> > > stop acceptingTCPconnectionsl suddenly? >> >> >> > > The errors I am getting is a handshake error trying to connect >> >> > > locally >> >> > > usingTCP, and I get a connection failed error remotely. >> >> >> > > Connections are instant and lovely using named pipes. >> >> >> > > Thanks for any help.- Hide quoted text - >> >> >> > - Show quoted text -- Hide quoted text - >> >> >> - Show quoted text - >> >> > Another issus that may have had an impact is that just before the >> > problem started, we had a 2019 Srv error: Server was unable to >> > allocate from the system nonpaged pool because pool was empty. >> >> > Can this have an impact on SQL ServerTCPconnections only, but allow >> > named pipes to connect?- Hide quoted text - >> >> - Show quoted text - > >
Thanks for the info. Doing the math, this could be our issue. But
how could that cause TPC only to stop working but allow named pipes to work without issue? [quoted text, click to view] On Apr 17, 1:50 pm, "Geoff N. Hiten" <SQLCrafts...@gmail.com> wrote:
> .Net uses an 8k packet size by default. This is larger than the SQL 2000 > default packet size and requests for allocations must be serviced from the > system nonpaged memory pool rather than the internal network packet pool. > The high use from this pool can cause severe fragmentation and memory > starvation. You may want to lower the amount of physical memory allocated > to SQL Server in this situation. > > -- > Geoff N. Hiten > Senior Database Administrator > Microsoft SQL Server MVP > > <ken.sum...@gmail.com> wrote in message > > news:1176830036.621596.271920@o5g2000hsb.googlegroups.com... > > > > > We have a medium to high amount of .net connections Please explain > > further... I am interested. > > > On Apr 17, 11:17 am, "Geoff N. Hiten" <SQLCrafts...@gmail.com> wrote: > >> Yes. IIRC, that is where systmem network buffers come from. By chance, > >> do > >> you have a lot of .Net client application connections? > > >> -- > >> Geoff N. Hiten > >> Senior Database Administrator > >> Microsoft SQL Server MVP > > >> <ken.sum...@gmail.com> wrote in message > > >>news:1176821541.594949.216660@q75g2000hsh.googlegroups.com... > > >> > On Apr 17, 9:35 am, ken.sum...@gmail.com wrote: > >> >> The clusteipaddr was fine on both instances on both all servers within > >> >> thecluster. > > >> >> I want a root cause, but we took theclustergroup offline and brought > >> >> it back online and that resolved theTCPconnect issue. > > >> >> On Apr 17, 5:51 am, "Gabe Matteson" <gmatteson.rounder.com.nospam> > >> >> wrote: > > >> >> > Can you check > >> >> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Cluster > >> >> > and make sure the clusteripaddr is set to the virtual server ip? > > >> >> > <ken.sum...@gmail.com> wrote in message > > >> >> >news:8n0823tmas9r1tia19u6v6193fsl8glt3i@4ax.com... > > >> >> > >I am running a large mission critical application on acluster. > >> >> > >This > >> >> > > is a 2003 server latest SP with SQL 2000 Enterprise latest SP > >> >> > > also. > > >> >> > > This app has run for years with little change. Today at around > >> >> > > 3:00 > >> >> > > all connections stopped coming in. > > >> >> > > After some debugging, we found that we could connect with named > >> >> > > pipes., but notTCP. TCPhas been the default protocol for years. > > >> >> > > We have the server monitored and no changes occurred recently. The > >> >> > > server has not been rebooted in months, and the last time the > >> >> > > instance > >> >> > > was restarted was two months ago. > > >> >> > > What can cause a server that has run reliably usingTCPfor years to > >> >> > > stop acceptingTCPconnectionsl suddenly? > > >> >> > > The errors I am getting is a handshake error trying to connect > >> >> > > locally > >> >> > > usingTCP, and I get a connection failed error remotely. > > >> >> > > Connections are instant and lovely using named pipes. > > >> >> > > Thanks for any help.- Hide quoted text - > > >> >> > - Show quoted text -- Hide quoted text - > > >> >> - Show quoted text - > > >> > Another issus that may have had an impact is that just before the > >> > problem started, we had a 2019 Srv error: Server was unable to > >> > allocate from the system nonpaged pool because pool was empty. > > >> > Can this have an impact on SQL ServerTCPconnections only, but allow > >> > named pipes to connect?- Hide quoted text - > > >> - Show quoted text -- Hide quoted text - > > - Show quoted text -
I wasn't clear in the last post. The memory gets fragmented and the
OS is starved. There are issues and the noted error messages. Reducing SQL's memory footprint, and allowing the OS more room, should resolve the problem. Now the question goes to why it quits accepting TCP connections? Are you saying that the non-paged pool doesn't recover-- when the load drops, and you must reinitialize this pool after this issue happens? [quoted text, click to view] On Apr 17, 7:05 pm, ken.sum...@gmail.com wrote: > Thanks for the info. Doing the math, this could be our issue. But > how could that cause TPC only to stop working but allow named pipes > to work without issue? > > On Apr 17, 1:50 pm, "Geoff N. Hiten" <SQLCrafts...@gmail.com> wrote: > > > > > .Net uses an 8k packet size by default. This is larger than the SQL 2000 > > default packet size and requests for allocations must be serviced from the > > system nonpaged memory pool rather than the internal network packet pool. > > The high use from this pool can cause severe fragmentation and memory > > starvation. You may want to lower the amount of physical memory allocated > > to SQL Server in this situation. > > > -- > > Geoff N. Hiten > > Senior Database Administrator > > Microsoft SQL Server MVP > > > <ken.sum...@gmail.com> wrote in message > > >news:1176830036.621596.271920@o5g2000hsb.googlegroups.com... > > > > We have a medium to high amount of .net connections Please explain > > > further... I am interested. > > > > On Apr 17, 11:17 am, "Geoff N. Hiten" <SQLCrafts...@gmail.com> wrote: > > >> Yes. IIRC, that is where systmem network buffers come from. By chance, > > >> do > > >> you have a lot of .Net client application connections? > > > >> -- > > >> Geoff N. Hiten > > >> Senior Database Administrator > > >> Microsoft SQL Server MVP > > > >> <ken.sum...@gmail.com> wrote in message > > > >>news:1176821541.594949.216660@q75g2000hsh.googlegroups.com... > > > >> > On Apr 17, 9:35 am, ken.sum...@gmail.com wrote: > > >> >> The clusteipaddr was fine on both instances on both all servers within > > >> >> thecluster. > > > >> >> I want a root cause, but we took theclustergroup offline and brought > > >> >> it back online and that resolved theTCPconnect issue. > > > >> >> On Apr 17, 5:51 am, "Gabe Matteson" <gmatteson.rounder.com.nospam> > > >> >> wrote: > > > >> >> > Can you check > > >> >> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Cluster > > >> >> > and make sure the clusteripaddr is set to the virtual server ip? > > > >> >> > <ken.sum...@gmail.com> wrote in message > > > >> >> >news:8n0823tmas9r1tia19u6v6193fsl8glt3i@4ax.com... > > > >> >> > >I am running a large mission critical application on acluster. > > >> >> > >This > > >> >> > > is a 2003 server latest SP with SQL 2000 Enterprise latest SP > > >> >> > > also. > > > >> >> > > This app has run for years with little change. Today at around > > >> >> > > 3:00 > > >> >> > > all connections stopped coming in. > > > >> >> > > After some debugging, we found that we could connect with named > > >> >> > > pipes., but notTCP. TCPhas been the default protocol for years. > > > >> >> > > We have the server monitored and no changes occurred recently. The > > >> >> > > server has not been rebooted in months, and the last time the > > >> >> > > instance > > >> >> > > was restarted was two months ago. > > > >> >> > > What can cause a server that has run reliably usingTCPfor years to > > >> >> > > stop acceptingTCPconnectionsl suddenly? > > > >> >> > > The errors I am getting is a handshake error trying to connect > > >> >> > > locally > > >> >> > > usingTCP, and I get a connection failed error remotely. > > > >> >> > > Connections are instant and lovely using named pipes. > > > >> >> > > Thanks for any help.- Hide quoted text - > > > >> >> > - Show quoted text -- Hide quoted text - > > > >> >> - Show quoted text - > > > >> > Another issus that may have had an impact is that just before the > > >> > problem started, we had a 2019 Srv error: Server was unable to > > >> > allocate from the system nonpaged pool because pool was empty. > > > >> > Can this have an impact on SQL ServerTCPconnections only, but allow > > >> > named pipes to connect?- Hide quoted text - > > > >> - Show quoted text -- Hide quoted text - > > > - Show quoted text -- Hide quoted text - > > - Show quoted text -
That or something similar appears to be the case.
This error with non-paged memory happened at 3:00 yesterday afternoon. There was heavy traffic, but there has been worse without error. After this error no TCP connections could be made to the SQL server. Pings to the server were fine. I could Telnet to the SQL instance fine via both UDP port and to TCP port. Connections were great with Named Pipes. The connection error everyone got when they tried to connect to the server was either an invalid connnect string error or a handshake error, like TCP was suddenly Greek to the SQL instance. We brought the clustergroup offline and then back online, TCP worked problem resolved. The group was never moved nor did it fail over. [quoted text, click to view] On 17 Apr 2007 16:21:53 -0700, ken.sumner@gmail.com wrote:
>I wasn't clear in the last post. The memory gets fragmented and the >OS is starved. There are issues and the noted error messages. >Reducing SQL's memory footprint, and allowing the OS more room, should >resolve the problem. > >Now the question goes to why it quits accepting TCP connections? Are >you saying that the non-paged pool doesn't recover-- when the load >drops, and you must reinitialize this pool after this issue happens? > >On Apr 17, 7:05 pm, ken.sum...@gmail.com wrote: >> Thanks for the info. Doing the math, this could be our issue. But >> how could that cause TPC only to stop working but allow named pipes >> to work without issue? >> >> On Apr 17, 1:50 pm, "Geoff N. Hiten" <SQLCrafts...@gmail.com> wrote: >> >> >> >> > .Net uses an 8k packet size by default. This is larger than the SQL 2000 >> > default packet size and requests for allocations must be serviced from the >> > system nonpaged memory pool rather than the internal network packet pool. >> > The high use from this pool can cause severe fragmentation and memory >> > starvation. You may want to lower the amount of physical memory allocated >> > to SQL Server in this situation. >> >> > -- >> > Geoff N. Hiten >> > Senior Database Administrator >> > Microsoft SQL Server MVP >> >> > <ken.sum...@gmail.com> wrote in message >> >> >news:1176830036.621596.271920@o5g2000hsb.googlegroups.com... >> >> > > We have a medium to high amount of .net connections Please explain >> > > further... I am interested. >> >> > > On Apr 17, 11:17 am, "Geoff N. Hiten" <SQLCrafts...@gmail.com> wrote: >> > >> Yes. IIRC, that is where systmem network buffers come from. By chance, >> > >> do >> > >> you have a lot of .Net client application connections? >> >> > >> -- >> > >> Geoff N. Hiten >> > >> Senior Database Administrator >> > >> Microsoft SQL Server MVP >> >> > >> <ken.sum...@gmail.com> wrote in message >> >> > >>news:1176821541.594949.216660@q75g2000hsh.googlegroups.com... >> >> > >> > On Apr 17, 9:35 am, ken.sum...@gmail.com wrote: >> > >> >> The clusteipaddr was fine on both instances on both all servers within >> > >> >> thecluster. >> >> > >> >> I want a root cause, but we took theclustergroup offline and brought >> > >> >> it back online and that resolved theTCPconnect issue. >> >> > >> >> On Apr 17, 5:51 am, "Gabe Matteson" <gmatteson.rounder.com.nospam> >> > >> >> wrote: >> >> > >> >> > Can you check >> > >> >> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Cluster >> > >> >> > and make sure the clusteripaddr is set to the virtual server ip? >> >> > >> >> > <ken.sum...@gmail.com> wrote in message >> >> > >> >> >news:8n0823tmas9r1tia19u6v6193fsl8glt3i@4ax.com... >> >> > >> >> > >I am running a large mission critical application on acluster. >> > >> >> > >This >> > >> >> > > is a 2003 server latest SP with SQL 2000 Enterprise latest SP >> > >> >> > > also. >> >> > >> >> > > This app has run for years with little change. Today at around >> > >> >> > > 3:00 >> > >> >> > > all connections stopped coming in. >> >> > >> >> > > After some debugging, we found that we could connect with named >> > >> >> > > pipes., but notTCP. TCPhas been the default protocol for years. >> >> > >> >> > > We have the server monitored and no changes occurred recently. The >> > >> >> > > server has not been rebooted in months, and the last time the >> > >> >> > > instance >> > >> >> > > was restarted was two months ago. >> >> > >> >> > > What can cause a server that has run reliably usingTCPfor years to >> > >> >> > > stop acceptingTCPconnectionsl suddenly? >> >> > >> >> > > The errors I am getting is a handshake error trying to connect >> > >> >> > > locally >> > >> >> > > usingTCP, and I get a connection failed error remotely. >> >> > >> >> > > Connections are instant and lovely using named pipes. >> >> > >> >> > > Thanks for any help.- Hide quoted text - >> >> > >> >> > - Show quoted text -- Hide quoted text - >> >> > >> >> - Show quoted text - >> >> > >> > Another issus that may have had an impact is that just before the >> > >> > problem started, we had a 2019 Srv error: Server was unable to >> > >> > allocate from the system nonpaged pool because pool was empty. >> >> > >> > Can this have an impact on SQL ServerTCPconnections only, but allow >> > >> > named pipes to connect?- Hide quoted text - >> >> > >> - Show quoted text -- Hide quoted text - >> >> > - Show quoted text -- Hide quoted text - >> >> - Show quoted text -
TCP packet allocation is different than named pipes and is not as sensitive
to nonpaged pool fragmentation. Wyy something breaks today and not yestereday or tomorrow on an apparantly stable system is a question that keeps many DBAs gainfully employed. I wish I had the easy answer to that one. -- Geoff N. Hiten Senior Database Administrator Microsoft SQL Server MVP [quoted text, click to view] <ken.sumner@gmail.com> wrote in message
news:8n0823tmas9r1tia19u6v6193fsl8glt3i@4ax.com... >I am running a large mission critical application on a cluster. This > is a 2003 server latest SP with SQL 2000 Enterprise latest SP also. > > This app has run for years with little change. Today at around 3:00 > all connections stopped coming in. > > After some debugging, we found that we could connect with named > pipes., but not TCP. TCP has been the default protocol for years. > > We have the server monitored and no changes occurred recently. The > server has not been rebooted in months, and the last time the instance > was restarted was two months ago. > > What can cause a server that has run reliably using TCP for years to > stop accepting TCP connectionsl suddenly? > > The errors I am getting is a handshake error trying to connect locally > using TCP, and I get a connection failed error remotely. > > Connections are instant and lovely using named pipes. > > Thanks for any help. >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |