Fatal MSI Error bgbisapi msi could not be installed

6376

Very recently I was troubleshooting an issue where the customer was getting error as SMS_Notification_Server for installing bgbisapi.msi. The error read Fatal MSI Error bgbisapi.msi could not be installed. When I looked into the issue I also found the below error as well.

Site Component Manager failed to install this component on this site system.

Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager will automatically retry the installation in 60 minutes. To force Site Component Manager to immediately retry the installation, stop and restart Site Component Manager using the Configuration Manager Service Manager.

Message ID: 4951 error SMS_NOTIFICATION_SERVER
Site Component Manager failed to install this component, because the Microsoft Installer File for this component (bgbisapi.msi) could not install.
Refer to the BgbSetup.log, the bgbisapimsi.log, as well as the ConfigMgr Documentation and the Microsoft Knowledge Base for further information.

Upon reviewing the BgbSetup.log, I found some more information.

<02/22/15 06:20:22> CTool::RegisterComPlusService: run command line: “C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegSvcs.exe” /u “E:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll”
<02/22/15 06:20:22> CTool::RegisterComPlusService: Failed to unregister E:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll with .Net Fx 4.0
<02/22/15 06:20:22> CTool::RegisterComPlusService: run command line: “C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegSvcs.exe” /extlb /tlb:”E:\Program Files\SMS_CCM\microsoft.configurationmanager.bgbserverchannel.tlb” “E:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll”
<02/22/15 06:20:22> CTool::RegisterComPlusService: Failed to register E:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll with .Net Fx 4.0
<02/22/15 06:20:22> Cannot register BGB server channel DLL E:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll. Installation cannot continue.
<02/22/15 06:20:22> Fatal MSI Error – bgbisapi.msi could not be installed.
<02/22/15 06:20:22> ~RoleSetup().

From the log file we see that the configuration manager was installed on the E: drive. While the default location where the SCCM gets installed is “C:\Program Files\Microsoft Configuration Manager”, the change in location of installation sometimes causes such errors. In this case the .NET framework would be installed on the C: drive and this is leading the .NET to trust your judgement.

One of the errors that we see in Bgbsetup.log is “Cannot register BGB server channel DLL E:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll. Installation cannot continue.”

Fatal MSI Error bgbisapi msi could not be installed

To fix this issue you need add the below code to both InstallUtil.exe and RegSvcs.exe .config files. Note that these are .exe files but you will look for Type of the file you find the XML .config files for the same exe’s. I would recommend you to backup the files before you add the code.

<runtime>
<loadFromRemoteSources enabled=”true”/>
</runtime>

1) Navigate to C:\Windows\Microsoft.NET\Framework64\v4.0.30319.

2) Find and open the file named regsvcs.exe of Type XML configuration file. You can open it with Notepad app.

Fatal MSI Error bgbisapi msi could not be installed

3) Add the code as shown in the below screenshot.

Fatal MSI Error bgbisapi msi could not be installed

4) Repeat the same for InstallUtil.exe .config file.

5) Once you have done that open the services.msc > restart the Distributed Transaction Coordinator service. Also restart the SMS_SITE_COMPONENT_MANAGER once.

  • Ann Lee

    I made the changes to the two files but cannot start the Distributed Transaction Coordinator service

  • Ann Lee

    I made the changes to the two files but cannot start the Distributed Transaction Coordinator service

    • @Ann – What error are you getting ?. Did you check event viewer for the event ?.

      • Ann Lee

        My SCCM is installed on the E: Drive.
        MP is on the site server together with the database.

        The error when starting Distributed Transaction Coordinator service:
        MSDTC encountered an error (HR=0x80000171) while attempting to establish a secure connection with system SCCM-1.

        I tried running the command listed in BgbSetup.log

        Command:
        “C:WindowsMicrosoft.NETFramework64v4.0.30319RegSvcs.exe” /extlb /tlb:” E:Program FilesSMS_CCMmicrosoft.configurationmanager.bgbserverchannel.tlb” “E:Program FilesMicrosoft Configuration Managerbinx64microsoft.configurationm
        anager.bgbserverchannel.dll”

        An unknown exception occurred during installation:
        1: System.Transactions.TransactionException – The Transaction Manager is not available. (Exception from HRESULT: 0x8004D01B)
        2: System.Runtime.InteropServices.COMException – The Transaction Manager is notavailable. (Exception from HRESULT: 0x8004D01B)

  • James Vreeling

    Hi Prajwal, I too am having this problem still after making the changes listed here. This happened after I upgraded our site from 2012 R2, up to 2012 R2 SP1 CU2. The strange thing is that on the 2 servers that this is happening on, it has reinstalled other site components.
    Eg, Server 2 is an MP and a DP, once the upgrade was done, the MP was reinstalled, but the DP fails. and on Server 3, the DP has installed, but not the MP, and in each case, the error listed above is shown in the log files. [Note. Server 1 is my Primary site server].

    I’m able to restart the services fine after making the changes.

    Any suggestions?

  • Dexxx

    Hello Prajwal, I did exactly as you explained in this topic, however I still see red in my logs :

    Apparently install is successful but not registration???

    Please help me
     ======== Completed Installation of Pre Reqs for Role SMSBGB ========
     Installing the SMSBGB
    Passed OS version check.
    IIS Service is installed.
    SMSBGB already installed (Product Code: {518894D7-2C43-4E6A-933F-C36A1759C25D}). Upgrading/Reinstalling SMSBGB
    New SMSBGB is the same product code. This is a minor upgrade.
    Enabling MSI logging. bgbisapi.msi will log to C:Program FilesMicrosoft Configuration ManagerlogsbgbisapiMSI.log
    Installing C:Program FilesMicrosoft Configuration Managerbinx64bgbisapi.msi REINSTALL=ALL REINSTALLMODE=vmaus CCMINSTALLDIR=”C:Program FilesSMS_CCM” CCMSERVERDATAROOT=”C:Program FilesMicrosoft Configuration Manager” USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1
    bgbisapi.msi exited with return code: 0
    Installation was successful.
    CTool::RegisterComPlusService: run command line: “C:WindowsMicrosoft.NETFramework64v4.0.30319RegSvcs.exe” /u “C:Program FilesMicrosoft Configuration Managerbinx64microsoft.configurationmanager.bgbserverchannel.dll”
    CTool::RegisterComPlusService: Failed to unregister C:Program FilesMicrosoft Configuration Managerbinx64microsoft.configurationmanager.bgbserverchannel.dll with .Net Fx 4.0
    CTool::RegisterComPlusService: run command line: “C:WindowsMicrosoft.NETFramework64v4.0.30319RegSvcs.exe” /extlb /tlb:”C:Program FilesSMS_CCMmicrosoft.configurationmanager.bgbserverchannel.tlb” “C:Program FilesMicrosoft Configuration Managerbinx64microsoft.configurationmanager.bgbserverchannel.dll”
    CTool::RegisterComPlusService: Failed to register C:Program FilesMicrosoft Configuration Managerbinx64microsoft.configurationmanager.bgbserverchannel.dll with .Net Fx 4.0
    Cannot register BGB server channel DLL C:Program FilesMicrosoft Configuration Managerbinx64microsoft.configurationmanager.bgbserverchannel.dll. Installation cannot continue.
    Fatal MSI Error – bgbisapi.msi could not be installed.
    ~RoleSetup().

  • Charles Katzke

    Hello Prajwal, is there any service or process that would prevent editing of the InstallUtil.exe.cofig file?

    Receiving access denied error when trying to save the changes.

    • Hi Charles, you could try the below steps :-

      1. Copying InstallUtil.exe.config to desktop

      2. Edit the original file’s Security to deny everyone to access

      3. Change the permission for the original file back

      4. Replace with the edited file

      You could also try to use the tool in the following link to find the processes that is keeping the file open.

      http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx