otakuon
New Member
- Messages
- 1
- Reaction score
- 1
- Points
- 3
Been bashing my head against an issue for the past few days and starting to run out of ideas. Have searched high and low for answers which frequently bring be back to this site so I thought I would ask here.
I am trying to migrate our existing SCCM Current Branch (version 2203) site to a new site as the old site is still running on Windows 2012 R2 and SQL Server 2012 and thus can't install the more recent updates. I have a new site/primary site server installed and updated with the most recent version 2309 Hotfix rollup from 2/27/2024. I haven't started the migration yet because the installation of the management point is failing on the new server/primary site. The two components that won't install are SMS_CONTROL_MANAGER and SMS_NOTIFICATION_SERVER. In both cases, the reason for the failure is that the MSI installers bomb out with error code 1603. I am assuming the SMS_NOTIFICAION_SERVER installation (bgbisapi.msi) is failing because the MP.MSI installation is failing and thus the management point isn't actually fully installed. Here is what seems to be the relevant error in the mpmsi.log file:
MSI (s) (EC:70) [09:24:11:743]: Executing op: CustomActionSchedule(Action=CcmInitializePolicy,ActionType=3073,Source=BinaryData,Target=CcmInitializePolicy,CustomActionData=SMS:MP
efault:{0E1817A9-7219-4B56-911E-A17FF5353AE9}
10
C:\Program Files\SMS_CCM\PolicyAgentEndpoint.dll)
MSI (s) (EC:B0) [09:24:11:753]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI144C.tmp, Entrypoint: CcmInitializePolicy
[9:24:11] Initializing default policy
[9:24:12] Checking machine policies...
[9:24:12] Invoking policy agent to initialize policy
[9:24:13] ERROR: Policy agent failed to initialize (8004100E)
[9:24:13] @@ERR:25001
MSI (s) (EC!14) [09:24:13:366]: Product: ConfigMgr Management Point -- Error 25001. Setup failed due to unexpected circumstances
The error code is 8004100E
Error 25001. Setup failed due to unexpected circumstances
The error code is 8004100E
CustomAction CcmInitializePolicy returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (EC:70) [09:24:13:461]: Note: 1: 2265 2: 3: -2147287035
MSI (s) (EC:70) [09:24:13:461]: User policy value 'DisableRollback' is 0
MSI (s) (EC:70) [09:24:13:462]: Machine policy value 'DisableRollback' is 0
Action ended 9:24:13: InstallFinalize. Return value 3.
Looking up that specific error code (8004100E) kept bringing up BitLocker so I installed that feature on the server and even manually registered it with WMI by running mofcomp.exe c:\windows\system32\wbem\win32_encryptablevolume.mof . However, the mp.msi installation continues to fail with the exact same error.
When the installation runs, I do see it creates all the directories for the MP, but then they all get removed as the installation fails and it performs a rollback. However, it does leave one Log directory behind that contains a setuppolicyevaluator.log. Inside this file I see this:
<![LOG[==========[ ccminitializepolicy started in process 9992 ]==========]LOG]!><time="15:46:08.935+420" date="03-13-2024" component="setuppolicyevaluator" context="" type="1" thread="2288" file="PolicySetup.cpp:465">
<![LOG[Failed to load policy agent configuration. Error 0x80041010]LOG]!><time="15:46:08.991+420" date="03-13-2024" component="setuppolicyevaluator" context="" type="3" thread="2288" file="globals.cpp:418">
<![LOG[Failed to open namespace '\\.\root\ccm\policy\S_1_1_0\RequestedConfig'. Error 0x8004100e]LOG]!><time="15:46:09.000+420" date="03-13-2024" component="setuppolicyevaluator" context="" type="3" thread="2288" file="PolicyNamespaceCache.cpp:295">
<![LOG[Failed to initialize global objects. Error 0x8004100e]LOG]!><time="15:46:09.000+420" date="03-13-2024" component="setuppolicyevaluator" context="" type="3" thread="2288" file="globals.cpp:191">
Not sure if any of that is related or what it actually is referring to. The error code on that last entry is the same error code reported in the mpmsi.log file but still, doesn't really tell me much as to where to look that I haven't looked already. Any suggestions on how to resolve this or should I just trash this VM and start over again from scratch?
EDIT: Ok, well, I guess I just needed to try "one more thing". I took the "less-than-nuclear" option of rebuilding the WMI repository by stopping the WMI service, renaming the Repository folder under C:\Windows\System32\wbem to Repository.Old and then restarted the server. Once the server came back up and the component manager kicked off the install process again for the MP, both the mp.msi and bgbisapi.msi completed their install without errors (as suspected, the bgbisapi.msi was needing the mp.msi process to successfully install first). Will report back if anything changes.
I am trying to migrate our existing SCCM Current Branch (version 2203) site to a new site as the old site is still running on Windows 2012 R2 and SQL Server 2012 and thus can't install the more recent updates. I have a new site/primary site server installed and updated with the most recent version 2309 Hotfix rollup from 2/27/2024. I haven't started the migration yet because the installation of the management point is failing on the new server/primary site. The two components that won't install are SMS_CONTROL_MANAGER and SMS_NOTIFICATION_SERVER. In both cases, the reason for the failure is that the MSI installers bomb out with error code 1603. I am assuming the SMS_NOTIFICAION_SERVER installation (bgbisapi.msi) is failing because the MP.MSI installation is failing and thus the management point isn't actually fully installed. Here is what seems to be the relevant error in the mpmsi.log file:
MSI (s) (EC:70) [09:24:11:743]: Executing op: CustomActionSchedule(Action=CcmInitializePolicy,ActionType=3073,Source=BinaryData,Target=CcmInitializePolicy,CustomActionData=SMS:MP
efault:{0E1817A9-7219-4B56-911E-A17FF5353AE9}10
C:\Program Files\SMS_CCM\PolicyAgentEndpoint.dll)
MSI (s) (EC:B0) [09:24:11:753]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI144C.tmp, Entrypoint: CcmInitializePolicy
[9:24:11] Initializing default policy
[9:24:12] Checking machine policies...
[9:24:12] Invoking policy agent to initialize policy
[9:24:13] ERROR: Policy agent failed to initialize (8004100E)
[9:24:13] @@ERR:25001
MSI (s) (EC!14) [09:24:13:366]: Product: ConfigMgr Management Point -- Error 25001. Setup failed due to unexpected circumstances
The error code is 8004100E
Error 25001. Setup failed due to unexpected circumstances
The error code is 8004100E
CustomAction CcmInitializePolicy returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (EC:70) [09:24:13:461]: Note: 1: 2265 2: 3: -2147287035
MSI (s) (EC:70) [09:24:13:461]: User policy value 'DisableRollback' is 0
MSI (s) (EC:70) [09:24:13:462]: Machine policy value 'DisableRollback' is 0
Action ended 9:24:13: InstallFinalize. Return value 3.
Looking up that specific error code (8004100E) kept bringing up BitLocker so I installed that feature on the server and even manually registered it with WMI by running mofcomp.exe c:\windows\system32\wbem\win32_encryptablevolume.mof . However, the mp.msi installation continues to fail with the exact same error.
When the installation runs, I do see it creates all the directories for the MP, but then they all get removed as the installation fails and it performs a rollback. However, it does leave one Log directory behind that contains a setuppolicyevaluator.log. Inside this file I see this:
<![LOG[==========[ ccminitializepolicy started in process 9992 ]==========]LOG]!><time="15:46:08.935+420" date="03-13-2024" component="setuppolicyevaluator" context="" type="1" thread="2288" file="PolicySetup.cpp:465">
<![LOG[Failed to load policy agent configuration. Error 0x80041010]LOG]!><time="15:46:08.991+420" date="03-13-2024" component="setuppolicyevaluator" context="" type="3" thread="2288" file="globals.cpp:418">
<![LOG[Failed to open namespace '\\.\root\ccm\policy\S_1_1_0\RequestedConfig'. Error 0x8004100e]LOG]!><time="15:46:09.000+420" date="03-13-2024" component="setuppolicyevaluator" context="" type="3" thread="2288" file="PolicyNamespaceCache.cpp:295">
<![LOG[Failed to initialize global objects. Error 0x8004100e]LOG]!><time="15:46:09.000+420" date="03-13-2024" component="setuppolicyevaluator" context="" type="3" thread="2288" file="globals.cpp:191">
Not sure if any of that is related or what it actually is referring to. The error code on that last entry is the same error code reported in the mpmsi.log file but still, doesn't really tell me much as to where to look that I haven't looked already. Any suggestions on how to resolve this or should I just trash this VM and start over again from scratch?
EDIT: Ok, well, I guess I just needed to try "one more thing". I took the "less-than-nuclear" option of rebuilding the WMI repository by stopping the WMI service, renaming the Repository folder under C:\Windows\System32\wbem to Repository.Old and then restarted the server. Once the server came back up and the component manager kicked off the install process again for the MP, both the mp.msi and bgbisapi.msi completed their install without errors (as suspected, the bgbisapi.msi was needing the mp.msi process to successfully install first). Will report back if anything changes.
Last edited:
