none
Issue installing DPM - Error ID 4307

    Question

  • Hi,

    I am trying to install DPM 2019. I installed locally SQL 2017 with a named instance, but it's giving me an error 4307. When I specify the SQL instance, it's not allowing me to specify username and password, it automatically greyed it out saying it will be using the logged username (that username has access to the SQL server, but still it's failing)

    Firewall was disabled so I can troubleshoot.

    I am able to log in to SQL by command line.

    Any help here is much appreciated.

    Friday, May 3, 2019 1:27 PM

Answers

All replies

  • Hello!

    The 4307 error means that the DPM setup is not able to connect to the specified instance of the SQL Server.

    Make sure of the following:

    • Check that the SQL Server Browser is enabled and running.
    • Only use <Computer name> for the default instance, otherwise use <Computer name\<Instance name>
    • Make sure you have enough permissions to the SQL instance.
    • Make sure you have a supported SQL collation.

    You can find more detailed information in the DPM installation log, you can find it over here:

    • "C:\Program Files\Microsoft System Center\DPM\DPMLogs\DpmSetup.log"

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:


    • Edited by Leon Laude Friday, May 3, 2019 1:58 PM
    Friday, May 3, 2019 1:42 PM
  • Hi,

    I followed all the points since yesterday, I used default instance and a named instance just to try both. Permissions on sql are all set as I am able to connect to it with command line.

    And SQL Browser is running as well. SQL collation is also checked.

    Here is the logs:

    [5/3/2019 3:23:09 AM] Information : The setup wizard is initialized.
    [5/3/2019 3:23:09 AM] Information : Starting the setup wizard.
    [5/3/2019 3:23:09 AM] Information : <<< Dialog >>> Welcome Page : Entering
    [5/3/2019 3:23:13 AM] Information : <<< Dialog >>> Welcome Page : Leaving
    [5/3/2019 3:23:13 AM] Information : <<< Dialog >>> Inspect Page : Entering
    [5/3/2019 3:23:23 AM] * Exception :  => DPM Setup is unable to connect to DPM instance of SQL Server Amala6.Verify that the specified computer and the instance of SQL Server meets the following requirements:
    1)The computer is accessible over the network.
    2)A firewall is not blocking requests from the DPM computer. For steps to configure the firewall on the SQL Server, follow the steps described here: http://go.microsoft.com/fwlink/?LinkId=94001.
    3)The specified user belongs to the Administrator group on the computer running the SQL Server instance and the sysadmin role on the SQL Server instance.
    4)The SQL Browser service is running on the SQL server.
    5)TCP/IP protocol is enabled for the specified instance of the SQL server.Microsoft.Internal.EnterpriseStorage.Dls.Setup.Exceptions.BackEndErrorException: Exception of type 'Microsoft.Internal.EnterpriseStorage.Dls.Setup.Exceptions.BackEndErrorException' was thrown.
       at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.InspectPage.ValidateReportingInputs(String machineName, String instanceName)
       at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.InspectPage.InspectThreadEntry()
    *** Mojito error was: RemoteSQLConnectionFailed; 0; None

    Friday, May 3, 2019 2:23 PM
  • What is the name of the instance?

    Blog: https://thesystemcenterblog.com LinkedIn:

    Friday, May 3, 2019 3:04 PM
  • Instance name is DPM
    Friday, May 3, 2019 3:21 PM
  • Make sure that you have installed and configured SQL Server 2017 Reporting Services, note that this doesn't come with SQL Server 2017 anymore so you will have to download it separately.

    Microsoft SQL Server 2017 Reporting Services
    https://www.microsoft.com/en-us/download/details.aspx?id=55252


    Blog: https://thesystemcenterblog.com LinkedIn:

    • Marked as answer by Mehdi eee Friday, May 3, 2019 4:15 PM
    Friday, May 3, 2019 3:40 PM
  • I didn't install SSRS. Maybe that is the issue.

    Friday, May 3, 2019 3:49 PM
  • Thanks, I overlooked that one and lost hours of troubleshooting!!

    Thanks again.

    Friday, May 3, 2019 3:58 PM
  • No problem, it's easy to miss :-)

    (Please don't forget to mark as answer)


    Blog: https://thesystemcenterblog.com LinkedIn:

    Friday, May 3, 2019 3:59 PM