Export (0) Print
Expand All
Expand Minimize

Cannot connect to SQL Server - Event 3355 (SharePoint 2010 Products)

 

Applies to: SharePoint Server 2010, SharePoint Foundation 2010

Topic Last Modified: 2009-11-10

Alert Name:   Cannot connect to SQL Server

Event ID:   3355

Summary:   Microsoft SharePoint Foundation 2010 uses Microsoft SQL Server 2008 databases to store configuration settings and most of the content for the Microsoft SharePoint Foundation Web site. 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 Foundation 2010 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 or 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.

This error indicates that Microsoft SharePoint Foundation could not connect to the SQL Server database.

Symptoms:   One or more of the following symptoms might appear:

  • Attempts to communicate with SQL Server fail and no content from databases hosted on the SQL Server can be accessed.

  • This event appears in the event log: Event ID: 3355 Cannot connect to SQL Server. <Server Name> not found. Additional error information from SQL Server is included below.

Cause:   One or more of the following might be the cause:

  1. The SQL Server might be offline.

  2. The SharePoint Foundation database access account might not have the necessary permissions to communicate with the SQL Server.

  3. A firewall that runs on either the local server or on SQL Server might be blocking network communications.

Resolution:   Grant correct permissions to the database access account
  • You must be a member of the Farm Administrators group to perform this task.

    Assign the database access account:

    1. On the Central Administration home page, click Security and in the General Security section click Configure service accounts.

    2. On the Service Accounts page, in the Credential Management section, in the upper drop-down list click the correct Web application pool for your Web application.

    3. In the Select an account for this component drop-down list, click the domain account that you want to associate with this Web application pool, or click Register new managed account to associate a new domain account with this application pool.

    4. Click OK to save changes.

    Verify that the account has correct permissions in SQL Server:

    1. Connect to the computer that runs SQL Server by using an account that has Administrator permissions.

    2. In SQL Server Management Studio, Object Explorer navigation pane, expand the Security node, and then expand the Logins node. The name of the database access account indicates that it is a SQL login.

    3. If the account exists, in the Object Explorer navigation pane, expand the Databases node, expand the configuration database node, expand the Security, and then click Roles.

    4. Expand the Database Roles node, right-click db_owner role and select Properties.

    5. In the Database Role Properties dialog box, check whether the database access account is in the Members of this role list. If the account is not listed, click Add.

    Verify that any database issues are 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 ensure 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, on the Quick Launch, 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 SQL Server 2008 configuration database in Microsoft SharePoint Foundation is restored.

    7. Click Delete to delete the quota template.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft