Visual Studio 11 beta installation disabled my abillity to connect remote MS SQL Server but not local databases - by SPAvidin

Status : 


Sign in
to vote
ID 729323 Comments
Status Active Workarounds
Type Bug Repros 16
Opened 3/7/2012 1:38:40 AM
Access Restriction Public
Moderator Decision Sent to Engineering Team for consideration


I installed Visual Studio 11 Pro and it looks really awesome!

Unfortunately it disabled my abillity to connect remote MS SQL Server 2008 or MS SQL Server 2008 R2 Express and through Visual Studio (both 2010 and 11 Beta). 
I have no problems connecting to my local database which is version 10.0.5500 and
I can connect to the remote databases through SQL Server Management Studio 2008.

This problem only exist in Visual Studio. 
I am working with Windows 7.

Additional Info: 
My own programs connecting remote databases via EF or LinqToSQL are also compromised. (before i installed VS 11 beta they worked well.) They can not connect the remote database server!
May be some shared functionality is responsible for this failure. (.net 4.5 beta? or some old cached settings, connections... )

The error i get when i try to connect is:
Cannot connect to\SQLEXPRESS.

Additional information:
A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: SSL Provider, error: 0 - Something with:  "Timeout was cancelled" in my own language .)
(Microsoft SQL Server, Error: 258)

I'm pretty lost here as everything seems to work except in Visual Studio :/
Sign in to post a comment.
Posted by Ch. Bilal Ahmed on 11/6/2014 at 1:21 AM
The solution provided by Daniel i.e. .Net 4.5.2 resolved my problem.
After downloading and applying the update:, I restarted my machine and BANG!!!
Posted by Kamran Shahid on 7/17/2014 at 11:47 PM
What Can a Person using VS2012 can do if even [netsh Winsock reset] command not working?
Posted by Microsoft on 5/7/2014 at 2:49 PM
Hi SPAvidin,

This issue has been resolved in .Net 4.5.2.
Please download and apply the update:

Daniel Paoliello
Software Development Engineer
SQL DataSet and Managed Providers Team
Posted by Cem Karadeniz on 3/23/2013 at 10:23 AM
I was having this problem when I had .NET framework 4.5 installed on my workstation with PANDA antivirus. When I uninstalled PANDA problem is resolved.
Posted by Faiz VP on 2/11/2013 at 11:30 PM Proxy was causing trouble for me. Uninstalled and all working fine now. ("remove non-IFS LSP")
I had same issue with SSMS 2012 but all worked fine on SSMS 2008 on the same box connecting to the same remote server.
Posted by Mirrh on 11/23/2012 at 1:08 PM
I had the same issue and tried the same thing as [zpittman]
and I found that [Sendori.dll] got installed somehow and that was using LSP.
So after removing this Sendori and It works great.

Thank you [zpittman]
Posted by AndreasGra on 11/23/2012 at 5:50 AM
I have the same Problem.
I think its not a problem of VS2012. Just of .net4.5.
Everythink works fine if I work with VS2012 but with .net4.0 for my Project.
I can reproduce the error on every Client PC with .net 4.5 installed.
Please help.
Posted by zpittman on 11/21/2012 at 7:52 AM
I had this same issue and resolved it, here is how:
netsh winsock show catalog > lsp.txt

I opened the txt file that was created and found a fullsock.dll entry and that dll didn't exist in the directory the entry specified (old antivirus maybe?).

I used this open source program to remove the entry and was back in business :)
Posted by Ali Alimardani on 8/22/2012 at 10:02 PM
i had the same issue, i use "netsh WinSock Show Catalog" command to determine if a non-IFS BSP or LSP is installed on my computer, i found IDM, after i remove that everything goes fine.
follow this linke and go to More Information section for information about how to use the netsh command and find out which non-IFS is installed.
Posted by SPAvidin on 7/3/2012 at 2:51 AM
In my case i uninstalled Panda virus detection software and now it works normally. I can connect remote databases. May be some virus scanner could cause the problem.

Posted by Rosewood99 on 6/13/2012 at 9:55 AM
I was having this same issue with the Visual Studio 2012 RC, but after following the workaround instructions I found an LSP provider installed by a program called StationRipper by Ratajik Software. Once I uninstalled StationRipper, everything started working normally again.

Posted by Microsoft on 5/31/2012 at 11:38 AM
Thank you for reporting this issue. We investigated the issue and most likely the cause of the problem is non-IFS BSP/LSP installed on your machine interfering with our call to Winsock. Once installed BSP/LSP provider can intercept and modify inbound and outbound Internet traffic. Please refer to the following KB article for details and instruction on how to identify if you are running into the same issue:

For the background, the existing synchronous API code path was modified in .NET Framework 4.5 to add asynchronous support in ADO.NET. Ideally it would have been better if the modification to the existing code path could be avoided, but to add asynchronous support the change on the existing code path was inevitable.

If removing non-IFS BSP/LSP solved your issue, it will be helpful for us if you can share the information of the non-IFS BSP/LSP. If you don’t have an issue giving the information to us, please send us an e-mail with the information to We will share the list with Windows networking team so that they can follow up with the provider companies to see if they can move toWindows Filtering Platform which is a new interface introduced in Windows Vista.

If you don’t have non-IFS BSP/LSP on your machine or still have connectivity issue even after removing the provider, please let us know and we will do further investigation.

Thanks again for reporting this issue and if you have further questions, please don’t hesitate to contact us.

Young Gah Kim
Development Lead
ADO.NET Managed Providers and DataSet Team
Posted by Spursoft Solutions on 5/3/2012 at 9:36 AM
Sorry that was TrustServerCertificate
Posted by Spursoft Solutions on 5/3/2012 at 9:34 AM
I tried yesterday changing the Encrypt=True in vs 2010 and if I left the TrustCertificate=False I recieved an invalid certificate chain error. When I enabled TrustCertificate=True it connected.
Posted by Spursoft Solutions on 5/2/2012 at 3:21 PM
Do you mean in 4.0 or 4.5?
Posted by Microsoft on 4/24/2012 at 4:14 PM
Thanks for reporting this issue. We are working on reproducing this issue in our lab but having difficult time. For those who have this issue and was successfully roll back to .NET Framework 4.0, would you please see if you can connect with encryption on? This information will help us to narrow down the issue.


Young Gah Kim
Development Lead
ADO.NET and DataSet Team
Posted by khurley on 4/24/2012 at 8:18 AM
I have had the same issue when installing VS11. It is repaired after uninstalling VS11 and Net 4.5 and Repairing VS2010. After getting everything repaired, I installed JUST NET 4.5 from the VS11 Premium ISO image and had the same issues when connecting to a remote SQL express database so I'm guessing it has more to do with NET 4.5 than with VS11. End result is still can't use either.
Posted by Spursoft Solutions on 4/19/2012 at 10:17 AM
I am having the same issue. For a remote server inside my network I have control over I can enable Named Pipes and it works fine if I change the network library to Named Pipes. This is not a solution however because it does not help on hosted networks where I cannot force them to enable named pipes.

This has also affected my VS 2010 installation.
Posted by SPAvidin on 3/22/2012 at 1:52 AM
Until now, there is no good solution.
The following post address the same issue:

Solution until now: uninstall .Net 4.5 beta or Vs 11Beta

I like to use .net 4.5 (async, await ...) and VS 11.
Hopefully someone has an better idea.
Posted by Karl Schulze on 3/21/2012 at 11:01 AM
I have the same issue - is there any progress on this?
Posted by SPAvidin on 3/14/2012 at 1:20 AM
I have attached the logfile of the following procedure...

- started VS11 beta
- go to SQL menu -> add sql server...
- selected my remote SQL server
- windows authentication
- pressed connect
- time out error...



A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: SSL Provider, error: 0 - The wait operation timed out.) (.Net SqlClient Data Provider)

For help, click:

Server Name: xxxx\SQLEXPRESS
Error Number: 258
Severity: 20
State: 0

Program Location:

at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.ConsumePreLoginHandshake(Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, Boolean& marsCapable)
at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, Boolean withFailover)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, SqlConnection owningObject, Boolean withFailover)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry)
at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.VisualStudio.Data.Tools.SqlEditor.DataModel.SqlConnectionStrategy.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.VisualStudio.Data.Tools.Package.Explorers.SqlServerObjectExplorer.ConnectionService.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
Posted by Microsoft on 3/13/2012 at 10:16 PM
Also, could you try running Visual Studio with the /log option? This might help us catch something.

Devenv.exe /log "C:\My Files\MyLog.txt"

-Janet Yeilding
Posted by Microsoft on 3/13/2012 at 5:56 PM
Sorry you're running into this issue. Can you help me understand the repro better? Are you connecting via Server Explorer or SQL Server Object Explorer? And you only experiencing this issue with remote servers?

Janet Yeilding
Posted by David Snedecor on 3/12/2012 at 12:26 PM
I also had this same issue. It was not resolved until I uninstalled VS 11 AND .NET Framework 4.5.
Posted by MS-Moderator10 [Feedback Moderator] on 3/7/2012 at 10:29 PM
Thanks for your feedback. We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by MS-Moderator01 on 3/7/2012 at 5:40 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(