Blog on Microsoft and Other Technologies.

Fatal MSI Error bgbisapi msi could not be installed

13 10,609

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:WindowsMicrosoft.NETFramework64v4.0.30319RegSvcs.exe” /u “E:Program FilesMicrosoft Configuration Managerbinx64microsoft.configurationmanager.bgbserverchannel.dll”
<02/22/15 06:20:22> CTool::RegisterComPlusService: Failed to unregister E:Program FilesMicrosoft Configuration Managerbinx64microsoft.configurationmanager.bgbserverchannel.dll with .Net Fx 4.0
<02/22/15 06:20:22> CTool::RegisterComPlusService: run command line: “C:WindowsMicrosoft.NETFramework64v4.0.30319RegSvcs.exe” /extlb /tlb:”E:Program FilesSMS_CCMmicrosoft.configurationmanager.bgbserverchannel.tlb” “E:Program FilesMicrosoft Configuration Managerbinx64microsoft.configurationmanager.bgbserverchannel.dll”
<02/22/15 06:20:22> CTool::RegisterComPlusService: Failed to register E:Program FilesMicrosoft Configuration Managerbinx64microsoft.configurationmanager.bgbserverchannel.dll with .Net Fx 4.0
<02/22/15 06:20:22> Cannot register BGB server channel DLL E:Program FilesMicrosoft Configuration Managerbinx64microsoft.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 FilesMicrosoft 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 FilesMicrosoft Configuration Managerbinx64microsoft.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:WindowsMicrosoft.NETFramework64v4.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.