I get this at boot and when restarting the Microsoft Exchange Diagnostics service ever since I updated to CU7.  Anyone know anything about this?

Log Name:      Application
Source:        MSExchangeDiagnostics
Date:          12/19/2014 12:30:09 PM
Event ID:      1039
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Server.contoso.com
Description:
Failed to detect the bitlocker state for EDS log drive 'C:\'.
Exception
System.Management.ManagementException: Invalid namespace
   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
   at System.Management.ManagementScope.InitializeGuts(Object o)
   at System.Management.ManagementScope.Initialize()
   at System.Management.ManagementObjectSearcher.Initialize()
   at System.Management.ManagementObjectSearcher.Get()
   at Microsoft.Exchange.Diagnostics.Service.DiagnosticsService.DriveLocked(String diagnosticsRootDrive)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSExchangeDiagnostics" />
    <EventID Qualifiers="49156">1039</EventID>
    <Level>2</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-12-19T19:30:09.000000000Z" />
    <EventRecordID>68590</EventRecordID>
    <Channel>Application</Channel>
    <Computer>server.contoso.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>C:\</Data>
    <Data>
Exception
System.Management.ManagementException: Invalid namespace
   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
   at System.Management.ManagementScope.InitializeGuts(Object o)
   at System.Management.ManagementScope.Initialize()
   at System.Management.ManagementObjectSearcher.Initialize()
   at System.Management.ManagementObjectSearcher.Get()
   at Microsoft.Exchange.Diagnostics.Service.DiagnosticsService.DriveLocked(String diagnosticsRootDrive)</Data>
  </EventData>
</Event>

• Edited by MnM Show Saturday, December 20, 2014 3:00 AM

Description: 
Failed to detect the bitlocker state for EDS log drive 'C:\'.

Hi MnM,

Did you install bitlocker in your exchange server?

If you disabled this 3rd party software, how about the result?

Best regards,

No I did not enable bitlocker and what 3rd party software are you referring to?

Hi MnM,

The 3rd party software is referring to something which could encrypt the hard drive, like some anti-virus.

Best regards,

Niko

This is wrong. This is not the actual issue. I too get this on all my Exchange 2013 servers (running Windows 2012 R2 fully windows updated) on Exchange 2013 CU7 ONLY

I dont have bitlocker, never had, never will and don't have any Anti Virus or similiar

The error message is misleading because its checking for BitLocker since Exchange 2013 CU7 is deployed. I guarantee if you build a Windows 2012 R2 Server and install Exchange 2013 CU7 on it fresh you will also get this error.

I too get it to the Original Poster, so its not just you

Andy

Same issue here.

I am managing 4 different Exchange 2013 organizations, CU7 is installed on all servers and the issue exists on every server.

Regards
Peter

Same issue on Exchange 2013 CU6 with Security Update  (KB3011140) installed.

Same here. Looks like a CU7 bug - causing service to crash

The Microsoft Exchange Diagnostics service terminated unexpectedly. 

Same issue here CU7, haven't found solution yet.

Same issue here CU7, haven't found solution yet.

• Proposed as answer by Krisztián Major Friday, February 27, 2015 10:30 AM
• Unproposed as answer by Krisztián Major Friday, February 27, 2015 10:30 AM

Same here 3 Exchange 2013 CU7 installs on 2012R2...

Same here.

One clean install of CU6, two clean installs of CU7.

• Edited by Wouter Ooms Thursday, February 26, 2015 1:39 PM

I think your solution krisztian major is for complete different problem than the asked question

Try install the Bitlocker-Driveencryption feature in the server manager. It's not necessary to enable Bitlocker but it must be installed for some reason.

This should resolve the issue.

This seems to be resolved my issue:

http://blogs.technet.com/b/anya/archive/2014/11/25/microsoft-exchange-diagnostics-service-crashing-post-cu6-upgrade.aspx

• Proposed as answer by Krisztián Major Friday, February 27, 2015 10:31 AM

I had the same 1039 error in Application log along with 7031 Exchange Diagnostics service crash in the system log and since I applied that fix the service is no longer crashing and also stopped the 1039 error in the application log.

If you have no 7031 service crash then it is a different issue alright.

Hey all,

I know this is not a "fix" but it will stop the events from appearing.

In the Microsoft.Exchange.Diagnostics.Service.exe.config file, usually located under: C:\Program Files\Microsoft\Exchange Server\V15\Bin\, change the DriveLockCheckEnabled to false.

<add key="DriveLockCheckEnabled" value="false" />

Restart the Microsoft Exchange Diagnostics service.

Hope this helps :)

Mike

• Proposed as answer by Mike R Carter Wednesday, August 12, 2015 2:09 AM

Great to hear Peter, thanks for the feedback.  :)

Mike