Microsoft KB Archive Search

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.

  1. Home
  2. Event ID 137 is logged when you back up the system state in a 32-bit version of Windows Server 2008

Event ID 137 is logged when you back up the system state in a 32-bit version of Windows Server 2008

View products that this article applies to.

Symptoms

When you back up the system state on a computer that is running a 32-bit version of Windows Server 2008, the following event may be logged in the System log:

Log Name: System
Source: Ntfs
Event ID: 137
Description:
The default transaction resource manager on volume VHD encountered a non-retryable error and could not start. The data contains the error code.0000: 0004001C 00300002 00000002 C0040089
0010: 00000000 C0000034 00000000 00000000
0020: 00000000 00000000 C0000034

↑ Back to the top

Cause

This problem occurs because NTFS handles wrong data widths for x86 environments. This triggers an unnecessary snapshot deletion and returns NTFS ID 137 together with STATUS_OBJECT_NAME_NOT_FOUND (C0000034).

↑ Back to the top

Resolution

Hotfix information

A supported hotfix is available from Microsoft Support. 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, go to the following Microsoft website:
http://support.microsoft.com/contactus/?ws=support
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 Service Pack 2 for Windows Server 2008.



Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

↑ Back to the top

File information
The English (United States) 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 Server 2008 file information and notes

Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table. The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.

    VersionProductSR_LevelService branch
    6.0.600
    2.
    23xxx    		Windows Server 2008SP2LDR
  • GDR service branches contain only those fixes that are widely released to address widespread, extremely important issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • Service Pack 1 is integrated into the release version of Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxx version number.
  • 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" section. MUM files 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 Server 2008
File nameFile versionFile sizeDateTimePlatform
Ntfs.sys6.0.6002.233501,083,32816-Mar-201415:33x86
For all supported x64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Ntfs.sys6.0.6002.233501,500,60816-Mar-201415:42x64
For all supported IA-64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Ntfs.sys6.0.6002.233503,284,92816-Mar-201414:44IA-64

Additional file information

Additional file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008
File nameX86_a8bc15d6ce494aabae7d6b34055308f1_31bf3856ad364e35_6.0.6002.23350_none_3356dd2e2cd55df3.manifest
File versionNot applicable
File size692
Date (UTC)18-Mar-2014
Time (UTC)07:59
PlatformNot applicable
File nameX86_microsoft-windows-ntfs_31bf3856ad364e35_6.0.6002.23350_none_a8ab1b8a3358259a.manifest
File versionNot applicable
File size16,265
Date (UTC)16-Mar-2014
Time (UTC)15:50
PlatformNot applicable
Additional files for all supported x64-based versions of Windows Server 2008
File nameAmd64_13d5f588defce1f23f4151cf81664f0b_31bf3856ad364e35_6.0.6002.23350_none_8f5350af0845fbe0.manifest
File versionNot applicable
File size696
Date (UTC)18-Mar-2014
Time (UTC)07:59
PlatformNot applicable
File nameAmd64_microsoft-windows-ntfs_31bf3856ad364e35_6.0.6002.23350_none_04c9b70debb596d0.manifest
File versionNot applicable
File size16,525
Date (UTC)16-Mar-2014
Time (UTC)16:00
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008
File nameIa64_b3f82eac2f17aada39908102b63ec251_31bf3856ad364e35_6.0.6002.23350_none_9580ab6f11834836.manifest
File versionNot applicable
File size694
Date (UTC)18-Mar-2014
Time (UTC)07:59
PlatformNot applicable
File nameIa64_microsoft-windows-ntfs_31bf3856ad364e35_6.0.6002.23350_none_a8acbf8033562e96.manifest
File versionNot applicable
File size16,517
Date (UTC)16-Mar-2014
Time (UTC)15:00
PlatformNot applicable

↑ 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

References

Learn about the terminology that Microsoft uses to describe software updates.

↑ Back to the top

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

↑ Back to the top

Article Info
Article ID : 2951098
Revision : 1
Created on : 1/7/2017
Published on : 5/21/2014
Exists online : False
Views : 152