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

7

我已经搜索了数小时,但找不到任何有用的信息。

使用ASP.NET MVC4和Windows Azure。

当我在我的开发计算机上本地运行站点时,使用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.'

这种说法是胡扯的,因为根本没有设置“部署/FTP用户”。如果您能提供帮助,将不胜感激。

连接字符串指定了一个本地 Sql Server Express 实例,该实例使用应用程序 App_Data 目录中的数据库位置。看起来你的连接字符串有误,它指向了本地开发机器上的资源,而这些资源在 Azure 服务器上并不存在。你是否可以贴出你的 web.config 文件?你正在使用 SQL Azure 数据库吗? - Ray Suelzer
我有同样的问题https://dev59.com/AXfZa4cB1Zd3GeqPXu2G,但当我第一次搜索时没有看到这篇文章。我发现在服务器的配置文件中有一个连接字符串名称为“LocalSqlServer”,由“AspNetSqlMembershipProvider”使用,这导致了问题。我仍然没有解决方案。 - Old Geezer
4个回答

5
看起来应用程序正在使用错误的连接字符串。有时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;

您可以在管理门户中找到正确的内容。 输入图像描述 输入图像描述

我遇到了同样的问题,尝试过你的建议。我有2个DataContexts,并且通过ViewBag将Database.Connection.ConnectionString发送到一个视图,该视图不需要连接到数据库才能加载。当页面加载时,ViewBag中的连接字符串与我在web.config中设置为默认连接的正确SQL Azure字符串匹配。我还尝试在两个DataContexts的构造函数中设置该连接字符串,但似乎没有帮助解决原始问题。您有什么其他修复建议吗?谢谢。 - Alec Menconi

1
我知道这是一个旧的帖子,但我想分享我的解决方案。
我的问题是我可以在本地计算机上运行连接到Azure SQL的应用程序,并且登录验证是在Azure SQL上完成的。
当在Azure上运行应用程序时,无法登录,但具有匿名访问权限的页面可以正确连接到数据库。
在Azure管理中,DefaultConnection的连接字符串在项目发布时没有更改。我认为这个连接在项目第一次发布到Azure时被创建。 将默认连接字符串设置为与web.config中相同后,一切都运作得非常顺畅。

这正是我的问题,我在克隆应用服务后遇到了这个问题。在新的应用服务中,转到“配置”->“应用程序设置”->“连接字符串”,然后将默认连接更改为来自web.config的连接字符串。 - VBStarr

1
我解决这个问题的方法是通过FTP登录网站,下载并查看web.config中的连接字符串。但它并不是我所期望的。然后我将其删除并修复了该问题,然后重新发布了该网站。我再次通过FTP登录网站,现在它有了正确的连接字符串。
在我的情况下,问题是我使用了一个web.release.config文件,但它配置不正确,因此实际上并没有被使用。

0
我最近也遇到了同样的问题,但我的情况原因不同。我已经配置了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>  

解决了问题。我确实不得不重新配置所有的角色,因为它们存储在本地文件中。

网页内容由stack overflow 提供, 点击上面的
可以查看英文原文,
原文链接