You are currently offline, waiting for your internet to reconnect

[SDP 5][1033BE70-3EB1-4AD0-A477-C2E7E5D22492] The SharePoint 2007 Performance Monitor Wizard

Summary
The Support Diagnostics Platform (SDP) manifest creates a user-defined data collector set in the Windows Reliability and Performance Monitor tool. This article discusses how this manifest file operates.
More information
This article describes the intent and outcome when you run the Microsoft SharePoint 2007 Performance Monitor Wizard. This utility creates a series of batch files that can be executed by the user either at the request of Microsoft or on his or her own. No performance data is automatically transmitted to Microsoft. However, there are several diagnostic files that are created and can be uploaded.

When the manifest is executed, the user is prompted (through dialog boxes) for several pieces of information. This information is used to construct the batch and command files that are used to manage the collection of performance data. 

Required permissions

Depending on the target server, elevated permissions may be required in order to set up the performance data collectors. If this is the case, hold down the Shift key and right-click the batch file in question. You will be given the option to run the batch file as an administrator or as a different user. Regardless of the option that you select, the user must have server administrative permissions on the target computers. This is required for %windir%\system32\LOGMAN.EXE to set up the data collector sets correctly. 

The required permissions may not be attainable when the Performance Monitor Wizard is run on Server 2003 and another server in the SharePoint Farm is post 2003 (2008, 2008 R2, etc). If this situation is encountered, you may receive the following error. For more information on this topic, see the article Connecting Between Different Operating Systems.
"The version of the operating system on the computer named _______ is later than that on the local computer. This operation is not available from the local computer."


Information that is collected

The following information is collected: 
  • A unique identifier. Typically, this is a support case number. However, it can be anything that has significance to the user. If no value is provided, a value will be automatically generated for the user. 
  • Path of the output log folder. If you are setting up performance counters on multiple computers, you will have to make sure that this folder exists on all servers or specify a UNC path that can be accesed by all computers. 
  • A semicolon-delimited list of NetBIOS names for the Web Front End (WFE) or Query servers
  • A semicolon-delimited list of NetBIOS names for the Indexer/Crawler servers
  • A semicolon-delimited list of NetBIOS names for the instances of Microsoft SQL Server

Data collector sets

User-defined data collector sets
Data collector setDescriptionFile name
BASELINE_<identifier>This is a data collector set that is created to record baseline performance data on the specified computer. The counters are determined by the role of the computer in the server farm.

The placeholder <identifier> typically represents the support case number. However, it can be any unique value that will allow for the quick and easy identification of this counter among potentially many other counters.
BASELINE_<identifier>_%COMPUTERNAME%mmddhhmm.blg
INCIDENT_<identifier>This is a data collector set that is created to record performance data during the occurrence of the issue that is being investigated. This counter set is meant to be run on demand and stopped when the incident stops.

The placeholder <identifier> typically represents the support case number. However, it can be any unique value that will allow for the quick and easy identification of this counter among potentially many other counters.
INCIDENT_<identifier>_%COMPUTERNAME%mmddhhmm.blg

Batch/CMD files


Batch/CMD files that are created by the wizard
DescriptionFile nameLocation
A batch file that sets up the baseline and incident data collectors on all the specified servers CreateCounters_<identifier>.cmd%USERPROFILE%\Desktop\PerfWizard
A batch file that disables the ProcessNameFormat registry value.DisableProcessNameFormat_<identifier>.cmd%USERPROFILE%\Desktop\PerfWizard
A batch file that disables the ThreadNameFormat registry value.DisableThreadNameFormat_<identifier>.cmd%USERPROFILE%\Desktop\PerfWizard
A batch file that enables the ProcessNameFormat registry value. For more information see this article.EnableProcessNameFormat_<identifier>.cmd%USERPROFILE%\Desktop\PerfWizard
A batch file that enables the ThreadNameFormat registry value. For more information see this article.EnableThreadNameFormat_<identifier>.cmd%USERPROFILE%\Desktop\PerfWizard
A batch file that deletes the baseline data collectors on all serversDeleteBaselineCounters_<identifier>.cmd%USERPROFILE%\Desktop\PerfWizard
A batch file that deletes the incident data collectors on all serversDeleteIncidentCounters_<identifier>.cmd%USERPROFILE%\Desktop\PerfWizard
A batch file that queries and displays information about the baseline data collectors on all serversQueryBaselineCounters_<identifier>.cmd%USERPROFILE%\Desktop\PerfWizard
A batch file that queries and displays information about the incident data collectors on all serversQueryIncidentCounters_<identifier>.cmd%USERPROFILE%\Desktop\PerfWizard
A batch file that starts the baseline data collectors on all serversStartBaselineCounters_<identifier>.cmd%USERPROFILE%\Desktop\PerfWizard
A batch file that starts the incident data collectors on all serversStartIncidentCounters_<identifier>.cmd%USERPROFILE%\Desktop\PerfWizard
A batch file that stops the baseline data collectors on all serversStopBaselineCounters_<identifier>.cmd%USERPROFILE%\Desktop\PerfWizard
A batch file that stops the incident data collectors on all serversStopIncidentCounters_<identifier>.cmd%USERPROFILE%\Desktop\PerfWizard

More information

For the diagnostic packages to run a customer’s computer, we assume the following to be true: 
  • The customer has access to the Internet (either directly or indirectly).
  • The relevant diagnostic services are running on the destination computer.
  • Diagnostic Policy Service. The Diagnostic Policy Service enables problem detection, troubleshooting, and resolution for Windows components. If this service is stopped, diagnostics no longer function. 
  • Diagnostic Service Host. The Diagnostic Service Host is used by the Diagnostic Policy Service to host diagnostics that have to run in a Local Service context. If this service is stopped, any diagnostics that depend on it no longer function. 
  • Diagnostic System Host. The Diagnostic System Host is used by the Diagnostic Policy Service to host diagnostics that have to run in a Local System context. If this service is stopped, any diagnostics that depend on it no longer function.

References
Diagnostics Infrastructure

973559 Frequently asked questions about the Microsoft Support Diagnostic Tool (MSDT) when it is used with Windows 7 or Windows Server 2008 R2  
Properties

Article ID: 2608303 - Last Review: 07/23/2013 21:01:00 - Revision: 10.0

Microsoft Office SharePoint Server 2007, Microsoft Office SharePoint Server 2007 for Internet Sites, Microsoft Office SharePoint Server 2007 for Search (Enterprise Edition), Microsoft Office SharePoint Server 2007 for Search (Standard Edition), Microsoft Windows SharePoint Services 3.0, Microsoft Windows SharePoint Services 3.0 Language Pack Service Pack 1, Microsoft Windows SharePoint Services 3.0 Service Pack 1, Microsoft Windows SharePoint Services 3.0 Service Pack 2, Microsoft Windows SharePoint Services Service Pack 1, Microsoft Windows SharePoint Services Service Pack 3, Microsoft Windows SharePoint Services Service Pack 3 for Language Template Pack

  • KB2608303
Feedback
>