Event ID 5214 (Windows SharePoint Services health model)

Applies To: Windows SharePoint Services 3.0

Windows SharePoint Services 3.0 uses SQL Server databases to store most of the content for the Web site and configuration settings. For example, all pages in the site, files in document libraries, files attached to lists, and information in lists are stored in the content database, and security and permission settings along with other configuration settings are stored in the configuration database in SQL Server.

Windows SharePoint Services 3.0 uses a service account to communicate with the database on behalf of a user request. This service account can be either a specific user name and password (domain name and password) or a predefined system account, such as Local System or Network Service. When a SQL Server database is created, a value for the maximum database size is set. Each database has a separate database size setting. Note that a Web application might be associated with one or many databases.

Event Details

Resolve

Grant correct permissions to the database access account

You must be a member of the SharePoint Administrators group to perform this task.

To assign the database access account

1. In Central Administration, on the left navigation pane, click Operations.

2. On the Operations page, in the Security Configuration section, click Security accounts.

3. On the Security Accounts page, in the Credential Management section, select the Web application pool option.

4. Select the Web service from the Web service drop-down list. The default is "Windows SharePoint Services Web Application".

5. Select the Web application pool from the Application pool drop-down list.

6. Select the Configurable option.

7. Type the correct domain account into the User name box and the password for that account into the Password box.

8. Click OK to save changes.

9. Restart IIS.

To ensure that this account has correct permission in SQL Server

1. Connect to the computer running SQL Server by using an account with administrator permissions.

2. In SQL Server Management Studio, open the Security node, and then open the Logins node. You should see the account listed as a SQL Login.

3. If the account is there, then open the database node, open the Security node under the database, and then open the Roles node.

4. Open the Database Roles node and double-click the db_owner role to open its properties.

5. In the Database Roles Properties dialog box, under Members of this role, you should see the database access account. If the account is not there, add it by clicking Add.

Verify

You must be a member of the SharePoint Administrators group to perform this task.

To ensure that any database issues have been resolved

1. Use the command Stsadm.exe -o enumsites to list the sites for each Web application to list all sites in the various databases, and locate one site in each database.

2. Browse to that site, and ensure that the appropriate page rendered. If you get an access denied page with an option to request access, or the option to sign in as a different user, the operation completed successfully.

3. In Central Administration, on the left-hand navigation pane, click Application Management.

4. On the Application Management page, in the SharePoint Site Management section, click Quota templates.

5. On the Quota Templates page, create a new quota template. The specific settings are not relevant to this verification test. You are creating the template to see if it can be accessed in step 7.

6. Click OK to save the quota template.

7. Refresh the browser window, and then return to the quota templates page. If the quota template that you created can be selected, then access to the Windows SharePoint Services 3.0 Configuration database has been restored.

8. Click Delete to delete the quota template.

Related Management Information

Databases (Health model)

Windows SharePoint Services 3.0 health model