Fix SCCM Fatal MSI Error bgbisapi msi could not be installed , CustomAction CcmRegisterPerfCounters returned actual error code 1603

During the SCCM Management Point installation, you may encounter the error that the SMS Notification Server is not installed. In this scenario, client's status will appear with a question mark.

You may also try adding below lines to regsvcs.exe and InstallUtil.exe with their .config files by adding the following:

<runtime>

    <loadFromRemoteSources enabled="true"/>

</runtime>

However, this did not resolve the issue. 



In the Component Status within the SCCM console, the SMS Notification Server status will appear as Critical and display a message similar to the one below.



In the BgbSetup.log, you will see entries similar to the following.

 Fatal MSI Error - bgbisapi.msi could not be installed


In the BgbisapiMSI.log, you can see the following details.

Product: BGB http proxy -- Installation operation failed 

Windows Installer installed the product. Product Name: BGB http proxy. Product Version: 5.00.9128.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.


You will also see the error message similar to the one below

CustomAction CcmRegisterPerfCounters returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)






Try to manually install using the command below. (The path may be different in your environment; usually it is located under C:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi.)


msiexec /i "C:\SMS\bin\x64\bgbisapi.msi"


It will show the same error

Now here is the fix 


Navigate to the SMS_CCM path and rename the file causing the issue.



After renaming the file, run the command again: msiexec /i "C:\SMS\bin\x64\bgbisapi.msi"


Check the log file again; it should now show that the installation was completed successfully and service is running.







Popular Posts

Windows 11 24H2 Upgrade using Intune Feature Updates Policy

Image
How to Deploy Feature Updates Using Intune: A Step-by-Step Guide Microsoft Intune provides a streamlined method for managing Windows feature updates across your organization. In this guide, I'll walk through the essential prerequisites, policy creation steps, deployment, and monitoring process to ensure a smooth rollout of feature updates using Intune. 1. Verify Prerequisites Before you create a feature update policy, ensure the following prerequisites are met on the target devices: Device Enrollment : Devices must be enrolled in Intune, either as Microsoft Entra hybrid joined or Microsoft Entra joined . Supported OS : Devices must be running a supported version of Windows 10 or Windows 11 . Telemetry Settings : Devices must have the telemetry level set to Required . You can configure this via Devices > Windows> Configuration > Create Policy > Templates>  Device Restrictions > Reporting and Telemetry > Share Usage Data >Set as Required...
Read more

Deploying a Script through Intune to a Linux PC

Image
Can Intune Deploy Shell Scripts to Linux Devices? Yes! Just like deploying PowerShell scripts to Windows, Intune can also deploy shell scripts to Linux devices. In this blog, I'll walk you through the process of deploying shell scripts to Linux using Intune, making it easier to automate tasks and manage Linux endpoints efficiently. Prerequisites Before deploying a shell script via Intune, ensure the following requirements are met: 1. Intune and Microsoft Entra ID Your environment must have Microsoft Intune configured for device management. This setup enables secure enrollment and policy enforcement on Linux devices. 2. Linux Device Enrollment The Linux PC must be properly enrolled in Intune to receive policies and scripts. If the device is not enrolled, follow Microsoft's documentation on Linux enrollment in Intune. Deploying the Shell Script Once the prerequisites are met, follow these steps to deploy your shell script through Intune: Access Microsoft Intune Sign in to the ht...
Read more

Remove CCMCache, Windows.old, and Temp folders using Powershell script

Image
This PowerShell script automates the cleanup of: CCM Cache Files : Removes files older than 14 days from C:\Windows\ccmcache. Temporary Files : Cleans up files older than 14 days from the user’s temp folder ($env:Temp) and the system-wide temp folder (C:\Windows\Temp). Windows.old Folder : Deletes the Windows.old folder if it’s older than 14 days. This folder is typically created during a Windows upgrade and can take up significant disk space. The script also logs all actions to a log file (C:\TempCleanupLog.txt), making it easy to track what was deleted and troubleshoot any issues. # Define paths $ccmCachePath = "C:\Windows\ccmcache" $tempPath = "$env:Temp" $systemTempPath = "C:\Windows\Temp" $windowsOldPath = "C:\Windows.old" $logFile = "C:\TempCleanupLog.txt" # Change log file location if needed # Function to clean up files and directories older than a specific number of days function Clean-Ol...
Read more

SCCM Feature Upgrade Failure on HP Computers: Insufficient System Partition Disk Space (Error 0xC1900200 / -1047526912)

Image
When attempting to install Windows 11 feature upgrade via SCCM, you might notice that the update fails quickly, and under the “More Information” section, it shows the error code 0xC1900200 (-1047526912) . Additionally, you may observe that the update content is not downloading properly, and within a few minutes, the installation fails. I encountered this issue on several HP laptops and was able to identify the root cause and solution. The first step in troubleshooting should be reviewing the Panther logs , which can help pinpoint the exact blocker. You can find the Panther logs at the following location: C:\$WINDOWS.~BT\Sources\Panther Next, you need to check the XML files located in the Panther folder, as shown in the screenshot above. Look for the most recently created CompatData.xml file. This file corresponds to the latest SCCM feature update attempt that failed. Open this file using CMTrace , which makes it easier to read and highlight error codes or issues in a structured form...
Read more