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

Question

0.00/5 (No votes)

See more:

SQL-server-2000

VS2005

, +

Hi,

I have dot net application which update several table in my database for a single functionality Example (pass file).

One button "pass file" is there when I click it do many DML and sql query.
For first few click it will work successfully, but after some times it show below message.

VB

Error Occured: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. The statement has been terminated.

I have tried by increase timeout and make it zero also. Still not able to solve the issue.

Please suggest me how i can resolve this issue.

Thanks and Regards
Asutosha Sarangi

Posted 23-Sep-11 1:39am

Asutosha

Add a Solution

Comments

Mehdi Gholam 23-Sep-11 7:48am

It seems you might have locking issues? Post your exception details.

P.Salini 23-Sep-11 7:49am

increase maxrequestlength in httpruntime tag in web.config file
and then try once again

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)

bbirajdar · Answer 1 · 2011-09-23T03:30:00

Solution 1

Make sure that you are releasing the connection objects in your data access layer.

If you are running multiple statements in the stored procedure, then seperate them with 'GO'

Also try specifying the timeout in the conenction string. Keep the timeout to 10 or 20 minutes.

Posted 23-Sep-11 3:30am

bbirajdar

zhang zhirong · Answer 2 · 2014-02-05T18:20:00

Solution 2

Try this in your web.config,

<addkey value="server=LocalHost;uid=sa;pwd=;database=DataBaseName;Connect Timeout=200; pooling='true'; Max Pool Size=200" />

Alternatively, try to Select Top 50 or less records in your SQL Statement

Posted 5-Feb-14 18:20pm

zhang zhirong

Updated 5-Feb-14 18:21pm

v3