"Connecting to sql server files" error

realJSOP

Vista/64 VS2008 I'm to add a SQL Server database object to my project, but when I try, I get this error message: Connecting to sql server files (*.mdf) require sql server express 2005 to function properly. Well, it is installed, and when I run express manager studio, everything seems to be fine. I can also create connections in the server explorer in vsiual studio. When I googled the error, there was exactly one hit that I can't browse top (because of the restrictions on our network).

.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001

Tim Carmichael

Can you post either the link you can't get to or the exact search phrase in case someone CAN get to it and then render help? Tim

Luc Pattyn

Hi John, IMO the relevant part of http://social.msdn.microsoft.com/Forums/en-US/sqldataaccess/thread/6615124e-5501-4fb2-b498-638d3a7f01c6[^] is this: I encountered the same error message while trying to create a data connection from Visual Studio 2005 using the Server Explorer. This is what I did: # 1. Started Visual Studio 2005 # 2. Opened the Server Explorer (View | Server Explorer) # 3. Right-clicked the Data Connections node # 4. Selected Create New SQL Server Database... from the context menu # 5. Selected my computer from the Server Name dropdown list # 6. Selected authentication method (Use Windows Authentication) # 7. Typed a name in the New Database Name field # 8. Hit the OK button That's when I received the following error message An error has occured while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error:40 – Could not open a connection to SQL Server) It made absolutely no sense. I wasn't trying to connect to a remote computer. I was simply trying to connect to the SQL Server 2005 Express Edition which was installed on my local computer during the Visual Studio 2005 installation. After numerous attempts on several computers, I finally realized what I was doing wrong. By adding the database instance name to the server name (# 5), it actually worked. Instead of selecting from the dropdown list, I entered \SQLExpress manually. That was obviously the problem. SQL Server 2005 Express Edition is obviously installed as a named instance, since one has to provide the instance name in addition to the server name (even when there is only one instance running on the requested server). :)

Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]

Prolific encyclopedia fixture proof-reader browser patron addict?
We all de

realJSOP

We're not running sqlexpress...

.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001

dan sh

Does this[^] helps?

Luc Pattyn

Does it relate to SQL Express? :^)

Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]

Prolific encyclopedia fixture proof-reader browser patron addict?
We all depend on the beast below.

dan sh

Luc Pattyn wrote:

Does it relate to SQL Express?

:confused:

Luc Pattyn

http://www.codeproject.com/Messages/3447012/Re-Connecting-to-sql-server-files-error.aspx[^]

Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]

Prolific encyclopedia fixture proof-reader browser patron addict?
We all depend on the beast below.