Shulou(Shulou.com)05/31 Report--

Today, I will talk to you about how to analyze the com+, in Microsoft Windows Server 2003. Many people may not know much about it. In order to make you understand better, the editor has summarized the following contents for you. I hope you can get something according to this article.

Consider the following situations:

You applied Windows Server 2003 SP2.

The call time of the COM + component is more than 10 minutes.

Open the component Services Microsoft Management console (MMC) snap-in when you are still running the application that hosts this long-running COM + component.

In this case, the following events are logged in the application log:

Event types: information

COM + event source:

Event category: (117)

Event ID: 782

Description: the average call duration exceeds 10 minutes. If this is not the expected behavior, please refer to article 910904 Microsoft knowledge Base for details on how to use the COM + AutoDump feature to automatically generate dump files and / or terminate the process if the problem occurs again.

Server application ID: {YourAppID}

Server application instance ID: {YourAppInstanceID}

Server Application name: YourAppName

When you can configure the system to detect a long running COM + component, do one or all of the following:

Automatically collect process dump files.

Terminate the process.

To do this, use the following registry values:

Value name: AverageCallThreshold

Data type: REG_DWORD

Description: the appropriate action will be taken when the threshold is in seconds

Default value: 0

Value name: DumpType

Data type: REG_DWORD

Description:

0 = generate a full dump file

1 = generate a small dump file

2 = No dump file

Default value: 0

Value name: termination

Data type: REG_DWORD

Description:

0 = the process will continue

1 = process will be terminated

Default value: 0

For actions taken on the computer by all COM + components defined globally, add configuration values under the following registry key:

HKEY_LOCAL_MACHINE\ SOFTWARE\ Microsoft\ COM3\ AutoDump

To define global settings for specific COM + components regardless of actions, add configuration values under the following registry key:

HKEY_CLASSES_ROOT\ AppId\ {}\ AutoDump\ {}

It is recommended that you collect full dump files

To get the best support for collecting full dump files, when the COM + component encounters a high call time. For example, to do this, you can create the following single registry value:

HKEY_LOCAL_MACHINE\ SOFTWARE\ Microsoft\ COM3\ AutoDump AverageCallThreshold = 300

See the considerations section for more information on how to select the appropriate AverageCallThreshold registry value for your specific environment.

When an unhandled exception occurs in a COM + application, the full dump file is also collected. To do this, click to select the enable image dump application error check box on the dump tab of each COM + application in the properties.

Analyze the dump file

When a dump file is generated, the initial analysis of the problem is performed. To do this, follow these steps:

Download and install the appropriate version of the Microsoft Internet Information Services (IIS) diagnostic kit.

Use the debug diagnostic tool (DebugDiag) of the IIS diagnostic kit to generate an analysis report of the dump file. To do this, follow these steps:

Click start, point to programs, point to IIS Diagnostics (32-bit), point to Debug Diagnostics tool, and then click Debug Diagnostics tool 1.0.

Click cancel in the Select Rule Type dialog box if it will open.

Click options and Settings on the tools menu.

Click the folders and search paths tab.

Type srv*C:\ symbols\ * http://msdl.microsoft.com/download/symbols in the analysis box of the symbol search path.

Click the Advanced Analysis tab.

Click $IISAnalysis.asp in the list of available analysis scripts.

Click add data File.

Select the dump file you want to analyze, and then click OK.

Click to start the analysis.

Displays the generated HTML report on the desktop in a new Microsoft Internet browser window. In addition, this report is saved to the DebugDiag report directory. The default location for this directory is Files\ IIS Resources\ DebugDiag\ Reports.

To resolve the problem, follow the guidelines provided in the recommendations section of the report. This section of the report may recommend the following actions:

It may lead you to an Microsoft knowledge base article that describes some known problems.

It may provide information and application developers that they can use to make corrections.

It may recommend that you use the appropriate vendor or Microsoft support as much as possible. When you support more help with Microsoft, the speed of the report file in the analysis process is provided. If necessary, a complete dump file may also be required.

Go back to the top

Considerations AverageCallThreshold registry value

A value of 300 seconds is the corresponding threshold for many environments. However, the ideal value may vary, depending on the specific environment. To ensure that the operation is performed as quickly as possible, but only if there is a legal problem, and only if there is a problem, choose to exceed the minimum possible value allowed.

TerminateProcess registry value

High-calling COM + components that may be helpful when terminating this process automatically recover from some problems. This may be particularly necessary in an environment where high availability is a major consideration. When you use this feature, it is particularly important to select the appropriate AverageCallThreshold registry value to avoid inadvertently terminating the process.

DumpType registry value

Files with small dump files are created faster and cost less disk space than full dump files. However, small dump files are of little use for problem analysis because they often lack the required data. A typical full dump file for a Dllhost.exe process is about 10 megabytes (MB) for 50 MB and takes less than a few seconds to generate. However, the size of the full dump file varies depending on the working set size of the process being dumped.

Dump File option

By default, the dump file is stored in the% systemroot%\ system32\ com\ dmp directory. In the image dump directory box, and under the appropriate COM + application's maximum number of dump images area, you can use this setting to control the location of the dump file and the $dump file.

Call time

The invocation time of the COM + component is the running average of all instances of the COM + component. The call time will be calculated by the COM + system application. In addition, the call time is displayed in the talk time (millisecond) column of the status view in the component Services MMC snap-in.

After reading the above, do you have any further understanding of how to analyze com+ in Microsoft Windows Server 2003? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.