I recently had some trouble getting an application connected to an SQL Server database. In SSMS, logon sometimes failed with a message about named-pipe connections not being enabled on the server. Apparently applications won't always fall back to a supported connection method if their preferred one isn't enabled?
Connection methods can be managed with the SQL Server Configuration Manager. There are several sections in the SSCM; for me, named pipes only seemed disabled in one of them. After enabling such connections there, this error was no longer a problem.
No comments:
Post a Comment