Database could not be accessed - Event 3760 (SharePoint 2010 Products)


Applies to: SharePoint Server 2010, SharePoint Foundation 2010

Alert Name:   Database could not be accessed

Event ID:   3760

Summary:   Microsoft SharePoint Server 2010 uses Microsoft SQL Server 2008 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.

SharePoint Server 2010 uses a service account to communicate with the database on behalf of a user request. This service account can be either a specific domain name/user 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.

Symptoms:   The following symptoms might appear:

  • Content in the database is not available and attempts to access the database generate errors.

  • This event appears in the event log: Event ID: 3760 Description: SQL Database '<database name>' on SQL Server instance '<instance name>' not found. Additional error information from SQL Server is included below. <error information>

Cause:   One or more of the following might cause this:.

  • The SQL Server user login failed.

  • The database has been deleted or renamed.

  • The database is currently unavailable because it is in an offline or loading state.


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

Resolution:   Verify that SQL Server is running

  • On the database server, in the Services snap-in, verify that the SQL Server (MSSQLSERVER) service is running.

Resolution:   Verify that the user account can connect to SQL Server

  • Log onto Microsoft SQL Server Management Studio as the account provided in the error details and click Connect and then Database Engine.

  • Type the server name provided in the error details and click Connect.

Resolution:   Verify that the database exists

  • In Microsoft SQL Server Management Studio, expand the server node.

  • Expand the Databases node.

  • Verify that the database exists.


You must be a member of the Farm Administrators SharePoint group to perform these tasks.

Resolution:   Restore database

  • If the SQL Server database is not present or accessible on the computer that is running SQL Server, restore the database from a backup and reconnect it to SharePoint Server 2010.

    To restore the database from a backup:

    1. On the SharePoint Central Administration Web site, click Backup and Restore and in the Farm Backup and Restore section click Restore from a backup.

    2. On the Restore from Backup page, type the backup path in the Backup Directory Location text box, select the backup you want to restore, and then click Next.

    3. Select the database from the list and then click Next.


      The backup must include the database and the accompanying Web application.

    4. In the Restore Options section, select the Same configuration option. This action overwrites the existing database.

    5. Click Start Restore.

    To reconnect the database in Central Administration:

    1. On the Central Administration page, click Application Management and in the Databases section click Manage Content databases.

    2. On the Manage Content Databases page, click Add a content database and in the Web Application section select the Web application.

    3. Under Database Name and Authentication, type the name of the server in the Database Server text box and type the database name in the Database Name text box.

    4. Click OK to save the changes.

    To verify that any database issues have been resolved:

    1. In the SharePoint Management Shell, run the Windows PowerShell command Get-SPSite | Format-Table -Property ID,WebApplication,ContentDatabase to obtain a list of 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 make sure that the appropriate page rendered. An Access Denied page with an option to request access, or the option to log on as a different user, indicates that the operation completed successfully.

    3. On the Central Administration page, click Application Management and in the Site Collections section click Specify Quota Templates.

    4. 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 verify that it can be accessed in step 7.

    5. Click OK to save the quota template.

    6. Refresh the browser window, and then return to the Quota Templates page. If the quota template that you created can be selected, access to the SharePoint Server 2010 configuration database has been restored.

    7. Click Delete to delete the quota template.