Server Error in '/' Application. Request timed out. HttpException (0x80004005):

[SHOPS]

Hi all,

I know this is probably not the first time this questions has been asked, however I feel that we have an exceptional circumstance.

We get the afforementioned error on almost every page in our .net application. We even get in on the login screen to the app. The annoyance is that we have set teh timeout in the web.config file to 100000000. The timeout error happens within a couple of seconds of trying to loads a page. Clearly it isn't giving teh application time to finish the request.

Wea re using .net 2.0 and server 2003. I am not on the tech team, but our development team have no idea how to fix this problem. I am emploring anyone for help.

Sadly this error has occured since we sent the software live and hence we are losing money every minute this error is present. We haven't added any new patches to the webserver or the database server. The problem has only started since Monday this week. We haven't done anything to instigate this problem.

We are stumped.

Anyone got any ideas?

[CalBob]

Hi all,

I know this is probably not the first time this questions has been asked, however I feel that we have an exceptional circumstance.

We get the afforementioned error on almost every page in our .net application. We even get in on the login screen to the app. The annoyance is that we have set teh timeout in the web.config file to 100000000. The timeout error happens within a couple of seconds of trying to loads a page. Clearly it isn't giving teh application time to finish the request.

Wea re using .net 2.0 and server 2003. I am not on the tech team, but our development team have no idea how to fix this problem. I am emploring anyone for help.

Sadly this error has occured since we sent the software live and hence we are losing money every minute this error is present. We haven't added any new patches to the webserver or the database server. The problem has only started since Monday this week. We haven't done anything to instigate this problem.

We are stumped.

Anyone got any ideas?

If you are running a stored procedure, use CommandTimeout = (and the number of seconds you need). I have this issue for some reports and had to set it to 90 (seconds). I don't remember the default setting.