Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

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

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

Back to article view | Back to microsoft.public.sqlserver.programming

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  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

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

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/

[toc] | [standalone]

Back to top | Article view | microsoft.public.sqlserver.programming

csiph-web