Access the answers to your technology questions today.
Subscribe Now
30-day free trial. Register in 60 seconds.
What Makes Experts Exchange Unique?
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
Subscribe Now
30-day free trial. Register in 60 seconds.
Join the Community
Give a Little. Get a Lot.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Join the Community
by: Goalie3533Posted on 2009-03-15 at 14:54:41ID: 23893367
Hi Stu.
Is this by any chance a remote connection? If so, the following may fix it:
In a default installation, SQL Server only allows local applications to connect. To resolve this, and grant remote systems access to the database as well, follow these steps:
1. Open the SQL Server Configuration Manager from the Microsoft SQL Server 2005 start menu item. Depending on the version of SQL Server you're using, this item may be located under the Configuration Tools sub menu.
2. In the window that appears, locate your instance of SQL Server under the SQL Server 2005 Network Configuration item and click it.
3. In the list with protocols on the right, right-click Named Pipes and choose Enable if its status is currently set to Disabled.
4. Repeat the previous step but this time configure TCIP/IP.
You'll need to restart SQL Server for the changes to take effect. You can do this under the SQL Server 2005 Services node in the same dialog, or through the Services panel of the Administrative Tools of Windows.
Hope this helps.
-Goalie35