SCDPM 2022 installation error 4387 "Unable to get machine name information"

Question

Hello,

I am trying to install SCDPM 2022 on windows server 2022 with sql 2019. I re-installed all required software (SQL Server, SQL Studio, SSMS, Reporting Service + configure...) to ensure that I didn't miss anything.

The installation fails again at the first step "Prerequisites check". As soon as I enter the name in field "Instance of SQL Server" I get the error 4387.

I checked the DPM error Logs and the only thing I see is "Unable to get machine name information". I just don't understand where this error is coming from. There are no tmp folders with additional logs.

I would highly appreciate any ideas on how to solve this error.

The DPMSetup Log shows:

*** Error : Application_ThreadException

• Exception : Invoking Watson with Exception: => System.Configuration.ConfigurationErrorsException: Unable to get machine name information at Microsoft.Internal.EnterpriseStorage.Dls.Utils.FqMachineName.GetDpmMachineName() at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Inspect.InspectHelper.CheckIfLocalMachine(String sqlServerName) at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.InspectPage.SetReportingInstanceName() at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.InspectPage.sqlServerInstanceTextBox_LeavingBox(Object sender, EventArgs e) at System.Windows.Forms.Control.OnLeave(EventArgs e) at System.Windows.Forms.ContainerControl.UpdateFocusedControl()

Thanks.

Answer 1

Hi, @SRS-2740

Thank you for posting in Microsoft Q&A forum.

It seems that you are encountering error 4387 during the installation of SCDPM 2022 on Windows Server 2022 with SQL 2019.

This error can occur if the machine name cannot be determined.

One possible cause is that the FQDN of the machine is not properly configured. You can try to fix this by checking the FQDN configuration of the machine and ensuring that it is properly set up.

Additionally, you can try running the installation with elevated privileges by right-clicking on the installer and selecting "Run as administrator".

If the issue persists, you can try contacting Microsoft Support for further assistance.

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Add comment".