Re: TCP connections suddenly failing.
- From: "Geoff N. Hiten" <SQLCraftsman@xxxxxxxxx>
- Date: Tue, 17 Apr 2007 11:17:22 -0400
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.sumner@xxxxxxxxx> wrote in message news:1176821541.594949.216660@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Apr 17, 9:35 am, ken.sum...@xxxxxxxxx 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...@xxxxxxxxx> wrote in message
>news:8n0823tmas9r1tia19u6v6193fsl8glt3i@xxxxxxxxxx
> >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?
.
- Follow-Ups:
- Re: TCP connections suddenly failing.
- From: ken . sumner
- Re: TCP connections suddenly failing.
- References:
- TCP connections suddenly failing.
- From: ken . sumner
- Re: TCP connections suddenly failing.
- From: Gabe Matteson
- Re: TCP connections suddenly failing.
- From: ken . sumner
- Re: TCP connections suddenly failing.
- From: ken . sumner
- TCP connections suddenly failing.
- Prev by Date: Re: TCP connections suddenly failing.
- Next by Date: Re: drive not visible in the SQL server
- Previous by thread: Re: TCP connections suddenly failing.
- Next by thread: Re: TCP connections suddenly failing.
- Index(es):
Relevant Pages
|