Microsoft Office SharePoint Portal Server 2003 Management Pack Guide
| Archived content. No warranty is made as to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
Published: November 1, 2003
Microsoft Office SharePoint Portal Server 2003* *Management Pack for Microsoft Operations Manager 2000 SP1
Developed by: The Microsoft Office SharePoint Portal Server Team
Click here to download a copy of this guide
On This Page
Recommended Knowledge and Skills
Overview of the SharePoint Portal Server 2003 Management Pack
SharePoint Portal Server 2003 Management Pack Monitoring Scenarios
SharePoint Portal Server 2003 Monitoring Solution Components and Topologies
Setup and Configuration
Operations Tasks
Reference
Recommended Knowledge and Skills
To deploy and operate the Management Pack for Microsoft® Office SharePoint™ Portal Server 2003, it is recommended that you possess the following knowledge and skills:
A working knowledge of the Microsoft Operations Manager 2000 (MOM) monitoring features.
An understanding of the three MOM design architectures and the design architecture that is deployed in your organization. For more information, see Chapter 2, “Architecture Overview,” in the Microsoft Operations Manager 2000 SP1 Deployment Guide.
Be familiar with the recommended process for deploying Management Packs as described in Chapter 7, “Deploying Management Packs,” in the Microsoft Operations Manager 2000 SP1 Deployment Guide.
Overview of the SharePoint Portal Server 2003 Management Pack
The SharePoint Portal Server 2003 Management Pack monitors events placed in the application event log. This Management Pack highlights events that might indicate possible service outages or configuration problems, so you can quickly take corrective or preventative actions. For example, this Management Pack alerts you about the following critical conditions:
Data backup or restore fails
Core services (such as search, alert notifications, and administration) are not running
Content source crawl fails
Search propagation of one or more content indexes fails
Audience compilation or profile import fails
This Management Pack quickly brings any failures or configuration problems to your attention, which increases the availability and performance of SharePoint Portal Server 2003. This Management Pack also provides the knowledge and expertise that you need to leverage MOM and get an immediate return on your investment.
If the import is successful, a new entry appears under Rules, Processing Rule Groups, Microsoft Office SharePoint Portal Server 2003.
This Management Pack is intended to be used in combination with the Windows® SharePoint Services Management Pack.
SharePoint Portal Server 2003 Management Pack Monitoring Scenarios
Service Availability
The service availability scenario monitors the availability of the SharePoint Portal Server 2003 infrastructure. Service availability monitoring:
Generates alerts when one of the following SharePoint Portal Server-based services stop on SharePoint Portal Server 2003 systems:
Administration
Alert Notification
Search
Single Sign-On
Gatherer
Provides data when core SharePoint Portal Server 2003 services are started, so you can monitor the uptime of SharePoint Portal Server 2003 services.
Data Backup and Restore Monitoring
It is critical to a SharePoint Portal Server 2003 system to have a working backup and restore in place. The Management Pack helps in this task by monitoring the status of the backup and restore of the following SharePoint Portal Server 2003 components:
Backward-compatible document library
Content Index
SQL Server
Search
Content Source Crawl Failures
SharePoint Portal Server 2003 can include external sources in the search indexes. These sources need to be specified and approved by an administrator. The Management Pack monitors and generates alerts for failures for the following components of this process:
Crawl
Gatherer
Search Propagation Failures
By using SharePoint Portal Server 2003, you can propagate indexes from the index management server to the search server (that is, the server dedicated to processing user search queries). Propagation allows you to distribute your resources. You can limit the resource-intensive processes that are required to create indexes to the index management server. This allows SharePoint Portal Server 2003 to create extensive indexes without affecting the performance of the search server. The Management Pack monitors and generates alerts for the most critical failures of this process:
Propagation Failed (events 3063 or 7012)
Propagation Failure - Cannot commit index (event 7060)
Propagation Failure - Cannot commit index to any server (event 7077)
Propagation Failure - disk/mem (event 7027)
Propagation Failure - insufficient disk space (event 7057)
Audience Compilation or Profile Import Failures
When you compile an audience, the property values in user profiles and the membership in the distribution lists, security groups, and reporting structure are checked to see whether they match the audience rules that you created. Users that match the audience rules for an audience are included in that audience and receive content targeted to that audience. The Management Pack monitors the compilation process and generates alerts for any failure that might occur during this process.
You can import user profile information from the directory service of Active Directory®. This saves time entering user information for every user in your organization but might not include all the properties that you want to show for each user. The Management Pack monitors the import process and generates an alert for any failure that occurs during the import (such as connection problems to Active Directory).
Disk Space and Security Failures
The Management Pack monitors and generates alerts for following types of failures:
Insufficient disk space
Insufficient service account credentials
Insufficient credentials to propagate an index
SharePoint Portal Server 2003 Monitoring Solution Components and Topologies
This section describes and illustrates common deployment topologies of SharePoint Portal Server 2003 and demonstrates the physical relationship between MOM and SharePoint Portal Server 2003. It also notes additional Management Packs that can contribute to the SharePoint Portal Server 2003 monitoring solution.
SharePoint Portal Server 2003 Components and Sites
Understanding the individual components of SharePoint Portal Server 2003 and how these components are physically deployed is necessary to understanding the monitoring requirements of SharePoint Portal Server 2003.
Components
SharePoint Portal Server 2003 is made up of several components. Your performance, scalability, and load balancing goals for SharePoint Portal Server 2003 impact:
The total number of active components.
Whether individual components are installed on shared servers or dedicated servers.
The following summary of SharePoint Portal Server 2003 components indicates the potential number of each component and provides a brief description of each component’s role:
Front-end Web servers (1 to 10)
The front-end servers that provide user access to SharePoint Portal Server 2003 data.
Database servers (1 to 5)
The servers that host the SharePoint Portal Server 2003 databases.
Search servers (1 to 4)
The servers that are dedicated to processing user search queries.
Index management servers (1 to 4)
Servers that keep and maintain the full text index, the pointer to the property store, and other data that describes content across content sources, scopes, and servers.
Component for backward-compatible document libraries (1)
This optional component provides backward-compatibility with Microsoft SharePoint Portal Server 2001 document libraries. There is a specific processing rule group for this component in the SharePoint Portal Server 2003 Management Pack.
Sites
The site concept of a SharePoint Portal Server 2003 deployment has no influence on the management by MOM. The SharePoint Portal Server 2003 Management Pack has only two rules that are related to portal sites:
The portal site that is providing shared services does not exist (event 107).
Cannot synchronize the portal site state for backup (event 206).
Therefore, the servers on which these portal sites are hosted need to have the SharePoint Portal Server 2003 Management Pack deployed.
Additional Management Packs
To monitor a SharePoint Portal Server 2003 system, you need the SharePoint Portal Server 2003 Management Pack and all the Management Packs for the underlying and helping technologies. Therefore, a server that is running MOM and monitoring any kind of SharePoint Portal Server 2003 deployment needs the following Management Packs installed:
Microsoft Office SharePoint Portal Server 2003 (Web download from October 2003)
Microsoft Windows SharePoint Services (Web download from October 2003)
Windows Operating Systems (Web download from May 2003)
Internet Information Services (IIS) (Web download from May 2003)
Microsoft SQL Server™ 7.0 and SQL Server™ 2000 (Web download from November 2003)
Microsoft Windows Active Directory (Web Download from May 2003)
Microsoft Operations Manager 2000 (Web download from May 2003)
The following Management Packs are only necessary in deployment scenarios, where one or more services are either load balanced or clustered:
Network Load Balancing (Web download from May 2003)
Server Clusters (Web download from May 2003)
If a Microsoft Exchange server is used as a Simple Mail Transfer Protocol (SMTP) server, one of the following Management Packs is also required (depending on the Exchange version that is used):
Microsoft Exchange 2000 Server (Web download from May 2003)
Microsoft Exchange Server 2003 (Web download from September 2003)
For specific configurations and definitions in these Management Packs, see the related Management Pack guides.
SharePoint Portal Server 2003 Deployment Topologies
There are five common SharePoint Portal Server 2003 deployment topologies:
Single server
Small server farm
Medium server farm
Large server farm
Shared services deployment
It is important to understand how SharePoint Portal Server 2003 is deployed in your environment to ensure that:
All SharePoint Portal Server 2003 computers are being monitored by MOM.
Additional configuration of the MOM agent on SharePoint Portal Server 2003 servers is complete, if needed.
The appropriate additional Management Packs are deployed to assist with monitoring SharePoint Portal Server 2003 component servers.
Single Server
There are two possible configurations for hosting SharePoint Portal Server 2003 on a single server:
Single server without SQL Server
The first configuration (single server without SQL Server) is where one computer is running the Web component, index component, and search component and is running as the job server. This computer does not have Microsoft SQL Server 2000 installed. Microsoft Office SharePoint Portal Server 2003 Setup installs SQL Server Desktop Engine to store the databases. This computer can optionally run the components for backward-compatibility with Microsoft SharePoint Portal Server 2001 document libraries.
SQL Server Desktop Engine has limited throughput ability and supports databases with a maximum size of 2 GB. If a deployment requires significant scalability or must store more than 2 GB of documents, it is recommended that SQL Server be used instead.
Single server with SQL Server
The second configuration (single server with SQL Server) is where one computer is running the Web component, index component, and search component and is running as the job server. This computer has SQL Server 2000 installed. SQL Server is used to store the databases. This computer can optionally run the components for backward-compatibility with Microsoft SharePoint Portal Server 2001 document libraries. The components for backward-compatible document libraries might be installed on another server.
Using MOM to monitor the single server deployments
The single server topology is the simplest SharePoint Portal Server 2003 topology. The following illustration shows how MOM is used to monitor this SharePoint Portal Server 2003 topology.
.gif "Cc723720.sps0301(en-us,TechNet.10).gif")
Figure 1: Using MOM to monitor the SharePoint Portal Server 2003 single server topology
The following table lists the recommended Management Packs to deploy for the single server topology.
Table 1 Recommended Management Packs for the Single Server Topology
Server |
Management Pack |
|---|---|
Front-end Web server, index management server, search server with SQL Server (optional) |
Operating System Windows SharePoint Services SharePoint Portal Server 2003 IIS SQL Server |
Small Server Farm
Servers in the small server farm are configured as follows:
One computer is running the Web component, index component, and search component and is running as the job server. This computer can optionally run the components for backward-compatibility with Microsoft SharePoint Portal Server 2001 document libraries.
One or more computers is running Microsoft SQL Server 2000.
The following illustration shows the small server farm topology.
.gif "Cc723720.sps0302(en-us,TechNet.10).gif")
Figure 2: Using MOM to monitor the SharePoint Portal Server 2003 small farm topology
The following table lists the recommended Management Packs to deploy for the small server farm topology.
Table 2 Recommended Management Packs for the Small Server Farm Topology
Server |
Management Pack |
|---|---|
Front-end Web server, index management server, and search server |
Operating System SharePoint Portal Server 2003 Windows SharePoint Services IIS |
SQL Server |
Operating System SQL Server |
Medium Server Farm
Servers in the medium server farm are configured as follows:
One or more front-end Web servers with the search component enabled.
One index management and job server.
One or more computers running SQL Server 2000.
Optional. One computer running the components for backward-compatibility with Microsoft SharePoint Portal Server 2001 document libraries.
The following illustration shows the medium server farm topology.
.gif "Cc723720.sps0303(en-us,TechNet.10).gif")
Figure 3: Using MOM to monitor the SharePoint Portal Server 2003 medium farm topology
The following table lists the recommended Management Packs to deploy for the medium server farm topology.
Table 3 Recommended Management Packs for the Medium Server Farm Topology
Server |
Management Pack |
|---|---|
Front-end Web server and search server installed on a Network Load Balancing cluster |
Operating System SharePoint Portal Server 2003 Windows SharePoint Services IIS Network Load Balancing Cluster |
Index management server |
Operating System SharePoint Portal Server 2003 Windows SharePoint Services IIS |
SQL Server |
Operating System SQL Server |
Large Server Farm
Servers in the large server farm are configured as follows:
Two or more front-end Web servers.
Two or more search servers. It is recommended that you have no more than four search servers.
One or more index management servers, one of which is the job server. It is recommended that you have no more than four index management servers.
One or more computers running SQL Server 2000.
Optional. One computer running the components for backward-compatibility with Microsoft SharePoint Portal Server 2001 document libraries.
The following illustration shows the large server farm topology.
.gif "Cc723720.sps0304(en-us,TechNet.10).gif")
Figure 4: Using MOM to monitor the SharePoint Portal Server 2003 large farm topology
The following table lists the recommended Management Packs to deploy for the large server farm topology.
Table 4 Recommended Management Packs for the Large Server Farm Topology
Server |
Management Pack |
|---|---|
Front-end Web server installed on a Network Load Balancing cluster |
Operating System SharePoint Portal Server 2003 Windows SharePoint Services IIS Network Load Balancing |
Search server installed on a Network Load Balancing cluster |
Operating System SharePoint Portal Server 2003 Windows SharePoint Services IIS Network Load Balancing |
Index management server installed on a Network Load Balancing cluster |
Operating System SharePoint Portal Server 2003 Windows SharePoint Services IIS Network Load Balancing |
SQL Server installed on a Microsoft Cluster service cluster |
Operating System SQL Server Microsoft Cluster Service |
Load Balancing SharePoint Portal Server 2003 Servers Across DCAMs
The load balancing between two or more DCAMs is static (that is, the monitored servers have a primary DCAM defined that they always use if it is available). Therefore, you might consider the following points when deciding how to assign your SharePoint Portal Server 2003 servers to the DCAMs:
Split up the servers in almost equal numbers (for example, with two DCAMs assign half of your servers to DCAM1 and the other half to DCAM2).
Do not assign all servers of one type (for example, all front-end Web servers or all search servers) to one DCAM, unless you use status variables on a DCAM that needs information about all servers of one type.
Shared Services Deployments
Shared services are portal site services that are shared across server farms. The services are centrally managed from a single portal site for one or more portal sites on one or more server farms.
Using Shared Services
In a typical organization, there might be multiple deployments of Microsoft Office SharePoint Portal Server 2003. Each portal site can store user profiles, conduct searches and indexing, and provide alerts. It becomes expensive to deploy each portal site with all the services, because many of the services are common to all portal sites. To consolidate resources, you can factor out the common services of search, indexing, alerts, and user profile management by using shared services provided by a parent portal site. The child portal sites in the organization can then provide content that is based on division or application without using resources on the technical details of import and crawl. They use these services from the parent portal site.
Effects of Using Shared Services on the Monitoring
Using shared services has no impact on the monitoring of a SharePoint Portal Server 2003 implementation. The SharePoint Portal Server 2003 Management Pack must be deployed to any server that has a shared component installed. The MOM SP1 infrastructure and the SharePoint Portal Server 2003 Management Pack are not aware of the way in which the services of SharePoint Portal Server 2003 are allocated across several servers.
Setup and Configuration
The initial configuration of the SharePoint Portal Server 2003 Management Pack includes the following tasks:
Installing the MOM agent
Creating views for SharePoint Portal Server 2003 servers
Enabling IIS event logging
Configuring settings for slow WAN links or large branch office configurations
Considerations for Deploying the MOM Agent
Some additional configuration of the MOM agent might be necessary for monitoring SharePoint Portal Server 2003 servers. Review this section to determine whether any of these considerations apply to your SharePoint Portal Server 2003 environment.
Agent log file settings
The SharePoint Portal Server 2003 Management Pack uses the following event logs to monitor the SharePoint Portal Server 2003 system:
Windows system event log
Windows application event log
Other Management Packs that are deployed to monitor SharePoint Portal Server 2003 servers might use additional providers, such as Windows Management Instrumentation (WMI) or application log providers (such as IIS).
The best practice is to resize the event logs to at least 10 MB for optimal monitoring. For more information, see the “Configuring Agent Logs” section in Chapter 6 “Deploying Agents,” in the Microsoft Operations Manager 2000 SP1 Deployment Guide.
Security settings
The SharePoint Portal Server 2003 Management Point does not require specific security settings for the service account of the server running MOM (CAM service account) and the MOM agent service account. For more information about security requirements for the agent, see the “Security Requirements” section in Chapter 6 “Deploying Agents,” in the Microsoft Operations Manager 2000 SP1 Deployment Guide.
Clustering
Some SharePoint Portal Server 2003 components can be installed on clustered servers. By default, when Clustering is installed on servers running Windows 2000 Advanced Server or Windows 2000 Datacenter, events that are logged in the event log of one node in the cluster are also shown in the event log of the other nodes. To monitor these servers by using MOM, Event Log Replication must be disabled on each of the servers within the cluster. For more information, see the “Clustered Servers” section in Chapter 6 “Deploying Agents,” in the Microsoft Operations Manager 2000 SP1 Deployment Guide.
Corporate extranet hosting
If the SharePoint Portal Server 2003 deployment solution includes hosting an extranet site that is separated by a firewall, you must manually install the agent on SharePoint Portal Server 2003 servers that are on the other side of the firewall. For more information, see the “Firewalls” and “Installing Agents Manually” sections in Chapter 6 “Deploying Agents,” in the Microsoft Operations Manager 2000 SP1 Deployment Guide.
Creating Views for SharePoint Portal Server 2003 Servers
Because the SharePoint Portal Server 2003 Management Pack comes without any predefined views, it is recommended that you create some public views to help maintain the overview health of the SharePoint Portal Server 2003 servers. The example in the following section creates a view that shows all computers with components of SharePoint Portal Server 2003 installed.
To create a new view
Right-click Public Views or My Views, and then select New Folder.
Enter Microsoft Office SharePoint Portal Server 2003 as the new folder name.
To create a new view
Right-click the Microsoft Office SharePoint Portal Server 2003 folder, and then select New - Computer View.
Select Computers in a specified computer group, and then click Next.
In the View description box, click specified, enter a wildcard match for the computer groups that contain the SharePoint Portal Server 2003 components (Microsoft Office SharePoint Portal Server 2003*), and then click Next.
Enter a name and description for the view (such as All SharePoint Portal Server 2003), and then click Finish.
You can also create a view that shows all alerts from computers that run SharePoint Portal Server 2003 components.
To create a view that shows all alerts from computers that run SharePoint Portal Server 2003 components
Right-click the new Microsoft Office SharePoint Portal Server 2003 folder, and then select New - Alert View.
Select Alerts that satisfy specified criteria, and then click Next.
Select with specified resolution status and raised by computer in specified group.
Click specified, and then enter Microsoft Office SharePoint Portal Server 2003*.
Click Next, and then enter a name and description for the view (such as All Alerts from Microsoft Office SharePoint Portal Server 2003 Computers).
Click Finish.
You can create other private views (My Views) and public views (Public Views) by using the processes in the previous procedures. Examples of other helpful reports are:
Service Level Exceptions for Microsoft Office SharePoint Portal Server 2003 computers.
Performance View: ASP.NET requests per second.
For more information about how to create your own views, see Chapter 6 “MOM Administrator Console,” in the Microsoft Operations Manager 2000 User Guide.
Configuring IIS Event Logging
The SharePoint Portal Server 2003 Management Pack contains a processing rule group (External Events) that monitors the Internet Information Services (IIS) log for events that are relevant and critical to the SharePoint environment. Because IIS event logging is not enabled by default, an administrator must enable this feature on each IIS computer in the SharePoint environment.
To enable IIS event logging
At the command prompt, type cd \inetpub\adminscripts.
Type cscript adsutil.vbs set /w3svc/apppools/CentralAdminAppPool/LohEventOnRecycle 255.
Repeat steps 1 and 2 for each application pool that IIS has on the server (such as defaultAppPool) and even for Web sites that SharePoint Portal Server 2003 is not using.
This causes an event to be written to the event log for each application pool, if for any reason it is reset or restarted.
Configuring Settings for Slow WAN Links or Large Branch Office Deployments
There are several cases in which you might decide not to collect warnings, performance data, and miscellaneous non-critical events. These include:
Deployments across satellite links.
Large branch office deployments.
Deployments with very slow WAN links.
Deployments where alerts are forwarded to a global network operations center.
Situations where warnings and informational messages are not needed.
You can filter events that you do not want to be notified about. First, you must create a folder to hold the new filter rules and then add the filter rules. Next, you might decide to disable certain performance data to decrease traffic. After making such changes, you need to commit the changes to the system.
If you have not already created a folder to hold new rules, perform the following procedure.
To configure filters
In the MOM Administrator console, navigate to Rules, Processing Rule Groups.
Right-click Microsoft Office SharePoint Portal Server 2003, click New, and then click New Processing Rule Group.
In the Processing Rule Group Properties - General dialog box, type a name for the new folder in the Name box (for example, Custom SharePoint Portal Server 2003 Rules).
In the Processing Rule Group Properties - General dialog box, type a description for the new folder in the Description box (for example, Use this folder to hold custom SharePoint Portal Server 2003 rules).
In the Processing Rule Group Properties - General dialog box, make sure that the Enabled check box is selected.
Click Next, and then click Finish.
When a dialog box appears with the following message, click Yes: Would you like to deploy the processing rules in this newly created processing rule group to a group of computers?
Click Add.
Select Microsoft Office SharePoint Portal Server 2003 and Microsoft Office SharePoint Portal Server 2003 Document Library, and then click OK.
Expand the Microsoft Office SharePoint Portal Server 2003 rule group, and then expand Custom SharePoint Portal Server 2003 Rules.
Right-click Event Processing Rules, and then click Event Filter.
Verify that the provider name is Application, and then click Next.
Click Advanced.
In the Advanced Criteria dialog box, select the following:
In the Field box, select Event Type.
In the Condition box, select is less than.
In the Value box, select Error.
Click Add to list.
Click Close, and then click Next.
In the Filter Processing Rule Properties - Schedule dialog box, click Always process data, and then click Next.
In the Filter Processing Rule Properties - Filter dialog box, select Do not evaluate further processing rules, nor insert matching events into the database (Pre-Filter), and then click Next.
In the Company Knowledge Base dialog box, click Next.
In the Filter Processing Rule Properties - General dialog box, type a name for the filter in the Name box (for example, Filter non-error Application events).
In the MOM Administrator console, right-click Rules, and then click Commit. These changes take approximately 10 minutes to take effect.
To disable performance data
In the MOM Administrator console, navigate to Rules, Processing Rule Groups, Microsoft Office SharePoint Portal Server 2003.
Click Performance Processing Rules.
For each Measuring type rule (in the right pane), perform the following steps to disable the rule.
Double-click the rule.
Make sure that the Enabled check box is cleared, and then click OK.
In the MOM Administrator console, navigate to Rules, Processing Rule Groups.
Right-click Rules, and then click Commit. This process takes about 10 minutes.
Operations Tasks
You must review and prioritize all alerts on a daily basis. In addition, you must perform other tasks on a regular basis, depending on your environment. Many important problems do not cause alerts, but they still require periodic attention. You can perform the daily, weekly, and monthly tasks as specified in the tables in this section, but you must adjust the frequency of these tasks to meet the needs of your particular environment.
Important: Because Microsoft Office SharePoint Portal Server 2003 relies on a number of other servers and technologies, it is highly recommended that you familiarize yourself with tasks that need to be performed for the following Management Packs:
Windows 2000 and Windows Server™ 2003 Base Operating System
SQL Server
Internet Information Services
Microsoft Operations Manager 2000
Daily Tasks
On a daily basis, perform the following tasks:
Review all open alerts.
Verify that all SharePoint Portal Server 2003 servers are communicating with the MOM Administrator console.
Review warnings (optional).
Reviewing All Open Alerts
Review all new alerts in the following order of priority:
Critical errors
SharePoint Portal Server 2003 Services alerts (such as Service Unavailable and Service stopped)
Warnings (optional)
Informational messages (optional)
It is expected that not all problems can be repaired in one day or less. Commonly, parts must be ordered or computers must be scheduled for restart. It is important that you follow up on these open alerts to ensure that they are addressed in a timely manner.
To review open alerts
In the MOM Administrator console, navigate to Monitor, All Open Alerts.
Review all alerts that are older than 24 hours to ensure that they are addressed in a timely manner.
Verify That All SharePoint Portal Server 2003 Servers Are Communicating with the MOM Administrator Console
Communication failure between the SharePoint Portal Server 2003 servers and the monitoring infrastructure prevents you from receiving alerts so that you can examine and resolve them.
To verify that domain controllers are communicating with the MOM Administrator console
In the MOM Administrator console, navigate to Monitor, All Agents.
In the right pane, click the Last Contact column heading. This sorts all computers based on the last contact time. If the last contact time is greater than five minutes, determine why the computer is not communicating with MOM.
Reviewing Warnings
It is recommended, but not required, that you review warnings because they indicate pending failures. Warnings are not displayed by default.
To review warnings
In the MOM Administrator console, navigate to Monitor, Public Views, Microsoft Office SharePoint Portal Server 2003.
Click All New SPSAlerts.
To sort by severity, click the Severity column heading.
Review all warnings.
Weekly Tasks
There are no weekly tasks specific to the SharePoint Portal Server 2003 Management Pack. However, it is recommended that you review the following availability reports for SharePoint Portal Server 2003 services and computers:
Windows NT®/2000 Operations: Service Availability by Computer Group
Windows NT/2000 Operations: Service Availability by Service
Windows NT/2000 Operations: Service Availability by Server
Windows NT/2000 Operations: Computer Availability by Computer Group
Windows NT/2000 Operations: System Dirty Shutdown Events
Monthly Tasks
In addition to the tasks that you perform daily, review the following reports on a monthly basis:
Microsoft Operations Manager Report: Most Common Alerts by Processing Rule Group
Microsoft Operations Manager Report: Most Common Events
These reports help identify the areas where your system needs the most attention. They list the alerts and events that happen most often in your environment. By identifying the origin of these problems (or simply filtering the events and disabling the rules), you will:
Decrease the number of notifications to the operators and administrators.
Decrease the number of false alarms.
Increase the stability and availability of the SharePoint Portal Server 2003 environment.
Increase the visibility of alerts that need attention.
Review other reports as appropriate for your environment.
As Needed Tasks
As needed tasks usually come with a high severity alert (such as Critical Error or Service Unavailable) and therefore usually need immediate attention. It is absolutely necessary to have a contingency plan in place for such events.
Reference
Processing Rules That Generate Critical Error and Service Unavailable Alerts
This section lists the processing rule groups and event processing rules in the SharePoint Portal Server 2003 Management Pack that generate critical error or service unavailable alerts. These rules are found in the MOM Administrator console at the following location:
- Processing Rule Groups\Microsoft Office SharePoint Portal Server 2003
Processing Rule Group: Microsoft Office SharePoint Portal Server 2003
The Microsoft Office SharePoint Portal Server 2003 processing rule group contains processing rules for errors related to Microsoft Office SharePoint Portal Server 2003.
Table 5 Processing Rules in the Microsoft Office SharePoint Portal Server 2003 Processing Rule Group
Rule |
Default Alert Severity |
|---|---|
Search service stopped |
Service Unavailable |
Administration service stopped |
Service Unavailable |
Alert notification service stopped |
Critical Error |
Processing Rule Group: Administration
The Administration processing rule group contains processing rules for errors related to the administration of SharePoint Portal Server 2003. There are no critical error alerts generated from this processing rule group.
Processing Rule Group: Alert Notification Service
The Alert Notification Service processing rule group contains processing rules for errors related to the Alert Notification Service component of SharePoint Portal Server 2003. There are no critical error alerts generated from this processing rule group.
Processing Rule Group: Backward-compatible Document Library Server
The Backward-compatible Document Library Server processing rule group contains processing rules for errors related to the Backward-compatible Document Library Server component of SharePoint Portal Server 2003. There are no critical error alerts generated from this processing rule group.
Processing Rule Group: Data Backup/Restore
The Data Backup/Restore processing rule group contains processing rules for errors related to the Data Backup/Restore component of SharePoint Portal Server 2003.
Table 6 Processing Rules in the Data Backup/Restore Processing Rule Group
Rule |
Default Alert Severity |
|---|---|
Error preparing for SQL Server backup |
Critical Error |
Content index restore failed |
Critical Error |
Content index backup failed |
Critical Error |
SQL Server backup failed |
Critical Error |
Cannot acquire backup lock on index server(s) |
Critical Error |
SQL Server restore failed |
Critical Error |
Error preparing for search backup |
Critical Error |
Error preparing for backward-compatible document library backup |
Critical Error |
Backward-compatible document library backup failed |
Critical Error |
Backward-compatible document library restore failed |
Critical Error |
Processing Rule Group: People and Audiences
The People and Audiences processing rule group contains processing rules for errors related to the People and Audiences component of SharePoint Portal Server 2003. There are no critical error alerts generated from this processing rule group.
Processing Rule Group: Search Service
The Search Service processing rule group contains processing rules for errors related to the Search Service component of SharePoint Portal Server 2003.
Table 7 Processing Rules in the Search Service Processing Rule Group
Rule |
Default Alert Severity |
|---|---|
Disk is full |
Critical Error |
Critical Index Error |
Critical Error |
Out of memory |
Critical Error |
Processing Rule Group: Services and Licensing
The Services and Licensing processing rule group contains processing rules for errors related to the Services and Licensing component of SharePoint Portal Server 2003.
Table 8 Processing Rules in the Services and Licensing Processing Rule Group
Rule |
Default Alert Severity |
|---|---|
Evaluation license has expired |
Critical Error |
Alert notification service stopped |
Critical Error |
Search service stopped |
Service Unavailable |
Administration service stopped |
Service Unavailable |
Single Sign-on service stopped |
Service Unavailable |
Processing Rule Group: Single Sign-on
The Single Sign-on processing rule group contains processing rules for errors related to the Single Sign-on component of SharePoint Portal Server 2003.
Table 9 Processing Rules in the Single Sign-on Processing Rule Group
Rule |
Default Alert Severity |
|---|---|
Error retrieving credentials |
Critical Error |
Internal SSO service error |
Critical Error |
SSO audit failure |
Critical Error |
RPC service failed to start |
Critical Error |
Error retrieving cryptographic sign |
Critical Error |
Service failed to start |
Critical Error |
Failed to load settings |
Critical Error |
Reports
There are no reports defined in the SharePoint Portal Server 2003 Management Pack.
Default Views
There are two default views defined in the SharePoint Portal Server 2003 Management Pack:
CPU usage
ASP.NET requests per second
Computer Groups
The SharePoint Portal Server 2003 Management Pack defines two computer groups:
Microsoft Office SharePoint Portal Server 2003
Microsoft Office SharePoint Portal Server 2003 Document Library
Scripts
There are no scripts defined in the SharePoint Portal Server 2003 Management Pack.
However, customizing scripts that are available through other Management Packs or including new scripts for certain monitoring scenarios might be useful and add some insight and proactive management to your SharePoint Portal Server 2003 monitoring environment. Because the scripting abilities of the MOM environment are very powerful and flexible, it is highly recommended that you use this feature to extend and deepen your monitoring.
The following examples show what is possible:
Using the URL ping script that comes with the IIS Management Pack, you can set up timed event rules that ping either the NetBIOS name or the IP addresses of all computers in your farms. This allows MOM to monitor the home page of each portal site and ensure that they are responding. This script could be extended to create events that are based on certain situations (such as response time issues and response issues), which could then be captured and reacted to through MOM event processing rules.
Create a script that posts a search request to each portal site and attempts to parse the response that is received to ensure that one or more results are returned for a common keyword. This would help monitor the quality of the search indexes and the response time for a search request. Again, this script could create events that a MOM event processing rule can respond to.
Notification Groups
The SharePoint Portal Server 2003 Management Pack installs one new notification group:
- SharePoint Portal Server Administrators
Acknowledgements
Program Manager: Brad Stevenson
Writer: Markus Klein
Technical Reviewers: Brenda Carter, Emily Schroeder, Erik Heino, Jörgen Bergström
Editors: Scott Kendall, Anne Reese, Crystal Thomas