Tuesday, November 29, 2011

November Updates

Published the week of November 14, 2011

New articles
Database has large amounts of unused space (SharePoint Server 2010)   Describes how to resolve the SharePoint Health Analyzer event by shrinking the database.
Databases exist on servers running SharePoint Foundation (SharePoint Server 2010)   Describes how to resolve the SharePoint Health Analyzer event by moving the databases to a separate server.
Databases require upgrade or not supported (SharePoint Server 2010)   Describes how to resolve the SharePoint Health Analyzer event by installing software updates.
Databases running in compatibility range, upgrade recommended (SharePoint Server 2010)   Describes how to resolve the SharePoint Health Analyzer event by installing software updates.
Databases used by SharePoint have outdated index statistics (SharePoint Server 2010)   Describes how to resolve the SharePoint Health Analyzer event by editing the rule definition so that the configuration is automatically repaired.
Databases within this farm are set to read only and will fail to upgrade unless it is set to a read-write state (SharePoint Server 2010)   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 Server 2010)   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.
One or more servers is not responding (SharePoint Server 2010)   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 Application Discovery and Load Balancer Service is not running in this farm (SharePoint Server 2010)   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.
The local machine is not joined to a SharePoint server farm (SharePoint Server 2010)   Describes how to resolve the SharePoint Health Analyzer event by creating a new farm or adding this computer to an existing SharePoint farm.
The Security Token Service is not available (SharePoint Server 2010)   Describes how to resolve the SharePoint Health Analyzer event by restarting the Security Token Service application pool.
The timer service failed to recycle (SharePoint Server 2010)   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.
Web Analytics: Monitors the health of the Data Analyzer Light component (SharePoint Server 2010)   Describes how to resolve the SharePoint Health Analyzer event by adding more staging databases for the Web Analytics service to balance the load.
Web Analytics: Monitors the health of the Logging Extractor component (SharePoint Server 2010)   Describes how to resolve the SharePoint Health Analyzer event by adding more staging databases for the Web Analytics service to balance the load.
Web Analytics: Monitors the health of the User Behavior Analyzer component (SharePoint Server 2010)   Describes how to resolve the SharePoint Health Analyzer event by adding more staging databases for the Web Analytics service to balance the load.
Web Analytics: Verify that there is a data processing service started when there is a web service started (SharePoint Server 2010)   Describes how to resolve the SharePoint Health Analyzer event by starting the Web Analytics Data Processing service on any server in the farm.
Web.config files are not identical on all machines in the farm (SharePoint Server 2010)   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.
Updated article
User Profile Replication Engine overview (SharePoint Server 2010)   Added that the account should have Manage Social Data permission for social information replication.

No comments:

Post a Comment