DotNetNewsgroup.com  
web access to complete list of Microsoft.NET newsgroups
   home   |   control panel login   |   archive  |  
 
  carried group
academic
adonet
aspnet
aspnet.announcements
aspnet.buildingcontrols
aspnet.caching
aspnet.datagridcontrol
aspnet.mobile
aspnet.security
aspnet.webcontrols
aspnet.webservices
assignment_manager
datatools
dotnet.distributed_apps
dotnet.general
dotnet.myservices
dotnet.nternationalization
dotnet.scripting
dotnet.security
dotnet.vjsharp
dotnet.vsa
dotnet.xml
dotnetfaqs
framework
framework.clr
framework.compactframework
framework.component_services
framework.controls
framework.databinding
framework.drawing
framework.enhancements
framework.interop
framework.odbcnet
framework.performance
framework.remoting
framework.sdk
framework.setup
framework.webservices
framework.windowsforms
framework.wmi
frwk.windowsforms.designtime
lang.csharp
lang.jscript
lang.vb
lang.vb.controls
lang.vb.data
lang.vb.upgrade
lang.vc
lang.vc.libraries
  
 
start date: Tue, 14 Aug 2007 16:45:37 -0600,    posted on: microsoft.public.dotnet.framework.adonet        back       

Thread Index
  1    Jonathan Wood
          2    Jonathan Wood
                 3    Braulio Diez


Still More Database Connection Problems   
I'm going through several books on ASP.NET database programming. They all
make it look so easy. But it just never seems to work for me.

So I created a new ASP.NET application.

I right click on Data Connections in Server Explorer and select 'Create New
SQL Server Database...'

The Server name box is empty and all the online help tells me about this box
and what I can enter here is "Shows the name of the server for this
connection. To choose a different server, select one from the drop-down list
or type the server name into the text box." So I entered localhost. I also
tried entering local.

I enter a name for my database, test1.

After a considerable pause, I get the error "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)"

I'm running as an administrator on Windows Vista with SQL Server Express
installed. I had the same problems previously on a different computer
running XP.

Is there anyone who can tell me why I cannot do basic database connection?

-- 
Jonathan Wood
SoftCircuits Programming
http://www.softcircuits.com
Date:Tue, 14 Aug 2007 16:45:37 -0600   Author:  

Re: Still More Database Connection Problems   
Looks like I got help on this elsewhere. The answer is to use .\SQLEXPRESS 
as the server.

-- 
Jonathan Wood
SoftCircuits Programming
http://www.softcircuits.com

"Jonathan Wood"  wrote in message 
news:ex3tcTs3HHA.3600@TK2MSFTNGP02.phx.gbl...

> I'm going through several books on ASP.NET database programming. They all
> make it look so easy. But it just never seems to work for me.
>
> So I created a new ASP.NET application.
>
> I right click on Data Connections in Server Explorer and select 'Create 
> New
> SQL Server Database...'
>
> The Server name box is empty and all the online help tells me about this 
> box
> and what I can enter here is "Shows the name of the server for this
> connection. To choose a different server, select one from the drop-down 
> list
> or type the server name into the text box." So I entered localhost. I also
> tried entering local.
>
> I enter a name for my database, test1.
>
> After a considerable pause, I get the error "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)"
>
> I'm running as an administrator on Windows Vista with SQL Server Express
> installed. I had the same problems previously on a different computer
> running XP.
>
> Is there anyone who can tell me why I cannot do basic database connection?
>
> -- 
> Jonathan Wood
> SoftCircuits Programming
> http://www.softcircuits.com
> 
Date:Tue, 14 Aug 2007 17:58:05 -0600   Author:  

Re: Still More Database Connection Problems   
Hello,

   localhost\SQLExpress should do the trick as well. 

   I think SQL Server Express only has by default enabled "Shared Memory", 
maybe if you type the name of your machine it thinks it's a remote computer 
and tries to connect via Named Pipes or TCP /IP (you can see if this is 
enabled in SQL Server Configuration >> Services Running).

  Take care as well using windows account for connecting on ASP .net (I woul 
rather use custom login from SQL Server).

  Good Luck
   Braulio

/// ------------------------------
/// Braulio Diez
///
/// http://www.tipsdotnet.com
/// ------------------------------




"Jonathan Wood" wrote:


> Looks like I got help on this elsewhere. The answer is to use .\SQLEXPRESS 
> as the server.
> 
> -- 
> Jonathan Wood
> SoftCircuits Programming
> http://www.softcircuits.com
> 
> "Jonathan Wood"  wrote in message 
> news:ex3tcTs3HHA.3600@TK2MSFTNGP02.phx.gbl...
> > I'm going through several books on ASP.NET database programming. They all
> > make it look so easy. But it just never seems to work for me.
> >
> > So I created a new ASP.NET application.
> >
> > I right click on Data Connections in Server Explorer and select 'Create 
> > New
> > SQL Server Database...'
> >
> > The Server name box is empty and all the online help tells me about this 
> > box
> > and what I can enter here is "Shows the name of the server for this
> > connection. To choose a different server, select one from the drop-down 
> > list
> > or type the server name into the text box." So I entered localhost. I also
> > tried entering local.
> >
> > I enter a name for my database, test1.
> >
> > After a considerable pause, I get the error "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)"
> >
> > I'm running as an administrator on Windows Vista with SQL Server Express
> > installed. I had the same problems previously on a different computer
> > running XP.
> >
> > Is there anyone who can tell me why I cannot do basic database connection?
> >
> > -- 
> > Jonathan Wood
> > SoftCircuits Programming
> > http://www.softcircuits.com
> > 
> 
> 
Date:Thu, 16 Aug 2007 18:08:45 -0700   Author:  

Google
 
Web dotnetnewsgroup.com


COPYRIGHT ?2005, EUROFRONT WORLDWIDE LTD., ALL RIGHT RESERVE  |   Contact us