Opertation has Timeout ; on Login screen when more than 1 user access.

Question

0.00/5 (No votes)

See more:

Opertaion has Timeout

I m using (My own)WebMethods in My Project, when more hen 1 user access the showing error "Opertation has Timeout" on Login screen and 1 more place when have 5-6 tables joined in query, there showing "Server was unable to process request".
For this problem i tried may solutions
1.Added Connect Timeout=5000; pooling='true'; Max Pool Size=200; in Connection string.
2. Added in

HTML

<System Web><httpRuntime  executionTimeout="5000" maxRequestLength="2097151"/>

3.Added in my function SqlCommand.CommandTimeout=5000;
4.Increased "Remote Query Timeout" from Sql Server usinf sp_Configure.

But Still getting same issue, If any one knows, Please suggest me.
Thanks in advance.

Posted 5-Jan-13 0:25am

SHAJANCHERIAN

Updated 6-Jan-13 1:57am

Sandeep Mewara

v2

Add a Solution

Comments

Kalyan_A 6-Jan-13 9:23am

Setting timeout is useful only when you know that the process will finish in said time. Looks like you have locking issues with simultaneous access.

Identify the source of timeout/locks (DB or front-end) and fix the underlying problem. setting a large enough timeout without identifying the problem may be counter productive.

Cheers

1 solution

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)

Christian Graus · Answer 1 · 2013-01-06T09:44:00

The timeout is still pretty low. But, overall it sounds like your table design or SQL is very inefficient. You can try adding 'nolock' to your select statements, so they don't lock the tables, but I suspect a more complete redesign is needed, if you can't get two people to log in at once.