ayi <t>First, make sure your database engine is configured to accept remote connections:<br/> <br/> Start > All Programs > SQL Server 2005 > Configuration Tools > SQL Server Surface Area Configuration<br/> <br/> Click on Surface Area Configuration for Services and Connections<br/> <br/> Select the instance that is having a problem > Database Engine > Remote Connections<br/> <br/> Enable local and remote connections<br/> <br/> Restart instance<br/> <br/> Second, You may need to create an exception on the firewall for the SQL Server instance and port you are using<br/> <br/> Start > Run > Firewall.cpl<br/> <br/> Click on exceptions tab<br/> <br/> Add the sqlservr.exe (typically located in C:\Program Files (x86)\Microsoft SQL Server\MSSQL.x\MSSQL\Binn, check your installs for the actual folder path), and port (default is 1433)<br/> <br/> Check your connection string as well<br/> <br/> Third, check if your SQL server services is up and running properly<br/> <br/> Go to All Programs >> Microsoft SQL Server 2008 >> Configuration Tools >> SQL Server Configuration Manager >> SQL Server Services, and check if SQL Server service status is “Running”.<br/> <br/> In addition, ensure that your remote server is in the same network. Run “sqlcmd -L” in your command prompt to ascertain if your server is included in your network list. You can even find tutorial for the same here SQL SERVER – Find All Servers From Local Network – Using sqlcmd – Detect Installed SQL Server on Network.<br/> <br/> Next, Enable TCP/IP in SQL Server Configuration<br/> <br/> Go to All Programs >> Microsoft SQL Server 2008 >> Configuration Tools >> SQL Server Configuration Manager >> Select TCP/IP. Right click and select enable<br/> <br/> Last, Go to your firewall setting, under exception tab, select add port include TCP:1433 and tick the SQL check box.<br/> <br/> References:<br/> <br/> <br/> http://www.sswug.org/articlesection/default.aspx?TargetID=44331<br/> <br/> <br/> [http://blog.sqlauthority.com/2009/05/21/sql-server-fix-error-provider-named-pipes-provider-error-40-could-not-open-a-connect<br/> <br/> (Réponse tronquée)</t>
