Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

An access violation occurs when Logman.exe starts in Windows Vista, in Windows Server 2008, in Windows 7, or in Windows Server 2008 R2


View products that this article applies to.

Symptoms

Assume that you try to use the Logman command prompt utility (Logman.exe) to create and manage event tracing sessions and performance logs on a computer that is running one of the following operating systems:
  • Windows Vista
  • Windows Server 2008
  • Windows 7
  • Windows Server 2008 R2
 However, an access violation occurs when Logman.exe starts.

↑ Back to the top


Cause

This issue occurs because the C runtime calls the GetModuleHandle function to check whether the Mscoree.dll module is still loaded in the Logman.exe process when Logman.exe exits. If the Mscoree.dll module is loaded, the CorExitProcess function in this module is called to end the process. However, the Mscoree.dll module may be unloaded by another process when the CorExitProcess function is called. Therefore, an access violation occurs.

↑ Back to the top


Resolution

To resolve this issue in Windows 7 or in Windows Server 2008 R2, install this hotfix. Currently, there is no hotfix available for Windows Vista or for Windows Server 2008. To work around this issue in Windows Vista or in Windows Server 2008, use one of the methods that are described in the "Workaround" section.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running one of the following operating systems:
  • Windows 7
  • Windows 7 Service Pack 1 (SP1)
  • Windows Server 2008 R2
  • Windows Server 2008 R2 Service Pack 1 (SP1)
For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 7 and Windows Server 2008 R2 file information notes
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductMilestoneService branch
    6.1.760
    0.21xxx
    Windows 7 and Windows Server 2008 R2RTMLDR
    6.1.760
    1.21xxx
    Windows 7 and Windows Server 2008 R2SP1LDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2 and for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7
File nameFile versionFile sizeDateTimePlatform
Msvcrt.dll7.0.7600.21078690,68827-Oct-201104:28x86
Msvcrt.dll7.0.7601.21848690,68827-Oct-201106:20x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Msvcrt.dll7.0.7600.21078634,88027-Oct-201105:38x64
Msvcrt.dll7.0.7601.21848634,88027-Oct-201106:53x64
Msvcrt.dll7.0.7600.21078690,68827-Oct-201104:28x86
Msvcrt.dll7.0.7601.21848690,68827-Oct-201106:20x86
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Msvcrt.dll7.0.7600.210781,479,68027-Oct-201104:23IA-64
Msvcrt.dll7.0.7601.218481,479,68027-Oct-201104:17IA-64
Msvcrt.dll7.0.7600.21078690,68827-Oct-201104:28x86
Msvcrt.dll7.0.7601.21848690,68827-Oct-201106:20x86

↑ Back to the top


Workaround

To work around this issue in Windows Vista or in Windows Server 2008, use one of the following methods.

Method 1

Start or stop the data collector set manually. To do this, follow these steps:
  1. Start Performance Monitor.
  2. Expand the Data Collector Sets tree.
  3. Right-click the data collector set that you want to start or stop, and then click Start or Stop.

Method 2

Use a schedule to start or stop the data collector set manually. To do this, follow these steps:
  1. Start Performance Monitor.
  2. Expand the Data Collector Sets tree.
  3. Right-click the data collector set that you want to start or stop.
  4. Click Properties, select the Schedule tab, and then configure the schedule.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More Information

For more information about the Logman command prompt utility, visit the following Microsoft website:For more information about the GetModuleHandle function, visit the following Microsoft website:For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7
File nameX86_0e0d8c9ed04ec548b5f23252a31da97d_31bf3856ad364e35_6.1.7600.21078_none_012eb06c6ea1ffe3.manifest
File versionNot Applicable
File size694
Date (UTC)27-Oct-2011
Time (UTC)23:13
File nameX86_66f4fa533b9336ba46bac604683e17bc_31bf3856ad364e35_6.1.7601.21848_none_dfa2018e8db6f0a2.manifest
File versionNot Applicable
File size694
Date (UTC)27-Oct-2011
Time (UTC)23:13
File nameX86_microsoft-windows-msvcrt_31bf3856ad364e35_6.1.7600.21078_none_d1c2db79194ca801.manifest
File versionNot Applicable
File size2,327
Date (UTC)27-Oct-2011
Time (UTC)05:27
File nameX86_microsoft-windows-msvcrt_31bf3856ad364e35_6.1.7601.21848_none_d3c9d207165a89ff.manifest
File versionNot Applicable
File size2,327
Date (UTC)27-Oct-2011
Time (UTC)13:58
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_00726fbf1f1661726e571c3c8875ba81_31bf3856ad364e35_6.1.7600.21078_none_e679d7bfc8be6565.manifest
File versionNot Applicable
File size698
Date (UTC)27-Oct-2011
Time (UTC)23:13
File nameAmd64_0e0d8c9ed04ec548b5f23252a31da97d_31bf3856ad364e35_6.1.7600.21078_none_5d4d4bf026ff7119.manifest
File versionNot Applicable
File size696
Date (UTC)27-Oct-2011
Time (UTC)23:13
File nameAmd64_1c00b9b59b653406b6419ddbef92d391_31bf3856ad364e35_6.1.7601.21848_none_077b4effb3d83337.manifest
File versionNot Applicable
File size1,036
Date (UTC)27-Oct-2011
Time (UTC)23:13
File nameAmd64_1f8268230f6cdfd95254142543798301_31bf3856ad364e35_6.1.7600.21078_none_ee08a545d8fc1d2a.manifest
File versionNot Applicable
File size1,036
Date (UTC)27-Oct-2011
Time (UTC)23:13
File nameAmd64_66f4fa533b9336ba46bac604683e17bc_31bf3856ad364e35_6.1.7601.21848_none_3bc09d12461461d8.manifest
File versionNot Applicable
File size696
Date (UTC)27-Oct-2011
Time (UTC)23:13
File nameAmd64_897861753484a1f384e1a89802bc4e6d_31bf3856ad364e35_6.1.7601.21848_none_4bd8d36af29b515c.manifest
File versionNot Applicable
File size698
Date (UTC)27-Oct-2011
Time (UTC)23:13
File nameAmd64_microsoft-windows-msvcrt_31bf3856ad364e35_6.1.7600.21078_none_2de176fcd1aa1937.manifest
File versionNot Applicable
File size2,329
Date (UTC)27-Oct-2011
Time (UTC)12:07
File nameAmd64_microsoft-windows-msvcrt_31bf3856ad364e35_6.1.7601.21848_none_2fe86d8aceb7fb35.manifest
File versionNot Applicable
File size2,329
Date (UTC)27-Oct-2011
Time (UTC)19:32
File nameX86_microsoft-windows-msvcrt_31bf3856ad364e35_6.1.7600.21078_none_d1c2db79194ca801.manifest
File versionNot Applicable
File size2,327
Date (UTC)27-Oct-2011
Time (UTC)05:27
File nameX86_microsoft-windows-msvcrt_31bf3856ad364e35_6.1.7601.21848_none_d3c9d207165a89ff.manifest
File versionNot Applicable
File size2,327
Date (UTC)27-Oct-2011
Time (UTC)13:58
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_546ebf35e6faf55a7758e2ac7b2cce6d_31bf3856ad364e35_6.1.7601.21848_none_34873bbbd90997e0.manifest
File versionNot Applicable
File size1,034
Date (UTC)27-Oct-2011
Time (UTC)23:13
File nameIa64_b883277d04aedffa1876978f61a220d9_31bf3856ad364e35_6.1.7600.21078_none_a4c7985641d4a5de.manifest
File versionNot Applicable
File size1,034
Date (UTC)27-Oct-2011
Time (UTC)23:13
File nameIa64_microsoft-windows-msvcrt_31bf3856ad364e35_6.1.7600.21078_none_d1c47f6f194ab0fd.manifest
File versionNot Applicable
File size2,328
Date (UTC)27-Oct-2011
Time (UTC)05:49
File nameIa64_microsoft-windows-msvcrt_31bf3856ad364e35_6.1.7601.21848_none_d3cb75fd165892fb.manifest
File versionNot Applicable
File size2,328
Date (UTC)27-Oct-2011
Time (UTC)08:25
File nameX86_microsoft-windows-msvcrt_31bf3856ad364e35_6.1.7600.21078_none_d1c2db79194ca801.manifest
File versionNot Applicable
File size2,327
Date (UTC)27-Oct-2011
Time (UTC)05:27
File nameX86_microsoft-windows-msvcrt_31bf3856ad364e35_6.1.7601.21848_none_d3c9d207165a89ff.manifest
File versionNot Applicable
File size2,327
Date (UTC)27-Oct-2011
Time (UTC)13:58

↑ Back to the top


Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseinter

↑ Back to the top

Article Info
Article ID : 2635217
Revision : 1
Created on : 3/21/2017
Published on : 12/14/2011
Exists online : False
Views : 293