BGBISAPI.msi fatal error 1603

Question

Hi,
I am setting up a test SCCM 2012 environment and have a primary SCCM server up and working and deployed 2 Distribution & Management point servers fine however when i go into SCCM, Monitoring, Site Hierarchy when I right click my site it shows a load
of failures, for each of my 3 servers i have 2 errors reported every 60 minutes,
Message ID 1016 and- site component manager failed to install this component of this site system
Message ID4951 - Site Component Manager Failed to install this component, because the Microsoft installer for this component (bgbisapi.msi) could not install
When I look at the bgbsetup log file its showing
bgbisapi.msi exited with return code 1603
Fatal msi error bgbisapi could not be installed
I have done a lot of research into this trying a host of stuff and it wont install, any help much appreciated

Answer 1

I had this same issue on another thread. 
other threadI worked with a Microsoft engineer on the case.  The issue is now resolved.  The problem was due to the server not being part of a local security group that caused it to not install a function.  We reviewed several logs to isolate
the problem.  The Microsoft engineer approached this from a "what is the expected outcome" rather than just the specified error code.  Before this was fixed all of my EU desktops were showing up inactive and with no inventory, and no historical data. 
Now everything works properly.
Details below
Had Microsoft review my settings on support call
confirmed boundaries were correct.
Discovery groups and settings are correct.
Secondary site settings and roles are correct.
Overall health of SCCM is correct.
Site hierarchy is correct
Server installation procedure is correct.
Server SCCM patch installation is correct.
Site to site functions are correct, however we have to double check logs to make sure all components are correct.  Since imaging and remote controlling are functioning there might be a component error as initially suspected.
We isolated a machine in one office, and reviewed log files (inventoryagent.log and others)
confirmed that the machine is sending it logs files to management point.
We then took a look at log files on the servers to further isolate the issue.
<PROBLEM SECONDARY SITE SERVER>
U_ex***.log – iis server logs
Compmon.log – component information including installation
Perfsetup.log – performance counter information
Mpfdm.log - Moves client files to the corresponding SMS\INBOXES folder
Mp_Hinv.log to confirm that the mp is receiving and processing inventory
dataldr.log – logs .mif file processing for inventory  on primary site
<PRIMARY SCCM SERVER>
dataldr.log – logs .mif file processing for inventory  on primary site
dataldr.lo_ - logs .mif file processing for inventory  on primary site
We noticed that the associated .mif file for the desktop machine was not present on <PRIMARY SCCM SERVER>. ( search on ConfigMgr\inboxes\auth\dataldr.box )
We reviewed additional logs and found errors in the
compmon.log files
We concluded that there is a communication error between <PROBLEM SECONDARY SITE SERVER> and <PRIMARY SCCM SERVER>, since the inventory logs were present and processing on <PROBLEM SECONDARY SITE SERVER>.  Deeper analysis of the logs
pointed us to the root communication issue between <PROBLEM SECONDARY SITE SERVER>
Local administrators group was correct with <PRIMARY SCCM SERVER> and <PROBLEM SECONDARY SITE SERVER> added.  
The sitecomp & compmon logs were reviewed further and we found some additional issue with components not installing fully.
Per one of the logs we see a failed installation and a removal of the server from a local group.
<PROBLEM SECONDARY SITE SERVER> was being removed from a local group – SMS_SiteToSiteConnection_[SITECODE]
We added the server back to the group and restarted the SMS_SITE_COMPONENT_MANAGER service.
Once this was restarted we reviewed the logs again.
<PROBLEM SECONDARY SITE SERVER> started processing and completing any installation of missing components.  Exit codes-0 for completed installations.
Sender.log started showing progress in transmitting the inventory and collected data from the workstations.
Results
BGB installed correctly.
<PROBLEM SECONDARY SITE SERVER> – shows green status in component settings in SCCM Console
Refreshed the SCCM Console on <PRIMARY SCCM SERVER>
<SECONDARY SITE> machines were now listed with the correct management point – <PROBLEM SECONDARY SITE SERVER> and are now showing as active.
Software deployment status has been updated for EU offices.