none
Failed to get DmpClient HRESULT=0x8007007F RRS feed

  • Question

  • Running SQL Server 2016 developer edition as the default instance on Windows 2012 with all the latest patches

    Microsoft SQL Server 2016 (RTM-GDR) (KB3194716) - 13.0.1722.0 (X64)   Sep 26 2016 13:17:23   Copyright (c) Microsoft Corporation  Developer Edition (64-bit) on Windows Server 2012 Standard 6.2 <X64> (Build 9200: ) (Hypervisor)

    Services were installed and are running under the default contexts

    NT Service\SQL Server Distributed Replay Controller

    NT Service\SQL Server Distributed Replay Client

    Error "Failed to get DmpClient. [HRESULT=0x8007007F]" is thrown to log on service start for both Controller and Client:

    2016-11-14 13:36:06:735 OPERATIONAL  [Controller Service]  Microsoft SQL Server Distributed Replay Controller - 13.0.1601.5.
    2016-11-14 13:36:06:750 OPERATIONAL  [Controller Service]  © Microsoft Corporation.
    2016-11-14 13:36:06:766 OPERATIONAL  [Controller Service]  All rights reserved.
    2016-11-14 13:36:06:781 OPERATIONAL  [Controller Service]  Current edition is: [Developer Edition].
    2016-11-14 13:36:06:813 OPERATIONAL  [Controller Service]  The number of maximum supported client is 1.
    2016-11-14 13:36:06:813 OPERATIONAL  [Controller Service]  Windows service "Microsoft SQL Server Distributed Replay Controller" has started under service account "NT Service\SQL Server Distributed Replay Controller". Process ID is 5212.
    2016-11-14 13:36:06:813 OPERATIONAL  [Controller Service]  Time Zone: Eastern Standard Time.
    2016-11-14 13:36:06:813 OPERATIONAL  [Common]              Initializing dump support.
    2016-11-14 13:36:06:813 OPERATIONAL  [Common]              Failed to get DmpClient. [HRESULT=0x8007007F]

    2016-11-14 13:36:10:985 OPERATIONAL  [Client Service]      Microsoft SQL Server Distributed Replay Client - 13.0.1601.5.
    2016-11-14 13:36:11:000 OPERATIONAL  [Client Service]      © Microsoft Corporation.
    2016-11-14 13:36:11:000 OPERATIONAL  [Client Service]      All rights reserved.
    2016-11-14 13:36:11:016 OPERATIONAL  [Client Service]      Current edition is: [Developer Edition].
    2016-11-14 13:36:11:016 OPERATIONAL  [Common]              Initializing dump support.
    2016-11-14 13:36:11:016 OPERATIONAL  [Common]              Failed to get DmpClient. [HRESULT=0x8007007F]
    2016-11-14 13:36:11:016 OPERATIONAL  [Client Service]      Windows service "Microsoft SQL Server Distributed Replay Client" has started under service account "NT Service\SQL Server Distributed Replay Client". Process ID is 6020.

    No COM errors are being thrown to the windows event logs.

    Any help would be appreciated. 


    Matt

    Monday, November 14, 2016 6:44 PM

All replies

  • I am able to get Distributed Replay to work against a SQL 2016 target using Win 2012 R2 and SQL 2014 for both Distributed Replay Controller and Client:)  I was not able to get SQL 2016 working for Distributed Replay Controller and Client on windows 10 or windows 2012.  I tried both domain and builtin NT Service accounts to no avail for running Controller and Client services.  The issue appears to be with SQL 2016 Distributed Replay components.  It will be interesting to see if anyone else is getting the same issue.

    Matt


    • Edited by Matt7 Thursday, November 17, 2016 7:26 PM
    Thursday, November 17, 2016 7:26 PM
  • Hi Matt,

    I am running into the same problem: Failed to get DmpClient. [HRESULT=0x8007007F]

    Have you figured it out?

    Thanks


    • Edited by Mark Varnas Monday, January 16, 2017 10:16 PM
    Monday, January 16, 2017 10:16 PM
  • I am running into same issue
    Saturday, February 18, 2017 12:12 AM
  • Did you configure dcom and the firewall for the client?

    This is covered here.

    https://blogs.msdn.microsoft.com/datamigration/distributed-replay-controller-and-client-setup/

    Saturday, February 18, 2017 2:05 AM
  • I did, the issue was i was using controller name other than the server name. Changing it to the Servername fixed my issue

    Monday, February 27, 2017 8:10 PM
  • Using the controller name Where?  Where did you make this change?  Having the same issue....

    Dianne

    Monday, March 26, 2018 8:19 PM
  • Changed in the config file - fixed!

    Dianne

    Wednesday, March 28, 2018 12:50 PM