OpsMgr R2 by Example: the SharePoint MP

The Office SharePoint Server 2007 management pack and SharePoint Portal Server 2003 management pack are separate management packs. This discussion focuses on the Office SharePoint Server 2007 management pack, as this is the more current version of the two.

How to Install the SharePoint MP

  1. If your environment is running SharePoint 2007, download the Office SharePoint Server 2007 Management Pack from the Management Pack Catalog. The Office SharePoint Server 2007 Management Pack Guide is included in the download and labeled “Microsoft_Office_SharePoint_Server_Management_Pack_Guide.doc.”
  2. Read the Management Pack guide, which includes tips such as resizing the Windows System and Application logs to at least 10240 in size.
  3. Import the Office SharePoint Server 2007 management pack (using either the Operations console or PowerShell).
  4. Create a SharePoint_Overrides management pack to contain any overrides required for the MP.

The Office SharePoint 2007 management pack does not support agentless monitoring.

SharePoint MP Tuning / Alerts to look for

The following alerts were encountered and resolved when tuning the various SharePoint management packs (listed in alphabetical order by Alert name). Alerts from the SharePoint Portal Server 2003 management pack are also provided as additional information in the event similar issues are found in the SharePoint 2007 version of the management pack.

Alert: Can not load virus scanner

Issue: SharePoint 2003 alert. This looks for event number 1000 from the source of Windows SharePoint Services 2.0 containing the description.

Resolution: There is no virus scanner on this system specifically for SharePoint, so this rule was disabled for this system.

Alert: Failed to load index

Issue: This appears to be a side effect of an underlying corruption that occurred on an index. See http://objectmix.com/sharepoint/298641-sharepoint-search-index-corrupt.html.

Resolution: This environment had three SharePoint servers; two of them were for SharePoint content and the third server to provide indexing. In SharePoint Central administration it was determined there was no indexing server. Configured the third server to perform indexing and these issues no longer occurred.

Alert: Failure in loading assembly

Issue: Per the management pack guide: Discovery for the SharePoint Portal Server Management Pack relies on the file wssDiscovery.exe. This file is run automatically when you import the Management Pack. You must configure the Agent Action Account so that is has administrative access to the SharePoint Portal Server API and administrator rights to the SQL Server databases.

Resolution: For this to work correctly, you must enable Proxy. Be sure to enable Proxy for each of the SharePoint (including SharePoint 2003) servers.

Alert: IIS Stop Command

Issue: IIS was stopped on the server while a portal protection program was installed on the system. This action was performed by a system administrator. This is an alert rule so it will not close automatically.

Resolution: Created a web monitor for the SharePoint website. Changed the severity of this item from 2 to 1 (critical to warning) as this is by itself not a critical situation. If the website was down as a result, that would be a critical situation but these are checked separately with web monitors.

Alert: Index is corrupt

Issue: Index corruption identified on multiple SharePoint servers.

Resolution: This environment had three SharePoint servers; two of them were for SharePoint content and the third server to provide indexing. In SharePoint Central administration, it was determined there was no indexing server. Configured the third server to perform indexing and these issues no longer occurred.

Alert: Query server removed from rotation

Issue: This appears to be a side effect of an underlying corruption that occurred on an index. See http://objectmix.com/sharepoint/298641-sharepoint-search-index-corrupt.html.

Resolution: This environment had three SharePoint servers; two of them were for SharePoint content and the third server to provide indexing. In SharePoint Central administration, it was determined there was no indexing server. Configured the third server to perform indexing and these issues no longer occurred.

Alert: Sweep Synch failed

Issue: Errors reported on various SharePoint servers in the server farm. This appears to be a side effect of an underlying corruption that occurred on an index. http://objectmix.com/sharepoint/298641-sharepoint-search-index-corrupt.html

Resolution: This environment had three SharePoint servers, two of them were for SharePoint content and the third server to provide indexing. In SharePoint Central administration, it was determined there was no indexing server. Configured the third server to perform indexing and these issues no longer occurred.

Alert: The Microsoft Single Sign-on Service State

Issue: This service is not running on the SharePoint 2007 servers in the environment. This service is used to store login credentials for 3rd party applications so you can create links from SharePoint to those apps and auto login users if they aren’t using Windows Authentication. That is the only reason you would need to have it running.

Resolution: This functionality was not in use in the environment, so created an override to disable the alert, and stored it in a Sharepoint_Overrides management pack.

Alert: The Office SharePoint Server Search Service State

Issue: Office SharePoint Server Search is not running. This appears to be a side effect of an underlying corruption that occurred on an index. See http://objectmix.com/sharepoint/298641-sharepoint-search-index-corrupt.html.

Resolution: This environment had three SharePoint servers; two of them were for SharePoint content and the third server to provide indexing. In SharePoint Central administration, it was determined there was no indexing server. Configured the third server to perform indexing and these issues no longer occurred.

Alert: Unable to discovery sharepoint components

Issue: Per the management pack guide: Discovery for the SharePoint Portal Server Management Pack relies on the file wss Discovery.exe. This file is run automatically when you import the management pack. You must configure the Agent Action Account so that is has administrative access to the SharePoint Portal Server API and administrator rights to the SQL Server databases.

Resolution: For discovery to work correctly, you must enable Proxy. Be sure to enable Proxy for each of the SharePoint (including SharePoint 2003) servers.

About these ads
This entry was posted in Tuning and Configuration. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s