After upgrading a standalone Hybrid Deployment of Exchange 2013 to Exchange 2013 CU2 on Server 2012 the MSExchangeHMWorker.exe application is faulting, while accessing module Windows.Devices.Sensors.dll
We went from a relatively clear event log to one of these errors approximately every 45 seconds.
—————————————————————————————————————————————————
Log Name: Application
Source: Application Error
Date: 7/29/2013 5:56:16 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: server.domain.com
Description:
Faulting application name: MSExchangeHMWorker.exe, version: 15.0.712.0, time stamp: 0x5199cd1a
Faulting module name: Windows.Devices.Sensors.dll, version: 6.2.9200.16384, time stamp: 0x50108ff4
Exception code: 0xc0000005
Fault offset: 0x000000000002f608
Faulting process id: 0x8dec
Faulting application start time: 0x01ce8cbf8dccdb30
Faulting application path: C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeHMWorker.exe
Faulting module path: C:\Windows\System32\Windows.Devices.Sensors.dll
Report Id: d5dc4d77-f8b2-11e2-9426-9c8e994c5ff0
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-07-30T00:56:16.000000000Z" />
<EventRecordID>770120</EventRecordID>
<Channel>Application</Channel>
<Computer>server.domain.com</Computer>
<Security />
</System>
<EventData>
<Data>MSExchangeHMWorker.exe</Data>
<Data>15.0.712.0</Data>
<Data>5199cd1a</Data>
<Data>Windows.Devices.Sensors.dll</Data>
<Data>6.2.9200.16384</Data>
<Data>50108ff4</Data>
<Data>c0000005</Data>
<Data>000000000002f608</Data>
<Data>8dec</Data>
<Data>01ce8cbf8dccdb30</Data>
<Data>C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeHMWorker.exe</Data>
<Data>C:\Windows\System32\Windows.Devices.Sensors.dll</Data>
<Data>d5dc4d77-f8b2-11e2-9426-9c8e994c5ff0</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>
———————————————————————————————————————————
The error is having impact on system stability and the MSExchangeHMWorker.exe process does not automatically start after reboot despite being set to automatic.
Troubleshooting Steps Taken:
We have already replaced the MSExchangeHMWorker.exe.config file with a version from CU1 prior to the CU2 update (though, the differences were extremely minimal, and we did not expect that to resolve the issue) the MSExchangeHMWorker.exe was updated during CU2 installation and since then the file was re-verified against the file in the CU2 \Setup\serverroles\common folder.
(We also ran the SFC as a troubleshooting step despite it’s somewhat dubious value in a post isolated application and SxS assemblies world)
sfc /VERIFYFILE=C:\Windows\System32\Windows.Devices.Sensors.dll yielded the following CBS.log
————————————————————————————————————————————
2013-07-29 18:27:10, Info CBS TI: --- Initializing Trusted Installer ---2013-07-29 18:27:10, Info CBS TI: Last boot time: 2013-07-28 23:17:04.496
2013-07-29 18:27:10, Info CBS Starting TrustedInstaller initialization.
2013-07-29 18:27:10, Info CBS Ending TrustedInstaller initialization.
2013-07-29 18:27:10, Info CBS Starting the TrustedInstaller main loop.
2013-07-29 18:27:10, Info CBS TrustedInstaller service starts successfully.
2013-07-29 18:27:10, Info CBS No startup processing required, TrustedInstaller service was not set as autostart
2013-07-29 18:27:10, Info CBS Startup processing thread terminated normally
2013-07-29 18:27:10, Info CBS Starting TiWorker initialization.
2013-07-29 18:27:10, Info CBS Ending TiWorker initialization.
2013-07-29 18:27:10, Info CBS Starting the TiWorker main loop.
2013-07-29 18:27:10, Info CBS TiWorker starts successfully.
2013-07-29 18:27:10, Info CBS TiWorker: Client requests SFP repair object.
2013-07-29 18:27:10, Info CBS Universal Time is: 2013-07-30 01:27:10.375
2013-07-29 18:27:10, Info CBS Loaded Servicing Stack v6.2.9200.16613 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.2.9200.16613_none_6273bd8950d6cae2\cbscore.dll
2013-07-29 18:27:10, Info CSI 00000001@2013/7/30:01:27:10.375 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fb60236429 @0x7fb610095ca @0x7fb60fc4d64 @0x7f72631d1df @0x7f72631dc0f @0x7fbc66d2005)
2013-07-29 18:27:10, Info CBS Could not load SrClient DLL from path: SrClient.dll. Continuing without system restore points.
2013-07-29 18:27:10, Info CSI 00000002@2013/7/30:01:27:10.375 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fb60236429 @0x7fb61065e9c @0x7fb61027349 @0x7fb60fc4ed7 @0x7f72631d1df @0x7f72631dc0f)
2013-07-29 18:27:10, Info CBS SQM: Initializing online with Windows opt-in: False
2013-07-29 18:27:10, Info CBS SQM: Cleaning up report files older than 10 days.
2013-07-29 18:27:10, Info CBS SQM: Requesting upload of all unsent reports.
2013-07-29 18:27:10, Info CBS SQM: Failed to start upload with file pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005 - E_FAIL]
2013-07-29 18:27:10, Info CBS SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 - E_FAIL]
2013-07-29 18:27:10, Info CBS SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6
2013-07-29 18:27:10, Info CBS SQM: Warning: Failed to upload all unsent reports. [HRESULT = 0x80004005 - E_FAIL]
2013-07-29 18:27:10, Info CBS NonStart: Set pending store consistency check.
2013-07-29 18:27:10, Info CSI 00000003@2013/7/30:01:27:10.390 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fb60236429 @0x7fb965e82c0 @0x7fb965e83ee @0x7f72631c925 @0x7f72631dc26 @0x7fbc66d2005)
2013-07-29 18:27:10, Info CSI 00000004 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0xf596e3e0d0
2013-07-29 18:27:10, Info CSI 00000005 Creating NT transaction (seq 1), objectname [6]"(null)"
2013-07-29 18:27:10, Info CSI 00000006 Created NT transaction (seq 1) result 0x00000000, handle @0x250
2013-07-29 18:27:10, Info CSI 00000007 Poqexec successfully registered in [ml:26{13},l:24{12}]"SetupExecute"
2013-07-29 18:27:10, Info CSI 00000008@2013/7/30:01:27:10.936 Beginning NT transaction commit...
2013-07-29 18:27:10, Info CSI 00000009@2013/7/30:01:27:10.936 CSI perf trace:
CSIPERF:TXCOMMIT;273
2013-07-29 18:27:10, Info CSI 0000000a CSI Store 1054795131584 (0x000000f596b06ac0) initialized
2013-07-29 18:27:10, Info CSI 0000000b [SR] Verifying 1 components
2013-07-29 18:27:10, Info CSI 0000000c [SR] Beginning Verify and Repair transaction
2013-07-29 18:27:10, Info CSI 0000000d [SR] Cannot repair member file [l:54{27}]"Windows.Devices.Sensors.dll" of Microsoft-Windows-MobilePC-Sensors-WinRT, Version = 6.2.9200.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2013-07-29 18:27:10, Info CSI 0000000e [SR] Cannot repair member file [l:54{27}]"Windows.Devices.Sensors.dll" of Microsoft-Windows-MobilePC-Sensors-WinRT, Version = 6.2.9200.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2013-07-29 18:27:10, Info CSI 0000000f [SR] This component was referenced by [l:298{149}]"Microsoft-Windows-ServerDesktopExperience-drivers~31bf3856ad364e35~amd64~~6.2.9200.16384.microsoft-windows-serverdesktopexperience-deployment-drivers"
2013-07-29 18:27:10, Info CSI 00000010 [SR] Verify complete
Any insight or suggestions would be greatly appreciated.