Connect without async but get timeout error when async=true

[Joseph]

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?

 

[Joseph]

It's a WinForms application. At one point in the application we do a
connection without async=true and do a few things. For all subsequent
connections, we use an asynchronous connection.

Here's what we're doing:

create a system.data.sqlclient.sqlconnection
set connectionstring equal to something like Persist Security
Info=False;Integrated
Security=SSPI;server=serverxxxx;database=dbxxxx;Asynchronous Processing=true;
try .open
and we're catching an SqlException.

Thanks,
Joseph

 

[Joseph]

Sorry - I had the password part stripped out - it really is in there. Yes,
definitely using the 2.0 framework all around.

Where my confusion lies is in what the fundamental difference is between
async & non-async that would cause one method to always work and another to
always fail? And why only on certain machines (regardless of the user logged
in)? And why a timeout/not responding error?

Thanks,
Joseph

 

[Joseph]

No; all the .net dll's are 2.0.50727. Is this a known issue fixed in 2.1?

 

[Joseph]

I should add that the same version (2.0.50727) is on the machines that aren't
having any problems connecting.

 

[Kurt]

I ran into the same issue yesterday and I have not been able to fix it.

Data Source=mySqlServer;Initial Catalog=testDB;User
ID=mytestuser;Password=mytestpassword;Asynchronous Processing=True;Connect
Timeout=1000

Is there any new helpful information anyone could share about this issue?