Installsqlstate sql aspnet_regsql exe

If the category already exists, an error from msdb. SQL What am I doing wrong? I need to store session state in SQL Server. Monday, June 6, PM. User posted Hi, Thank you for the post. I understand that running InstallSqlState. According to the detail error message.

Please refer to following suggestion: 1. Do not try to run InstallSqlState. See comments under marcc's post to learn of my stupidity! RickNZ Hmmm, I ran it 'by hand' and it's working great. I was under the impression that session state also is responsible for maintaining forms authentication I'm running a few servers under a balancer.

Session state is indeed being saved just unused on the pages I was testing. What I actually needed to do was set the same machineKey keys to preserve authentication as users are shunted between nodes of my farm. A severe case of RTFM.

Larry Silverman Larry Silverman 1, 1 1 gold badge 10 10 silver badges 28 28 bronze badges. Sign up or log in Sign up using Google.

Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. Tables are created in temdb database. In this case session is lost if SQL Server restarts, p , represents persistent storage. Session state tables are created in AspState database, c , custom storage. In this case, you specify database name where sessions will be stored. Database name is set using -D parameter. Some example configuration, which uses custom database named "YourCustomDatabaseName" for session storage and uses windows authentication to connect to SQL Server, would be:.

If you prefer graphical user interface, you can use this wizard to specify each parameter and avoid using of command line arguments. SQL Server Agent runs job to delete data on session expiration.

In most cases, Agent is not allowed by hosting providers in shared web hosting scenario. Also, on shared web hosting you are probably not allowed to create new database in code.

It will just create. Generated scripts include part for creating database. But, on shared hosting we'll create database using web hosting control panel or use some existing predefined databases. Because of that, we need to remove this part from script. T-SQL code which should be removed is located on top of the script and in our case will look like this:.

Since shared hosting providers mostly don't allow SQL Server Agent too, you need to remove parts that create job for deleting of sessions.

After that, script can be executed against database in shared hosting scenario. But, we have another problem. We need other mechanism to delete expired session. Expired sessions are deleted when DeletedExpiredSessions stored procedure is executed. By default, this procedure is called by Agent. As an alternative, you can call this procedure using line:.

Exec [dbo]. In this case expired sessions will be deleted any time session data are requested. On high traffic web sites, this could be too often and possibly overburden SQL Server. Also, you probably don't need to check expired session so often. Another option is to create scheduled task which will execute in regular time intervals and call DeleteExpiredSessions procedure. This will display the Attach Databases dialog box. From here, click the Add button, browse to the SecurityTutorials.

Figure 4 shows the Attach Databases dialog box after the SecurityTutorials. Figure 5 shows Management Studio's Object Explorer after the database has been successfully attached.

Figure 4 : Attach the SecurityTutorials. Figure 5 : The SecurityTutorials. As Figure 5 shows, the SecurityTutorials. Let's change it to a more memorable and easier to type name. Right-click on the database, choose Rename from the context menu, and rename it SecurityTutorialsDatabase.

This does not change the filename, just the name the database uses to identify itself to SQL Server. At this point we know the server and database names for the SecurityTutorials. Either approach will net the same results. The wizard makes it easy to add or remove the ASP. NET application services on a specified database. The first screen of the wizard, shown in Figure 7, describes the purpose of the tool.

Figure 7 : Use the ASP. The second step in the wizard asks us whether we want to add the application services or remove them.

Since we want to add the tables, views, and stored procedures necessary for the SqlMembershipProvider , choose the Configure SQL Server for application services option. Later, if you want to remove this schema from your database, re-run this wizard, but instead choose the Remove application services information from an existing database option.

The third step prompts for the database information: the server name, authentication information, and the database name. If you have been following along with this tutorial and have added the SecurityTutorials. Figure 9 : Enter the Database Information Click to view full-size image. After entering the database information, click Next.

The final step summarizes the steps that will be taken. Click Next to install the application services and then Finish to complete the wizard. If you used Management Studio to attach the database and rename the database file, be sure to detach the database and close Management Studio before reopening Visual Studio. To detach the SecurityTutorialsDatabase database, right-click on the database name and, from the Tasks menu, choose Detach. Upon completion of the wizard, return to Visual Studio and navigate to the Database Explorer.

Expand the Tables folder. Likewise, a variety of views and stored procedures can be found under the Views and Stored Procedures folders.

These database objects make up the application services schema. We will examine the membership- and role-specific database objects in Step 3. At this point we have created the database objects needed by the SqlMembershipProvider. We'll look at how to specify what provider to use and how to customize the selected provider's settings in Step 4.

But first, let's take a deeper look at the database objects that were just created. NET application, the implementation details are encapsulated by the provider. In future tutorials we will interface with these frameworks via the. When using these high-level APIs we do not need to concern ourselves with the low-level details, like what queries are executed or what tables are modified by the SqlMembershipProvider and SqlRoleProvider.

Given this, we could confidently use the Membership and Roles frameworks without having explored the database schema created in Step 2. However, when creating the tables to store application data we may need to create entities that relate to users or roles. It helps to have a familiarity with the SqlMembershipProvider and SqlRoleProvider schemas when establishing foreign key constraints between the application data tables and those tables created in Step 2.

Moreover, in certain rare circumstances we may need to interface with the user and role stores directly at the database level instead of through the Membership or Roles classes. The Membership and Roles frameworks are designed such that a single user and role store can be shared among many different applications. NET application that uses the Membership or Roles frameworks must specify what application partition to use.

In short, multiple web applications can use the same user and role stores. These three web applications each have their own unique users and roles, yet they all physically store their user account and role information in the same database tables.

Each application that uses the database to store user account information is represented by a row in this table. ApplicationId is of type uniqueidentifier and is the table's primary key; ApplicationName provides a unique human-friendly name for each application. The ApplicationId field in these tables specifies the application partition the user account or role belongs to. The three most pertinent columns are:.