Hi,

installed a SCCM 2012 R2 Primary site on a 2012 R2 server on the D: drive. Everything seemed to go well, however i am am now encountering issues with the SMS_NOTIFICATION_SERVER in that the site component manager is unable to install it. The status message viewer informs me that, "Site Component Manager failed to install this component, because the Microsoft Installer File for this component (bgbisapi.msi) could not install."

When i check the Bgbsetup.log, i see the following lines: 

<01/19/15 14:46:27> CTool::RegisterComPlusService: Failed to unregister D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll with .Net Fx 4.0
<01/19/15 14:46:27> CTool::RegisterComPlusService: run command line: "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegSvcs.exe" /extlb /tlb:"D:\Program Files\SMS_CCM\microsoft.configurationmanager.bgbserverchannel.tlb" "D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll"
<01/19/15 14:46:30> CTool::RegisterComPlusService: Failed to register D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll with .Net Fx 4.0
<01/19/15 14:46:30> Cannot register BGB server channel DLL D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll. Installation cannot continue.
<01/19/15 14:46:30> Fatal MSI Error - bgbisapi.msi could not be installed.

Having done a bit of reading, it seems a few other people have come accross this issue before:

https://rikkoss.wordpress.com/2013/12/11/tip-do-not-change-the-default-installation-location-for-configmgr-2012/

http://www.windows-noob.com/forums/index.php?/topic/7401-sms-notification-server-failed-critical-sccm-sp1-sql-2012-sp1/

The solution for these folks seems to be to edit 2 files in the .Net folder,InstallUtil.exe.config and Regsvc.exe.config, and insert the following code:

<runtime>

<loadFromRemoteSources enabled=true/>

</runtime>

However, this hasn't worked for me and i'm still getting stuck with the same error messages. Since i'd really like to avoid reinstalling SCCM on the C: drive, can anyone suggest any possible solutions to this issue? 

Check the bgbisapiMSI.log file. . . if you search for "Return Value 3" it should have a specific error above it.

Here is another forum post with a similar issue:

https://social.technet.microsoft.com/Forums/en-US/296ba167-5add-49d8-9c95-4d9249fba55f/bgbisapimsi-fatal-error-1603?forum=configmanagergeneral

As a side note, I install ConfigMgr on drives other than C: and do not typically have a problem with that at all.

Jeff

Hello,

Try the following solution:

1.Please navigate to C:\Windows\Microsoft.NET\Framework64\v4.0.30319\, make a backup copy of following files :
InstallUtil.exe.config
RegSvcs.exe.config
 
2.Edit the original files by adding the following under the configuration node:
 <runtime>
<loadFromRemoteSources enabled="true"/>
</runtime>
 
3.Restart the SMS_SITE_COMPONENT_MANAGER service.

4.Make sure the below services are running:
MSDTC
COM+ System Application

5.Please monitor BgbSetup.log.

Hi Jeff,

cheers for reply. Here's what i see in the log (i assume these are the relevant points):

MSI (s) (FC:EC) [13:54:04:865]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSID037.tmp, Entrypoint: CcmRegisterPerfCounters
[13:54:04] @@ERR:25001
Internal Error 25001. 80070057
MSI (s) (FC!10) [13:54:04:880]: Product: BGB http proxy -- Internal Error 25001. 80070057
CustomAction CcmRegisterPerfCounters returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox).............

.......MSI (s) (FC:70) [13:54:05:099]: Error in rollback skipped. Return: 5
MSI (s) (FC:70) [13:54:05:105]: Note: 1: 2318 2:  
MSI (s) (FC:70) [13:54:05:106]: No System Restore sequence number for this installation.
MSI (s) (FC:70) [13:54:05:106]: Unlocking Server
MSI (s) (FC:70) [13:54:05:111]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is '1'.
Action ended 13:54:05: INSTALL. Return value 3.

Sounds like my problem is similar to the one mentioned in that post but the solution mentioned in the post (Installing IIS Server Extension) doesn't apply since it's already in place. Am hoping to avoid having to edit the two config files if i can so do you have any further suggestions as to things i could try?

Thanks!

Since this component is failing, it is really a failed management point installation.  You could try removing the management point role and reinstall it.

Also, you could try reviewing the management point install logs:

mpsetup.log

mpMSI.log

In addition, make sure your site server computer account is in the local administrators group on the site server.

Jeff

Cheers for the swift reply. So removing the MP and reinstalling generated exactly the same errors as before. The site server was already a member of the local admin group. After that i edited both the config files as suggested by Daniel and then restarted the Site Component Manager Service. Again, this produced the exact same results.

Feel like i've hit a complete brick wall with this. Don't suppose you've got any other suggestions to try do you? Otherwise i guess it might be time to try a complete re-install since there's not much point in running SCCM if the MP is bust.....

Did you find any errors in the mpmsi.log or mpsetup.log?

You could try disabling User Account Control on the server temporarily.  So, remove the MP, disable UAC, reinstall the MP.

Also, make sure there are no GPOs applying to the server that might impact the installation.

Jeff

The MPsetup.log has this:

<01/20/15 16:28:11>         ======== Completed Installation of Pre Reqs for Role SMSMP ========
<01/20/15 16:28:11> Installing the SMSMP
<01/20/15 16:28:11> Passed OS version check.
<01/20/15 16:28:11> IIS Service is installed.
<01/20/15 16:28:11> No versions of SMSMP are installed.  Installing new SMSMP.
<01/20/15 16:28:11> Enabling MSI logging.  mp.msi will log to D:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log
<01/20/15 16:28:11> Installing D:\Program Files\Microsoft Configuration Manager\bin\x64\mp.msi CCMINSTALLDIR="D:\Program Files\SMS_CCM" CCMSERVERDATAROOT="D:\Program Files\Microsoft Configuration Manager" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1
<01/20/15 16:28:12> mp.msi exited with return code: 1603
<01/20/15 16:28:12> Backing up D:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log to D:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log.LastError
<01/20/15 16:28:12> Fatal MSI Error - mp.msi could not be installed.

and the MPmsi.log has this:

MSI (s) (B0:E0) [16:37:14:660]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI23F6.tmp, Entrypoint: CcmRegisterPerfCounters
[16:37:14] @@ERR:25001
Internal Error 25001. 80070057
MSI (s) (B0!F8) [16:37:14:676]: Product: BGB http proxy -- Internal Error 25001. 80070057
CustomAction CcmRegisterPerfCounters returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

Had a go at removing the MP, disabled the UAC and reinstalling the MP. Same result unfortunately...The server is temporarily housed in a block GPO OU so group policy shouldn't be an issue. Thanks for all the help so far!

Another thing to try would be uninstalling the MP, disable UAC, and then reboot the server.  Then reinstall the MP.  Not sure if the reboot will make a difference or not. . .

Jeff

Hello,

Have you tried the solution in my last post. I found it in another similar thread, and the solution could also be found in a blog:

http://myitforum.com/myitforumwp/2014/03/12/configmgr-2012-r2-notification-server-install-errors/

So I think it worth a try.

Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

Hi Daniel, thanks for the suggestion - i have already tried the aforementioned method and unfortunately it made no difference. Happy to try any other suggestions you may have though!

Jeff, wasn't a bad idea but unfortunately the disabling of UAC made no difference. Decided to rebuild the box from scratch and make damn sure the server won't get the 2007 client installed on it. See if that makes any difference....In the meanwhile, if anything else occurs please let me know. Thanks again!

Right, some good news. Having blown away the server and rebuilt it from scratch (ensuring first that the build task sequence wouldn't install the 2007 client and having disabled the client push in the 2007 SCCM site) i managed to install SCCM 2012 R2, on the D: drive, and all the components installed first time. 

Overall, i'd definitely blame the failed install of the MP components on the fact that the original server had the SCCM 2007 client installed on it. Even though i ran 'ccmsetup.exe /uninstall' i suspect that lurking somewhere in the system (probably in the wmi repository) were some remnants which were enough to confuse the SCCM 2012 R2 install.

Many thanks to both you guys for all the help. People who take the time to help other folk really make this site!

As a sidenote, while waiting for mt server to rebuild i found a powershell command which clears down all the old wmi entries which the sccm 2007 client leaves behind, even after it has been 'uninstalled':

Get-WMIObject -namespace "root" -query "SELECT * FROM __Namespace where name = 'ccm'" | remove-wmiobject

On a problem server, remove the MP, run the above in elevated powershell, re-install the MP. Haven't actually tested this but the logic seems sound and people on various sites have said it works. Forgot to jot down the url but i'll try and post it here when i manage to relocate it

• Marked as answer by Robot Archive Wednesday, January 21, 2015 11:18 AM
• Edited by Robot Archive Wednesday, January 21, 2015 3:53 PM

Yuck. I wish you would have mentioned that the 2007 client had been installed accidentally as the above is what I would have recommended straight off. At least it's sorted now.

Glad you got it sorted out.  I should have asked about the 2007 client. . .many of the other threads I read referenced that being a big issue.

Jeff

Thanks a lot for this. The above solution worked.

Uninstalled MP.

Ran Get-WMIObject -namespace "root" -query "SELECT * FROM __Namespace where name = 'ccm'" | remove-wmiobject in elevated mode.

Installed MP. the issue was resolved and MP installed successfully.

thank you.