I'm trying to publish a web project and database using VS 2010. The project builds ok but when it connects to the server it doesn't upload the database.
This is pretty vague:
Error 3 Web deployment task failed.((03/02/12 11:12:43 AM) An error occurred when the request was processed on the remote computer.)
(03/02/12 11:12:43 AM) An error occurred when the request was processed on the remote computer.
The database '*******' could not be created.
There's probably a permissions issue creating the new database. Does the SQL credentials you've specified have CREATE DATABASE permissions? If not, you may need to have the database created for you (but empty) before publishing.
If this post has solved your problem, please select 'Mark as answer'
- Jimmy Lewis
Microsoft SDET
Visual Web Developer Team
<p>I've already created an empty database on the server and provided the connection string settings. Also, when I turn off custom errors on the server and try to log into my site, it tells me that the sql database isn't found, so clearly it hasn't been
created.</p> <p>So I'm left with two options: trying to get VS to upload my database or trying another route.</p> <p>1 - VS: I'm kind of curious about these parts of my web.config:</p> <p>What is that "metadata" value? Is there something in there that should
change between the local and server environment?</p> <p>2. A seemingly simple question...if VS can't magically create my database on the server, what are my other options. I've tried making a backup with SSMS and uploading to my database on the server, but
I still get the error that my code can't access the database.</p>
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to 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 application's 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:
If the application is running on either Windows 7 or Windows Server 2008R2, special configuration steps are necessary to enable automatic creation of the provider database. Additional information is available at: http://go.microsoft.com/fwlink/?LinkId=160102.
If the application's App_Data directory does not already exist, the web server account must have read and write access to the application's directory. This is necessary because the web server account will automatically create the App_Data directory if it does
not already exist.
If the application's App_Data directory already exists, the web server account only requires read and write access to the application's 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 application's 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 account's credentials are used when creating the new database.
Sql Server Express must be installed on the machine.
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): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)]
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +5009598
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning() +234
System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity) +341
System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, SqlConnection owningObject) +129
System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, TimeoutTimer timeout) +270
System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, TimeoutTimer timeout, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +195
System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +232
System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +5023255
System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup) +31
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +76
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +126
System.Data.SqlClient.SqlConnection.Open() +125
System.Web.Management.SqlServices.GetSqlConnection(String server, String user, String password, Boolean trusted, String connectionString) +82
[HttpException (0x80004005): Unable to connect to SQL Server database.]
System.Web.Management.SqlServices.GetSqlConnection(String server, String user, String password, Boolean trusted, String connectionString) +137
System.Web.Management.SqlServices.SetupApplicationServices(String server, String user, String password, Boolean trusted, String connectionString, String database, String dbFileName, SqlFeatures features, Boolean install) +94
System.Web.Management.SqlServices.Install(String database, String dbFileName, String connectionString) +27
System.Web.DataAccess.SqlConnectionHelper.CreateMdfFile(String fullFileName, String dataDir, String connectionString) +395
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1
Thanks, I couldn't get VS studio to publish, so I uploaded a backup.
That being said, the error I was getting was because I still had a reference to my localhost connection string in the membership section of my config file. Anyone else facing this error should give their web.config a thorough reading.
Turning the customerrors off on the server was helpful in figuring this out.
panchoLopez
Member
67 Points
49 Posts
error publishing database
Feb 03, 2012 06:20 AM|LINK
I'm trying to publish a web project and database using VS 2010. The project builds ok but when it connects to the server it doesn't upload the database.
This is pretty vague:
Error 3 Web deployment task failed.((03/02/12 11:12:43 AM) An error occurred when the request was processed on the remote computer.)
(03/02/12 11:12:43 AM) An error occurred when the request was processed on the remote computer.
The database '*******' could not be created.
Any ideas?
balamsc
Member
167 Points
117 Posts
Re: error publishing database
Feb 03, 2012 09:14 AM|LINK
set the customErrors mode off in web.config file
<customErrors mode= "Off">
</customErrors>
and try and show me the error what you are getting..
jamlew
Participant
1977 Points
256 Posts
Microsoft
Re: error publishing database
Feb 03, 2012 06:34 PM|LINK
There's probably a permissions issue creating the new database. Does the SQL credentials you've specified have CREATE DATABASE permissions? If not, you may need to have the database created for you (but empty) before publishing.
- Jimmy Lewis
Microsoft SDET
Visual Web Developer Team
panchoLopez
Member
67 Points
49 Posts
Re: error publishing database
Feb 03, 2012 09:10 PM|LINK
panchoLopez
Member
67 Points
49 Posts
Re: error publishing database
Feb 03, 2012 09:16 PM|LINK
This is the error from the server:
Server Error in '/' Application.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to 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 application's 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:
Source Error:
Stack Trace:
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1
Dino He - MS...
Star
8068 Points
1023 Posts
Microsoft
Re: error publishing database
Feb 08, 2012 07:05 AM|LINK
Hi
You can try stop the SQL service and to copy the mdf file to you remote server.Then use DataSource to create the connection string.
I think the problem may because you haven't get the correct connection string.
If you have any feedback about my replies, please contact msdnmg@microsoft.com
Microsoft One Code Framework
panchoLopez
Member
67 Points
49 Posts
Re: error publishing database
Feb 08, 2012 07:55 AM|LINK
Thanks, I couldn't get VS studio to publish, so I uploaded a backup.
That being said, the error I was getting was because I still had a reference to my localhost connection string in the membership section of my config file. Anyone else facing this error should give their web.config a thorough reading.
Turning the customerrors off on the server was helpful in figuring this out.