PENDING SCCM/MECM Management point install keeps failing - CCM_Incoming Virtual Directory failed

[Alfred]

Hello all, I thought I could hopefully solve this with all the information already publicly available but it seems I can't.

We are having issues with the Management Point not installing correctly on our SCCM server that has the following roles;
Component server / Distribution Point / Management Point / Service Connection Point / Site server / Site system / SMS provider

So far we have tried the following;
1) Completely disable the Anti-virus software
2) Reinstall BITS
3) Check if the MECM client is installed (it's not as far as I can see)
4) Reinstall the MP role multiple times
5) Check if the IIS Default Site is running (it is)
6) Check if the BITS Server Extension / WebDAV extensions are allowed to run in IIS (they are)

The problem manifests itself as following in the MECM Site Status logs;

ID: 4963 Component: SMS_MP_CONTROL_MANAGER	MP Control Manager detected MPsetup has failed to create the CCM_Incoming Virtual Directory. Possible cause: The IIS IWAM account has expired, been disabled, or has invalid or too restrictive logon hours. You may verify this information by running the net user command line for the IWAM account. (i.e.: "net user IWAMMachineName) Solution: Use the output to verify that the account is enabled, and logon is possible during the time of installation. Note: You can use "net user" to modify the account properties. Possible cause: The IIS IUSR account has expired, been disabled, or has invalid or too restrictive logon hours. You may verify this information by running the net user command line for the IUSR account. (i.e.: "net user IWAMMachineName) Solution: Use the output to verify that the account is enabled, and logon is possible during the time of installation. Note: You can use "net user" to modify the account properties. Possible cause: The designated Web Site is disabled in IIS. Solution: Verify that the designated Web Site is enabled, and functioning properly.
ID: 1016 Component: SMS_MP_CONTROL_MANAGER	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.
ID: 4951 Component: 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.
ID: 1016 Component: SMS_NOTIFICATION_SERVER	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.

The logs can be seen in the replies (too many characters to post).

If anyone has valuable tips to solve these issues it would be highly appreciated, this has cost me multiple days already.

 

[Alfred]

mpMSI log;

---

MSI (s) (10:C0) [09:14:28:817]: Executing op: ComponentUnregister(ComponentId={823AF0E0-2CBE-4511-B309-64B0BF6EA406},ProductKey={DC097C51-F9C3-4B18-98C0-0F50FBD40B3C},BinaryType=1,)
MSI (s) (10:C0) [09:14:28:817]: Executing op: ComponentUnregister(ComponentId={19FDDCF2-7C28-462B-80E6-4C236CD9BE83},ProductKey={DC097C51-F9C3-4B18-98C0-0F50FBD40B3C},BinaryType=0,)
MSI (s) (10:C0) [09:14:28:817]: WIN64DUALFOLDERS: 'C:\Windows\system32\' will substitute 20 characters in 'C:\Windows\SysWOW64\ccmcore.dll' folder path. (mask argument = 1, the folder pair's iSwapAttrib member = 1).
MSI (s) (10:C0) [09:14:28:817]: Executing op: ComponentUnregister(ComponentId={A203678B-98C4-435D-8D15-6C300BB44838},ProductKey={DC097C51-F9C3-4B18-98C0-0F50FBD40B3C},BinaryType=1,)
MSI (s) (10:C0) [09:14:28:818]: Executing op: ComponentUnregister(ComponentId={7012789F-E1C9-4EDB-AF83-9EE2135AF357},ProductKey={DC097C51-F9C3-4B18-98C0-0F50FBD40B3C},BinaryType=1,)
MSI (s) (10:C0) [09:14:28:818]: Executing op: ActionStart(Name=CcmStopServiceRollback,Description=Calls CcmStartService. Starts the ccmexec service.,)
MSI (s) (10:C0) [09:14:28:821]: Executing op: CustomActionRollback(Action=CcmStopServiceRollback,ActionType=3329,Source=BinaryData,Target=CcmStartService,)
MSI (s) (10:8C) [09:14:28:825]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIA3E9.tmp, Entrypoint: CcmStartService
[9:14:28] WARNING: Failed to delete setup in progress time-stamp with error 0x80070002
MSI (s) (10:C0) [09:14:28:840]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=0)
MSI (s) (10:C0) [09:14:28:840]: Error in rollback skipped. Return: 5
[9:14:28] The service 'ccmexec' is not installed
MSI (s) (10:C0) [09:14:28:843]: Note: 1: 2318 2:
MSI (s) (10:C0) [09:14:28:861]: Note: 1: 2318 2:
MSI (s) (10:C0) [09:14:28:861]: No System Restore sequence number for this installation.
MSI (s) (10:C0) [09:14:28:861]: Unlocking Server
MSI (s) (10:C0) [09:14:28:864]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is '1'.
Action ended 9:14:28: INSTALL. Return value 3.
Property(S): UpgradeCode = {ABD0F60F-1622-4311-8989-106B60D784FF}
Property(S): SourceDir = D:\Program Files\Microsoft Configuration Manager\bin\x64\
Property(S): TARGETDIR = D:\Program Files\SMS_CCM\
Property(S): ALLUSERS = 1
Property(S): ErrorDialog = ErrorDialog
Property(S): ProductName = ConfigMgr Management Point
Property(S): ProductCode = {DC097C51-F9C3-4B18-98C0-0F50FBD40B3C}
Property(S): PackageCode = {004063FF-FF10-4041-87DE-EE508F276A56}
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductVersion = 5.00.9096.1000
Property(S): ProductLanguage = 1033
Property(S): AppDataFolder = C:\Windows\system32\config\systemprofile\AppData\Roaming\
Property(S): CcmRemoveIISApplicationPools = CCM Client Deployment Pool

....................

Property(S): SOURCEDIR = D:\Program Files\Microsoft Configuration Manager\bin\x64\
Property(S): SourcedirProduct = {DC097C51-F9C3-4B18-98C0-0F50FBD40B3C}
Property(S): LASTSTATESERIALNUM = 0
Property(S): CCMHTTPSPORT = 443
Property(S): CCMHTTPSSTATE = 0
Property(S): CCMHTTPPORT = 80
Property(S): ProductToBeRegistered = 1
MSI (s) (10:C0) [09:14:28:924]: Note: 1: 1708
MSI (s) (10:C0) [09:14:28:924]: Product: ConfigMgr Management Point -- Installation operation failed.

MSI (s) (10:C0) [09:14:28:924]: Windows Installer installed the product. Product Name: ConfigMgr Management Point. Product Version: 5.00.9096.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.

MSI (s) (10:C0) [09:14:28:931]: Deferring clean up of packages/files, if any exist
MSI (s) (10:C0) [09:14:28:931]: MainEngineThread is returning 1603
MSI (s) (10:70) [09:14:28:934]: RESTART MANAGER: Session closed.
MSI (s) (10:70) [09:14:28:934]: No System Restore sequence number for this installation.
=== Logging stopped: 1/10/2023 9:14:28 ===
MSI (s) (10:70) [09:14:28:937]: User policy value 'DisableRollback' is 0
MSI (s) (10:70) [09:14:28:937]: Machine policy value 'DisableRollback' is 0
MSI (s) (10:70) [09:14:28:937]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (10:70) [09:14:28:937]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (10:70) [09:14:28:938]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (10:70) [09:14:28:938]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (10:70) [09:14:28:938]: Destroying RemoteAPI object.
MSI (s) (10:C0) [09:14:28:938]: Custom Action Manager thread ending.
MSI (c) (04:20) [09:14:28:939]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (04:20) [09:14:28:940]: MainEngineThread is returning 1603
=== Verbose logging stopped: 1/10/2023 9:14:28 ===

MPSetup log;

---

<Tue Jan 10 09:10:12 2023> ====================================================================
<Tue Jan 10 09:10:12 2023> SMSMP Setup Started....
<Tue Jan 10 09:10:12 2023> Parameters: D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /install /siteserver:MECM1 SMSMP 0
<Tue Jan 10 09:10:12 2023> Installing Pre Reqs for SMSMP
<Tue Jan 10 09:10:12 2023> ======== Installing Pre Reqs for Role SMSMP ========
<Tue Jan 10 09:10:12 2023> Found 1 Pre Reqs for Role SMSMP
<Tue Jan 10 09:10:12 2023> Pre Req SqlNativeClient found.
<Tue Jan 10 09:10:12 2023> SqlNativeClient already installed (Product Code: {x}). Would not install again.
<Tue Jan 10 09:10:12 2023> Pre Req SqlNativeClient is already installed. Skipping it.
<Tue Jan 10 09:10:12 2023> ======== Completed Installation of Pre Reqs for Role SMSMP ========
<Tue Jan 10 09:10:12 2023> Installing the SMSMP
<Tue Jan 10 09:10:12 2023> Passed OS version check.
<Tue Jan 10 09:10:12 2023> IIS Service is installed.
<Tue Jan 10 09:10:12 2023> No versions of SMSMP are installed. Installing new SMSMP.
<Tue Jan 10 09:10:12 2023> Enabling MSI logging. mp.msi will log to D:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log
<Tue Jan 10 09:10:12 2023> 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=1024 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1
<Tue Jan 10 09:14:28 2023> mp.msi exited with return code: 1603
<Tue Jan 10 09:14:28 2023> Backing up D:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log to D:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log.LastError
<Tue Jan 10 09:14:28 2023> Fatal MSI Error - mp.msi could not be installed.
<Tue Jan 10 09:14:28 2023> ~RoleSetup().

 

[Alfred]

bgbisapMSI log;

---

MSI (s) (10:8C) [09:14:43:883]: Note: 1: 2318 2:
MSI (s) (10:8C) [09:14:43:884]: Executing op: ActionStart(Name=CcmUnregisterPerfCounters,Description=Removes performance counters gathered in the CcmUnregisterPerfCountersInit action,Template=[1])
MSI (s) (10:8C) [09:14:43:884]: Executing op: ActionStart(Name=CcmRemoveIISApplicationPools,,Template=[1])
MSI (s) (10:8C) [09:14:43:884]: Executing op: ActionStart(Name=CcmRemoveIISVirtualDirectories,Description=Removes IIS Virtual Directories found in CcmRemoveIISVirtualDirectoriesInit.,Template=[1])
MSI (s) (10:8C) [09:14:43:885]: Executing op: ActionStart(Name=ProcessComponents,Description=Updating component registration,)
MSI (s) (10:8C) [09:14:43:885]: Executing op: RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDLLs,SecurityDescriptor=BinaryData,BinaryType=1,,)
MSI (s) (10:8C) [09:14:43:885]: Executing op: RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDLLs,SecurityDescriptor=BinaryData,BinaryType=1,,)
MSI (s) (10:8C) [09:14:43:885]: Executing op: RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDLLs,SecurityDescriptor=BinaryData,BinaryType=0,,)
MSI (s) (10:8C) [09:14:43:885]: Executing op: RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDLLs,SecurityDescriptor=BinaryData,BinaryType=0,,)
MSI (s) (10:8C) [09:14:43:885]: Executing op: ComponentUnregister(ComponentId={9AE651B4-CCC2-4B53-92A5-F5909BC6413D},ProductKey={E292C902-FBA3-4950-A6EC-973F4D806941},BinaryType=1,)
MSI (s) (10:8C) [09:14:43:886]: Executing op: ComponentUnregister(ComponentId={8BE7475E-0900-46F2-A463-A11335062B96},ProductKey={E292C902-FBA3-4950-A6EC-973F4D806941},BinaryType=1,)
MSI (s) (10:8C) [09:14:43:886]: Executing op: ComponentUnregister(ComponentId={A4DFE491-763D-4D53-AC12-BBB763427240},ProductKey={E292C902-FBA3-4950-A6EC-973F4D806941},BinaryType=0,)
MSI (s) (10:8C) [09:14:43:886]: WIN64DUALFOLDERS: 'C:\Windows\system32\' will substitute 20 characters in 'C:\Windows\SysWOW64\BgbPerf.dll' folder path. (mask argument = 1, the folder pair's iSwapAttrib member = 1).
MSI (s) (10:8C) [09:14:43:886]: Executing op: ComponentUnregister(ComponentId={347EE521-8676-48F8-9983-78B55CA08582},ProductKey={E292C902-FBA3-4950-A6EC-973F4D806941},BinaryType=1,)
MSI (s) (10:8C) [09:14:43:887]: Executing op: ComponentUnregister(ComponentId={9CB0B34C-141F-47CC-B92F-750118703F43},ProductKey={E292C902-FBA3-4950-A6EC-973F4D806941},BinaryType=1,)
MSI (s) (10:8C) [09:14:43:887]: Executing op: ComponentUnregister(ComponentId={5E21B30A-CB4D-40FD-A915-50A36C819A8F},ProductKey={E292C902-FBA3-4950-A6EC-973F4D806941},BinaryType=1,)
MSI (s) (10:8C) [09:14:43:887]: Executing op: ComponentUnregister(ComponentId={BE7D2DD3-0EE8-4DEB-934A-0F1EC1C65120},ProductKey={E292C902-FBA3-4950-A6EC-973F4D806941},BinaryType=1,)
MSI (s) (10:8C) [09:14:43:888]: Executing op: ComponentUnregister(ComponentId={E8E8F2CE-782A-4BE6-B078-AA5866B12BF6},ProductKey={E292C902-FBA3-4950-A6EC-973F4D806941},BinaryType=0,)
MSI (s) (10:8C) [09:14:43:888]: WIN64DUALFOLDERS: 'C:\Windows\system32\' will substitute 20 characters in 'C:\Windows\SysWOW64\ccmperf.dll' folder path. (mask argument = 1, the folder pair's iSwapAttrib member = 1).
MSI (s) (10:8C) [09:14:43:888]: Executing op: ComponentUnregister(ComponentId={4AB00519-015E-4DBF-8CED-2AE7EE06D348},ProductKey={E292C902-FBA3-4950-A6EC-973F4D806941},BinaryType=1,)
MSI (s) (10:8C) [09:14:43:888]: Executing op: ComponentUnregister(ComponentId={B1B51247-61AD-4E10-9C18-7F0BF07C673A},ProductKey={E292C902-FBA3-4950-A6EC-973F4D806941},BinaryType=1,)
MSI (s) (10:8C) [09:14:43:888]: Executing op: ComponentUnregister(ComponentId={376A39B9-7527-4929-B788-8E076BEDCFE1},ProductKey={E292C902-FBA3-4950-A6EC-973F4D806941},BinaryType=1,)
MSI (s) (10:8C) [09:14:43:889]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=0)
MSI (s) (10:8C) [09:14:43:889]: Error in rollback skipped. Return: 5
MSI (s) (10:8C) [09:14:43:891]: Note: 1: 2318 2:
MSI (s) (10:8C) [09:14:43:893]: Note: 1: 2318 2:
MSI (s) (10:8C) [09:14:43:894]: No System Restore sequence number for this installation.
MSI (s) (10:8C) [09:14:43:894]: Unlocking Server
MSI (s) (10:8C) [09:14:43:898]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is '1'.
Action ended 9:14:43: INSTALL. Return value 3.

..........

Property(S): SMSCWSID = 1
Property(S): SOURCEDIR = D:\Program Files\Microsoft Configuration Manager\bin\x64\
Property(S): SourcedirProduct = {E292C902-FBA3-4950-A6EC-973F4D806941}
Property(S): ProductToBeRegistered = 1
MSI (s) (10:8C) [09:14:43:935]: Note: 1: 1708
MSI (s) (10:8C) [09:14:43:936]: Product: BGB http proxy -- Installation operation failed.

MSI (s) (10:8C) [09:14:43:936]: Windows Installer installed the product. Product Name: BGB http proxy. Product Version: 5.00.9096.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.

MSI (s) (10:8C) [09:14:43:939]: Deferring clean up of packages/files, if any exist
MSI (s) (10:8C) [09:14:43:939]: MainEngineThread is returning 1603
MSI (s) (10:70) [09:14:43:942]: RESTART MANAGER: Session closed.
MSI (s) (10:70) [09:14:43:942]: No System Restore sequence number for this installation.
=== Logging stopped: 1/10/2023 9:14:43 ===
MSI (s) (10:70) [09:14:43:945]: User policy value 'DisableRollback' is 0
MSI (s) (10:70) [09:14:43:945]: Machine policy value 'DisableRollback' is 0
MSI (s) (10:70) [09:14:43:945]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (10:70) [09:14:43:946]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (10:70) [09:14:43:946]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (10:70) [09:14:43:946]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (10:70) [09:14:43:947]: Destroying RemoteAPI object.
MSI (s) (10:48) [09:14:43:947]: Custom Action Manager thread ending.
MSI (c) (54:F0) [09:14:43:948]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (54:F0) [09:14:43:948]: MainEngineThread is returning 1603
=== Verbose logging stopped: 1/10/2023 9:14:43 ===

bgbsetup log;

---

<Tue Jan 10 09:14:42 2023> ====================================================================
<Tue Jan 10 09:14:42 2023> SMSBGB Setup Started....
<Tue Jan 10 09:14:42 2023> Parameters: D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /install /siteserver:MECM1 SMSBGB 0
<Tue Jan 10 09:14:42 2023> Installing Pre Reqs for SMSBGB
<Tue Jan 10 09:14:42 2023> ======== Installing Pre Reqs for Role SMSBGB ========
<Tue Jan 10 09:14:42 2023> Found 1 Pre Reqs for Role SMSBGB
<Tue Jan 10 09:14:42 2023> Pre Req SqlNativeClient found.
<Tue Jan 10 09:14:42 2023> SqlNativeClient already installed (Product Code: {x}). Would not install again.
<Tue Jan 10 09:14:42 2023> Pre Req SqlNativeClient is already installed. Skipping it.
<Tue Jan 10 09:14:42 2023> ======== Completed Installation of Pre Reqs for Role SMSBGB ========
<Tue Jan 10 09:14:42 2023> Installing the SMSBGB
<Tue Jan 10 09:14:42 2023> Passed OS version check.
<Tue Jan 10 09:14:42 2023> IIS Service is installed.
<Tue Jan 10 09:14:42 2023> No versions of SMSBGB are installed. Installing new SMSBGB.
<Tue Jan 10 09:14:42 2023> Enabling MSI logging. bgbisapi.msi will log to D:\Program Files\Microsoft Configuration Manager\logs\bgbisapiMSI.log
<Tue Jan 10 09:14:42 2023> Installing D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.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
<Tue Jan 10 09:14:43 2023> bgbisapi.msi exited with return code: 1603
<Tue Jan 10 09:14:43 2023> Backing up D:\Program Files\Microsoft Configuration Manager\logs\bgbisapiMSI.log to D:\Program Files\Microsoft Configuration Manager\logs\bgbisapiMSI.log.LastError
<Tue Jan 10 09:14:43 2023> Fatal MSI Error - bgbisapi.msi could not be installed.
<Tue Jan 10 09:14:43 2023> ~RoleSetup().

 

[Garth]

Hello all, I thought I could hopefully solve this with all the information already publicly available but it seems I can't.

We are having issues with the Management Point not installing correctly on our SCCM server that has the following roles;
Component server / Distribution Point / Management Point / Service Connection Point / Site server / Site system / SMS provider

So far we have tried the following;
1) Completely disable the Anti-virus software
2) Reinstall BITS
3) Check if the MECM client is installed (it's not as far as I can see)
4) Reinstall the MP role multiple times
5) Check if the IIS Default Site is running (it is)
6) Check if the BITS Server Extension / WebDAV extensions are allowed to run in IIS (they are)

The problem manifests itself as following in the MECM Site Status logs;

ID: 4963 Component: SMS_MP_CONTROL_MANAGER	MP Control Manager detected MPsetup has failed to create the CCM_Incoming Virtual Directory. Possible cause: The IIS IWAM account has expired, been disabled, or has invalid or too restrictive logon hours. You may verify this information by running the net user command line for the IWAM account. (i.e.: "net user IWAMMachineName) Solution: Use the output to verify that the account is enabled, and logon is possible during the time of installation. Note: You can use "net user" to modify the account properties. Possible cause: The IIS IUSR account has expired, been disabled, or has invalid or too restrictive logon hours. You may verify this information by running the net user command line for the IUSR account. (i.e.: "net user IWAMMachineName) Solution: Use the output to verify that the account is enabled, and logon is possible during the time of installation. Note: You can use "net user" to modify the account properties. Possible cause: The designated Web Site is disabled in IIS. Solution: Verify that the designated Web Site is enabled, and functioning properly.
ID: 1016 Component: SMS_MP_CONTROL_MANAGER	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.
ID: 4951 Component: 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.
ID: 1016 Component: SMS_NOTIFICATION_SERVER	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.

The logs can be seen in the replies (too many characters to post).

If anyone has valuable tips to solve these issues it would be highly appreciated, this has cost me multiple days already.

Since you didn't say, did you try each one of the solution listed?

 

[Garth]

mpMSI log;

---

MSI (s) (10:C0) [09:14:28:817]: Executing op: ComponentUnregister(ComponentId={823AF0E0-2CBE-4511-B309-64B0BF6EA406},ProductKey={DC097C51-F9C3-4B18-98C0-0F50FBD40B3C},BinaryType=1,)
MSI (s) (10:C0) [09:14:28:817]: Executing op: ComponentUnregister(ComponentId={19FDDCF2-7C28-462B-80E6-4C236CD9BE83},ProductKey={DC097C51-F9C3-4B18-98C0-0F50FBD40B3C},BinaryType=0,)
MSI (s) (10:C0) [09:14:28:817]: WIN64DUALFOLDERS: 'C:\Windows\system32\' will substitute 20 characters in 'C:\Windows\SysWOW64\ccmcore.dll' folder path. (mask argument = 1, the folder pair's iSwapAttrib member = 1).
MSI (s) (10:C0) [09:14:28:817]: Executing op: ComponentUnregister(ComponentId={A203678B-98C4-435D-8D15-6C300BB44838},ProductKey={DC097C51-F9C3-4B18-98C0-0F50FBD40B3C},BinaryType=1,)
MSI (s) (10:C0) [09:14:28:818]: Executing op: ComponentUnregister(ComponentId={7012789F-E1C9-4EDB-AF83-9EE2135AF357},ProductKey={DC097C51-F9C3-4B18-98C0-0F50FBD40B3C},BinaryType=1,)
MSI (s) (10:C0) [09:14:28:818]: Executing op: ActionStart(Name=CcmStopServiceRollback,Description=Calls CcmStartService. Starts the ccmexec service.,)
MSI (s) (10:C0) [09:14:28:821]: Executing op: CustomActionRollback(Action=CcmStopServiceRollback,ActionType=3329,Source=BinaryData,Target=CcmStartService,)
MSI (s) (10:8C) [09:14:28:825]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIA3E9.tmp, Entrypoint: CcmStartService
[9:14:28] WARNING: Failed to delete setup in progress time-stamp with error 0x80070002
MSI (s) (10:C0) [09:14:28:840]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=0)
MSI (s) (10:C0) [09:14:28:840]: Error in rollback skipped. Return: 5
[9:14:28] The service 'ccmexec' is not installed
MSI (s) (10:C0) [09:14:28:843]: Note: 1: 2318 2:
MSI (s) (10:C0) [09:14:28:861]: Note: 1: 2318 2:
MSI (s) (10:C0) [09:14:28:861]: No System Restore sequence number for this installation.
MSI (s) (10:C0) [09:14:28:861]: Unlocking Server
MSI (s) (10:C0) [09:14:28:864]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is '1'.
Action ended 9:14:28: INSTALL. Return value 3.
Property(S): UpgradeCode = {ABD0F60F-1622-4311-8989-106B60D784FF}
Property(S): SourceDir = D:\Program Files\Microsoft Configuration Manager\bin\x64\
Property(S): TARGETDIR = D:\Program Files\SMS_CCM\
Property(S): ALLUSERS = 1
Property(S): ErrorDialog = ErrorDialog
Property(S): ProductName = ConfigMgr Management Point
Property(S): ProductCode = {DC097C51-F9C3-4B18-98C0-0F50FBD40B3C}
Property(S): PackageCode = {004063FF-FF10-4041-87DE-EE508F276A56}
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductVersion = 5.00.9096.1000
Property(S): ProductLanguage = 1033
Property(S): AppDataFolder = C:\Windows\system32\config\systemprofile\AppData\Roaming\
Property(S): CcmRemoveIISApplicationPools = CCM Client Deployment Pool

....................

Property(S): SOURCEDIR = D:\Program Files\Microsoft Configuration Manager\bin\x64\
Property(S): SourcedirProduct = {DC097C51-F9C3-4B18-98C0-0F50FBD40B3C}
Property(S): LASTSTATESERIALNUM = 0
Property(S): CCMHTTPSPORT = 443
Property(S): CCMHTTPSSTATE = 0
Property(S): CCMHTTPPORT = 80
Property(S): ProductToBeRegistered = 1
MSI (s) (10:C0) [09:14:28:924]: Note: 1: 1708
MSI (s) (10:C0) [09:14:28:924]: Product: ConfigMgr Management Point -- Installation operation failed.

MSI (s) (10:C0) [09:14:28:924]: Windows Installer installed the product. Product Name: ConfigMgr Management Point. Product Version: 5.00.9096.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.

MSI (s) (10:C0) [09:14:28:931]: Deferring clean up of packages/files, if any exist
MSI (s) (10:C0) [09:14:28:931]: MainEngineThread is returning 1603
MSI (s) (10:70) [09:14:28:934]: RESTART MANAGER: Session closed.
MSI (s) (10:70) [09:14:28:934]: No System Restore sequence number for this installation.
=== Logging stopped: 1/10/2023 9:14:28 ===
MSI (s) (10:70) [09:14:28:937]: User policy value 'DisableRollback' is 0
MSI (s) (10:70) [09:14:28:937]: Machine policy value 'DisableRollback' is 0
MSI (s) (10:70) [09:14:28:937]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (10:70) [09:14:28:937]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (10:70) [09:14:28:938]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (10:70) [09:14:28:938]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (10:70) [09:14:28:938]: Destroying RemoteAPI object.
MSI (s) (10:C0) [09:14:28:938]: Custom Action Manager thread ending.
MSI (c) (04:20) [09:14:28:939]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (04:20) [09:14:28:940]: MainEngineThread is returning 1603
=== Verbose logging stopped: 1/10/2023 9:14:28 ===

MPSetup log;

---

<Tue Jan 10 09:10:12 2023> ====================================================================
<Tue Jan 10 09:10:12 2023> SMSMP Setup Started....
<Tue Jan 10 09:10:12 2023> Parameters: D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /install /siteserver:MECM1 SMSMP 0
<Tue Jan 10 09:10:12 2023> Installing Pre Reqs for SMSMP
<Tue Jan 10 09:10:12 2023> ======== Installing Pre Reqs for Role SMSMP ========
<Tue Jan 10 09:10:12 2023> Found 1 Pre Reqs for Role SMSMP
<Tue Jan 10 09:10:12 2023> Pre Req SqlNativeClient found.
<Tue Jan 10 09:10:12 2023> SqlNativeClient already installed (Product Code: {x}). Would not install again.
<Tue Jan 10 09:10:12 2023> Pre Req SqlNativeClient is already installed. Skipping it.
<Tue Jan 10 09:10:12 2023> ======== Completed Installation of Pre Reqs for Role SMSMP ========
<Tue Jan 10 09:10:12 2023> Installing the SMSMP
<Tue Jan 10 09:10:12 2023> Passed OS version check.
<Tue Jan 10 09:10:12 2023> IIS Service is installed.
<Tue Jan 10 09:10:12 2023> No versions of SMSMP are installed. Installing new SMSMP.
<Tue Jan 10 09:10:12 2023> Enabling MSI logging. mp.msi will log to D:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log
<Tue Jan 10 09:10:12 2023> 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=1024 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1
<Tue Jan 10 09:14:28 2023> mp.msi exited with return code: 1603
<Tue Jan 10 09:14:28 2023> Backing up D:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log to D:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log.LastError
<Tue Jan 10 09:14:28 2023> Fatal MSI Error - mp.msi could not be installed.
<Tue Jan 10 09:14:28 2023> ~RoleSetup().

Did you review the MSI log for errors?

 

[Prajwal Desai]

mp.msi exited with return code: 1603 - https://www.prajwaldesai.com/sccm-management-point-uninstall-error-1603/

 

[Alfred]

Since you didn't say, did you try each one of the solution listed?

What do you mean exactly? I have executed everything it says under "So far we have tried the following;"

"Did you review the MSI log for errors?"
Yes (the ones above, and my comment with the bgbsetup log / bgbisapMSI log is still pending apparently: "This message is awaiting moderator approval, and is invisible to normal visitors.") but the answer is not cut and dry.

The logs basically show very generic errors; return code: 1603 and the information above "type 3" is also not very useful or maybe that's just me.

That's why im asking for some assistance, the logs do not give me enough information.

 

[Alfred]

mp.msi exited with return code: 1603 - https://www.prajwaldesai.com/sccm-management-point-uninstall-error-1603/

Thank you for the reply Prajwal, but that's one of the first things I have checked.

The client is not installed on the server it seems, there's also no C:\Windows\CCMsetup folder or client entry in the installed software list.

Get-WMIObject -namespace "root" -query "SELECT * FROM __Namespace where name = 'ccm'" also gives no results

 

[Prajwal Desai]

Typically, exit code 1603 is caused either by client or a security software that blocks the installation/uninstallation of MP role. I have gone through the information and steps that you have performed but except the error code 1603, I am not seeing any other issues. Can you go to my contact form and send me the details. I will reply back and then we can discuss more on this.

 

[Alfred]

Typically, exit code 1603 is caused either by client or a security software that blocks the installation/uninstallation of MP role. I have gone through the information and steps that you have performed but except the error code 1603, I am not seeing any other issues. Can you go to my contact form and send me the details. I will reply back and then we can discuss more on this.

Sure, done.

 

[Alfred]

Never mind, issue has been fixed after a LOT of headaches.

What finally did it for us:
While troubleshooting I noticed the IIS admin service failed to start and that seemed to have something to do with the CCM_Incoming folder not getting created correctly (roll backs in the logs).

helped me investigate this further and since we had no working back-ups of the C23 system state key we needed to do some kind of reinstallation.

We decided to go with option 3;
"3) Un-install and then re-install just the "IIS 6 Metabase Compatibility" Role Service also works."

This in turn uninstalled a ton of features we needed so then we needed to reinstall those. WSUS (which was the last part for us) then gave us another bunch of inexplicable errors and log files that were empty.

But the above was not enough as apparently registry keys and some remnants still remained which we got rid of with:

WSUS reinstallation and post install configuration fails - Microsoft Q&A

Hi All, i had issue with synchronization of SCCM SUP with WSUS. after doing all troubleshooting steps nothing has worked. Hence uninstalled the SUP and WSUS. when i did the reinstallation of WSUS below two issue has been observed. Tools folder not…

learn.microsoft.com

and then most noteworthy:
"1) Open a PowerShell session as Administrator and uninstall WSUS completely with the following command:
Remove-WindowsFeature –Name UpdateServices,UpdateServices-DB,UpdateServices-RSAT,UpdateServices-API,UpdateServices-UI –IncludeManagementTools"

"2) Delete the registry key HKLM\SOFTWARE\Microsoft\Update Services"

"6) Run the System File Checker to find and repair any inconsistencies by typing the command below into the PowerShell prompt. SFC /scannow"

and

"7) *Reboot the server *"

you'd think that removing WSUS via programs and features would be enough but this was not the case. The other parts of this link were also covered in the first WSUS removal link (for us).

Then we finally managed to reinstall WSUS again (directly with a database connection, so not separate as that second link mentions).

Once that was completed we could successfully install the MECM MP role without errors and now have clients communicating too