Microsoft Dynamics CRM 4.0 Statistics

This SAM application monitor template assesses the status and overall performance of a Microsoft Dynamics CRM 4.0 server by retrieving statistics from performance counters.

Prerequisites

WMI access to the target server.

Credentials

Windows Administrator on the target server.

Component monitors

Server: Failed CrmService Requests

This component returns the number of requests to the Microsoft Dynamics CRM Web service (part of the Microsoft Dynamics CRM SDK) that failed because of a time-out error or other SOAP failure.

This component has Count statistic as difference enabled. It will return the difference between two polling intervals.

Server: Failed InProcess CrmService Requests

This component returns the number of failed web service requests made by applications to the InProcess CrmService. The InProcess CrmService is a part of the Microsoft Dynamics CRM SDK used internally at Microsoft.

This component has Count statistic as difference enabled. It will return the difference between two polling intervals.

Server: Failed MetadataService Requests

This component returns the number of requests made to the MetadataService that failed because of a time-out or other SOAP failure.

This component has Count statistic as difference enabled. It will return the difference between two polling intervals.

Server: Failed Report Render Requests

This component returns the number of requests made to render Microsoft SQL Server Reporting Services reports that failed because of a time-out or error.

This component has Count statistic as difference enabled. It will return the difference between two polling intervals.

Server: Script Error Reports

This component returns the total number of error reports generated by the web client as well as Microsoft Dynamics CRM for the Outlook client. This counter is reset weekly to zero.

This counter is an indicator of high script error frequency. If a large number of error reports are received in a short time, the Operations team should investigate to determine which pages are producing errors.

It is recommend that you set a monitoring alert to notify you if there are more than 500 error reports in a 10-minute period.

This component has Count statistic as difference enabled. It will return the difference between two polling intervals.

Auth: DB Authentication Failures in the Last Minute

This component returns the number of unsuccessful authentication requests per minute that are processed by using the Active Directory authentication credentials. This counter measures the entire Microsoft Dynamics CRM deployment including all organizations.

A high count may indicate that the system is possibly under a Denial of Service attack, or there may be a problem with the Authentication service configuration.

Auth: CRM Authentication Failures in the Last Minute

This component returns the number of unsuccessful authentication requests per minute that are processed by using the Microsoft Dynamics CRM authentication credentials. This counter measures the entire deployment including all organizations.

A high count may indicate that the system is possibly under a Denial of Service attack, or there may be a problem with the Authentication service configuration.

Auth: Windows Live ID Authentication Failures in the Last Minute

This component returns the number of failed authentication requests per minute that are processed by using the Windows Live ID authentication credentials. This counter measures the entire Microsoft Dynamics CRM deployment including all organizations.

A high count may indicate that the system is possibly under a Denial of Service attack, or there may be a problem with the Authentication service configuration.

Auth: Windows Authentication Failures in the Last Minute

This component returns the total number of authentication requests that are processed per minute. This counter includes successful and unsuccessful authentication attempts, and measures the entire Microsoft Dynamics CRM deployment including all organizations.

This counter is useful to show the authentication engine throughput of requests that use Active Directory authentication credentials and are requests for access to a specific organization. Together with the Processor and Memory counters, this counter can indicate whether the Microsoft Dynamics CRM server is overloaded with authentication requests and may require load balancing.

Outlook Sync: Total ABP Sync Requests

This component returns the total number of Address Book Provider (ABP) synchronization requests made from Microsoft Dynamics CRM for Outlook clients to a Microsoft Dynamics CRM Server.

This counter is useful to indicate the client load on the Asynchronous Processing Service. A high count indicates a high client load on that service.

You should set thresholds according to your environment.

This component has Count statistic as difference enabled. It will return the difference between two polling intervals.

Outlook Sync: Total Offline Sync Requests

This component returns the total number of offline synchronization requests made from Microsoft Dynamics CRM for Outlook clients to a Microsoft Dynamics CRM Server.

This counter is useful to indicate the client load on the Asynchronous Processing service. A high count indicates a high client load on the service.

You should set thresholds according to your environment.

This component has Count statistic as difference enabled. It will return the difference between two polling intervals.

Outlook Sync: Total Outlook Sync Requests

This component returns the total number of ABP Sync Requests and the Offline Sync Requests.

This counter is useful to indicate the client load on the Asynchronous Processing Service. A high count indicates a high client load on that service.

You should set thresholds according to your environment.

This component has Count statistic as difference enabled. It will return the difference between two polling intervals.

Outlook Sync: Total Succeeded Offline Sync Requests

This component returns the number of successful offline synchronization requests made from Microsoft Dynamics CRM for Outlook clients to a Microsoft Dynamics CRM Server.

A count that is much lower than the total number of offline synchronization requests may indicate a problem with clients that try to synchronize with the server.

You should set thresholds according to your environment.

This component has Count statistic as difference enabled. It will return the difference between two polling intervals.

Discovery: Failed Discovery Service Requests

This component returns the number of requests to the Microsoft Dynamics CRM Discovery service that are unsuccessful for any reason. For example, a request may fail because the requesting party is not recognized as user in the requested organization.

A high count may indicate that the system is possibly under a Denial of Service attack, or there is some problem with the Discovery service configuration.

Locator: Failed Cache Flush Requests

This component returns the number of LocatorService cache flush requests that were unsuccessful for any reason. For example, a request may fail because it was for an invalid cache entry, or the cache may not flush because of an incorrect cache state.

A high count may indicate a problem with the LocatorService cache, or a problem with the connection to CONFIG_DB. For information about the cause, review the event log for errors.

This component has Count statistic as difference enabled. It will return the difference between two polling intervals.

Locator: Total Cache Flush Requests

This component returns the total number of LocatorService flush requests that were received. This includes successful and unsuccessful requests.

A high count may indicate that the caching algorithm is not optimized, or that the data is changing too frequently.

This component has Count statistic as difference enabled. It will return the difference between two polling intervals.

Platform: Average time of import request

This component returns the average time that is required to process Microsoft Dynamics CRM data import requests.

Import requests are resource-intensive SQL operations. If the average time is too high and the number of concurrent imports is high, some organizations may have to be moved to a different server. Also, you may want to consider processing import jobs during a maintenance window to reduce the performance effect on users.

You should set thresholds according to your environment.

Async Service: Active Organizations

This component returns the total number of organizations in the Microsoft Dynamics CRM deployment that are actively being polled by the Microsoft CRM Asynchronous Processing Service.

Async Service: Total Operations Failed

This component returns the total number of asynchronous operations that failed for all organizations in the deployment.

This component has Count statistic as difference enabled. It will return the difference between two polling intervals.

Microsoft CRM Asynchronous Processing Service

This component returns the CPU and memory usage of Microsoft CRM Asynchronous Processing service. This service handles the processing of queued Asynchronous Events.

Dynamics CRM TCP Port

This component monitor tests the ability of a Dynamics CRM service to accept incoming sessions.

By default, TCP port 80 is monitored.