Problem with Login Control

[Juan Romero]

Hi Guys,

I have setup a SQL 2005 DB with ASP.NET membership tables.

Everything seems to work and I am able to connect to this DB (sitting in
different server) because the WSAT allows me to create users and roles.

However, when I place a login control on the application and hit the login
button I get a connection 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 have no idea why this happens. As I understand it the provider is defined
in the web config file and the WSAT uses that information for its interface
so theoretically it should work.

Any help would be much appreciated.

Thank you in advance!

[nahid]

On Jun 30, 1:54 am, "Juan Romero" <[e-mail]:

Hi Guys,

I have setup a SQL 2005 DB with ASP.NET membership tables.

Everything seems to work and I am able to connect to this DB (sitting in
different server) because the WSAT allows me to create users and roles.

However, when I place a login control on the application and hit the login
button I get a connection 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 have no idea why this happens. As I understand it the provider is defined
in the web config file and the WSAT uses that information for its interface
so theoretically it should work.

Any help would be much appreciated.

Thank you in advance!

hi,

go ...Configuration Tools>>SQL Server Surface Area Configuration from
start menu

then you get several option from surface area configuration and
connection
Choose local and remote connection

hope this solve your problem

nahid
http://nahidulkibria.blogspot.com/
http://kaz.com.bd/

[Juan Romero]

Hi Nahid,

Thank you for your reply. This solved my issue!

"nahid" <na******@gmail.comwrote in message
news:11**********************@e9g2000prf.googlegro ups.com...

On Jun 30, 1:54 am, "Juan Romero" <[e-mail]:

>Hi Guys,

I have setup a SQL 2005 DB with ASP.NET membership tables.

Everything seems to work and I am able to connect to this DB (sitting in
different server) because the WSAT allows me to create users and roles.

However, when I place a login control on the application and hit the
login
button I get a connection 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 have no idea why this happens. As I understand it the provider is
defined
in the web config file and the WSAT uses that information for its
interface
so theoretically it should work.

Any help would be much appreciated.

Thank you in advance!

hi,

go ...Configuration Tools>>SQL Server Surface Area Configuration from
start menu

then you get several option from surface area configuration and
connection
Choose local and remote connection

hope this solve your problem

nahid
http://nahidulkibria.blogspot.com/
http://kaz.com.bd/