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.
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.
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.
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.
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?
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>
nnnnnpatel
Member
225 Points
53 Posts
Error Message: The user instance login flag is not supported on this version of SQL Server. The ...
Aug 22, 2005 09:47 PM|LINK
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:
Stack Trace:
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
slickb
Member
5 Points
1 Post
Re: Error Message: The user instance login flag is not supported on this version of SQL Server. ...
Sep 11, 2005 03:00 AM|LINK
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
OWScott
Participant
1939 Points
360 Posts
ASPInsiders
MVP
Re: Error Message: The user instance login flag is not supported on this version of SQL Server. ...
Oct 19, 2005 03:02 PM|LINK
Scott Forsyth
http://www.orcsweb.com
Managed Complex Hosting
#1 in Service and Support
Microsoft MVP - IIS
Vaasnet
www.vaasnet.com
nnnnnpatel
Member
225 Points
53 Posts
Re: Error Message: The user instance login flag is not supported on this version of SQL Server. ...
Oct 19, 2005 06:35 PM|LINK
Nick
JimRieck
Member
105 Points
21 Posts
Re: Error Message: The user instance login flag is not supported on this version of SQL Server. ...
Nov 18, 2005 12:17 PM|LINK
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
OWScott
Participant
1939 Points
360 Posts
ASPInsiders
MVP
Re: Error Message: The user instance login flag is not supported on this version of SQL Server. ...
Nov 18, 2005 04:06 PM|LINK
http://asp.net/default.aspx?tabindex=5&tabid=41#Reports
Scott
Microsoft MVP - IIS
Vaasnet
www.vaasnet.com
JimRieck
Member
105 Points
21 Posts
Re: Error Message: The user instance login flag is not supported on this version of SQL Server. ...
Nov 18, 2005 04:40 PM|LINK
Jim
OWScott
Participant
1939 Points
360 Posts
ASPInsiders
MVP
Re: Error Message: The user instance login flag is not supported on this version of SQL Server. ...
Nov 18, 2005 07:57 PM|LINK
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
Microsoft MVP - IIS
Vaasnet
www.vaasnet.com
JimRieck
Member
105 Points
21 Posts
Re: Error Message: The user instance login flag is not supported on this version of SQL Server. ...
Nov 20, 2005 06:40 PM|LINK
Hi Scott,
It took some doing, but I got it. Thanks for your help. Good solution!
Jim
OWScott
Participant
1939 Points
360 Posts
ASPInsiders
MVP
Re: Error Message: The user instance login flag is not supported on this version of SQL Server. ...
Nov 21, 2005 12:42 AM|LINK
Scott
Microsoft MVP - IIS
Vaasnet
www.vaasnet.com