Develop Reference

IIS 8.5 connection timeout is _always_ 60 seconds

I have an ASP.NET application running on IIS 8.5 that times out at 60 seconds regardless of what I set. In other words, I can set the connection timeout to 300 seconds or 30 seconds and the page will still time out at 60 seconds. The Request status code is 504 GATEWAY_TIMEOUT.
Site:
Connection timeout = 300 seconds (5 mins)
Session timeout = 20 minutes
Script timeout = 10 minutes
App Pool:
.NET CLR v4.0
Integrated pipeline
64-bit (32-bit not allowed)
Idle timeout = 20 mins (default)
Other things I've done:
Read just about every article I can on this subject
Set the executionTimeout in my web.config
Restarted the site or ran iisreset after each change
Disabled all sites except this one to isolate it
Created a simple ASPX page in which I set a Sleep thread to under or over 60 seconds, and tried every combination with the connection timeout value.
I'm at a loss. Any ideas?

The answer turned out to be a load balancer, which I was unaware existed, that had its own timeout setting.

Check your maxRequestLength, apparently that can cause a 504 if the incoming request exceeds the default limit of 4MB.
504 Error On Server
Can big ViewState content result a HTTP Error 504 - Gateway timeout?

timeout exception in asp.net application

I cannot figure out why I am getting timeout exception in asp.net application upon signing into application and when I restart my webserver I don't get timeout exception?
Environment:
Asp.net application(IIS webserver) and DB (Sql server)
both IIS and Sql server are on two different machines.
Sql server timeout:600 seconds
Webconfig setting:
<httpRuntime maxRequestLength="16384" executionTimeout="270"/>
<sessionState mode="InProc" cookieless="false" timeout="60" stateConnectionString="">
Thanks in advance.
Screenshot of error:

Try to add connection timeout in connection string as "Data Source=SQLSERVER;Initial Catalog=MYCATALOG;Integrated Security=True;Connection Timeout=1000".if again "The wait operation timed out" then it is likely you have a database call that took longer than expected. This could be due to any number of things:
Transient network problem
High SQL server load
Problem with SAN, RAID, or storage device
Deadlock or other form of multiprocess contention
You haven't shared enough information to troubleshoot. The way I would manage this would be to check for other occurrences of the problem and see if there is a pattern, e.g. if the problem occurs at a certain time of day.
Certainly increasing the timeout is not a bad idea (if it is currently set pretty low) and may resolve the problem in and of itself.

IIS ASP.NET Session is lost

I know that this has been asked several times, but in the web config we set the
<sessionState timeout="2880"></sessionState>
the app pool recycle is 1740 minutes, the application pool timeout is also 1740 mins now,
ping and rapid fail protection is turned off, and in the global.asax we log every application start, session start/end, application error.
I see 2 "application start" than 2 "session start" in the logs, nothing changes, a few minutes later, we get a new "application start" (2 of them again) with 2 "session start"-s, with the same sessionid as before (no "session end" in between). The result is a web application that quits every few minutes.

Not sure about this, but how many instance of the application do you allow?
Under IIS>Application Pools>YourAppPool>Advanced Settings;
you'll find relevant settings:
idle time-out (set to 0?)
Disable Overlapped Recycle (this might be your culprit;a new instance starts before the old one is disposed?)
Another thing i can think of is 'Service Throttling' on your binding, or perhaps there are multiple Sessions or Instances allowed?

My ASP.NET web service on localhost is timing out too quickly

So here I am, trying to debug a little problem in my ASP.NET web service on localhost, and while I am stepping through it, the darned thing times out. Here I thought the default timeout value was 20 minutes. But the timeout appears to happen at 30 seconds -- I've timed it twice -- although it was 20 seconds in another timing I did.
I've tried to govern this by setting sessionState timeout to 30, in accordance with what MSDN says about HttpSessionState HERE. With this code:
<sessionState
mode="InProc"
cookieless="true"
timeout="30" />
in .
MSDN says the value of the timeout is supposed to be in minutes ("Gets and sets the amount of time, in minutes..."), but it doesn't really seem to make any difference what it's set to. Machine.config does not specify any value, so it should default to 20 minutes.
I am running in IIS 7.5. I checked the properties of the ASP.NET Session State Mode Settings in IIS, and it is selected as "In process". I don't know how this affects things, if it does.
So this is a mystery to me.

If your client is timing out when calling a web service take a look at-
http://msdn.microsoft.com/en-us/library/system.web.services.protocols.webclientprotocol.timeout.aspx

Setting Connection time out programmatically in asp.net

Is there a way to Set Connection timeout used in IIS in asp.net programaticaly in one page ? without setting it globally for all the website from IIS itself ?

Update your connection string.
Add Connection Timeout=900 in your connection string.
Connection Timeout always specified in seconds and Default is 30 seconds.
You can set these according to your need.
Your connection string may look like:
server=servername;database=DBName;User ID=UserID;Password=PWD; Connect Timeout=timeinseconds
Hope its helpful.

Create a second cpnnection string in your web config with out timeout and in the page you want, add timeout you want.