WEB SITE PROJECT DEPLOYMENT ~ Help please??

[Brad Isaacs]

I am working with ASP.NET 2.0 and using an SQL Server 2000 database.

I am using Visual Studio 2005 and developing on my Local machine. I am
working with Login controls ASP.Configurati on, I wanted to move my work
and needed to place it on the server.

Using VS 2005 , went to BUILD
-Publish Web Site
Checked the box for :: Alow this precompiled site to be updatable.

The files are all now sitting on my Server, and when I load my web site, it
loads the first default.aspx page that contains my LOGIN control. However,
when I try to login it is trying to load a SQL Server Express 2005 database.
Yet I am not using SQL Server 2005, and in my App_Data file folder I DO NOT
have an databasename.MD F inside it. However VS 2005 had created a file and
stuck it into my Project. I then receive the following error. See below:

Can anyone suggest why this is occurring and what I can do to resolve this
issue??

Why is it trying to perform an SQLExpress database file auto-creation error,
when I am using an SQL Server 2000 databse???

Any ideas would be greatly appreciated,

Thanks in advance,

Sincerely,

~Brad
_______________ _______________ _____
ERROR: MESSAGE BELOW:

Server Error in '/gddb' Application.

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)
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.

SQLExpress database file auto-creation error:
The connection string specifies a local Sql Server Express instance using a
database location within the applications App_Data directory. The provider
attempted to automatically create the application services database because
the provider determined that the database does not exist. The following
configuration requirements are necessary to successfully check for existence
of the application services database and automatically create the
application services database:
1. If the applications App_Data directory does not already exist, the web
server account must have read and write access to the applications
directory. This is necessary because the web server account will
automatically create the App_Data directory if it does not already exist.
2. If the applications App_Data directory already exists, the web server
account only requires read and write access to the applications App_Data
directory. This is necessary because the web server account will attempt to
verify that the Sql Server Express database already exists within the
applications App_Data directory. Revoking read access on the App_Data
directory from the web server account will prevent the provider from
correctly determining if the Sql Server Express database already exists.
This will cause an error when the provider attempts to create a duplicate of
an already existing database. Write access is required because the web
server accounts credentials are used when creating the new database.
3. Sql Server Express must be installed on the machine.
4. The process identity for the web server account must have a local user
profile. See the readme document for details on how to create a local user
profile for both machine and domain accounts.
Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.

Stack Trace:

[SqlException (0x80131904): 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)]
System.Data.Sql Client.SqlInter nalConnection.O nError(SqlExcep tion
exception, Boolean breakConnection ) +734947
System.Data.Sql Client.TdsParse r.ThrowExceptio nAndWarning(Tds ParserStateObje ct
stateObj) +188
System.Data.Sql Client.TdsParse r.Connect(Boole an& useFailoverPart ner,
Boolean& failoverDemandD one, String host, String failoverPartner , String
protocol, SqlInternalConn ectionTds connHandler, Int64 timerExpire, Boolean
encrypt, Boolean trustServerCert , Boolean integratedSecur ity, SqlConnection
owningObject, Boolean aliasLookup) +820
System.Data.Sql Client.SqlInter nalConnectionTd s.OpenLoginEnli st(SqlConnectio n
owningObject, SqlConnectionSt ring connectionOptio ns, String newPassword,
Boolean redirectedUserI nstance) +628
System.Data.Sql Client.SqlInter nalConnectionTd s..ctor(DbConne ctionPoolIdenti ty
identity, SqlConnectionSt ring connectionOptio ns, Object providerInfo, String
newPassword, SqlConnection owningObject, Boolean redirectedUserI nstance)
+170
System.Data.Sql Client.SqlConne ctionFactory.Cr eateConnection( DbConnectionOpt ions
options, Object poolGroupProvid erInfo, DbConnectionPoo l pool, DbConnection
owningConnectio n) +130
System.Data.Pro viderBase.DbCon nectionFactory. CreateNonPooled Connection(DbCo nnection
owningConnectio n, DbConnectionPoo lGroup poolGroup) +27
System.Data.Pro viderBase.DbCon nectionFactory. GetConnection(D bConnection
owningConnectio n) +47
System.Data.Pro viderBase.DbCon nectionClosed.O penConnection(D bConnection
outerConnection , DbConnectionFac tory connectionFacto ry) +105
System.Data.Sql Client.SqlConne ction.Open() +111
System.Web.Mana gement.SqlServi ces.GetSqlConne ction(String server, String
user, String password, Boolean trusted, String connectionStrin g) +68

[HttpException (0x80004005): Unable to connect to SQL Server database.]
System.Web.Mana gement.SqlServi ces.GetSqlConne ction(String server, String
user, String password, Boolean trusted, String connectionStrin g) +124
System.Web.Mana gement.SqlServi ces.SetupApplic ationServices(S tring server,
String user, String password, Boolean trusted, String connectionStrin g,
String database, String dbFileName, SqlFeatures features, Boolean install)
+86
System.Web.Mana gement.SqlServi ces.Install(Str ing database, String
dbFileName, String connectionStrin g) +25
System.Web.Data Access.SqlConne ctionHelper.Cre ateMdfFile(Stri ng
fullFileName, String dataDir, String connectionStrin g) +397
Version Information: Microsoft .NET Framework Version:2.0.507 27.42; ASP.NET
Version:2.0.507 27.210

------------------------------
Brad Isaacs
..NET Web Developer, Consultant
www.webdevcreations.com
bi*****@rogers. com

[sloan]

I bypass all that drama.
Create a .bat file.
Call it:
Build_WebSite_R eleaseVersion.b at

--start batch, do not include this line
@echo off
ECHO When/If prompted with the question:
ECHO .

ECHO Does ".......... " specify a file name or directory name on the
target
ECHO (F = file, D = directory)?
ECHO _
ECHO You should answer with "D" for directory.

ECHO _
ECHO _
ECHO _

ECHO When/If prompted with the question:
ECHO _
ECHO Overwrite (...........)
ECHO (Yes/No/All)?
ECHO _
ECHO You should answer with "A" for "All"
ECHO _

@echo on
"C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\d evenv.exe"
NorthwindManage r.sln /Rebuild Release
XCOPY .\Presentation. Web1\*.* c:\wutemp\Relea seBuild_Web_Nor thwindManager
/EXCLUDE:.\exclu de.txt /e/s

-- end batch, do not include this line
Create a exclude.txt file
-- start exclude.txt do not include this line
..pdb
Build_WebSite.b at
exclude.txt
..sln
..vbproj
..csproj
-- end exclude.txt

Put the 2 files in the directory where your .sln file lives.
My example above presupposes that the .sln file is in one directory higher
than where you have the .aspx files (aka, you may need to adjust the
\Presentation.W eb.1\ value.

...



"Brad Isaacs" <bi*****@rogers .comwrote in message
news:uq******** ******@TK2MSFTN GP03.phx.gbl...

I am working with ASP.NET 2.0 and using an SQL Server 2000 database.

I am using Visual Studio 2005 and developing on my Local machine. I am
working with Login controls ASP.Configurati on, I wanted to move my work
and needed to place it on the server.

Using VS 2005 , went to BUILD
-Publish Web Site
Checked the box for :: Alow this precompiled site to be updatable.

The files are all now sitting on my Server, and when I load my web site,

it

loads the first default.aspx page that contains my LOGIN control.

However,

when I try to login it is trying to load a SQL Server Express 2005

database.

Yet I am not using SQL Server 2005, and in my App_Data file folder I DO

NOT

have an databasename.MD F inside it. However VS 2005 had created a file

and

stuck it into my Project. I then receive the following error. See below:

Can anyone suggest why this is occurring and what I can do to resolve this
issue??

Why is it trying to perform an SQLExpress database file auto-creation

error,

when I am using an SQL Server 2000 databse???

Any ideas would be greatly appreciated,

Thanks in advance,

Sincerely,

~Brad
_______________ _______________ _____
ERROR: MESSAGE BELOW:

Server Error in '/gddb' Application.

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)
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.

SQLExpress database file auto-creation error:
The connection string specifies a local Sql Server Express instance using

a

database location within the applications App_Data directory. The provider
attempted to automatically create the application services database

because

the provider determined that the database does not exist. The following
configuration requirements are necessary to successfully check for

existence

of the application services database and automatically create the
application services database:
1. If the applications App_Data directory does not already exist, the web
server account must have read and write access to the applications
directory. This is necessary because the web server account will
automatically create the App_Data directory if it does not already exist.
2. If the applications App_Data directory already exists, the web server
account only requires read and write access to the applications App_Data
directory. This is necessary because the web server account will attempt

to

verify that the Sql Server Express database already exists within the
applications App_Data directory. Revoking read access on the App_Data
directory from the web server account will prevent the provider from
correctly determining if the Sql Server Express database already exists.
This will cause an error when the provider attempts to create a duplicate

of

an already existing database. Write access is required because the web
server accounts credentials are used when creating the new database.
3. Sql Server Express must be installed on the machine.
4. The process identity for the web server account must have a local user
profile. See the readme document for details on how to create a local user
profile for both machine and domain accounts.
Source Error:
An unhandled exception was generated during the execution of the current

web

request. Information regarding the origin and location of the exception

can

be identified using the exception stack trace below.

Stack Trace:

[SqlException (0x80131904): 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)]
System.Data.Sql Client.SqlInter nalConnection.O nError(SqlExcep tion
exception, Boolean breakConnection ) +734947

System.Data.Sql Client.TdsParse r.ThrowExceptio nAndWarning(Tds ParserStateObje c
t

stateObj) +188
System.Data.Sql Client.TdsParse r.Connect(Boole an& useFailoverPart ner,
Boolean& failoverDemandD one, String host, String failoverPartner , String
protocol, SqlInternalConn ectionTds connHandler, Int64 timerExpire, Boolean
encrypt, Boolean trustServerCert , Boolean integratedSecur ity,

SqlConnection

owningObject, Boolean aliasLookup) +820

System.Data.Sql Client.SqlInter nalConnectionTd s.OpenLoginEnli st(SqlConnectio n

owningObject, SqlConnectionSt ring connectionOptio ns, String newPassword,
Boolean redirectedUserI nstance) +628

System.Data.Sql Client.SqlInter nalConnectionTd s..ctor(DbConne ctionPoolIdenti t
y

identity, SqlConnectionSt ring connectionOptio ns, Object providerInfo,

String

newPassword, SqlConnection owningObject, Boolean redirectedUserI nstance)
+170

System.Data.Sql Client.SqlConne ctionFactory.Cr eateConnection( DbConnectionOpt i
ons

options, Object poolGroupProvid erInfo, DbConnectionPoo l pool, DbConnection
owningConnectio n) +130

System.Data.Pro viderBase.DbCon nectionFactory. CreateNonPooled Connection(DbCo n
nection

owningConnectio n, DbConnectionPoo lGroup poolGroup) +27
System.Data.Pro viderBase.DbCon nectionFactory. GetConnection(D bConnection
owningConnectio n) +47
System.Data.Pro viderBase.DbCon nectionClosed.O penConnection(D bConnection
outerConnection , DbConnectionFac tory connectionFacto ry) +105
System.Data.Sql Client.SqlConne ction.Open() +111
System.Web.Mana gement.SqlServi ces.GetSqlConne ction(String server,

String

user, String password, Boolean trusted, String connectionStrin g) +68

[HttpException (0x80004005): Unable to connect to SQL Server database.]
System.Web.Mana gement.SqlServi ces.GetSqlConne ction(String server,

String

user, String password, Boolean trusted, String connectionStrin g) +124
System.Web.Mana gement.SqlServi ces.SetupApplic ationServices(S tring

server,

String user, String password, Boolean trusted, String connectionStrin g,
String database, String dbFileName, SqlFeatures features, Boolean install)
+86
System.Web.Mana gement.SqlServi ces.Install(Str ing database, String
dbFileName, String connectionStrin g) +25
System.Web.Data Access.SqlConne ctionHelper.Cre ateMdfFile(Stri ng
fullFileName, String dataDir, String connectionStrin g) +397
Version Information: Microsoft .NET Framework Version:2.0.507 27.42;

ASP.NET

Version:2.0.507 27.210

------------------------------
Brad Isaacs
.NET Web Developer, Consultant
www.webdevcreations.com
bi*****@rogers. com