Timeout Error in SQL server

Question

0.00/5 (No votes)

See more:

SQL-Server-2008R2

Iam getting the following error in the C# console application which continuously runs in a server.

Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool.
This may have occurred because all pooled connections were in use and max pool size was reached

I have tried by setting sqlcmd.CommandTimeout = 120;

Please suggest a solution for this error.

Posted 9-Apr-13 19:01pm

Member 8445821

Add a Solution

Comments

crazie.coder 10-Apr-13 1:28am

go to your management studio where you connect your sql server instance,select your instance then before click on "connect", press "option>>" button ,you'll able to see connection properties ,set "connection timeout" is "0". might be your problem will solve.

crazie.coder 10-Apr-13 1:29am

if there is an error if max pool then please make sure you have closed connection every time after opened the same.
then let me know .

Member 8445821 10-Apr-13 1:56am

Thanks Juhi Paunikar. I have verified whether iam closing the connections or not.It remains opened.So Now i changed to close the connections.Will check and say you whether the error still persists. Thanks once again.

crazie.coder 12-Apr-13 4:25am

go to your management studio where you connect your sql server instance,select your instance then before click on "connect", press "option>>" button ,you'll able to see connection properties ,set "connection timeout" is "0". might be your problem will solve.have you tried that?

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

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

Bernhard Hiller · Answer 1 · 2013-04-10T21:58:00

Solution 2

You need the ConnectionTimeout property of the Connection object - the CommandTimeout is something different!

Posted 10-Apr-13 21:58pm

Bernhard Hiller

Abhimanyu Rawat · Answer 2 · 2013-04-10T02:01:00

Solution 1

Hello

you just add

command.CommandTimeout = 0;

happy coding

Thanks
Abhimanyu Rawat

Posted 10-Apr-13 2:01am

Abhimanyu Rawat