|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
forms authenticationauthentication and allowed the system to create the aspnetdb.mdf file for me under the App_Data directory. Everything works fine locally running the site locally with the sql server express edition. However, when I publish to an IIS site, I can see the login aspx page I created, but can't authenticate. I get an error listed below. Should an IIS server with asp.net 2.0 be able to see an mdf file based database? 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. Exception Details: System.Data.SqlClient.SqlException: 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) 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.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +734931 System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +188 System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner, Boolean& failoverDemandDone, String host, String failoverPartner, String protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject, Boolean aliasLookup) +820 System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +628 System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +170 System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +130 System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +28 System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +424 System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +66 System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +496 System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +82 System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105 System.Data.SqlClient.SqlConnection.Open() +111 System.Web.DataAccess.SqlConnectionHolder.Open(HttpContext context, Boolean revertImpersonate) +84 System.Web.DataAccess.SqlConnectionHelper.GetConnection(String connectionString, Boolean revertImpersonation) +197 System.Web.Security.SqlMembershipProvider.GetPasswordWithFormat(String username, Boolean updateLastLoginActivityDate, Int32& status, String& password, Int32& passwordFormat, String& passwordSalt, Int32& failedPasswordAttemptCount, Int32& failedPasswordAnswerAttemptCount, Boolean& isApproved, DateTime& lastLoginDate, DateTime& lastActivityDate) +1121 System.Web.Security.SqlMembershipProvider.CheckPassword(String username, String password, Boolean updateLastLoginActivityDate, Boolean failIfNotApproved, String& salt, Int32& passwordFormat) +105 System.Web.Security.SqlMembershipProvider.CheckPassword(String username, String password, Boolean updateLastLoginActivityDate, Boolean failIfNotApproved) +42 System.Web.Security.SqlMembershipProvider.ValidateUser(String username, String password) +83 System.Web.UI.WebControls.Login.OnAuthenticate(AuthenticateEventArgs e) +160 System.Web.UI.WebControls.Login.AttemptLogin() +105 System.Web.UI.WebControls.Login.OnBubbleEvent(Object source, EventArgs e) +99 System.Web.UI.Control.RaiseBubbleEvent(Object source, EventArgs args) +35 System.Web.UI.WebControls.Button.OnCommand(CommandEventArgs e) +115 System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) +163 System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +7 System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +11 System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +33 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +5102 The problem is that your application is set up to point to your development
database (on your dev machine). On your web server, you need to point your DB connection to the DB that is on your server (not your dev machine). VS2k5 does a nice job of finding your dev DB and running it for you and setting up your connection string. Your web server is probably not going to be as easy to deal with. I usually use FTP to get the web.config file from my server and I use notepad to edit the web.config file. I look for the line that says something about a connectionstring or databasesomethingsomething. Change the machine name to match the name of the web server (or production SQL server). Also, check the database name to make sure it matches. Of course, my suggestion will only work if you have your database running on your web server. Otherwise, you will need to attach your db (see sp_attach_db in SQL Books Online). Good luck. Show quote "Milton Snider" wrote: > I installed visual studio 2005 and created a website. I turned on the forms > authentication and allowed the system to create the aspnetdb.mdf file for me > under the App_Data directory. Everything works fine locally running the > site locally with the sql server express edition. However, when I publish > to an IIS site, I can see the login aspx page I created, but can't > authenticate. I get an error listed below. Should an IIS server with asp.net 2.0 be able to > see an mdf file based database? > > 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) .... > > Exception Details: System.Data.SqlClient.SqlException: 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) > > 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 - .... |
|||||||||||||||||||||||