none
DPM 2016 install fails with error 4387 RRS feed

  • Question

  • Trying to install DPM 2106 on Server 2016, SQL 2016. All fresh installs.

    Looks like a common problem, but none of the suggestions have worked for me.  Any suggestions would be appreciated.  (And why does DPM continue to be very difficult to install?  Very frustrating.)

    Here's the install log:

    [1/19/2018 3:58:51 PM] Information : Microsoft System Center 2016 Data Protection Manager setup started.
    [1/19/2018 3:58:51 PM] Data : Mode of setup = User interface
    [1/19/2018 3:58:51 PM] Data : OSVersion = Microsoft Windows NT 10.0.14393.0
    [1/19/2018 3:58:51 PM] Information : Check if the media is removable
    [1/19/2018 3:58:51 PM] Data : Folder Path = C:,Program Files,Microsoft System Center 2016,DPM
    [1/19/2018 3:58:51 PM] Data : Drive Name = C:,
    [1/19/2018 3:58:51 PM] Data : Drive Type = 3
    [1/19/2018 3:58:51 PM] Information : Check attributes of the directory
    [1/19/2018 3:58:51 PM] Data : Folder Path = C:,Program Files,Microsoft System Center 2016,DPM
    [1/19/2018 3:58:51 PM] Data : File Attributes = Directory
    [1/19/2018 3:58:51 PM] Information : Check if the media is removable
    [1/19/2018 3:58:51 PM] Data : Folder Path = C:,Program Files,Microsoft Data Protection Manager
    [1/19/2018 3:58:51 PM] Data : Drive Name = C:,
    [1/19/2018 3:58:51 PM] Data : Drive Type = 3
    [1/19/2018 3:58:51 PM] Information : Check attributes of the directory
    [1/19/2018 3:58:51 PM] Data : Folder Path = C:,Program Files,Microsoft Data Protection Manager
    [1/19/2018 3:58:51 PM] * Exception : Ignoring the following exception intentionally => System.IO.FileNotFoundException: Could not find file 'C:,Program Files,Microsoft Data Protection Manager'.
    File name: 'C:,Program Files,Microsoft Data Protection Manager'
       at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
       at System.IO.File.GetAttributes(String path)
       at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.InstallLocationValidation.CheckForDirectoryAttributes(String path)
    [1/19/2018 3:58:51 PM] Information : Check if the media is removable
    [1/19/2018 3:58:51 PM] Data : Folder Path = C:,Program Files,Microsoft System Center 2016,DPM,DPM,DPMDB
    [1/19/2018 3:58:51 PM] Data : Drive Name = C:,
    [1/19/2018 3:58:51 PM] Data : Drive Type = 3
    [1/19/2018 3:58:51 PM] Information : Check attributes of the directory
    [1/19/2018 3:58:51 PM] Data : Folder Path = C:,Program Files,Microsoft System Center 2016,DPM,DPM,DPMDB
    [1/19/2018 3:58:51 PM] * Exception : Ignoring the following exception intentionally => System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:,Program Files,Microsoft System Center 2016,DPM,DPM,DPMDB'.
       at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
       at System.IO.File.GetAttributes(String path)
       at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.InstallLocationValidation.CheckForDirectoryAttributes(String path)
    [1/19/2018 3:58:52 PM] Information : The setup wizard is initialized.
    [1/19/2018 3:58:52 PM] Information : Starting the setup wizard.
    [1/19/2018 3:58:52 PM] Information : <<< Dialog >>> Welcome Page : Entering
    [1/19/2018 3:58:54 PM] Information : <<< Dialog >>> Welcome Page : Leaving
    [1/19/2018 3:58:54 PM] Information : <<< Dialog >>> Inspect Page : Entering
    [1/19/2018 3:59:03 PM] Information : Query WMI provider for path of configuration file for SQL Server 2008 Reporting Services.
    [1/19/2018 3:59:03 PM] Information : Querying WMI Namespace: ,,LINK_REMOVED,root,Microsoft,SqlServer,ReportServer,RS_DPM,V13,admin for query: SELECT * FROM MSReportServer_ConfigurationSetting WHERE InstanceName='DPM'
    [1/19/2018 3:59:04 PM] Data : Path of configuration file for SQL Server 2008 Reporting Services = C:,Program Files,Microsoft SQL Server,MSRS13.DPM,Reporting Services,ReportServer,RSReportServer.config
    [1/19/2018 3:59:04 PM] * Exception :  => System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SqlServer.Smo, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
    File name: 'Microsoft.SqlServer.Smo, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
       at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Helpers.MiscHelper.IsSqlClustered(String sqlMachineName, String sqlInstanceName)
       at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Helpers.MiscHelper.IsMachineClustered(String sqlMachineName, String sqlInstanceName)

    WRN: Assembly binding logging is turned OFF.
    To enable assembly bind failure logging, set the registry value [HKLM,Software,Microsoft,Fusion!EnableLog] (DWORD) to 1.
    Note: There is some performance penalty associated with assembly bind failure logging.
    To turn this feature off, remove the registry value [HKLM,Software,Microsoft,Fusion!EnableLog].

    [1/19/2018 3:59:04 PM] * 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.Internal.EnterpriseStorage.Dls.Setup.Helpers.WmiHelper.IsMachineClustered(String machineName, String instanceName)
    [1/19/2018 3:59:04 PM] Information : OS >= win 8 , enable Dedupe role
    [1/19/2018 3:59:09 PM] Information : output : False
    ..
     error :
    [1/19/2018 3:59:26 PM] Information : output :
    Success Restart Needed Exit Code      Feature Result                              
    ------- -------------- ---------      --------------                              
    True    No             Success        {File and iSCSI Services, Data Deduplicati...


     
     error :
    [1/19/2018 3:59:26 PM] Data : Path of inspection output xml = C:,Program Files,Microsoft System Center 2016,DPM,DPMLogs,InspectReport.xml
    [1/19/2018 3:59:26 PM] Information : Instantiating inspect component.
    [1/19/2018 3:59:26 PM] Data : Path of output xml = C:,Program Files,Microsoft System Center 2016,DPM,DPMLogs,InspectReport.xml
    [1/19/2018 3:59:26 PM] Information : Deserializing the check XML from path : C:,Users,domainadmin,AppData,Local,Temp,DPMA17C.tmp,DPM2012,setup,checks.xml
    [1/19/2018 3:59:26 PM] Information : Loading the check XML from path : C:,Users,domainadmin,AppData,Local,Temp,DPMA17C.tmp,DPM2012,setup,checks.xml
    [1/19/2018 3:59:26 PM] Information : Deserialising the scenario XML from path : C:,Users,domainadmin,AppData,Local,Temp,DPMA17C.tmp,DPM2012,setup,scenarios.xml
    [1/19/2018 3:59:26 PM] Information : Loading the check XML from path : C:,Users,domainadmin,AppData,Local,Temp,DPMA17C.tmp,DPM2012,setup,scenarios.xml
    [1/19/2018 3:59:26 PM] Information : Getting scenarios for the product: DPM
    [1/19/2018 3:59:26 PM] Information : Getting scenarios for DPM
    [1/19/2018 3:59:26 PM] Information : Getting scenario for Mode:Install, DbLocation:Remote, SKU:Retail and CCMode:NotApplicable
    [1/19/2018 3:59:26 PM] *** Error : Initialize the SQLSetUpHelper Object
    [1/19/2018 3:59:26 PM] Information : [SQLSetupHelper.GetWMIReportingNamespace]. Reporting Namespace found. Reporting Namespace : V13
    [1/19/2018 3:59:26 PM] Information : [SQLSetupHelper.GetWMISqlServerNamespace]. SQL Namespace found. SQL Namespace : ,,LINK_REMOVED,root,Microsoft,SqlServer,ComputerManagement13
    [1/19/2018 3:59:26 PM] Information : Query WMI provider for SQL Server 2008.
    [1/19/2018 3:59:26 PM] Information : Querying WMI Namespace: ,,LINK_REMOVED,root,Microsoft,SqlServer,ComputerManagement13 for query: Select * from SqlServiceAdvancedProperty where ServiceName='MSSQL$DPM' and PropertyName='Version'
    [1/19/2018 3:59:27 PM] Information : SQL Server 2008 R2 SP2 instance DPM is present on this system.
    [1/19/2018 3:59:27 PM] Information : Query WMI provider for SQL Server 2008.
    [1/19/2018 3:59:27 PM] Information : Querying WMI Namespace: ,,LINK_REMOVED,root,Microsoft,SqlServer,ComputerManagement13 for query: Select * from SqlServiceAdvancedProperty where ServiceName='MSSQL$DPM' and PropertyName='Version'
    [1/19/2018 3:59:27 PM] Information : [SQLSetupHelper.GetSQLDepedency]. Reporting Namespace and SQL namespace for installed SQL server which will be used as DPM DB. Reporting Namespace : ,,LINK_REMOVED,root,Microsoft,SqlServer,ReportServer,RS_DPM,V13,admin SQL Namespace : ,,LINK_REMOVED,root,Microsoft,SqlServer,ComputerManagement13
    [1/19/2018 3:59:27 PM] Information : Check if SQL Server 2012 Service Pack 1 Tools is installed.
    [1/19/2018 3:59:27 PM] Information : [SQLSetupHelper.GetSqlSetupRegKeyPath]. Registry Key path that contains SQL tools location: Software,Microsoft,Microsoft SQL Server,130,Tools,Setup,
    [1/19/2018 3:59:27 PM] Information : Inspect.CheckSqlServerTools : MsiQueryProductState returned : INSTALLSTATE_DEFAULT
    [1/19/2018 3:59:27 PM] *** Error : CurrentDomain_UnhandledException
    [1/19/2018 4:01:50 PM] * Exception : Invoking Watson with Exception:  => System.ArgumentNullException: Value cannot be null.
    Parameter name: input
       at System.Version.Parse(String input)
       at System.Version..ctor(String version)
       at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Inspect.InspectPrerequisites.CheckSqlServerTools(InspectContext context)
       at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Inspect.Inspect.InitializeContext(String sqlMachineName, String sqlInstanceName, String reportingMachineName, String reportingInstanceName, ConnectionOptions wmiSqlConnectionOptions, ConnectionOptions wmiReportingConnectionOptions, Boolean isRemoteDb, Boolean isSqlClustered, List`1 sqlClusterNodes, Boolean isRemoteReporting, String oldSqlMachineName, String oldSqlInstanceName, ProductNameEnum productName, InspectModeEnum inspectMode, Boolean remoteTriggerJob)
       at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Inspect.Inspect..ctor(String reportFilePath, String sqlMachineName, String sqlInstanceName, String reportingMachineName, String reportingInstanceName, ConnectionOptions wmiSqlConnectionOptions, ConnectionOptions wmiReportingConnectionOptions, Boolean isRemoteDb, Boolean isSqlClustered, List`1 sqlClusterNodes, Boolean isRemoteReporting, String oldSqlMachineName, String oldSqlInstanceName, InspectModeEnum inspectMode, InspectSkuEnum inspectSku, ProductNameEnum productName, InspectCCModeEnum ccMode, Boolean remoteTriggerJob)
       at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.BackEnd.InstantiateInspect(String inspectFile, String sqlMachineName, String sqlInstanceName, String reportingMachineName, String reportingInstanceName, ConnectionOptions wmiSqlConnectionOptions, ConnectionOptions wmiReportingConnectionOptions)
       at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.InspectPage.RunInspect()
       at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.InspectPage.InspectThreadEntry()
       at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()

    Saturday, January 20, 2018 12:39 AM

Answers

  • I started over, using SQL 2014 instead of 2016.  Installed the 2014 version of SSMS, ran MS Updates, and installation ran correctly.

    It was sort of an educated guess on my part that the SQL version was the problem.  The documentation isn't very clear.

    Monday, January 22, 2018 11:59 PM

All replies

  • I started over, using SQL 2014 instead of 2016.  Installed the 2014 version of SSMS, ran MS Updates, and installation ran correctly.

    It was sort of an educated guess on my part that the SQL version was the problem.  The documentation isn't very clear.

    Monday, January 22, 2018 11:59 PM
  • I might be wrong, but DPM 2016 release version didn't support SQL server 2016 for its own database.

    Tuesday, January 23, 2018 4:30 PM