(Originally posted 3/12/2014. Reposting for reference)

 

Issue: Upon installing a new ConfigMgr 2012 R2 site, the component status for the SMS_NOTIFICATION_SERVER component shows the following error:

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 examining the BgbSetup.log file, the following errors are seen:

 CTool::RegisterComPlusService: Failed to unregister D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll with .Net Fx 4.0
CTool::RegisterComPlusService: Failed to register D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll with .Net Fx 4.0
Fatal MSI Error – bgbisapi.msi could not be installed.

Cause: This is presumably caused by installing ConfigMgr to a secondary drive location rather than to the default location of the “C:\Program Files\Microsoft Configuration Manager” folder, leading .NET to panic and question whether it should trust your judgement…

Resolution:  The resolution is to allow .NET to register libraries from remote sources using the loadFromRemoteSources element.  The utilities referenced in the BgbSetup.log file are InstallUtil.exe and RegSvcs.exe, both of which have a corresponding XML-based .config file.  To allow registration from remote sources, the following section must be added to the XML files (make a backup copy before you edit!):

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

Once this section has been added, restarting the SMS_SITE_COMPONENT_MANAGER will re-initiate the installation and allow it to complete successfully.