SharePoint Health Analyzer rules reference (SharePoint Foundation 2010)

 

Applies to: SharePoint Foundation 2010

The articles in this section are articles for the SharePoint Health Analyzer. Typically, you would see these articles after you click a link in a message in the SharePoint Health Analyzer in Central Administration. You can use these articles to help you troubleshoot problems in Microsoft SharePoint Foundation 2010.

In this section:

• Web Applications using Claims authentication require an update (SharePoint Foundation 2010)

  This article describes the SharePoint Health Analyzer rule "Web Applications using Claims authentication require an update", and describes how to update Claims Authentication.

• Automatic update setting inconsistent across farm servers (SharePoint Foundation 2010)

  This article describes the SharePoint Health Analyzer rule "Automatic update setting inconsistent across farm servers", and describes how to configure automatic update settings to be consistent across the farm.

• Diagnostic logging is set to verbose (SharePoint Foundation 2010)

  This article describes the SharePoint Health Analyzer rule "Diagnostic logging is set to verbose", and describes how to configure diagnostic logging.

• The server farm account should not be used for other services (SharePoint Foundation 2010)

  This article describes the SharePoint Health Analyzer rule "The server farm account should not be used for other services", and describes how to change the account that is used for other services.

• One or more services have started or stopped unexpectedly (SharePoint Foundation 2010)

  This article describes the SharePoint Health Analyzer rule "One or more services have started or stopped unexpectedly", and describes how to start the service that is not running.

• Databases used by SharePoint have fragmented indices (SharePoint Foundation 2010)

  This article describes the SharePoint Health Analyzer rule "Databases used by SharePoint have fragmented indices", and describes how to reorganize and rebuild indexes.

• Content databases contain orphaned items (SharePoint Foundation 2010)

  This article describes the SharePoint Health Analyzer rule "Content databases contain orphaned items", and describes how to remove orphan sites from the content.

• Outbound e-mail has not been configured (SharePoint Foundation 2010)

  This article describes the SharePoint Health Analyzer rule "Outbound e-mail has not been configured", and describes how to configure outgoing e-mail settings in Central Administration.

• Some health analyzer rules do not have associated timer jobs (SharePoint Foundation 2010)

  This article describes the SharePoint Health Analyzer rule "Some health analyzer rules do not have associated timer jobs", and describes how to create the health data collection timer jobs.

• Drives are running out of free space (SharePoint Foundation 2010)

  This article describes the SharePoint Health Analyzer rule "Drives are running out of free space", and describes how to free disk space on the server computer.

• The paging file size should exceed the amount of physical RAM in the system (SharePoint Foundation 2010)

  This article describes the SharePoint Health Analyzer rule "The paging file size should exceed the amount of physical RAM in the system", and describes how to increase the minimum size of the paging file.

• Built-in accounts are used as application pool or service identities (SharePoint Foundation 2010)

  This article describes the SharePoint Health Analyzer rule "Built-in accounts are used as application pool or service identities", and describes how to change the identity that is used for the service or application pool.

• Web Analytics: Monitors the health of the Report Consolidator component (SharePoint Foundation 2010)

  This article describes the SharePoint Health Analyzer rule "Web Analytics: Monitors the health of the Report Consolidator component", and describes how to enable data trimming to improve the performance of the Report Consolidator.

• Web Analytics: Verifies that when the Web Analytics is installed and running, usage logging is enabled in the farm (SharePoint Foundation 2010)

  This article describes the SharePoint Health Analyzer rule " Web Analytics: Verifies that when the Web Analytics is installed and running, usage logging is enabled in the farm", and describes how to enable usage logging.

• Web Analytics: Verifies that a web application is serviced by at most one Web Analytics service application proxy (SharePoint Foundation 2010)

  This article describes the SharePoint Health Analyzer rule "Web Analytics: Verifies that a web application is serviced by at most one Web Analytics service application proxy", and describes how to disassociate other Web Analytics service application proxies.

• Web Analytics: Verifies that the SQL Server Service Broker is enabled for the Web Analytics staging databases (SharePoint Foundation 2010)

  This article describes the SharePoint Health Analyzer rule "Web Analytics: Verifies that the SQL Server Service Broker is enabled for the Web Analytics staging databases", and describes how to enable the service broker queue.

• One or more categories are configured with verbose trace logging setting

  This article provides information about the SharePoint Health Analyzer rule "One or more categories are configured with verbose trace logging", describes the cause and includes a procedure that helps to ensure that diagnostic logging settings are configured correctly.

• Accounts used by application pools or service identities are in the local machine Administrators group (SharePoint Foundation 2010)

  This article describes how to resolve the SharePoint Health Analyzer event by changing the user account to a predefined account or to a domain user account that is not a member of the Administrators group.

• Application pools recycle when memory limits are exceeded (SharePoint Foundation 2010)

  This article describes how to resolve the SharePoint Health Analyzer event by disabling application pool recycling.

• Alternate access URLs have not been configured (SharePoint Foundation 2010)

  This article describes how to resolve the SharePoint Health Analyzer event by changing the default zone URL.

• Product / patch installation or server upgrade required (SharePoint Foundation 2010)

  This article describes how to resolve the SharePoint Health Analyzer event by deploying updates or upgrading.

• Web.config file has incorrect settings for the requestFiltering element (SharePoint Foundation 2010)

  This article describes how to resolve the SharePoint Health Analyzer event by changing the requestFiltering settings in the Web.config file.

• Web.config files are not identical on all machines in the farm (SharePoint Foundation 2010)

  This article describes how to resolve the SharePoint Health Analyzer event by making the Web.config files identical on all front-end Web servers in the farm.

• The timer service failed to recycle (SharePoint Foundation 2010)

  This article describes how to resolve the SharePoint Health Analyzer event by changing the schedule for the Timer Service Recycle job so that it does not conflict with other long-running timer jobs.

• The Application Discovery and Load Balancer Service is not running in this farm (SharePoint Foundation 2010)

  This article describes how to resolve the SharePoint Health Analyzer event by starting the Application Discovery and Load Balancer service on at least one server in the farm.

• Databases running in compatibility range, upgrade recommended (SharePoint Foundation 2010)

  This article describes how to resolve the SharePoint Health Analyzer event by installing software updates.

• Databases require upgrade or not supported (SharePoint Foundation 2010)

  This article describes how to resolve the SharePoint Health Analyzer event by installing software updates.

• Databases within this farm are set to read only and will fail to upgrade unless it is set to a read-write state (SharePoint Foundation 2010)

  This article describes how to resolve the SharePoint Health Analyzer event by setting the databases to read-write.

• Drives used for SQL databases are running out of free space (SharePoint Foundation 2010)

  This article describes how to resolve the SharePoint Health Analyzer event by freeing disk space on the database server computer or decreasing the number of days to store log files.

• Databases used by SharePoint have outdated index statistics (SharePoint Foundation 2010)

  This article describes how to resolve the SharePoint Health Analyzer event by editing the rule definition so that the configuration is automatically repaired.

• Databases exist on servers running SharePoint Foundation (SharePoint Foundation 2010)

  This article describes how to resolve the SharePoint Health Analyzer event by moving the databases to a separate server.

• Database has large amounts of unused space (SharePoint Foundation 2010)

  This article describes how to resolve the SharePoint Health Analyzer event by shrinking the database.

• One or more servers is not responding (SharePoint Foundation 2010)

  This article describes how to resolve the SharePoint Health Analyzer event by connecting the server to the network, restarting the SharePoint 2010 Timer service (SPTimerV4), or removing the server record from the SharePoint topology.

• The local machine is not joined to a SharePoint server farm (SharePoint Foundation 2010)

  This article describes how to resolve the SharePoint Health Analyzer event by creating a new farm or adding this computer to an existing farm.

• The Security Token Service is not available (SharePoint Foundation 2010)

  This article describes how to resolve the SharePoint Health Analyzer event by restarting the Security Token Service application pool.

• Some content databases are growing too large (SharePoint Foundation 2010)

  This article describes how to resolve the SharePoint Health Analyzer event by editing the rule definition to prevent new sites from being added to the databases, and then moving some site collections to other databases.