locked
login question for sqlserver 2000 and 2005 RRS feed

  • Question

  • User724951622 posted

    i currently have sql2000 running. what do i have to install to able to use Login control in visual studio 2005. thanks

    Wednesday, June 29, 2005 2:00 PM

All replies

  • User-842092983 posted

    aspnet_regsql.exe under framework folder/

    Thursday, June 30, 2005 4:00 PM
  • User724951622 posted
    I create login.aspx, drap login control in page. click on login task-> administer login
    website administer popup, click on security go this message

    The following message may help in diagnosing the problem: The application domain in which the thread was running has been unloaded.

    I click on choose data store button at bottom. got meeage below.

    Your application is currently configured to use the provider: AspNetSqlProvider

     then i test the AspNetSqlProvider and got error

    Server Error in '/asp.netwebadminfiles' Application.

    Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.

    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 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. Note that 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 SQL Server Express attempts to create a duplicate of an already existing database.
    3. SQL Server Express must be installed on the machine.
    4. If the application services database does not already exist, the SQL Server Express service account must have read and write access to the applications App_Data directory. This is necessary because the SQL Server Express service account will create the application services database.
    5. The web server account used to connect to SQL Server Express must have rights to create a new database.
      1. When using the local web server(Cassini) installed with Visual Studio, the logged-in user needs the dbcreator privilege in the appropriate SQL Server Express instance.
      2. When using IIS, the process account needs the dbcreator privilege in the appropriate SQL Server Express instance. Only consider granting a process account dbcreator privilege on secure development machines. Do not grant the dbcreator privilege on production machines without fully investigating and understanding the security ramifications of running a production web server with the dbcreator privilege. The process account requiring dbcreator privilege varies depending on operating system platform and ASP.NET configuration settings:
        • For IIS5, and IIS6 running in IIS5 isolation mode, the default web server account is the local ASPNET machine account.
        • For IIS6 native mode, the default web server account is NETWORK SERVICE.
        • If application impersonation is enabled, then the application impersonation account requires the dbcreator privilege.
        • If an explicit account was specified for the web server process (either in the <processModel> element for IIS5 and IIS5 isolation mode, or the application pool account on IIS6), then the explicit account requires the dbcreator privilege.


    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): Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.]
       System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +169
       System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +201
       System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner, Boolean& failoverDemandDone, String host, String failoverPartner, String protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean encrypt, Boolean integratedSecurity, SqlConnection owningObject, Boolean aliasLookup) +1157
       System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +598
       System.Data.SqlClient.SqlInternalConnectionTds..ctor(SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +178
       System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +173
       System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup) +27
       System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +49
       System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +89
       System.Data.SqlClient.SqlConnection.Open() +160
       System.Web.Management.SqlServices.GetSqlConnection(String server, String user, String password, Boolean trusted, String connectionString) +68
    
    [HttpException (0x80004005): Unable to connect to SQL Server database.]
       System.Web.Management.SqlServices.GetSqlConnection(String server, String user, String password, Boolean trusted, String connectionString) +124
       System.Web.Management.SqlServices.SetupApplicationServices(String server, String user, String password, Boolean trusted, String connectionString, String database, String dbFileName, SqlFeatures features, Boolean install) +90
       System.Web.DataAccess.SqlConnectionHelper.EnsureValidMdfFile(String fullFileName, String dataDir, String connectionString) +345
    


    Version Information: Microsoft .NET Framework Version:2.0.50215.44; ASP.NET Version:2.0.50215.44
    Thursday, June 30, 2005 5:46 PM
  • User287763314 posted
    Hello.

    do you also have sql server express? if not then you must change the connection string used by default so that it uses your sql server db (by default, it tries to use SQL Server Express). look in the config file for an entry placed inside the <connectionstrings> element (i think that you'll find it at maching.config or web.config placed on the same folder). copy that entry to your <connectionStrings> element placed oon your web.config file (placed at the top of the web site you're building) and change it so that it points to your SQL Server (i'm not sure about the name of the entrym but i think that it is something like LocalSqlServer- or something like that). so you'll have to put this in you web.config file:
    <connectionStrings>
      <remove name="LocalSqlServer" />
      <add name="LocalSqlServer"  connectionstring="put here teh connection string to the SQL Server instance" />
    </connectionStrings>
    Saturday, July 2, 2005 5:51 PM