Overview - Rules - Public MPWiki

Name	Enabled	Target Class	Description
.Net CLR Data-Sql Client Connections	0	MOSS 2007 Server	This rule uses the SqlClient: Current # pooled and nonpooled connections counter to count the current number of active SQL connections, pooled or not.
.Net CLR Data-Sql client Failed connections	0	MOSS 2007 Server	This rule uses the SqlClient: Total # failed connects counter to count the total number of connection open attempts that have failed for any reason.
.NET CLR Memory - % Time in GC	onEssentialMonitoring	MOSS 2007 Server	This rule uses the % Time in GC counter to measure the percentage of elapsed time that was spent in performing a garbage collection (GC) since the last GC cycle. This counter is usually an indicator of the work done by the Garbage Collector on behalf of the application to collect and compact memory. This counter is updated only at the end of every garbage collection, and the counter value reflects the last observed value; this is not an average.
.NET CLR Memory - Bytes	onEssentialMonitoring	MOSS 2007 Server	This rule uses the # Bytes in all Heaps counter to sum the following four other counters: Gen 0 Heap Size; Gen 1 Heap Size; Gen 2 Heap Size, and Large Object Heap Size. This counter indicates the current memory allocated in bytes on the Garbage Collector Heaps.
.NET CLR Memory - Large Objects	onEssentialMonitoring	MOSS 2007 Server	This rule uses the Large Object Heap Size counter to display the current size of the Large Object Heap in bytes. Objects greater than 20 KB are treated as large objects by the Garbage Collector and are directly allocated in a special heap; they are not promoted through the generations. This counter is updated at the end of a garbage collection; it is not updated on every allocation.
.NET CLR Object - Finalization Survivors	onEssentialMonitoring	MOSS 2007 Server	This rule uses the Finalization Survivors counter to display the number of garbage collected objects that survive a collection because they are waiting to be finalized. If these objects hold references to other objects, then those objects also survive but are not counted by this counter. The Promoted Finalization-Memory from Gen 0 and Promoted Finalization-Memory from Gen 1 counters represent all the memory that survived due to finalization. This counter is not a cumulative counter; it is updated at the end of every garbage collection with the count of the survivors during that particular garbage collection only. This counter was designed to indicate the extra overhead that the application might incur because of finalization.
A Content Query Web Part failed to return content	onEssentialMonitoring	MOSS Application Installation	A Content Query Web Part on your Web site is configured to run a specific query against the content of your Web site. This alert indicates that this Web Part failed to return content for the query for which it has been configured.
A form template’s business logic caused an OutOfMemory exception	0	MOSS Application Installation	An OutOfMemory exception has been generated from the form template's business logic.
A runtime exception occurred in the Business Data Catalog database adapter	onEssentialMonitoring	MOSS Application Installation	This alert indicates that the query or stored procedure that is associated with a method in the Business Data Catalog application definition file could not be run.
A runtime exception occurred in the Business Data Catalog Web service adapter	onEssentialMonitoring	MOSS Application Installation	This alert indicates that Microsoft Office SharePoint Server 2007 could either not run a method in the Web service that is specified in the Business Data Catalog application definition file, or that the method was run but an error was returned by the Web service that is specified in the BDC application definition file.
A site copy operation has failed, leaving the site structure in an unusual state	onEssentialMonitoring	MOSS Application Installation	This alert occurs when an administrator uses the Site Content and Structure page to copy a subsite or a group of sites, and the copy of the site or sites are left in an unusual state after the site copy operation fails.
A site deletion operation has failed, leaving the site structure in an unusual state	onEssentialMonitoring	MOSS Application Installation	This alert occurs when an administrator uses the Site Content and Structure page to delete a subsite or a group of sites, and the site or sites are left in an unusual state after the site deletion operation fails.
A site move operation has failed, leaving the site structure in an unusual state	onEssentialMonitoring	MOSS Application Installation	This alert occurs when an administrator uses the Site Content and Structure page on a SharePoint site to move a subsite or a group of sites, and the site or sites are left in an unintended state after the site move operation fails.
Administration site for the Shared Service Provider is missing	onEssentialMonitoring	MOSS Application Installation	This alert indicates that the administration site of the Shared Services Provider (SSP) is not available.
ASP Compiled Templates Cached	onEssentialMonitoring	MOSS 2007 Server	This rule uses the In Memory Templates Cached counter to count the number of compiled templates cached in memory.
ASP Current Templates Cache	onEssentialMonitoring	MOSS 2007 Server	This rule uses the Templates Cached counter to count the number of templates currently cached.
ASP.NET Applications	onEssentialMonitoring	MOSS 2007 Server	This rule uses the Requests/Sec counter to count the number of requests executed per second.
ASP.NET Worker Process Restart	onEssentialMonitoring	MOSS 2007 Server	This rule uses the Worker Process Restarts counter to measure the number of times a worker process has restarted on the machine.
Audience Compilation failed	onEssentialMonitoring	MOSS Application Installation	A failure occurred while compiling an audience rule.
Availabilty of Memory in Bytes	onEssentialMonitoring	MOSS 2007 Server	This rule uses the Available MBytes counter to measure the amount of physical memory in MB immediately available for allocation to a process or for system use. This amount is equal to the sum of memory assigned to the standby (cached), free, and zero page lists. For a full explanation of memory management, refer to MSDN or the System Performance and Troubleshooting Guide chapter in the Microsoft® Windows Server™ 2003 Resource Kit.
Business Data Catalog Web Service Adapter transport error	onEssentialMonitoring	MOSS Application Installation	This alert indicates that a transport error occurred while Microsoft Office SharePoint Server 2007 was trying to connect to the Web service that is specified in the Business Data Catalog application definition file.
Cache Bytes	onEssentialMonitoring	MOSS 2007 Server	This rule uses the counter Cache Bytes to show the sum of the Memory\System Cache Resident Bytes, Memory\System Driver Resident Bytes, Memory\System Code Resident Bytes, and Memory\Pool Paged Resident Bytes counters. This counter displays the last observed value only; it is not an average.
Cache Faults Per Sec	onEssentialMonitoring	MOSS 2007 Server	This rule uses the Cache Faults/sec counter to measure the rate at which faults occur when a page sought in the file system cache is not found and must be retrieved from elsewhere in memory (a soft fault) or from disk (a hard fault). The file system cache is an area of physical memory that stores recently used pages of data for applications. Cache activity is a reliable indicator of most application I/O operations. This counter shows the number of faults, without regard for the number of pages faulted in each operation.
Cannot initialize disk-based cache because the specified location is inaccessable	onEssentialMonitoring	MOSS Application Installation	While the content deployment job was running on the source server, the destination server could not be reached and the deployment package was not transferred to the production server.
Committed Memory in Use	onEssentialMonitoring	MOSS 2007 Server	This rule uses the % Committed Bytes In Use counter to measure the ratio of the Memory\Committed Bytes counter to the Memory\Commit Limit counter. Committed memory is the physical memory in use for which space has been reserved in the paging file should the contents of the memory need to be written to disk. The commit limit is determined by the size of the paging file. If the paging file is enlarged, the commit limit increases, and the ratio is reduced. This counter displays the current percentage value only; it is not an average.
Content Database Synchronization failed	onEssentialMonitoring	MOSS Application Installation	Profile and membership synchronization was abandoned for this content database. The profile synchronization timer job will attempt to synchronize this content database again the next time it is run.
Content deployment job could not contact the destination server	onEssentialMonitoring	MOSS Application Installation	This error indicates that the disk-based cache cannot be initialized because it is inaccessible. The disk-based cache provides faster rendering of items stored in document, picture, and form libraries. None of these items are cached until the disk-based cache is initialized.
Context Switches Per Sec	onEssentialMonitoring	MOSS 2007 Server	This rule shows the combined rate, in incidents per second, at which all processors on the computer were switched from one thread to another. It is the sum of the values of each thread divided by the counter Context Switches/sec for each thread running on all processors on the computer, and is measured in numbers of switches. Context switches occur when a running thread voluntarily relinquishes the processor, or is preempted by a higher priority, ready thread. This counter measures how often NT Server switches between threads.
Could not parse the regular expression for disk-based cache	onEssentialMonitoring	MOSS Application Installation	This error indicates that the regular expression used to specify the type of items that are cached in the disk-based cache could not be parsed. The disk-based cache provides faster rendering of items stored in document, picture, and form libraries.
CPU Total Processor Time	onEssentialMonitoring	MOSS 2007 Server	This rule uses the % Processor Time counter to measure the percentage of elapsed time that the processor spends to execute a non-Idle thread. It is calculated by measuring the duration that the idle thread is active in the sample interval, and subtracting that time from the interval duration. (Each processor has an idle thread that consumes cycles when no other threads are ready to run.) This counter is the primary indicator of processor activity, and displays the average percentage of busy time observed during the sample interval. It is calculated by monitoring the time that the service is inactive and subtracting that value from 100%.
Crawl failed because no contact e-mail is set	onEssentialMonitoring	MOSS Application Installation	When you crawl sites, you use resources on those sites that can potentially cause a performance problem for the sites being crawled. Because of this, an e-mail address that external site administrators can use to contact you if problems arise when their site is being crawled is required. The Office SharePoint Servers Search (OSearch) service will not crawl a site unless a contact e-mail address is specified.
Crawler cannot read from registry	onEssentialMonitoring	MOSS Application Installation	The crawler component of search uses the Office SharePoint Servers Search (OSearch) service to read its settings from the Windows registry of the index server. This alert indicates that the crawler was unable to read from the registry in order to load configuration information needed by the OSearch service.
Crawler exception	onEssentialMonitoring	MOSS Application Installation	The crawler component of search uses the Office SharePoint Servers Search (OSearch) service to read its settings from the Windows registry of the index server. This alert indicates that an unexpected error has occurred in the crawler.
Database out of space	onEssentialMonitoring	MOSS Application Installation	This alert indicates that the Office SharePoint Servers Search (OSearch) service attempted to update a database but the database was full.
Disk Block Read Size	onEssentialMonitoring	MOSS 2007 Server	This rule uses the Avg. Disk Bytes/Read counter to measure the average number of bytes transferred from the disk during read operations.
Disk Block Write Size	onEssentialMonitoring	MOSS 2007 Server	This rules use the Avg. Disk Bytes/Write counter to measure the average number of bytes transferred to the disk during write operations.
Disk Request Read Count	onEssentialMonitoring	MOSS 2007 Server	This rule uses the Disk Reads/sec counter to measure the rate of read operations on the disk.
Disk Request Read Size	onEssentialMonitoring	MOSS 2007 Server	This rule uses the Disk Read Bytes/sec counter to measure the rate at which bytes are transferred from the disk during read operations.
Disk Request Write Count	onEssentialMonitoring	MOSS 2007 Server	This rule uses the Disk Writes/sec counter to measure the rate of write operations on the disk.
Disk Request Write Size	onEssentialMonitoring	MOSS 2007 Server	This rule sues the Disk Write Bytes/sec counter to measure the rate at which bytes are transferred to the disk during write operations.
Disk Usage - Disk Time	onEssentialMonitoring	MOSS 2007 Server	This rule uses the % Disk Time counter to calculate the percentage of elapsed time that the selected disk drive was busy servicing read or write requests.
Document converter failed to create an HTML page	onEssentialMonitoring	MOSS Application Installation	The document converter ran but did not create an HTML page.
Document converter was unable to send confirmation email	onEssentialMonitoring	MOSS Application Installation	A document converter was unable to send a confirmation email message.
Enabling features failed on some sites	onEssentialMonitoring	MOSS Application Installation	The timer job used to enable features on existing sites succeeded, but some features could not be enabled on some sites.
Enabling features on existing sites failed	onEssentialMonitoring	MOSS Application Installation	The timer job that attempted to enable Features on existing sites failed.
Encountered errors while indexing anchor text	onEssentialMonitoring	MOSS Application Installation	While crawling content, the Office SharePoint Server Search (OSearch) service discovers the anchor text for each page that is crawled and stores this information in the computer running SQL Server. The OSearch service then uses this anchor text as part of the ranking calculation that is used to determine how close to the top of search results pages particular pages will appear.
Error adding enterprise application definition	onEssentialMonitoring	MOSS Application Installation	An error occurred while using Microsoft Single Sign-On (SSOSrv) and enterprise application definitions. This error indicates that the inputs to the Single Sign-On object model are invalid.
Error backing up registry to Shared Services Provider database	onEssentialMonitoring	MOSS Application Installation	In a search-enabled server farm, configuration settings for the index server are stored in the Windows registry on that server. The Office SharePoint Server Search (OSearch) service periodically backs up the registry keys on the index server that are used by the OSearch service to the Shared Services Provider (SSP) database.
Error communicating with Excel Calculation Services	onEssentialMonitoring	MOSS Application Installation	This error occurs when the front-end Web server attempts to establish a connection to Excel Calculation Services, but a communication error occurred.
Error deleting enterprise application definition	onEssentialMonitoring	MOSS Application Installation	An error occurred while using Microsoft Single Sign-On (SSOSrv) and enterprise application definitions. The requested application does not exist.
Error retreiving credentials	onEssentialMonitoring	MOSS Application Installation	An error occurred while attempting to retrieve credentials while using Microsoft Single Sign-On (SSOSrv) with an enterprise application definition. The credentials for a user cannot be retrieved.
Error retreiving cryptographic sign	onEssentialMonitoring	MOSS Application Installation	An error occurred while using Microsoft Single Sign-On (SSOSrv) and the cryptographic sign. An unauthorized user may have attempted to access the Single Sign-On database.
Excel Calculation Services is not running locally	onEssentialMonitoring	MOSS Application Installation	Excel Calculation Services provides a set of load-balancing schemes from which the administrator can choose. When the load-balancing scheme is configured as Local, the Excel Web components running on the front-end Web server always send requests to Excel Calculation Services running on the local computer.
Excel Calculation Services not available	onEssentialMonitoring	MOSS Application Installation	In order for a front-end Web server to use Excel Calculation Services, this service must be running on either the front-end Web server or on another server in the farm. This alert indicates that Excel Calculation Services is not running on any computer in the farm.
Exception occurred during Business Data Catalog Web service proxy generation	onEssentialMonitoring	MOSS Application Installation	This alert indicates that Microsoft Office SharePoint Server 2007 could not generate a Web Services Description Language (WSDL) proxy for the Web service that is specified in the Business Data Catalog application definition file.
Exception occurred in the Business Data Catalog database adapter connection	onEssentialMonitoring	MOSS Application Installation	This alert indicates that the Business Data Catalog database adapter used by Microsoft Office SharePoint Server 2007 cannot connect to the backend database that is specified in the BDC application file.
Exception occurred while processing an InfoPath form template request	onEssentialMonitoring	MOSS Application Installation	An error occurred while InfoPath Forms Services was processing a form template request.
Failed to connect to parent server farm	onEssentialMonitoring	MOSS Application Installation	This alert indicates that a server farm could not connect to the Shared Services Provider (SSP) of its parent server farm.
Failed to load index	onEssentialMonitoring	MOSS Application Installation	This alert indicates that the Office SharePoint Server Search (OSearch) service could not load the index. This can occur on either a query server or an index server.
Failed to load protocol handler	onEssentialMonitoring	MOSS Application Installation	Office SharePoint Server 2007 uses protocol handlers to access the content that you want to crawl. This alert indicates that the protocol handler cannot be loaded. This means that documents that require the protocol handler cannot be crawled.
Failed to load Single Sign-On configuration settings	onEssentialMonitoring	MOSS Application Installation	The Microsoft Single Sign-On (SSOSrv) service failed to load the configuration settings from the Single Sign-On database. The Single Sign-On database may be unavailable, or the Single Sign-On administrator account may have changed.
Failed to load word breaker	onEssentialMonitoring	MOSS Application Installation	A word breaker is a component that determines where the word boundaries are in the stream of characters in the query or document being crawled. A separate word breaker is required for each language installed on the farm. For example, the English and German languages each require a separate word breaker.
Failure to commit to SQL	onEssentialMonitoring	MOSS Application Installation	In a search-enabled server farm, the index server periodically writes to the search database on the computer running SQL Server. This alert indicates that an error occurred in the Office SharePoint Servers Search (OSearch) service while attempting to commit a write operation to the computer that is running SQL Server.
Idle Time of Logical Disk	onEssentialMonitoring	MOSS 2007 Server	This rule uses the counter % Idle Time to report the percentage of time during the sample interval that the logical disk was idle.
IIS Start Command	onEssentialMonitoring	MOSS Application Installation	This rule alerts the user when IIS is started.
IIS Stop Command	onEssentialMonitoring	MOSS Application Installation	This rule alerts the user when IIS is stopped.
Index is corrupt	onEssentialMonitoring	MOSS Application Installation	The Office SharePoint Server Search (OSearch) service has detected that the content index is corrupted. This can occur on either an index server or a query server. When this error occurs on an index server, the OSearch service automatically attempts to reset and start a full update of the content index.
InfoPath form templates have conflicting business logic assembly identities	onEssentialMonitoring	MOSS Application Installation	A form template running on InfoPath Forms Services can contain managed code. When a form template that has managed code is deployed to InfoPath Forms Services, the form template contains a business logic assembly. Each business logic assembly running on InfoPath Forms Services must have a strong name. When conflicting assemblies are identified, an entry is logged in the Windows NT Event log.
InfoPath Forms Services business logic attempted to store a nonserializable object	onEssentialMonitoring	MOSS Application Installation	In InfoPath Forms Services, the FormState property bag provides a way to maintain business logic state across multiple server postbacks. For example, within a particular method in business logic, local variables can be persisted in the form state bag for multiple postbacks. All objects stored in the property bag must be serializable.
InfoPath Forms Services business logic exceeded the maximum limit of operations	onEssentialMonitoring	MOSS Application Installation	This alert indicates that an error occurred in the business logic of a form.
InfoPath Forms Services business logic exception occurred while loading a form template	onEssentialMonitoring	MOSS Application Installation	The form template used by InfoPath Forms Services cannot be loaded due to a business logic exception. The logged event identifies the form template.
InfoPath Forms Services calculations exceeded the maximum limit	onEssentialMonitoring	MOSS Application Installation	This alert indicates that an error occurred when a form hosted by InfoPath Forms Services was running calculations.
InfoPath Forms Services cannot find or load ifsFileNames.xml	onEssentialMonitoring	MOSS Application Installation	InfoPath Forms Services includes a file named ifsFileNames.xml that contains pointers to downloadable files, such as scripts and images for forms.
InfoPath Forms Services event counter mismatch	onEssentialMonitoring	MOSS Application Installation	This alert indicates that the current version of session state does not match the version that the server running InfoPath Forms Services was expecting.
InfoPath Forms Services failed to load a form template	onEssentialMonitoring	MOSS Application Installation	This alert indicates that InfoPath Forms Services cannot load a particular form template.
InfoPath Forms Services found an unexpected session state version	onEssentialMonitoring	MOSS Application Installation	InfoPath Forms Services has found a session state entry from a version of InfoPath Forms Services that is a later version than the one that is currently running.
InfoPath Forms Services postback failure	onEssentialMonitoring	MOSS Application Installation	This alert indicates that an error occurred while a form request was being processed by InfoPath Forms Services.
InfoPath Forms Services rules exceeded the maximum limit	onEssentialMonitoring	MOSS Application Installation	This alert indicates that an error occurred in one of the form template’s rules. Specifically, the number of rule actions for a single update in the data has exceeded the maximum limit.
InfoPath Forms Services user has exceeded the maximum number of actions per postback	onEssentialMonitoring	MOSS Application Installation	This alert indicates that a user has exceeded the threshold set for the number of form actions allowed per postback. When this condition occurs, InfoPath Forms Services terminates the user session to protect the server.
InfoPath Forms Services user has exceeded the maximum session state size	onEssentialMonitoring	MOSS Application Installation	This alert indicates that a user has exceeded the threshold set in InfoPath Forms Services for the maximum amount of data that can be stored in a form session state. When this condition occurs, InfoPath Forms Services terminates the user session to protect the server and logs an error in the Windows NT Event log.
InfoPath Forms Services was running business logic when ASP.NET request timed out	onEssentialMonitoring	MOSS Application Installation	This alert indicates that the value set in the ASP.NET request timeout was exceeded when an InfoPath Forms Services form template was running business logic.
Instance of search could not be initialized	onEssentialMonitoring	MOSS Application Installation	As instances of the Windows SharePoint Services Search (SPSearch) and Office SharePoint Servers Search (OSearch) services start up, they must read configuration information from the Windows registry. The registry keys that store configuration information for search are backed up to the SQL Server database. If these registry keys are not present in the registry when the OSearch and SPSearch services start up, they attempt to read this configuration information from the computer that is running SQL Server.
Insufficient disk space	onEssentialMonitoring	MOSS Application Installation	When crawling one or more content sources, the Office SharePoint Servers Search (OSearch) service updates the index, which is stored in the file system of the index server. This index is then propagated to all query servers. If a hard disk that contains this index has inadequate free space to update the index, this alert occurs and the content sources update is paused.
Internal plug-in error	onEssentialMonitoring	MOSS Application Installation	A plug-in is a component of the search indexer that is used to process content and properties from crawled items. When this error occurs, a Dr. Watson report is usually created and an entry containing the call stack of the exception is written to the Windows NT Event log.
Internal Single Sign-On service error	onEssentialMonitoring	MOSS Application Installation	An unexpected error occurred while using Microsoft Single Sign-On (SSOSrv).
Invalid File Access method configured	onEssentialMonitoring	MOSS Application Installation	Excel Calculation Services provides a setting for configuring the file access method that is used for UNC and HTTP trusted locations. If the file access method is configured as impersonation, Excel Calculation Services must be able to delegate the end user credential for accessing files.
Invalid SessionID in the request	onEssentialMonitoring	MOSS Application Installation	Invalid SessionID in the request
IView runtime error	onEssentialMonitoring	MOSS Application Installation	This alert indicates that the IView Web Part (used for SAP connectivity) could not communicate with the SAP server.
Locale ID has changed	onEssentialMonitoring	MOSS Application Installation	Microsoft Windows SharePoint Services can be customized to use specific regional settings that apply to the users of your site. One of these settings, Locale ID, controls the numbering, sorting, calendar, and time formatting for the Web site.
Master merge error	onEssentialMonitoring	MOSS Application Installation	A master merge is the process of merging a group of indexes into a single index. This process occurs on index servers when you crawl content and on query servers when the index is propagated from the index server. If this alert occurs repeatedly, the Office SharePoint Server Search (OSearch) service will eventually be unable to index new documents.
Maximum memory configured for Excel Calculation Services has been exceeded	onEssentialMonitoring	MOSS Application Installation	Excel Calculation Services provides a configurable setting for Maximum Private Bytes that is used by the application pool in which Excel Calculation Services runs. When the number of private bytes used by the application pool process exceeds the value of the Maximum Private Bytes setting, Excel Calculation Services stops processing requests for new sessions and only processes navigation and find requests on existing sessions.
Membership Import failed	onEssentialMonitoring	MOSS Application Installation	An error occurred while attempting to import membership information from the directory service.
Memory - Pages Per Second	onEssentialMonitoring	MOSS 2007 Server	This rule uses the counter Pages/sec to measure the rate at which pages are read from or written to disk to resolve hard page faults. The Pages/sec counter is a primary indicator of the kinds of faults that cause system-wide delays. It is the sum of the Pages Input/sec and Pages Output/sec counters. It is counted in numbers of pages, so it can be compared to other counts of pages, such as Memory\Page Faults/sec, without conversion. It includes pages retrieved to satisfy faults in the file system cache (usually requested by applications) non-cached mapped memory files.
Memory Allocation Failed	onEssentialMonitoring	MOSS Application Installation	This error indicates that Excel Calculation Services attempted to allocate memory, but the memory allocation failed.
Microsoft Single Sign-On service failed to start	onEssentialMonitoring	MOSS Application Installation	The Microsoft Single Sign-On (SSOSrv) service did not start.
Microsoft Single Sign-On service failed to stop	onEssentialMonitoring	MOSS Application Installation	An error occurred while using Microsoft Single Sign-On (SSOSrv). This alert indicates that an administrator attempted to stop the SSOSrv service, but the service failed to stop.
My Site Creation failure	onEssentialMonitoring	MOSS Application Installation	A My Site could not be created for the user specified in the exception message.
Network Interface - Bytes Sent	onEssentialMonitoring	MOSS 2007 Server	This rule uses the Bytes Sent/sec counter to measure the rate at which bytes are sent over each network adapter. This includes framing characters. The Bytes Sent/sec counter is a subset of the Network Interface\Bytes Total/sec counter.
Network Interface - Bytes Received	onEssentialMonitoring	MOSS 2007 Server	This rule uses the Bytes Received/sec counter to measure the rate at which bytes are received over each network adapter. This includes framing characters. The Bytes Received/sec counter is a subset of the Network Interface\Bytes Total/sec counter.
Network Interface - Total Bytes	onEssentialMonitoring	MOSS 2007 Server	This rule uses the Bytes Total/sec counter to measure the rate at which bytes are sent and received over each network adapter. This includes framing characters. The Bytes Received/sec counter is the sum of the Network Interface\Bytes Received/sec counter and the Network Interface\Bytes Sent/sec counter.
Network Queue Length	onEssentialMonitoring	MOSS 2007 Server	This rule uses the Output Queue Length counter to measure the length of the output packet queue (in packets). If the queue is longer than two, delays may be caused and the bottleneck should be found and eliminated, if possible. Since the requests are queued by the Network Driver Interface Specification (NDIS) in this implementation, this value will always be 0.
Page Faults Per Second	onEssentialMonitoring	MOSS 2007 Server	This rule uses the counter Page Faults/sec to measure the average number of pages faulted per second. This rule is measured in number of pages faulted per second because only one page is faulted in each fault operation; this is also equal to the number of page fault operations. The Page Faults/sec counter includes both hard faults (those that require disk access) and soft faults (where the faulted page is found elsewhere in physical memory). Most processors can handle large numbers of soft faults without significant consequences. However, hard faults, which require disk access, can cause significant delays.
Paging File	onEssentialMonitoring	MOSS 2007 Server	This rule uses the % usage counter to measure the percentage of the Page File instance in use.
Performance Measuring: ASP.NET Cache – Hit ratio	onEssentialMonitoring	MOSS 2007 Server	This rule uses the Cache Total Hit Ratio counter to sum the ASP.NET application performance counters.
Performance Measuring: ASP.NET Cache - size	onEssentialMonitoring	MOSS 2007 Server	This rule uses the Cache Total Entries counter to count the total number of entries within the cache (both internal and user added).
Performance Measuring: Disk Based Cache – Size	onEssentialMonitoring	MOSS 2007 Server	This rule uses the Total blob disk size counter to count the current number of pools that are associated with the process.
Performance Measuring: Object Cache – Cache flushes	onEssentialMonitoring	MOSS 2007 Server	This rules uses the Publishing cache flushes/sec counter to count the current number of pools that are associated with the process.
Performance Measuring: Object Cache – Cache hits/sec	onEssentialMonitoring	MOSS 2007 Server	This rule uses the Publishing cache hits/sec counter to count the current number of pools that are associated with the process.
Performance Measuring: Object Cache – Hit ratio	onEssentialMonitoring	MOSS 2007 Server	This rule uses the Publishing cache hit ratio counter to count the Current number of pools that are associated with the process.
Performance Measuring: Object Cache - Size	onEssentialMonitoring	MOSS 2007 Server	This rule uses the Total objects counter to count the current number of pools that are associated with the process.
Plug-in failed to connect to SQL Server	onEssentialMonitoring	MOSS Application Installation	A plug-in is a component of the search indexer that is used to process content and properties from crawled items. This alert indicates that an error occurred in the Office SharePoint Server Search (OSearch) service. The plug-in did not connect to the computer that is running SQL Server instance, and the update of the content source cannot continue.
Process - W3WP Handle Count	onEssentialMonitoring	MOSS 2007 Server	This rule uses the Handle Count counter to measure the total number of handles currently open by this process. This number is equal to the sum of the handles currently open by each thread in this process.
Process - W3WP Private Bytes	onEssentialMonitoring	MOSS 2007 Server	This rule uses the Private Bytes counter to measure the current size, in bytes, of memory that this process has allocated and that cannot be shared with other processes.
Process - W3WP Processor Time	onEssentialMonitoring	MOSS 2007 Server	This rule uses the % Processor Time counter to measure the percentage of elapsed time that all process threads use the processor to execute instructions. An instruction is the basic unit of execution in a computer, a thread is the object that executes instructions, and a process is the object created when a program is run. Code executed to handle some hardware interrupts and trap conditions are included in this count.
Process - W3WP Working Set	onEssentialMonitoring	MOSS 2007 Server	This rule uses the Working Set counter to measure the current size, in bytes, of the Working Set of this process. The Working Set is the set of memory pages recently touched by the threads in the process. If free memory in the computer is above the threshold of this rule, pages are left in the Working Set of a process even if they are not in use. When free memory falls below the threshold, pages are trimmed from Working Sets. If they are needed, they will be soft-faulted back into the Working Set before leaving main memory.
Process (Sql Server) Private Bytes	onEssentialMonitoring	MOSS 2007 Server	This rule uses the Private Bytes counter to measure the current size in bytes of memory that this process has allocated and that cannot be shared with other processes.
Process (Sql Server) Processor Time	onEssentialMonitoring	MOSS 2007 Server	This rule uses the % Processor Time counter to determine the percentage of elapsed time for all of the process threads used by the processor to execute instructions. An instruction is the basic unit of execution in a computer, a thread is the object that executes instructions, and a process is the object created when a program is run. Code executed to handle some hardware interrupts and trap conditions are included in this count.
Process (Sql Server) Working Set	onEssentialMonitoring	MOSS 2007 Server	This rule uses the Working Set counter to determine the current size in bytes of the Working Set of this process. The Working Set is the set of memory pages recently touched by the threads in the process. If free memory in the computer is above the rule’s threshold, pages are left in the Working Set of a process even if they are not in use. When free memory falls below the threshold, pages are trimmed from the Working Set. If the pages are needed, they will be soft-faulted back into the Working Set before leaving main memory.
Processor Interrupts Per Sec	onEssentialMonitoring	MOSS 2007 Server	This rule uses the counter Interrupts/Sec to measure the average rate, in incidents per second, at which the processor received and serviced hardware interrupts. This counter does not count deferred procedure calls (DPCs); these are counted separately. The value of this counter is an indirect indicator of the activity of devices that generate interrupts, such as the system clock, the mouse, disk drivers, data communication lines, network interface cards, and other peripheral devices. These devices normally interrupt the processor when they have completed a task or require attention. Normal thread execution is suspended. The system clock typically interrupts the processor every 10 milliseconds, creating a background of interrupt activity. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.
Processor Privileged Time	onEssentialMonitoring	MOSS 2007 Server	This rule uses the % Privileged Time counter to measure the percentage of elapsed time that the process threads spent executing code in Privileged mode. When a Windows system service is called, the service will often run in Privileged mode to gain access to system private data. Such data is protected from access by threads executing in User mode. Calls to the system can be explicit or implicit, such as page faults or interrupts. Unlike some early operating systems, Windows uses process boundaries for subsystem protection in addition to the traditional protection of User and Privileged modes. Some work done by Windows on behalf of the application in addition to the privileged time in the process might appear in other subsystem processes.
Processor Queue Length	onEssentialMonitoring	MOSS 2007 Server	This rule uses the counter Processor Queue Length to measure the number of items in the processor’s queue. If the threshold of this rule is exceeded, it indicates that the processor is not fast enough. This is an instantaneous counter. A queue of two or more items indicates a bottleneck.
Processor User Time	onEssentialMonitoring	MOSS 2007 Server	This rule uses the % User Time counter to measure the percentage of elapsed time the processor spends in User mode. User mode is a restricted processing mode designed for applications, environment subsystems, and integral subsystems. The alternative Privileged mode is designed for operating system components and allows direct access to hardware and all memory. The operating system switches application threads to Privileged mode to access operating system services. This counter displays the average busy time as a percentage of the sample time.
Profile Import Failed	onEssentialMonitoring	MOSS Application Installation	An error was encountered while importing user profiles from the directory service.
Propagation failed to communicate with a query server	onEssentialMonitoring	MOSS Application Installation	If your search-enabled server farm contains a query server that is separate from the index server, the Office SharePoint Server Search (OSearch) service automatically propagates a copy of the index from the index server to each query server in the server farm. For this propagation to occur, a network share must exist on each query server, and the OSearch service must be granted permissions to write to these network shares.
Propagation of the content index paused because of a lagging query server	onEssentialMonitoring	MOSS Application Installation	If your search-enabled server farm contains a query server that is separate from the index server, the Office SharePoint Server Search (OSearch) service automatically propagates a copy of the index from the index server to each query server simultaneously.
Publication of ranking information failed	onEssentialMonitoring	MOSS Application Installation	After crawled content is indexed, relevant anchor text is then indexed. This alert indicates that publication of anchor text failed. In this case, the index might be available, but the relevance of search results will be diminished to some degree.
Query server removed from rotation	onEssentialMonitoring	MOSS Application Installation	This indicates that a query server has been removed from the load-balanced rotation because IIS has encountered errors while communicating with the query server.
Recycle Application Pool	onEssentialMonitoring	MOSS Application Installation	This rule alerts the user when ever the Application Pool is recycled in the server.
Remote Procedure Call service failed to start	onEssentialMonitoring	MOSS Application Installation	When the Microsoft Single Sign-On (SSOSrv) service starts up, it attempts to start the Remote Procedure Call (RPC) service. This alert indicates that the RPC service failed to start, which indicates a problem with the RPC subsystem of the operating system.
Remote Procedure Call service failed to stop	onEssentialMonitoring	MOSS Application Installation	An error occurred while the Microsoft Single Sign-On (SSOSrv) service attempted to call the Remote Procedure Call (RPC) service.
Search - Number of queries towards an index	0	MOSS 2007 Server	This rule uses the Total # of queries counter to count the total number of queries since the index was mounted.
Search - Query Rate	onEssentialMonitoring	MOSS 2007 Server	This rule uses the Queries counter to measure the number of queries posted to the server.
Search - Succeeded Queries	onEssentialMonitoring	MOSS 2007 Server	This rule uses the Queries Succeeded counter to count the number of queries that produce successful searches.
Search - Total Number of Documents	0	MOSS 2007 Server	This rule uses the Total # documents counter to count the total number of documents in the index.
Shared Services Provider provisioning failed	onEssentialMonitoring	MOSS Application Installation	This alert indicates that an attempt to create the Shared Services Provider (SSP) failed and will be retried.
Shared Services Provider synchronization failed	onEssentialMonitoring	MOSS Application Installation	This alert indicates that a Shared Services Provider (SSP) failed to synchronize information with the configuration database.
Single Sign-On audit failure	onEssentialMonitoring	MOSS Application Installation	An error occurred while the Microsoft Single Sign-On (SSOSrv) service was attempting to insert a row into the Audit table in Microsoft SQL Server.
Single Sign-On failure	onEssentialMonitoring	MOSS Application Installation	The Microsoft Single Sign-On service is a mechanism used to authenticate a user only once to allow the user to gain access to all computers and systems. Excel Services uses single sign-on for authenticating with external data sources.
Site Directory scan job failed	onEssentialMonitoring	MOSS Application Installation	The timer job that scans for broken links in the site directory has failed.
Site Synch failed	onEssentialMonitoring	MOSS Application Installation	A particular site collection encountered a failure during profile and membership synchronization. The profile synchronization timer job will attempt to synchronize this site collection again when it is next executed.
Spelling checker failed to load	onEssentialMonitoring	MOSS Application Installation	This rule monitors an attempt to invoke the functions of the spelling checker.
SQL Server Database Error	onEssentialMonitoring	MOSS Application Installation	In a search-enabled server farm, the index server periodically writes to or reads from the SQL Server database. This alert indicates that an unexpected SQL Server database error occurred while the Office SharePoint Servers Search (OSearch) service running on the index server attempted to communicate with the database.
SSL is required but is not configured	onEssentialMonitoring	MOSS Application Installation	Excel Calculation Services is configured to use Secure Sockets Layer (SSL), also referred to as HTTPS, but SSL is not configured. This results in client requests’ being denied by Excel Calculation Services.
Sweep Synch failed	onEssentialMonitoring	MOSS Application Installation	A failure was encountered while synchronizing user profiles for new active users on a content database.
Synch Job Scheduler failed	onEssentialMonitoring	MOSS Application Installation	A failure occurred while an administrator was creating and scheduling a profile synchronization timer job for sweep sync and site sync of Web applications. The failed profile synchronization timer job will attempt to schedule these again when it is re-run.
The connection to the destination server timed out while transporting the deployment package created by the content deployment job	onEssentialMonitoring	MOSS Application Installation	While running, the content deployment job successfully made a network connection to the destination server and began transferring the deployment package. However, the network connection timed out before completing the transfer.
The connection to the destination server was lost while transporting the deployment package created by the content deployment job	onEssentialMonitoring	MOSS Application Installation	While running, the content deployment job successfully made a network connection to the destination server and began transferring content. However, the network connection was dropped while transporting the deployment package to the destination server.
The content deployment job failed on the destination server during the import phase	onEssentialMonitoring	MOSS Application Installation	The deployment job successfully transferred the deployment package to the destination server; however, the job failed while attempting to import the content from the deployment package to the locations on the destination server that are predefined in the content deployment job.
The content deployment job failed on the source server during the export phase	onEssentialMonitoring	MOSS Application Installation	The deployment job failed while attempting to export the content into the deployment package on the source server.
The disk-based cache exceeded the specified limit	onEssentialMonitoring	MOSS Application Installation	This error indicates that the disk-based cache exceeded the size specified in the web.config file. The disk-based cache provides faster rendering of items stored in document, picture and form libraries.
The Document Conversions Launcher Service failed to start	onEssentialMonitoring	MOSS Application Installation	This alert indicates that the Office Document Conversions Launcher Service (DCLauncher) failed to start. Note that on the Services on Server page in Central Administration, the DCLauncher service is referred to as the Document Conversions Launcher Service.
The Document Conversions Load Balancer Service failed to start	onEssentialMonitoring	MOSS Application Installation	This alert indicates that the Office Document Conversions Load Balancer Service (DCLoadBalancer) failed to start. This means that the load balancer cannot communicate with the launcher.
The last query server was removed from rotation	onEssentialMonitoring	MOSS Application Installation	This indicates that a query server has been removed from the load-balanced rotation. This means that users cannot perform search queries until this issue is resolved.
The launcher cannot register with the load balancer	onEssentialMonitoring	MOSS Application Installation	This error indicates that the Office Document Conversions Launcher Service (DCLauncher) cannot register with the Office Document Conversions Load Balancer Service (DCLoadBalancer). This means that the load balancer cannot communicate with the launcher.
The launcher lacks permissions to write to disk	onEssentialMonitoring	MOSS Application Installation	This alert indicates that the Office Document Conversions Launcher Service (DCLauncher) does not have sufficient permissions to write to disk. This means the logs and output files generated by the launcher cannot be written and, therefore, document conversions will fail.
The location specified for the disk-based cache is no longer accessible	onEssentialMonitoring	MOSS Application Installation	This error indicates that the disk-based cache exceeded the size specified in the web.config file. The disk-based cache provides faster rendering of items stored in document, picture and form libraries.
The Microsoft Single Sign-on Service State	onEssentialMonitoring	MOSS Application Installation	This rule monitors the state of the Microsoft Single Sign-on Service.
The object cache exceeded its maximum assigned size	onEssentialMonitoring	MOSS Application Installation	This error indicates that the object cache has exceeded the value assigned to the Object Cache Size setting for the site collection.
The Office Document Conversions Launcher Service State	onEssentialMonitoring	MOSS Application Installation	This rule monitors the state of the Office Document Conversions Launcher Service.
The Office Document Conversions Load Balancer Service State	onEssentialMonitoring	MOSS Application Installation	This rule monitors the state of the Office Document Conversions Load Balancer Service.
The Office SharePoint Server Search Service State	onEssentialMonitoring	MOSS Application Installation	This rule monitors the state of the Office SharePoint Server Search Service.
The Page Editing toolbar detected missing or corrupted configuration files in the Master Page Gallery	onEssentialMonitoring	MOSS Application Installation	A site owner or site member was unable to author a Web page due to missing or corrupted configuration files in the Master Page Gallery for the Page Editing toolbar. In many cases, the affected Web pages cannot be rendered.
Unable to delegate credentials	onEssentialMonitoring	MOSS Application Installation	Excel Calculation Services is configured to use delegated credentials. This error indicates that the front-end Web server was unable to delegate end-user credentials to Excel Calculation Services.
Unable to establish a connection with Excel Calculation Services	onEssentialMonitoring	MOSS Application Installation	Excel Calculation Services can be installed on each front-end Web server or on a separate application server. Regardless of where Excel Calculation Services is installed, all front-end Web servers must be able to establish a connection with Excel Calculation Services.
Unauthorized attempt to access a session	onEssentialMonitoring	MOSS Application Installation	When a user attempts to hijack another user’s session, Excel Calculation Services denies requests made by the user who does not own the session and logs an event in the Windows NT Event log.
User has exceeded the maximum allowable number of postbacks	onEssentialMonitoring	MOSS Application Installation	A user has exceeded the maximum number of postbacks configured for InfoPath Forms Services. When this condition occurs, InfoPath Forms Services terminates the user session to protect the server.
User Profile Commit failure	onEssentialMonitoring	MOSS Application Installation	An attempt to save the user profile to the Shared Services Provider (SSP) database has failed.
User Profile Property Conversion failed	onEssentialMonitoring	MOSS Application Installation	During a directory import, a property could not be converted correctly.
W3WP Error	onEssentialMonitoring	MOSS Application Installation	This rule monitors the W3WP process and alerts the user when w3wp.exe could not be started.
Web Service	onEssentialMonitoring	MOSS 2007 Server	This rule uses the Total Method Requests/sec counter to measure the rate at which HTTP requests are received.
Web Service - Bytes Received Per Second	onEssentialMonitoring	MOSS 2007 Server	This rule uses Bytes Received/sec counter to measure the rate at which data bytes are received by the Web service.
Web Service - Bytes Sent Per Second	onEssentialMonitoring	MOSS 2007 Server	This rule uses the Bytes Sent/sec counter to measure the rate at which data bytes are being sent by the Web service.
Web Service Connection Attempts	onEssentialMonitoring	MOSS 2007 Server	This rule uses the counter Connection Attempts to measure the web service connection attempts in seconds.
Web Service Connection Attempts	onEssentialMonitoring	MOSS 2007 Server	This rule uses the Connection Attempts/second counter to measure the rate at which connections to the Web service are being attempted.
Web Service Current Connections	onEssentialMonitoring	MOSS 2007 Server	This rule uses the Current Connections counter to measure the current number of connections established with the Web service.
Web Services for Remote Portlets runtime error	onEssentialMonitoring	MOSS Application Installation	This alert indicates that the Web Services for Remote Portlets (WSRP) Web Part could not communicate with the Web service that it is associated with.
Workbook disk cache cannot be created	onEssentialMonitoring	MOSS Application Installation	Excel Calculation Services uses the workbook disk cache to store workbooks that have been previously opened by user request. This cache is created on the hard disk of each computer running Excel Calculation Services
Workbook disk cache is full	onEssentialMonitoring	MOSS Application Installation	Excel Calculation Services uses the workbook disc cache to store workbooks that have been previously opened by user request. This error indicates that the workbook cache is full and that there is no space to load a workbook.

0

MOSS 2007 Server

This rule uses the SqlClient: Current # pooled and nonpooled connections counter to count the current number of active SQL connections, pooled or not.

.Net CLR Data-Sql client Failed connections

0

MOSS 2007 Server

This rule uses the SqlClient: Total # failed connects counter to count the total number of connection open attempts that have failed for any reason.

.NET CLR Memory - % Time in GC

onEssentialMonitoring

MOSS 2007 Server

This rule uses the % Time in GC counter to measure the percentage of elapsed time that was spent in performing a garbage collection (GC) since the last GC cycle. This counter is usually an indicator of the work done by the Garbage Collector on behalf of the application to collect and compact memory. This counter is updated only at the end of every garbage collection, and the counter value reflects the last observed value; this is not an average.

.NET CLR Memory - Bytes

onEssentialMonitoring

MOSS 2007 Server

This rule uses the # Bytes in all Heaps counter to sum the following four other counters: Gen 0 Heap Size; Gen 1 Heap Size; Gen 2 Heap Size, and Large Object Heap Size. This counter indicates the current memory allocated in bytes on the Garbage Collector Heaps.

.NET CLR Memory - Large Objects

onEssentialMonitoring

MOSS 2007 Server

This rule uses the Large Object Heap Size counter to display the current size of the Large Object Heap in bytes. Objects greater than 20 KB are treated as large objects by the Garbage Collector and are directly allocated in a special heap; they are not promoted through the generations. This counter is updated at the end of a garbage collection; it is not updated on every allocation.

.NET CLR Object - Finalization Survivors

onEssentialMonitoring

MOSS 2007 Server

This rule uses the Finalization Survivors counter to display the number of garbage collected objects that survive a collection because they are waiting to be finalized. If these objects hold references to other objects, then those objects also survive but are not counted by this counter. The Promoted Finalization-Memory from Gen 0 and Promoted Finalization-Memory from Gen 1 counters represent all the memory that survived due to finalization. This counter is not a cumulative counter; it is updated at the end of every garbage collection with the count of the survivors during that particular garbage collection only. This counter was designed to indicate the extra overhead that the application might incur because of finalization.

A Content Query Web Part failed to return content

onEssentialMonitoring

Notification

Rules

See Also for SharePoint Server Management Pack

Downloads for SharePoint Server Management Pack