Click here to Skip to main content
15,889,266 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
HI All,
Good Evening,

In my project i am showing the dashboard in the home page ....

it is having more number of queries ...

whenever i am trying to login it shows the error like this...

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

How to solve this?

pls help me guys its urgent!!!@

Thanks In Advance.........
Posted
Comments
saguptamca 30-Apr-13 8:33am    
Where u stuck?? Show your code in order to help you...

Verify that you have closed all the connection after the completion of the operation on database(Connection.Close()). I suspect that you have too many connection that needs to be closed.
 
Share this answer
 
Comments
[no name] 30-Apr-13 8:31am    
Almost all the connections i closed...
Thanks7872 30-Apr-13 8:33am    
Close each and every connection.Recheck your code.Default value of max pool size is 100 and min pool size is 0.Have a look at this article to better understand the concept.
[no name] 30-Apr-13 8:38am    
can't we incrase the default size of connection pool?
Thanks7872 30-Apr-13 8:48am    
connectionString="Server=XXX;Database=XXX;User Id=XXX;password=XXX;connection timeout=0;Max Pool Size = 100;Pooling = True"
Hi,

You can even extend timeout value for specific function in cs file also.
SqlCommandObject.CommandTimeout = 500000;

It might work out for you.

Regards,
RK
 
Share this answer
 
v3
Comments
[no name] 30-Apr-13 8:39am    
how to extend the connection time out value in web.config file?
♥…ЯҠ…♥ 30-Apr-13 8:48am    
You can do it in app.config file, but it wont reflect in your application i believe
Thanks7872 30-Apr-13 8:48am    
connectionString="Server=XXX;Database=XXX;User Id=XXX;password=XXX;connection timeout=0;Max Pool Size = 100;Pooling = True"
[no name] 2-May-13 0:25am    
how much i need to keep timeout i tried with timeout=200 still same problem....what to do
♥…ЯҠ…♥ 2-May-13 0:57am    
try increasing the timeout value by thousands.....
Profile the SQL Server while executing this query ..after that apply the recommendations about indexes and statistics..It seems that query is taking too long to execute..increasing command timeout could be a temporary solution but you need to fix the query for performance issues..
 
Share this answer
 

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900