Groups > microsoft.public.sqlserver.programming > #31307

Re: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

X-Received	by 10.157.1.76 with SMTP id 70mr4386532otu.96.1477026862438; Thu, 20 Oct 2016 22:14:22 -0700 (PDT)
X-Received	by 10.157.6.102 with SMTP id 93mr2289142otn.11.1477026862407; Thu, 20 Oct 2016 22:14:22 -0700 (PDT)
Path	csiph.com!weretis.net!feeder6.news.weretis.net!news.glorb.com!e187no1204705itc.0!news-out.google.com!w143ni135itb.0!nntp.google.com!e187no1204694itc.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups	microsoft.public.sqlserver.programming
Date	Thu, 20 Oct 2016 22:14:22 -0700 (PDT)
In-Reply-To	<f63d6166-4db7-402d-8b3e-71596c98a5a1@w2g2000vbp.googlegroups.com>
Complaints-To	groups-abuse@google.com
Injection-Info	glegroupsg2000goo.googlegroups.com; posting-host=174.30.115.244; posting-account=lyLZNAoAAABoKQVTd1DfFS2pE0aTPl7Z
NNTP-Posting-Host	174.30.115.244
References	<f83225e8-d3e8-42bf-b967-16ab98c7d511@i17g2000vbq.googlegroups.com> <Xns9E6AF07B5108FYazorman@127.0.0.1> <4a06a887-67c8-4a04-8183-efbc25cb061b@29g2000yqq.googlegroups.com> <Xns9E6B62D29335EYazorman@127.0.0.1> <e665a8d0-0598-4113-950e-2736ad976c78@15g2000vbz.googlegroups.com> <Xns9E6BEAE39E858Yazorman@127.0.0.1> <24b4ac57-d9ea-4218-9c84-7abdd8e42b1f@i18g2000yqn.googlegroups.com> <Xns9E757AD3EC503Yazorman@127.0.0.1> <9b5aeeba-7c06-4785-933f-62927200385d@n10g2000yqd.googlegroups.com> <Xns9E7683C0CFEA2Yazorman@127.0.0.1> <c0e3fb2b-b3ed-4098-bb79-ff240b4edfd4@r29g2000yqj.googlegroups.com> <Xns9E76A723CDF39Yazorman@127.0.0.1> <9c8c939d-8f9a-401f-a496-2a246a6b5b43@fm22g2000vbb.googlegroups.com> <f63d6166-4db7-402d-8b3e-71596c98a5a1@w2g2000vbp.googlegroups.com>
User-Agent	G2/1.0
MIME-Version	1.0
Message-ID	<a5bfcd6d-5b93-4e3e-8ba7-422fd14493d7@googlegroups.com> (permalink)
Subject	Re: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
From	007kpchowdary@gmail.com
Injection-Date	Fri, 21 Oct 2016 05:14:22 +0000
Content-Type	text/plain; charset=UTF-8
Content-Transfer-Encoding	quoted-printable
Xref	csiph.com microsoft.public.sqlserver.programming:31307

Show key headers only | View raw

On Monday, January 24, 2011 at 8:43:12 AM UTC-6, fniles wrote:
> Also, around the same time our network person was on that SQL Server
> machine and was on Windows explorer, and he said Windows Explorer was
> not responding at that time also.
> 
> 
> On Jan 24, 6:38 am, fniles <fiefie.ni...@gmail.com> wrote:
> > I have more information about the problem, because it happened again
> > last night, during a non busy time.
> >
> > We have 3 databases on that SQL Server machine, and multiple different
> > applications (on 3 different machines) connect to those 3 databases.
> > Those applications around the same time got the "Timeout expired"
> > error either when reading a query (different queries on different
> > applications) or opening the database.
> >
> > Meanwhile, another application that connect to a database on a
> > different SQL Server machine didn't get the error.
> >
> > It seems like there is a problem with that SQL Server machine may be ?
> > Like there is a network problem connecting to that SQL Server
> > machine ?
> >
> > On Jan 23, 9:25 am, Erland Sommarskog <esq...@sommarskog.se> wrote:
> >
> >
> >
> > > fniles (fiefie.ni...@gmail.com) writes:
> > > > Although it is a single application, it is using multiple threads,
> > > > each thread for every client that connects to it.
> > > > So, in this case you no longer think it is SQL Server run out of
> > > > worker threads ?
> >
> > > No. My prime guess is that this could be the reason.
> >
> > > But as I said, it's difficult to make a diagnosis of the situation on a
> > > distance. And to be honest, I have not experienced that particular situation
> > > myself, so I mainly rely on what I eavesdropped from discussions elsewhere.
> >
> > > --
> > > Erland Sommarskog, SQL Server MVP, esq...@sommarskog.se
> >
> > > Links for SQL Server Books Online:
> > > SQL 2008:http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
> > > SQL 2005:http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx- Hide quoted text -
> >
> > - Show quoted text -


http://www.sqlpassion.at/archive/2011/10/25/troubleshooting-threadpool-waits/

Back to microsoft.public.sqlserver.programming | Previous | Next | Find similar

Thread

Re: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. 007kpchowdary@gmail.com - 2016-10-20 22:14 -0700

csiph-web