|Connection to MS SQL server failed ({0}).
Please make sure that TCP/IP protocol is enabled on your target server and its TCP port is not blocked by a firewall.
When connecting to a named SQL Server instance, you can specify either SQL Server port or SQL Server instance
name parameters, but the connection may fail if both parameters are not empty.|
Connection handshake failed. The certificate used by this endpoint was not found: %1!s!. Use DBCC CHECKDB in master database ...
Connection handshake failed. The received premaster secret of size %1!s! does not have the expected size of %2!s!. State ...
Connection Page is not available. Please switch to use 'All' properties tab page to set the properties of connection string. ...
Connection string expressions cannot be evaluated at design time. You must preview or deploy the report to verify the connection. ...
Connection to MS SQL server failed ({0}). Please make sure that TCP/IP protocol is enabled on your target server and its ...
Connection to server %1!s! cannot be established. This error can occur when the server does not exist, or the proxy settings ...
Connection to SQL Server failed. Please make sure that TCP/IP protocol is enabled on your target server and its TCP port ...
Conn[ection id_or_name;connection_string Optional. Sets the connection string property of a ConnectionManager stored within ...
Consider changing the PROVIDER in the connection string to %1!s! or visit http://www.microsoft.com/downloads to find and ...