"Federico Caselli" wrote:

> FOUND!!
>
>
> In the "Add Connection" window, I was selecting my computer name in the
> "select server name" combobox. Now I've tried writing
> <computer_name>\<instance_name>, and it works. I think that Visual Studio
> should better list the complete string in that combobox... It would be nicer,
> wouldn't it?
>
> Thanks.
>
>
>
> "Rick Byham [MS]" wrote:
>
> > Are you connecting to SQLExpress as a named instance, e.g.
> > <computer_name>\sqlexpress which is the default name?
> > --
> > Rick Byham
> > MCDBA, MCSE, MCSA
> > Documentation Manager,
> > Microsoft, SQL Server Books Online
> > This posting is provided "as is" with
> > no warranties, and confers no rights.
> >
> > "Federico Caselli" <FedericoCaselli@discussions.microsoft.com> wrote in
> > message news:D04EE921-F289-4E1A-B7F5-0834E82B29E9@microsoft.com...
> > > Hi,
> > >
> > > I've installed Visual Studio 2005 pro SQL Server 2005 dev on a WMCE PC.
> > >
> > > When I try to connect from VS to SQL I get the following error:
> > >
> > > ----------------------------------------
> > > A connection cannot be made to the database.
> > > Set and test the connection string.
> > >
> > > An error has occurred 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) (Microsoft SQL Server, Error: 2)
> > >
> > > For help, click:
> > > http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476
> > > ------------------------------------
> > >
> > > I enabled remote connections, even though I'm just trying a local one.
> > >
> > > thank you.
> > >
> > >
> >
> >