Share via

Secure Store proxy unexpected exception - Event 7557 (SharePoint Server 2010)

  • Article

 

Applies to: SharePoint Server 2010

Alert Name:   Secure Store proxy unexpected exception

Event ID:   7557

Summary:   When a front-end Web server receives a request from a client computer, it routes the request to a Microsoft SharePoint Server 2010 application server through a load balancer. The load balancer maintains a list of available servers for a given service application. If the Secure Store service application on one or more application servers does not respond, the load balancer will remove the application server from the list of available servers and will raise this event.

If the Secure Store service application is enabled on more than one Microsoft SharePoint Server 2010 application server, the client computers will not be affected. If the service is not enabled on more than one application server, the client computers that rely on the secure store credential database to authenticate users will fail to authenticate.

Symptoms:   The following event appears in the event log: Event ID: 7557 Description: The Secure Store service application %name% is not accessible.

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

  • The application server is down or is not accessible due to network issues.

  • The Secure Store service application is not provisioned correctly.

Resolution:   Verify that the Secure Store application server is available

  1. Verify that the user account that is performing this procedure is a member of the Farm Administrators group.

  2. On the Central Administration Home page, under System Settings, click Manage services on server.

  3. On the Services on Server page, under Services, if the Secure Store service is not started, click Start.

  4. On the Central Administration Home page, click Application Management.

  5. On the Application Management page, in the Service Applications section, click Manage service applications.

  6. On the Service Applications page, click Secure Store.

  7. On the Secure Store Service Application page, ensure that at least one target application appears in the list.

  8. If the Secure Store service application is not started, do the following:

    1. On the Service Applications page, select the Secure Store service application name, and then click Properties on the ribbon.

    2. In the Edit Properties dialog box, in the Database section, ensure that the authentication method used is correct and that the account (if listed) has read and write permissions to the database.

    3. In the Application Pool section, ensure that the application pool account (if listed) has sufficient permissions to run the application pool.