Azure网站无法连接到SQL Azure数据库

Question

我搜索了几个小时，找不到任何有用的信息。

在Windows Azure中使用ASP.NET MVC4。

当我在开发机器上本地运行站点时，使用SQL Azure连接字符串。我可以访问远程数据库没有任何问题。然而，当我部署网站，并尝试从[mysite的] .azurewebsites.com我收到以下错误超时后访问它（在Azure的连接字符串是相同的;复制并粘贴）：

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: 

1.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. 
2.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. 
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): 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, Action`1 wrapCloseInAction) +5296071 
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean 
callerHasConnectionLock, Boolean asyncClose) +558 
System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds 
connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean 
trustServerCert, Boolean integratedSecurity, Boolean withFailover) +5308555 
System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String 
newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, 
Boolean withFailover) +145 
System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String 
newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString 
connectionOptions, SqlCredential credential, TimeoutTimer timeout) +920 
System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, 
SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, 
SecureString newSecurePassword, Boolean redirectedUserInstance) +307 
System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, 
SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String 
newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString 
userConnectionOptions) +434 
System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, 
DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection 
owningConnection, DbConnectionOptions userOptions) +5311099 
System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection 
owningConnection, DbConnectionPoolGroup poolGroup, DbConnectionOptions userOptions) +38 
System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, 
TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection) 
+5313314 
System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, 
DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions 
userOptions) +143 
System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry) +83 
System.Data.SqlClient.SqlConnection.Open() +96 
System.Web.Management.SqlServices.GetSqlConnection(String server, String user, String password, 
Boolean trusted, String connectionString) +76 

[HttpException (0x80004005): Unable to connect to SQL Server database.] 
System.Web.Management.SqlServices.GetSqlConnection(String server, String user, String password, 
Boolean trusted, String connectionString) +131 
System.Web.Management.SqlServices.SetupApplicationServices(String server, String user, String 
password, Boolean trusted, String connectionString, String database, String dbFileName, 
SqlFeatures features, Boolean install) +89 
System.Web.Management.SqlServices.Install(String database, String dbFileName, String 
connectionString) +27 
System.Web.DataAccess.SqlConnectionHelper.CreateMdfFile(String fullFileName, String dataDir, 
String connectionString) +386 

我尝试使用FTP，但每次我尝试“设置部署凭证”时间在远程web.config文件看我得到这个错误：

Failed to Set Credentials with error: 'Publishing username is already used. Specify a different publishing username.' 

这是BS，因为没有“部署/ FTP用户”组在所有。

任何帮助，将不胜感激。

Answer 1

看来，该应用程序正在使用错误的连接字符串。有时MVC 4/EF5具有如下默认连接字符串：

<add name="MovieDBContext" 
    connectionString="Data Source=(LocalDB)\v11.0;AttachDbFilename=|DataDirectory|\Movies.mdf;Integrated Security=True" 
    providerName="System.Data.SqlClient" 
/> 

对我来说，它依然使用的默认连接，这就是为什么在本地工作。

一些策略：

1，得到其连接字符串您的DbContext使用如下：

var myconn = db.Database.Connection.ConnectionString; //set this to a ViewBag for example 

2，只是可以肯定，使用相同的名称创建在web.config中的连接字符串您的DbContext或在构造函数中设置连接名称。

我现在你已经有了SQL Azure的CONNSTRING，但我会在这里发表太，因为它可以帮助别人：

默认SQL Azure的连接字符串

Server=tcp:[serverName].database.windows.net;Database=myDataBase; 
User ID=[LoginForDb]@[serverName];Password=myPassword;Trusted_Connection=False; 
Encrypt=True; 

你能找到您的管理门户中正确的一个。

Answer 2

最近我有同样的问题，但在我的情况的原因是不同的。我配置了Microsoft ASP.NET Universal Providers以连接到我的SQL Azure数据库。稍后，当我使用ASP.NET Configuration Tool来启用角色时，这就是我的配置。

<membership defaultProvider="DefaultMembershipProvider"> 
    <providers> 
    <add name="DefaultMembershipProvider" type="System.Web.Providers.DefaultMembershipProvider" connectionStringName="hidden" enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="false" requiresUniqueEmail="false" maxInvalidPasswordAttempts="5" minRequiredPasswordLength="0" minRequiredNonalphanumericCharacters="0" passwordAttemptWindow="10" applicationName="/" /> 
    </providers> 
</membership> 
<roleManager enabled="true" /> 

roleManager的部分由配置工具加入。然而，在没有万能供应商这样的事情发生的时候，这个工具就写成了。

看什么缺失？是的，roleManager部分没有定义任何连接字符串。然而，在我的本地机器上一切正常，因为这个缺少的连接字符串导致本地MDF被创建，现在应用程序可以存储这些角色，但在Azure中，这不起作用。我用类似这样的方式指定连接字符串来解决它：

<membership defaultProvider="DefaultMembershipProvider"> 
    <providers> 
    <add name="DefaultMembershipProvider" type="System.Web.Providers.DefaultMembershipProvider" connectionStringName="hidden" enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="false" requiresUniqueEmail="false" maxInvalidPasswordAttempts="5" minRequiredPasswordLength="0" minRequiredNonalphanumericCharacters="0" passwordAttemptWindow="10" applicationName="/" /> 
    </providers> 
</membership> 
<roleManager enabled="true" defaultProvider="DefaultRoleProvider"> 
    <providers> 
    <add name="DefaultRoleProvider" type="System.Web.Providers.DefaultRoleProvider" connectionStringName="hidden" applicationName="/" /> 
    </providers> 
</roleManager> 

解决了这个问题。我必须重新配置我的所有角色，因为他们坐在本地文件的某处。

Answer 3

我知道这是一个古老的步伐，但我想分享我的解决方案。

我的问题是，我可以在本地计算机上运行与Azure上的SQL连接的应用程序。并且登录验证在Azure SQL上完成。

在Azure上运行该应用程序时，无法登录，但具有匿名访问的页面可以精确地连接到数据库。

在Azure Mangement中，发布项目时，DefaultConnection的连接字符串不会更改。我认为这是我第一次将项目发布到Azure时创建的连接。 将默认连接字符串设置为与web.config中相同之后，所有内容都可以平滑地运行。

Answer 4

我解决这个问题的方式是通过FTP进入站点并下载并查看web.config中的连接字符串。

这不是我所期望的。然后我删除它并修复了该问题，然后重新发布了该网站。

我再次FTP'ed到网站，现在它确实有正确的连接字符串。

在我的情况下，问题是我使用的是web.release.config文件，但它的配置不正确，所以没有真正使用它。 “