Last post Jul 25, 2013 05:07 AM by sameer_khanjit
Jul 18, 2013 06:27 AM|PHJ|LINK
I try to generate the report for a particular team, but after around 2 and half seconds it shows "page cannot be displayed".
When I execute the procedure (behind this report) in SSMS in server, it shows the output in 2.39 seconds.
Below are the time out setting from my web.config.
<sessionState timeout="60" />
<httpRuntime maxRequestLength="153600" appRequestQueueLimit="50000" executionTimeout="300000"/>
Please let me know if miss anything...
Thanks in advance.
Jul 18, 2013 08:02 AM|aruna.puja|LINK
Add to database command the timeout attribute
dbCommand.CommandTimeout = 60; // (in sec)
Jul 19, 2013 03:09 AM|PHJ|LINK
Thanks for your comment...
But it still not working, it'sshowing "page cannot be displayed".
Below is the code u suggested.
cmd.CommandTimeout = 300;
Jul 19, 2013 03:51 AM|vijay_myl|LINK
Try this below lnk to find out prob for your post..
Jul 19, 2013 04:52 AM|PHJ|LINK
No I tried, its not working...
Any other suggestion...
Jul 23, 2013 05:16 AM|Shawn - MSFT|LINK
This behavior occurs because of the transaction time-out setting for the table designer and for the database designer in SQL Server Management Studio. You can specify this setting in the
Transaction time-out after box. By default, this setting is 30 seconds.
Notice that this setting differs from the setting in the
Execution time-out box in SQL Server Management Studio. By default, the setting in the
Execution time-out box for Query Editor in SQL Server Management Studio is zero. By default, the setting in the
Query time-out (seconds) box for Query Editor in Microsoft SQL Server 2000 SQL Query Analyzer is also zero. Therefore, Query Editor waits infinitely for the query to finish and never times out.
For more information and the solution, you could refer to:
Jul 23, 2013 05:22 AM|Sathesh_Pandian|LINK
it seems its not an error with your application setup. its an issue with your query. Please check your queries with execution plan to analyse.
Jul 24, 2013 05:32 AM|PHJ|LINK
I tried increasing the timeout value and also clearing the checkbox, but it's not working...
But thanks for the reply, atleast I came to know new thing.. :)
Jul 24, 2013 05:35 AM|Sathesh_Pandian|LINK
Have you verified your queries which are taking much time?
Check the query's result in sql browser and make sure that you are getting the same in all places.
Please use execution plan to verify the query
Jul 25, 2013 05:07 AM|sameer_khanjit|LINK
you can also try to increase connectiontimeout in sqlcommand or in wbeconfiguration