• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4497
  • Last Modified:

The semaphore timeout period has expired

A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.)

when running a 2minute SQL query from asp.net / c#

It was working everytime when I had it running on my local machine yet still reading data from the SQL box.
0
andrewmilner
Asked:
andrewmilner
  • 6
  • 4
1 Solution
 
RiteshShahCommented:
increase connection timeout limit from your web.config file, where you have declared your connection. It seems issue with big query only
0
 
andrewmilnerAuthor Commented:
Connection Timeout=600 already.
This is popping up after about 2 mins.
0
 
RiteshShahCommented:
can you please use following connection string with your own credential, just for testing.

"data source=;initial catalog=;password=;persist security info=True;user id=;packet size=4096;Connection Lifetime=202130;Pooling=false;Connect Timeout=202545"



0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
andrewmilnerAuthor Commented:
Still get same.
I had to add providerName="System.Data.SqlClient" at the end of the conn string in web.config.
0
 
andrewmilnerAuthor Commented:
The odd thing is is that if I run this out of Visual Studio's ASP.NETs development web server then it runs everytime.  But once I copy the files to my web-server that has Sql Server 2000 instaleld locally it fails 4 times out of 5.
0
 
RiteshShahCommented:
Can you set your application in separate pool in IIS?
0
 
andrewmilnerAuthor Commented:
OKay tried the new app pool.
Issue remains.
0
 
andrewmilnerAuthor Commented:
Any other ideas / fix?
0
 
RiteshShahCommented:
I don't have, let thread open for other experts.
0
 
andrewmilnerAuthor Commented:
SOLVED.
New Hardware with a faster CPU, + clean rebuild of the server.
It was in the pipeline anyway, just lucky that it resolved this issue.
I'm sure there would have been someway to fix without it though which remains a mystery.
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 6
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now