Share via

Access Services - configuration database access failed - Event 1 (SharePoint Server 2010)

  • Article

 

Applies to: SharePoint Server 2010 Enterprise

Alert Name:   Configuration database access failed

Event ID:   1

Summary:   Access Services in Microsoft SharePoint Server 2010 stores its settings in the Microsoft SharePoint Server 2010 configuration database. Either a web front end or a back end server component of Access Services was unable to read its settings from the configuration database.

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

  • Access Services in SharePoint might not start.

  • Access Services might fail to create Access Services applications.

  • Users might not be able to view applications in their browsers, or the service might be otherwise unavailable.

  • This event appears in the event log: Event ID: 1 Description: Access Services: Unexpected exception while trying to access <configuration database name>. Error = <exception message>

  • This event appears in the event log: Event ID: 32 Description: Unable to obtain configuration information.

  • This event appears in the event log: Event ID: 33 Description: Unable to obtain AccessWebServiceInstance.

  • This event appears in the event log: Event ID: 34 Description: There is no application associated with proxy <name of Access Services proxy>.

  • This event appears in the event log: Event ID: 35 Description: There is no SharePoint service context.

  • This event appears in the event log: Event ID: 36 Description: There is no default Access Services Application Proxy.

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

  • The configuration database might be experiencing a failure.

  • Permissions might have changed for the account that runs the application pool that Access Services is running, so Access Services no longer has access to the SharePoint Server 2010 configuration database.

  • The front end proxy for Access Services may have been deleted.

  • No front end proxy for Access Services is designated as the default.

  • An unexpected failure occurred during provisioning of the service.

Resolution for event ID 1 and 32:   Grant correct permissions to the database access account

  • Resolve this issue by finding the name of the database access account, adding the database access account in Microsoft SQL Server 2008 , and then verifying that the account has correct permissions in SQL Server 2008.

    Note

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

    To find the database access account:

    1. On the SharePoint Central Administration Web site, in the Security section click Configure service accounts.

    2. On the Service Accounts page, in the Credential Management section, in the upper drop-down list, select the application pool that is running Access Services. When the application pool is selected, the name of the Access Services application is listed in the text box; for example, AccessDataService-Type.

    3. Note the account that is selected in the Select an account for this component drop-down list.

    To add the database account in SQL Server 2008:

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

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

    3. If the account exists, expand the Databases node, expand the configuration database node, expand the Security node, and then expand the Roles node.

    4. Expand the Database Roles node and double-click the db_reader role.

    5. In the Database Roles 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.

    To verify that this account has correct permissions in SQL Server:

    1. Click Start, click All Programs, click Microsoft SharePoint 2010 Products, and then click SharePoint Management Shell. A Command Prompt window opens.

    2. Enter the Windows PowerShell command Get-SPAccessServiceApplication"<name of your access service>" | format-table.

    3. This command retrieves the Access Services application and displays the values for some settings. These values are read from the configuration database.

Ensure there is a default proxy for Access Services

  1. On the Central Administration home page, click Application Management.

  2. On the Application Management page, under Service Applications, click Configure service application associations.

  3. On the Service Application Associations page, clock on proxy listed in the Application Proxy Group column for the Web application.

  4. In the Configure Service Application Associations dialog, ensure that the AccessDataServiceInstance - Access Services Web Service Application Proxy box is checked and click OK.

  5. If the AccessDataServiceInstance - Access Services Web Service Application Proxy box does not exist, you must re-provision Access Services on the server.

Re-provision Access Services

  1. If you only have one Access Services application in your farm, you will want to remove it before provisioning a new one. This will ensure that any proxies are correctly cleaned up. To remove an existing Access Services application:

    1. On the Central Administration home page, click Application Management.

    2. On the Application Management page, under Service Applications, click Manage service applications.

    3. On the Manage service applications page, highlight the Access Services Web Service Application and click Delete on the ribbon.

    4. Important

      Do not check the Delete data associated with the Service Applications checkbox.

      On the Delete Service Application dialog, click OK.

  2. Add a new Access Services application to the server:

    1. On the Central Administration home page, click Application Management.

    2. On the Application Management page, under Service Applications, click Manage service applications.

    3. On the Manage service applications page, click New on the ribbon and select Access Services.

    4. In the Create New Access Services Application dialog, under Name, type in the name for the Access Services application. The name must be unique among all Access Services applications.

    5. Under Application Pool, choose to reuse an existing application pool, or create a new one and choose an account to run the application pool as.

    6. Click OK.