Error Message: The user instance login flag is not supported on this version of SQL Server. The connection will be closed

I installed my timetracker.mdf on SQL 2005 Server while following one of the suggestion on this forum (DBinstall posting: http://forums.asp.net/943216/ShowPost.aspx). However, I can't seem to configure my membership profile schema. There is no aspnet_regqsl command. I am getting the following errors:

The user instance login flag is not supported on this version of SQL Server. The connection will be closed

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: The user instance login flag is not supported on this version of SQL Server. The connection will be closed.

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): The user instance login flag is not supported on this version of SQL Server. The connection will be closed.]
   System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +684883
   System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +207
   System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +1751
   System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK) +32
   System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +601
   System.Data.SqlClient.SqlInternalConnectionTds..ctor(SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +159
   System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +108
   System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +28
   System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +445
   System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +66
   System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +304
   System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +85
   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) +173
   System.Web.DataAccess.SqlConnectionHelper.GetConnection(String connectionString, Boolean revertImpersonation) +225
   System.Web.Security.SqlMembershipProvider.GetPasswordWithFormat(String username, Int32& status, String& password, Int32& passwordFormat, String& passwordSalt, Int32& failedPasswordAttemptCount, Int32& failedPasswordAnswerAttemptCount, Boolean& isApproved) +777
   System.Web.Security.SqlMembershipProvider.CheckPassword(String username, String password, Boolean updateLastLoginActivityDate, Boolean failIfNotApproved, String& salt, Int32& passwordFormat) +152
   System.Web.Security.SqlMembershipProvider.CheckPassword(String username, String password, Boolean updateLastLoginActivityDate, Boolean failIfNotApproved) +68
   System.Web.Security.SqlMembershipProvider.ValidateUser(String username, String password) +100
   System.Web.UI.WebControls.Login.AuthenticateUsingMembershipProvider(AuthenticateEventArgs e) +99
   System.Web.UI.WebControls.Login.OnAuthenticate(AuthenticateEventArgs e) +113
   System.Web.UI.WebControls.Login.AttemptLogin() +165
   System.Web.UI.WebControls.Login.OnBubbleEvent(Object source, EventArgs e) +134
   System.Web.UI.Control.RaiseBubbleEvent(Object source, EventArgs args) +56
   System.Web.UI.WebControls.Button.OnCommand(CommandEventArgs e) +107
   System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) +164
   System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +31
   System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +32
   System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +72
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3870

Version Information: Microsoft .NET Framework Version:2.0.50215.44; ASP.NET Version:2.0.50215.44

Can some tell me what I did wrong?

thanks
Nick

Re: Error Message: The user instance login flag is not supported on this version of SQL Server. The connection will be closed

Hey nick, I'm not sure if you figured this out already, but I ran into the same problem by adding the correct permissions to my sql aspnetdb.mdf database. What it appears is happening is that the web app cannot

log into the database to check and see if you are authenticated.

Hope that helps..

Brian

Re: Error Message: The user instance login flag is not supported on this version of SQL Server. The connection will be closed

The issue is that User Instancing, which allows the automatic creation of databases from code, isn't support on the full version of SQL 2005. That is a function of SQL Express only. The solution is to manually create the database in SQL Server 2005 and set a connection string to point to it. You will also need to run aspnet_regsql.exe manually against the database if you will be using any of the new built-in database features of ASP.NET v2.0.

Scott Forsyth

http://www.orcsweb.com
Managed Complex Hosting
#1 in Service and Support

Re: Error Message: The user instance login flag is not supported on this version of SQL Server. The connection will be closed

Thanks Scott, I will try that.

Nick

Re: Error Message: The user instance login flag is not supported on this version of SQL Server. The connection will be closed

Scott,

I am having that same problem on this thread. My question is, what is the structure of the database that we need to create to correct this issue?

Jim

Re: Error Message: The user instance login flag is not supported on this version of SQL Server. The connection will be closed

Two of the current 3 starter kits have the .sql files available for download separately but the Time Tracker doesn't. My guess is that if you download it, extract it and search for files called *.sql you'll find the manual install files. Run that using Query Analyzer, or whatever you prefer, and it will build the database structure for you.

http://asp.net/default.aspx?tabindex=5&tabid=41#Reports

Scott

Re: Error Message: The user instance login flag is not supported on this version of SQL Server. The connection will be closed

Thanks so much for your help. OK, another question. I ran the aspnet_regsql.exe program and it the tables in one of my existing databases on SQL Server Standard edition. Where do I tell the new login controls to connect to that database? What would the connection string look like?

Jim

Re: Error Message: The user instance login flag is not supported on this version of SQL Server. The connection will be closed

Jim,

By default you should set a connection string in your web.config file called LocalSqlServer which will handle all of the ASP.NET database driven features. You can override this by setting your providers manually in web.config, or adjusting the global .config files, but the default is LocalSqlServer.

I don't know the Time Tracker Starter Kit but you should notice after you create a new one that the web.config has some connection strings already set in web.config. Just point them to your sql 2000 database.

www.connectionstrings.com has a good list of connection strings that you can use to connect to your database.

Note that to use LocalSqlServer in web.config, you must 'remove' it from web.config because it has already been defined in your global. config files. Something like this:
    <connectionStrings>
        <remove name="LocalSqlServer" />
        <add name="LocalSqlServer" connectionString="{connection string goes here}" providerName="System.Data.SqlClient"/>
    </connectionStrings>

Scott

Re: Error Message: The user instance login flag is not supported on this version of SQL Server. The connection will be closed

Hi Scott,

It took some doing, but I got it. Thanks for your help. Good solution!

Jim

Re: Error Message: The user instance login flag is not supported on this version of SQL Server. The connection will be closed

Great, glad that worked out in the end. Thanks for the confirmation.

Scott

Re: Error Message: The user instance login flag is not supported on this version of SQL Server. The connection will be closed

Scott,

I'm getting the same error message (The user instance login flag is not supported on this version of SQL Server. The connection will be closed), except it's from trying to run/access the Club web site starter kit from my localhost & local SQL Server 2005.

I have the LocalSqlServer connection string. I have the <remove name="LocalSqlServer" />. I have manually created my Club database. I've ran the aspnet_regsql.exe against my database.

However, I'm still getting that error message.

Any suggestions?

Re: Error Message: The user instance login flag is not supported on this version of SQL Server. The connection will be closed

Hi,
I had the same problem and now it seems that I can connect (Had to change the webconfig.)

The error now is:
Could not find stored procedure 'dbo.aspnet_CheckSchemaVersion'.

This SP can not be found in .sql that came with the download.

Any thoughts please?
Thanks

Re: Error Message: The user instance login flag is not supported on this version of SQL Server. The connection will be closed

That stored procedure is part of the ASP.NET v2.0 framework. To install that, run aspnet_regsql which is in your framework folder. It has a GUI so just double click and follow the prompts. That will install the .NET schema in your database which will solve this particular issue.

Scott

Re: Error Message: The user instance login flag is not supported on this version of SQL Server. The connection will be closed

Where do I find this folder please?
Thanks

Re: Error Message: The user instance login flag is not supported on this version of SQL Server. The connection will be closed

It's %windir%/microsoft.net/framework/v2.something. Should be v2.0.50727 if you are running the released version of the framework. For example:

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727

Scott

Re: Error Message: The user instance login flag is not supported on this version of SQL Server. The connection will be closed

Hi,
Ran the .exe
Now there is a new Db in sql 2005 called aspnetdb. I can see the missing SP now.
In the web.config of the timetracker I am pointing it to TimeTracker database. Is this ok?
And I am still getting the same error as before (i.e. dbo.aspnet_checksumversion sp is missing).
May be I should change the connectionstring of name="LocalSqlServer"

to be pointing to this new DB (i.e aspnetdb)

And the connectionstring of name="aspnet_staterKits_TimeTracker" to be pointing to TimeTracker database

Thanks

Re: Error Message: The user instance login flag is not supported on this version of SQL Server. The connection will be closed

Yep, looks like you're on the right track. I assume that the timetracker was developed so that the ASP.NET schema is controlled by the LocalSqlServerconnection string (by default). This allows you to have them both in the same database or have them separated.

Scott

Re: Error Message: The user instance login flag is not supported on this version of SQL Server. The connection will be closed

only need this one. you have to change as follow your connection string in Web.config please:

Re: Error Message: The user instance login flag is not supported on this version of SQL Server. The connection will be closed

Check in web.config for connectionString, configure it according to your server name, password etc.

In Time Tracking System, it uses inbuild Membership classes for user creation, updation etc..

You have to register your DB with ASP.NET Membership classes by executing the command line utility in VS prompt

aspnet_regsql, it will open one window, where you have to configure DB.

Hope it will help you, let me know.

Re: Error Message: The user instance login flag is not supported on this version of SQL Server. The connection will be closed

Hi,
I have SQL Server 2005 Developer Edition installed as an instance (computername\SQLServer2005) as the default one is SQL Server 2000. Now i changed the web.config as follows: connectionString="Data Source=.\SQLServer2005;

This solved an error

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) .

Then when i start the Time Tracker project I get error:

Exception Details: System.Data.SqlClient.SqlException: The user instance login flag is not supported on this version of SQL Server. The connection will be closed.

On one of the forum posting it mentioned to run C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regsql.exe (Not sure why, something about allowing SQL Server 2005 to create database from an ASP.net app which it doesn't support unlike SQL Express). Anyway after runnign it a new DB was created in my SQL Server 2005 instance - aspnetdb. As part of the creation i choose Windows integration since i have mixed mode support in my DB (so Windows Authentication works when i use SQL Management STudio) and i figured it should work here. But when i start the Time Tracker app in Visual Web Developer 2005 Express Edition it still causes the error

Exception Details: System.Data.SqlClient.SqlException: The user instance login flag is not supported on this version of SQL Server. The connection will be closed.

I don't even see the timetracker database as being created in SQL 2005. When i had tested this app with SQL Express on another machine it created this DB in SQL Express. But i cannot get it to do the same for this SQL Server 2005 Developer Edition instance. Any suggestions would be appreciated.
P.S.: As you notice I'm a complete novice in programming and maybe intermediate in SQL Server so please give detailed steps if possible

Thank you.