none
MSExchangeDiagnostics 1039 since installing CU7 RRS feed

  • Question

  • 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
    Saturday, December 20, 2014 2:16 AM

All replies

  • 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,


    Niko Cheng
    TechNet Community Support

    Tuesday, December 23, 2014 9:53 AM
    Moderator
  • No I did not enable bitlocker and what 3rd party software are you referring to?
    Tuesday, December 23, 2014 5:23 PM
  • Hi MnM,

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

    Best regards,


    Niko Cheng
    TechNet Community Support

    Wednesday, December 24, 2014 3:19 AM
    Moderator
  • 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

    Saturday, January 3, 2015 1:09 PM
  • 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

    Wednesday, January 7, 2015 12:47 PM
  • Same issue on Exchange 2013 CU6 with Security Update  (KB3011140) installed.
    Tuesday, January 20, 2015 1:55 PM
  • Same here. Looks like a CU7 bug - causing service to crash

    The Microsoft Exchange Diagnostics service terminated unexpectedly. 


    Oliver Pergler

    Tuesday, February 3, 2015 3:43 PM
  • Same issue here CU7, haven't found solution yet.
    Thursday, February 19, 2015 11:15 AM
  • Same here 3 Exchange 2013 CU7 installs on 2012R2...
    Sunday, February 22, 2015 3:10 PM
  • Same here.

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


    • Edited by Wouter Ooms Thursday, February 26, 2015 1:39 PM
    Thursday, February 26, 2015 1:39 PM
  • 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.

    • Proposed as answer by driederer Wednesday, September 21, 2016 9:48 PM
    Friday, February 27, 2015 9:48 AM
  • Friday, February 27, 2015 10:30 AM
  • I think your solution krisztian major is for complete different problem than the asked question

    Friday, February 27, 2015 12:06 PM
  • 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.
    Thursday, March 5, 2015 12:51 PM
  • I am getting the same issue with CU8 as well so not fixed in CU8 too. Please update if someone is able to fix it.
    Monday, June 8, 2015 5:30 AM
  • 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
    Wednesday, August 12, 2015 2:03 AM
  • Hello Mike

    Seems to work.

    Thanks and regards
    Peter

    Thursday, August 20, 2015 12:35 PM
  • Great to hear Peter, thanks for the feedback.  :)

    Mike

    Friday, August 28, 2015 6:21 AM
  • 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


    Reduced the frequency of the events but they still appear. Just to throw another wrench in the works, this did not start when CU7 was installed but started when patches were being installed in April this year. CU7 was installed in January. All 4 servers (2 mailbox, 2 CAS) were upgraded, only one of the mailbox servers is reporting this diagnostic issue
    Wednesday, September 9, 2015 1:42 PM
  • Many thanks GADavies.

    This helps solving the problem.

    Monday, October 26, 2015 4:48 PM
  • I managed to stop all errors being logged, maybe I missed this in other posts earlier, but I had only made the change to the config file on the server reporting the issues. I later made the same change on the one not reporting issues and the errors went away totally.
    Monday, October 26, 2015 6:07 PM