Connect without async but get timeout error when async=true
- From: Joseph <Joseph@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 6 May 2008 13:01:01 -0700
Have an app deployed on a network. On some machines, a regular connection to
the sql server establishes and works great, but the same exact connection
string along with "Asynchronous Processing=true" gives a 'Timeout expired.
The timeout period elapsed prior to completion of the operation or the server
is not responding.' error. I know the timeout setting isn't the actual
issue, and the client machine can demonstrate connectivity to the sql server
manually (and like I mentioned, has no problem connecting without the async).
Is anyone familiar with anything like this?
.
- Follow-Ups:
- Re: Connect without async but get timeout error when async=true
- From: William Vaughn [MVP]
- Re: Connect without async but get timeout error when async=true
- Prev by Date: Internal .Net Framework Data Provider error 6
- Next by Date: LinqDataSource Adding Row
- Previous by thread: Internal .Net Framework Data Provider error 6
- Next by thread: Re: Connect without async but get timeout error when async=true
- Index(es):
Relevant Pages
|
