Event ID 3758 (Windows SharePoint Services health model)

Event ID 3758 (Windows SharePoint Services health model)
Windows SharePoint Services 3.0

Applies To: Windows SharePoint Services 3.0


Topic Last Modified: 2008-04-27

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  


Windows SharePoint Services




Windows SharePoint Services 3



Symbolic Name:



Database full error on SQL Server instance ‘%1’ in database ‘%2’. Additional error information from SQL Server is included below.


Resolve Increase the size of the SQL Server database

Windows SharePoint Services 3.0 cannot write to a database if the database has run out of room. One solution is to increase the maximum size setting for the database that is full.

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

To increase the size of the database

  1. In SQL Server Management Suite, open the server node, right-click the database, and then click Properties. The database name is provided in the event message.

  2. On the Properties dialog box, on the left navigation pane, click Files.

  3. In the Database files box, in the Autogrowth column, click the ellipsis for the database file.

  4. In the Change Autogrowth dialog box, under Maximum File Size, if the Restricted File Growth option is selected, increase the maximum file size in the box to the right. You can also configure the database to grow without restrictions by selecting the Unrestricted File Growth option.

  5. Click OK.


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


Leave a Reply