Access failed to contact Access Services - Events 24 25 26 (SharePoint Server 2010)

  • Article

 

Applies to: SharePoint Server 2010 Enterprise

Alert Name:   Failed to contact Access Services

Event ID:   24 25 26

Summary:   The front-end Web application made a request to a specific Access Services in Microsoft SharePoint Server 2010 back-end server computer and encountered an unexpected exception. This can indicate an intermittent problem or a problem with a specific server computer. In these cases, the front-end Web application attempts to load balance to a different back-end server computer. The Access Services server computer is required to run queries and maintain cache state for those queries.

Symptoms:   

  • The following message may appear in the event log: Event ID: 24 Description: There was an error in communicating with Access Data Services exception: <exception description> [Session: <session ID> User: <username>].

  • The following message may appear in the event log: Event ID: 25. Description: There was an error in communicating with Access Data Services exception: <exception description> [Session: <session ID> User: <username>].

  • The following message may appear in the event log: Event ID: 26. Description: Unable to reach Access Data Services. [Session: <session ID> User: <username>].

Cause:   The Access Services in SharePoint server computer is in an unstable state and might need to be restarted.

  • The web front end encountered an intermittent failure when trying to contact the Access Data Services server.

  • The specific Access Data Services server is in an invalid state and may need to be restarted.

Restart the Access Data Services server

  1. Before restarting, verify that this is a problem that occurs often. It may be an intermittent problem that is automatically recovered from.

  2. Restart the Access Data Services server.

  3. If the problem continues to often, and restarting the server does not correct the problem, ensure that the hardware of the server is functioning correctly. If this is not the problem, reinstall Access Services on the server and re-add the server to the farm.