none
DPM2016 w/SQL2016: The installation failed, ID: 810 RRS feed

  • Question

  • Hi guys, need to get our backup platform up&running again ASAP.

    SQL2016 is suppose to be supported from DPM2016 Update Rollup 2 (released Feb. 9th). At first I installed SQL2016 with SP1 but got the ID: 4387 error. After reading this blog I tried to set up a new Hyper-V VM for DPM2016, installed Windows updates then installed SQL 2016 - this time without SP1. I am getting a bit further and installation appears to almost finish until I get error The DPM installation failed. Review the error details, take appropriate action, and then run DPM Setup again. ID: 810. Details: Fatal error during installation

    There is really not much to go on in the error log, it pretty much just summarizes the setup with the error message I pasted above. No more specific details.

    Any ideas? I'm in a hurry here so all suggestions are very much appreciated. In advance, thank you.

    Saturday, February 18, 2017 10:43 AM

Answers

  • There is a problem:

    MSI (s) (6C!BC) [13:10:26:735]: Creating MSIHANDLE (149) of type 790531 for thread 1724
    Error in DllUnregisterServer. hr=0x80070422
    MSI (s) (6C!BC) [13:10:26:735]: Closing MSIHANDLE (149) of type 790531 for thread 1724
    MSI (s) (6C!BC) [13:10:26:735]: Creating MSIHANDLE (150) of type 790531 for thread 1724
    Unregistering VSS provider failed with error. hr=0x80070422
    MSI (s) (6C!BC) [13:10:26:751]: Closing MSIHANDLE (150) of type 790531 for thread 1724
    Error in InstallProvider. hr=0x80070422
    MSI (s) (6C:48) [13:10:26:751]: Closing MSIHANDLE (145) of type 790536 for thread 4692
    CustomAction _InstallProvider.E785582E_DD9D_4A85_B866_3A1BC05C6110 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

    0x80070422 = The service cannot be started, either because it is disabled or because it
    has no enabled devices associated with it. ERROR_SERVICE_DISABLED

    This event may be related:

    Event ID:      10016Description: The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {8D8F4F83-3594-4F07-8369-FC3C3CAE4919}  and APPID  {F72671A9-012C-4725-9D2F-2A4D32D65169}  to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

    You can try to give the necessary permissions to the Local System account, despite it sounds crazy.

    • Marked as answer by ptbNO Wednesday, February 22, 2017 12:23 PM
    Sunday, February 19, 2017 3:15 PM
  • There is a problem:

    MSI (s) (6C!BC) [13:10:26:735]: Creating MSIHANDLE (149) of type 790531 for thread 1724
    Error in DllUnregisterServer. hr=0x80070422
    MSI (s) (6C!BC) [13:10:26:735]: Closing MSIHANDLE (149) of type 790531 for thread 1724
    MSI (s) (6C!BC) [13:10:26:735]: Creating MSIHANDLE (150) of type 790531 for thread 1724
    Unregistering VSS provider failed with error. hr=0x80070422
    MSI (s) (6C!BC) [13:10:26:751]: Closing MSIHANDLE (150) of type 790531 for thread 1724
    Error in InstallProvider. hr=0x80070422
    MSI (s) (6C:48) [13:10:26:751]: Closing MSIHANDLE (145) of type 790536 for thread 4692
    CustomAction _InstallProvider.E785582E_DD9D_4A85_B866_3A1BC05C6110 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

    0x80070422 = The service cannot be started, either because it is disabled or because it
    has no enabled devices associated with it. ERROR_SERVICE_DISABLED

    This event may be related:

    Event ID:      10016Description: The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {8D8F4F83-3594-4F07-8369-FC3C3CAE4919}  and APPID  {F72671A9-012C-4725-9D2F-2A4D32D65169}  to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

    You can try to give the necessary permissions to the Local System account, despite it sounds crazy.


    @EugenBerend

    I created a Microsoft support case today which actually was a very short conversation before everything was resolved. Basically thanks to you :)

    While creating the case I pasted the link to this conversation and the tech who called me had examined the log I posted for you and our dialogue here. Based on this the first thing he asked me to check was whether the Volume Shadow Copy (VSS) service was running. The service was disabled and was not running. As soon as I started the service DPM installed just fine. 

    The Microsoft tech pointed out the VSS service instantly based on you mentioning 

    Unregistering VSS provider failed with error. hr=0x80070422

    I have no idea whether our Windows Server 2016 VM template for some reason has VSS service disabled or if DPM installation caused it, this is something I have to investigate. It appears Windows Server 2016 shouldn't come with the service disabled out of the box (just like previous versions of Windows). 

    Anyway, very glad to resolve the issue and thanks so much for your time! :)


    • Marked as answer by ptbNO Wednesday, February 22, 2017 12:23 PM
    Wednesday, February 22, 2017 12:23 PM

All replies

  • Hi,


    Try to:

    1) set up SQL 2014

    2) set up DPM 2016

    3) set up UR2

    4) in-place upgrade SQL 2014 to 2016

    5) ensure that DPM works

    Saturday, February 18, 2017 11:11 PM
  • Good idea, thanks. It's late here but gonna do that first thing tomorrow morning and report back.
    Saturday, February 18, 2017 11:46 PM
  • Hi,


    Try to:

    1) set up SQL 2014

    2) set up DPM 2016

    3) set up UR2

    4) in-place upgrade SQL 2014 to 2016

    5) ensure that DPM works

    Ok, I'm sorta frustrated here: 

    I set up another brand new Hyper-V VM of Windows 2016 standard, ran Windows updates then Installed SQL 2014 w/SP2 (SW_DVD9_SQL_Svr_Standard_Edtn_2014w_SP2_64Bit_English_MLF_X21-04422.ISO). Installed SQL without issues, added all permissions needed on server + SQL, then ran through DPM setup. And I am getting the exact same error (!): ID 810. Details: Fatal error during installation

    This is the 8th time I'm trying to set up DPM2016 this weekend and as usual DPM logfiles is not giving me much to troubleshoot based on (see paste below). Eventlog is giving me a couple of errors while I doubt is relevant to my DPM troubleshooting (also see paste below). The only one that might be relevant is the Report Server Windows Service event

    Just for the record: All media is downloaded from Microsoft Volume Licensing

    Error log:
    ------------

    19.02.2017 13.10.30] Information : MsiInstallProduct returned 1603.

    [19.02.2017 13.10.30] Information : End install.
    [19.02.2017 13.10.30] Information : **************************************************************************************
    [19.02.2017 13.10.30] * Exception :  => The DPM installation failed.Review the error details, take appropriate action, and then run DPM Setup again.Microsoft.Internal.EnterpriseStorage.Dls.Setup.Exceptions.BackEndErrorException: exception ---> Microsoft.Internal.EnterpriseStorage.Dls.Setup.Exceptions.MsiInvokeException: Exception of type 'Microsoft.Internal.EnterpriseStorage.Dls.Setup.Exceptions.MsiInvokeException' was thrown.
       at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.Installer.Install()
       at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.BackEnd.Install(Installer installer)
       --- End of inner exception stack trace ---
       at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.BackEnd.Install(Installer installer)
       at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.DpmInstaller.Install()
       at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ProgressPage.InstallDpm()
       at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ProgressPage.InstallerThreadEntry()
    *** Mojito error was: InstallFailed; 1603; WindowsAPI
    [19.02.2017 13.10.31] *** Error : The DPM installation failed. Review the error details, take appropriate action, and then run DPM Setup again.
    ID: 810. Details: Fatal error during installation
    [19.02.2017 13.10.31] Information : Data Protection Manager installation has failed. All the items that were copied during the installation process have been removed.
    For details, click the Error tab.

    Errors in eventlog:

    Log Name:      Application
    Source:        Report Server Windows Service (LOCALDPM)
    Event ID:      110

    Description:
    The value for UrlRoot in RSReportServer.config is not valid. The default value will be used instead.

    Event ID:      7023


    Description:
    The description for Event ID 7023 from source Service Control Manager cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event: 

    Data Sharing Service
    %%3239247874

    Event ID:      10016

    Description:
    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
    {8D8F4F83-3594-4F07-8369-FC3C3CAE4919}
     and APPID 
    {F72671A9-012C-4725-9D2F-2A4D32D65169}
     to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.



    • Edited by ptbNO Sunday, February 19, 2017 12:26 PM
    Sunday, February 19, 2017 12:22 PM
  • If anyone have any sort of suggestion on how to troubleshoot it will be much, much appreciated. I really need to get the server up&running to push out clients and reboot the other servers before weekend is over. 
    Sunday, February 19, 2017 12:47 PM
  • Try to remove HTTPS bindings from SQL Reporting Services Configuration Manager, then re-run DPM setup.

    Or, in the SQL Server installation wizard, specify "Install and configure" option for SQL Server Reporting Services

    Sunday, February 19, 2017 1:04 PM
  • Try to remove HTTPS bindings from SQL Reporting Services Configuration Manager, then re-run DPM setup.

    Or, in the SQL Server installation wizard, specify "Install and configure" option for SQL Server Reporting Services

    Thanks but I did select the "install and configure" on reporting services during installation. 

    When I go to 'Web Service URL' in Reporting Services Configuration Manager it appears I have no HTTPS binding. "SSL port" is empty, only "TCP Port" 80.

    • Edited by ptbNO Sunday, February 19, 2017 1:20 PM
    Sunday, February 19, 2017 1:06 PM
  • Can you share your install log?
    Sunday, February 19, 2017 1:49 PM
  • Can you share your install log?
    Appreciate you taking a look. There shouldn't be any sensitive info in the setuplog right ? I have uploaded it here now
    Sunday, February 19, 2017 2:05 PM
  • There is a problem:

    MSI (s) (6C!BC) [13:10:26:735]: Creating MSIHANDLE (149) of type 790531 for thread 1724
    Error in DllUnregisterServer. hr=0x80070422
    MSI (s) (6C!BC) [13:10:26:735]: Closing MSIHANDLE (149) of type 790531 for thread 1724
    MSI (s) (6C!BC) [13:10:26:735]: Creating MSIHANDLE (150) of type 790531 for thread 1724
    Unregistering VSS provider failed with error. hr=0x80070422
    MSI (s) (6C!BC) [13:10:26:751]: Closing MSIHANDLE (150) of type 790531 for thread 1724
    Error in InstallProvider. hr=0x80070422
    MSI (s) (6C:48) [13:10:26:751]: Closing MSIHANDLE (145) of type 790536 for thread 4692
    CustomAction _InstallProvider.E785582E_DD9D_4A85_B866_3A1BC05C6110 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

    0x80070422 = The service cannot be started, either because it is disabled or because it
    has no enabled devices associated with it. ERROR_SERVICE_DISABLED

    This event may be related:

    Event ID:      10016Description: The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {8D8F4F83-3594-4F07-8369-FC3C3CAE4919}  and APPID  {F72671A9-012C-4725-9D2F-2A4D32D65169}  to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

    You can try to give the necessary permissions to the Local System account, despite it sounds crazy.

    • Marked as answer by ptbNO Wednesday, February 22, 2017 12:23 PM
    Sunday, February 19, 2017 3:15 PM
  • There is a problem:

    MSI (s) (6C!BC) [13:10:26:735]: Creating MSIHANDLE (149) of type 790531 for thread 1724
    Error in DllUnregisterServer. hr=0x80070422
    MSI (s) (6C!BC) [13:10:26:735]: Closing MSIHANDLE (149) of type 790531 for thread 1724
    MSI (s) (6C!BC) [13:10:26:735]: Creating MSIHANDLE (150) of type 790531 for thread 1724
    Unregistering VSS provider failed with error. hr=0x80070422
    MSI (s) (6C!BC) [13:10:26:751]: Closing MSIHANDLE (150) of type 790531 for thread 1724
    Error in InstallProvider. hr=0x80070422
    MSI (s) (6C:48) [13:10:26:751]: Closing MSIHANDLE (145) of type 790536 for thread 4692
    CustomAction _InstallProvider.E785582E_DD9D_4A85_B866_3A1BC05C6110 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

    0x80070422 = The service cannot be started, either because it is disabled or because it
    has no enabled devices associated with it. ERROR_SERVICE_DISABLED

    This event may be related:

    Event ID:      10016Description: The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {8D8F4F83-3594-4F07-8369-FC3C3CAE4919}  and APPID  {F72671A9-012C-4725-9D2F-2A4D32D65169}  to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

    You can try to give the necessary permissions to the Local System account, despite it sounds crazy.

    Nice find, thank you. However how to isolate which service we are talking about? When sorting on startup type and manually checking services that in my opinion could be related to DPM I don't see anyone that is not running.

    Update, I do have a few 10016 events:

    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
    {8D8F4F83-3594-4F07-8369-FC3C3CAE4919}
     and APPID 
    {F72671A9-012C-4725-9D2F-2A4D32D65169}
     to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

    However the 0x80070422 in error log + the info in the event above does not help me pinpoint which service we are talking about or where I should try to add Local System Account permissions.


    • Edited by ptbNO Sunday, February 19, 2017 3:58 PM
    Sunday, February 19, 2017 3:43 PM
  • Update #2 on 10016 events:

    I have 10016 events pointing towards 2 different CLSIDs/APPIDs, and a few entries of both:
    1) The first one pasted is on user <domain>\DPMSQLAdmin, the account I run SQL Server Agent, Database Engine + Reporting services on. The CLSID + APPID on this Event points to RunTimeBroker (?).
    NB! I also have 10016 events with same CLSID/APPID pointing towards NT AUTHORITY\SYSTEM

    2) The second one pasted is on NT AUTHORITY\SYSTEM only and I am not able to locate any specific APP based in Registry on CLSID/APPID and in Component Services it's listed with the actual ID both in the "name" field + "application ID" field

    When it comes to granting permission to these APPIDs I looked them both up in Component services and it's greyed out. Which from my understanding means TrustedInstaller owns them and I would need to take ownership in Registry. I've never actually done so earlier and I'm a bit sceptical to be honest.

    First 10016 event:
    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
    {D63B10C5-BB46-4990-A94F-E40B9D520160}
     and APPID 
    {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
     to the user <domain>\DPMSQLAdmin SID (S-1-5-21-507921405-515967899-725345543-30642) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

    Second 10016 event:
    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
    {8D8F4F83-3594-4F07-8369-FC3C3CAE4919}
     and APPID 
    {F72671A9-012C-4725-9D2F-2A4D32D65169}
     to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.


    • Edited by ptbNO Sunday, February 19, 2017 5:52 PM Wrong info on local administrator rights
    Sunday, February 19, 2017 4:17 PM
  • unfortunately, at the moment I have no idea what to do. If I were you, I'd create a new VM, give them enough CPU and RAM and perform a clean install again. I'd also make a lot of shots in the dark like check time synchronization between the VM, the host and DC or disable windows firewall and windows update.

    >"The first one pasted is on user <domain>\DPMSQLAdmin, the account I run SQL Server Agent, Database Engine + Reporting services on. The account is local administrator on the DPM server + member of DPMAdmins AD group"

    It is not necessary to explicitly grant any access rights to the SQL server service account. The best practice is to use managed service accounts (MSA or gMSA) for such purposes. There are no reasons to give them local admin or SQL sysadmin role membership.

    Sunday, February 19, 2017 5:33 PM
  • unfortunately, at the moment I have no idea what to do. If I were you, I'd create a new VM, give them enough CPU and RAM and perform a clean install again. I'd also make a lot of shots in the dark like check time synchronization between the VM, the host and DC or disable windows firewall and windows update.

    >"The first one pasted is on user <domain>\DPMSQLAdmin, the account I run SQL Server Agent, Database Engine + Reporting services on. The account is local administrator on the DPM server + member of DPMAdmins AD group"

    It is not necessary to explicitly grant any access rights to the SQL server service account. The best practice is to use managed service accounts (MSA or gMSA) for such purposes. There are no reasons to give them local admin or SQL sysadmin role membership.

    Yeah I agree, I am really in the dark here and I can't find much to troubleshoot on. There's also very limited amount of resources available online. Everything is fairly new (Windows 2016 / SQL2016 / DPM2016) plus there is not much relevant to find on DPM ID 810 error either. I am grateful for your time though, thank you so much.

    As I'm writing this it's also 6:45 pm here so there will most likely not be enough time to uninstall all DPM2012 R2 clients, push out DPM2016 clients to all servers and reconfigure backup on the new setup - if I did manage to install. I think I will just have to cross my fingers I find a solution the upcoming days and roll out clients, perform reboots & configure backup the upcoming weekend instead.

    Re permissions: Part of my previous info was wrong. I have created a global AD group ("DPMAdmins") and I have created an AD user ("DPMAdmin") which is member of the global group. The group is local administrator, however the SQL Service Account "DPMSQLAdmin" is not local administrator.

    Sunday, February 19, 2017 5:48 PM
  • Does anyone else have suggestions on how to troubleshoot this? I assume there must be some particular setting, account, permission or something in particular with my setup that keeps causing this to fail over and over while others have been able to deploy DPM2016 just fine. Still open and grateful for all suggestions.
    Monday, February 20, 2017 11:27 AM
  • Another "bump", I'm still very eager to figure this out. Still hoping I can get some valuable input here. Will give it another day before I probably have to create a support case with Microsoft.
    Tuesday, February 21, 2017 8:48 AM
  • There is a problem:

    MSI (s) (6C!BC) [13:10:26:735]: Creating MSIHANDLE (149) of type 790531 for thread 1724
    Error in DllUnregisterServer. hr=0x80070422
    MSI (s) (6C!BC) [13:10:26:735]: Closing MSIHANDLE (149) of type 790531 for thread 1724
    MSI (s) (6C!BC) [13:10:26:735]: Creating MSIHANDLE (150) of type 790531 for thread 1724
    Unregistering VSS provider failed with error. hr=0x80070422
    MSI (s) (6C!BC) [13:10:26:751]: Closing MSIHANDLE (150) of type 790531 for thread 1724
    Error in InstallProvider. hr=0x80070422
    MSI (s) (6C:48) [13:10:26:751]: Closing MSIHANDLE (145) of type 790536 for thread 4692
    CustomAction _InstallProvider.E785582E_DD9D_4A85_B866_3A1BC05C6110 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

    0x80070422 = The service cannot be started, either because it is disabled or because it
    has no enabled devices associated with it. ERROR_SERVICE_DISABLED

    This event may be related:

    Event ID:      10016Description: The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {8D8F4F83-3594-4F07-8369-FC3C3CAE4919}  and APPID  {F72671A9-012C-4725-9D2F-2A4D32D65169}  to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

    You can try to give the necessary permissions to the Local System account, despite it sounds crazy.


    @EugenBerend

    I created a Microsoft support case today which actually was a very short conversation before everything was resolved. Basically thanks to you :)

    While creating the case I pasted the link to this conversation and the tech who called me had examined the log I posted for you and our dialogue here. Based on this the first thing he asked me to check was whether the Volume Shadow Copy (VSS) service was running. The service was disabled and was not running. As soon as I started the service DPM installed just fine. 

    The Microsoft tech pointed out the VSS service instantly based on you mentioning 

    Unregistering VSS provider failed with error. hr=0x80070422

    I have no idea whether our Windows Server 2016 VM template for some reason has VSS service disabled or if DPM installation caused it, this is something I have to investigate. It appears Windows Server 2016 shouldn't come with the service disabled out of the box (just like previous versions of Windows). 

    Anyway, very glad to resolve the issue and thanks so much for your time! :)


    • Marked as answer by ptbNO Wednesday, February 22, 2017 12:23 PM
    Wednesday, February 22, 2017 12:23 PM