none
DPM 2012 R2 fails on Prerequisites Check with "DPM requires SQL Native Client Configuration" RRS feed

  • Question

  • I'm trying to install System Center DPM 2012 R2 but it continues to fail on Prerequisites Check with "DPM requires SQL Native Client Configuration".

    I have SQL Server 2012 SP2 installed on the Windows Server 2008 R2 virtual as a default instance.  The Server and Agent are both running as DOMAIN\SA_DPM service accounts.

    The message I get is:

    DPM requires SQL Native Client Configuration TCP\IP to be enabled.  Enable SQL Native Client Configuration TCP\IP on the DPM machine.

    I've been through the SQL configuration manager and the TCP Client protocol is enabled for both 32 and 64 bit.

    Under SQL Server Network Configuration, I've played with LISTEN ALL=Yes and LISTEN ALL=No with no difference.

    Under TCP/IP Properties, there are no dynamic ports enabled.

    All the IP addresses are enabled and the TCP Port is the default 1433.

    The DpmSetup.log shows:

    [10/1/2014 1:56:44 PM] Information : Running the check: ClientTCPEnabled
    [10/1/2014 1:56:44 PM] Information : Getting the check for the checkId : ClientTCPEnabled
    [10/1/2014 1:56:44 PM] Information : Calling the method: CheckIfClientTCPEnabled
    [10/1/2014 1:56:44 PM] Information : Check if SQL Server has DPM Server already installed on it.
    [10/1/2014 1:56:44 PM] Information : Adding the check result entry for checkId: ClientTCPEnabled and result: 134348864
    [10/1/2014 1:56:44 PM] Information : Getting the error code for check : ClientTCPEnabled and result : 134348864
    [10/1/2014 1:56:44 PM] Information : Found Error Code:ClientTCPDisabled and Severity: Error
    [10/1/2014 1:56:44 PM] Information : Got Error Message: DPM requires SQL Native Client Configuration TCP\IP to be enabled.Enable SQL Native Client Configuration TCP\IP on the DPM machine.
    [10/1/2014 1:56:44 PM] Data : Result = 134348864

    I'm googled out on this. Anyone know how to fix this?

    Thursday, October 2, 2014 5:01 AM

All replies

  • Thursday, October 2, 2014 8:52 AM
  • Argh.  Good catch!

    I've removed SQL Server completely.  Reinstalled SQL 2012 and then SP1.

    Microsoft SQL Server 2012 (SP1) - 11.0.3000.0 (X64)
     Oct 19 2012 13:38:57
     Copyright (c) Microsoft Corporation
     Business Intelligence Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)

    When I attempted install of SC DPM 2012 R2, I still received message:  

         DPM requires SQL Native Client Configuration TCP\IP to be enabled.  Enable SQL Native Client Configuration TCP\IP on the DPM machine.

    I then went into SQL Serer Configuration Manager. I made sure that the native 32 and 64 client protocols were enabled:

        

    Then I enabled TCP for IP1 thru IP6.

        

    I then restarted the SQL Server Database service and attempted the Prerequisites check again -- same message needing Native Client.

    I looked at C:\Program Files\Microsoft System Center 2012\DPM\DPMLogs\DpmSetup.log which shows:

    [10/2/2014 1:42:29 PM] Data : checkId = ClientTCPEnabled
    [10/2/2014 1:42:29 PM] Information : Running the check: ClientTCPEnabled
    [10/2/2014 1:42:29 PM] Information : Getting the check for the checkId : ClientTCPEnabled
    [10/2/2014 1:42:29 PM] Information : Calling the method: CheckIfClientTCPEnabled
    [10/2/2014 1:42:29 PM] Information : Check if SQL Server has DPM Server already installed on it.
    [10/2/2014 1:42:29 PM] Information : Adding the check result entry for checkId: ClientTCPEnabled and result: 134348864
    [10/2/2014 1:42:29 PM] Information : Getting the error code for check : ClientTCPEnabled and result : 134348864
    [10/2/2014 1:42:29 PM] Information : Found Error Code:ClientTCPDisabled and Severity: Error
    [10/2/2014 1:42:29 PM] Information : Got Error Message: DPM requires SQL Native Client Configuration TCP\IP to be enabled.Enable SQL Native Client Configuration TCP\IP on the DPM machine.
    [10/2/2014 1:42:29 PM] Data : Result = 134348864

    Other thoughts?

    Thursday, October 2, 2014 6:51 PM
  • Friday, October 3, 2014 4:59 AM
  • Yes, that was the document that I used to configure SQL Config Manager.

    I'm going to start a $$$$$ case with PSS.  Seems ridiculous to have to do but c'est la vie.

    Thanks for helping.

    Friday, October 3, 2014 7:38 PM
  • It took PSS 3 days to resolve this issue and they were unable to determine why DPM kept giving this message.

    We ended up wiping the box completely, removing everything.  We lost all our 2010 DPM backups as they couldn't be restored.

    We still don't have DPM able to backup system state, BMR or Exchange 2013.  I'm now using BackupAssist as a safeguard.

    I've been told to look for better solutions as "DPM is obviously not a priority for MS".

    I used to brag on DPM. C'est la vie. :(

    Tuesday, October 21, 2014 5:14 PM