Is SQLExpress binaries required on server for forms authentication to work?

[CoderX]

Hello:

I am working on an ASP.NET 2.0 web app that uses forms authentication
with the ASPNETDB.mdf in the APP_Data folder. When I deploy it to my
test server, I get the following 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: SQL Network Interfaces, error: 26 - Error
Locating Server/Instance Specified) "

I saw an article on the web about configuring the "surface area" of
SQL Server on the server. But I don't have SQL server on that server,
just the ASPNETDB.mdf. Do I need to install at least SQL Express on
the test and ultimately production servers for this to work?

Thanks in advance for your comments.

[Cowboy \(Gregory A. Beamer\)]

Yes.

In order to run the file based .mdf file in your application, you will need
some version of SQL Server (Express is an option) on the server. Otherwise,
you a nice car body, but no engine to run it.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
http://gregorybeamer.spaces.live.com

*********************************************
Think outside the box!
*********************************************
"CoderX" <tg******@nc.rr.comwrote in message
news:11**********************@q75g2000hsh.googlegr oups.com...

Hello:

I am working on an ASP.NET 2.0 web app that uses forms authentication
with the ASPNETDB.mdf in the APP_Data folder. When I deploy it to my
test server, I get the following 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: SQL Network Interfaces, error: 26 - Error
Locating Server/Instance Specified) "

I saw an article on the web about configuring the "surface area" of
SQL Server on the server. But I don't have SQL server on that server,
just the ASPNETDB.mdf. Do I need to install at least SQL Express on
the test and ultimately production servers for this to work?

Thanks in advance for your comments.

[CoderX]

On Apr 18, 8:47 am, "Cowboy \(Gregory A. Beamer\)"
<[e-mail]:

Yes.

In order to run the file based .mdf file in your application, you will need
some version of SQL Server (Express is an option) on the server. Otherwise,
you a nice car body, but no engine to run it.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBAhttp://gregorybeamer.spaces.live.com

*********************************************
Think outside the box!
*********************************************"Code rX" <[e-mail] in message

news:11**********************@q75g2000hsh.googlegr oups.com...

Hello:

I am working on an ASP.NET 2.0 web app that uses forms authentication
with the ASPNETDB.mdf in the APP_Data folder. When I deploy it to my
test server, I get the following 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: SQL Network Interfaces, error: 26 - Error
Locating Server/Instance Specified) "

I saw an article on the web about configuring the "surface area" of
SQL Server on the server. But I don't have SQL server on that server,
just the ASPNETDB.mdf. Do I need to install at least SQL Express on
the test and ultimately production servers for this to work?

Thanks in advance for your comments.- Hide quoted text -

- Show quoted text -

Thanks!
That's what I thought. I guess I was hoping the ASP.NET runtime would
automagically have everything it needed.