Symptoms
When you try to use the Tiering Engine Service (Tieringengineservice.exe) in Windows Server 2012 R2, the service fails and you receive the following error code:
0x8e5e043e
Note To use the Tiering Engine Service, you typically have to do one of the following:
-
You run the Defrag.exe /g J: command, in which <J:> represents a tiered volume that has failed.
-
You run a Windows PowerShell applet that fails. For example, you run Get-FileStorageTier, Clear-FileStorageTier, or Set-FileStorageTier.
Resolution
To resolve this issue, install update rollup 2967917. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2967917 July 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2
Prerequisites
To apply this update, you must first have update 2919355 installed in Windows Server 2012 R2.
Restart requirement
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any previously released hotfix.
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 2012 R2 file information and notesImportant Windows 8.1 and Windows Server 2012 R2 hotfixes are included in the same packages. However, only "Windows 8.1" 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 8.1" 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, milestone (RTM,SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
Version
Product
Milestone
Service branch
6.3.960 0.16xxx
Windows Server 2012 R2
RTM
GDR
6.3.960 0.17xxx
Windows Server 2012 R2
RTM
DR
-
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 2012 R2" 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 x64-based versions of Windows Server 2012 R2
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Tieringengineproxy.dll |
6.3.9600.16384 |
18,432 |
22-Aug-2013 |
11:22 |
x64 |
|
Tieringengineservice.exe |
6.3.9600.17118 |
252,928 |
08-May-2014 |
05:47 |
x64 |
Additional file information for Windows Server 2012 R2
Additional files for all supported x64-based versions of Windows Server 2012 R2
|
File name |
Amd64_57702f8360e0d2247e644734938a1462_31bf3856ad364e35_6.3.9600.17118_none_038f819e49fa5c52.manifest |
|
File version |
Not Applicable |
|
File size |
705 |
|
Date (UTC) |
08-May-2014 |
|
Time (UTC) |
16:52 |
|
Platform |
Not Applicable |
|
SHA-1 hash |
Not Applicable |
|
MD5 hash |
Not Applicable |
|
File name |
Amd64_microsoft-windows-tieringengine_31bf3856ad364e35_6.3.9600.17118_none_a085bc1f3826e7e6.manifest |
|
File version |
Not Applicable |
|
File size |
13,022 |
|
Date (UTC) |
08-May-2014 |
|
Time (UTC) |
16:52 |
|
Platform |
Not Applicable |
|
SHA-1 hash |
Not Applicable |
|
MD5 hash |
Not Applicable |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
Learn about the terminology that Microsoft uses to describe software updates.
