ConfigMgr Management Point fails to install with error 1603

Posted: November 21, 2014 in Configuration Manager, IIS, Solved, System Center
Tags: , , , , , ,

While installing multiple new ConfigMgr 2012 Management Points I was seeing a non-specific failure with an error code of 1603. Much troubleshooting and any web searches later, I discovered that there were in fact three different issues across the different servers that all failed with the same uninformative error.

  1. HTTPS binding missing in IIS
  2. Old WMI information from previous CM2007 client
  3. BITS not installed correctly

This was really quite bizarre. When I had found the “solution” and tried applying it to other servers I found that they had a different issue, which led to a mix of all three of the above. The old WMI issue being the most prevalent.


SOLUTION

Searching through the SMS\Logs\mpMSI.log for “return value 3” is the quickest way to locate the main cause in each case.

In all cases after applying the fix, simply wait and the role will attempt to reinstall every hour. If you are in a rush then you can either remove and re-add the role, or stop and start the “SMS_SITE_COMPONENT_MANAGER” to hurry things along

Missing Binding

When using HTTPS for Management points and other roles you need to bind https to the Default Web Site on the server before installing the role. In some cases our process for doing this failed

[16:01:46] The name of the web site is "Default Web Site".
MSI (s) (24!40) [16:01:46:090]: PROPERTY CHANGE: Adding CCMSHAREMODE property. Its value is '1'.
[16:01:46] The state of web site "Default Web Site" is Started.
[16:01:46] ERROR: Certificate is not configured on the website for SSL.
[16:01:46] ERROR: Validate IIS failed with 0x80004005.
[16:01:46] @@ERR:25055
MSI (s) (24!40) [16:01:46:200]: Product: ConfigMgr Management Point -- Error 25055. Internet Information Services Default Web Site is not correctly configured for SSL
Error 25055. Internet Information Services Default Web Site is not correctly configured for SSL
CustomAction CcmValidateServerConfig returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 16:01:46: CcmValidateServerConfig. Return value 3.
Action ended 16:01:46: INSTALL. Return value 3.

On each server where IIS is installed, edit the bindings on the default web site and add the https binding and attach the appropriate certificate

sslbinding

Old WMI information

The servers we are using had been built by an older ConfigMgr 2007 OSD task sequence and as a result had the 2007 client installed. Part of our process is to do an uninstall of the old client and install the new 2012 client. In some cases though it seems there are remnants of the old client left in WMI, and the Management Point being a special role in this regard doesn’t seem to like the old info.

In this situation, the error appears as a failure to compile the ccmexec_global.mof and other mof files

Failed to compile ‘C:\SMS_CCM\CcmExec_Global.mof’ (Phase: 3, Object: 5, Lines: 76 – 83, Error: 80041002) 
Failed to compile ‘C:\SMS_CCM\PolicyDefaults.mof’ (Phase: 3, Object: 4, Lines: 49 – 57, Error: 80041002) 
Failed to compile ‘C:\SMS_CCM\DataTransferService.mof’ (Phase: 3, Object: 5, Lines: 318 – 323, Error: 80041002) 
Failed to compile ‘C:\SMS_CCM\CcmExec_MP.mof’ (Phase: 3, Object: 1, Lines: 31 – 36, Error: 80041002)

To check if there is any existing WMI information, run the following powershell command

Get-WMIObject -namespace "root" -query "select * from __NameSpace where name = 'ccm'"

and if you see something like this:

PS C:\WINDOWS\system32> Get-WMIObject -namespace "root" -query "
Namespace where name = 'ccm'"

__GENUS          : 2
__CLASS          : __NAMESPACE
__SUPERCLASS     : __SystemClass
__DYNASTY        : __SystemClass
__RELPATH        : __NAMESPACE.Name="ccm"
__PROPERTY_COUNT : 1
__DERIVATION     : {__SystemClass}
__SERVER         : 
__NAMESPACE      : ROOT
__PATH           : \\\ROOT:__NAMESPACE.Name="ccm"
Name             : ccm
PSComputerName   :

Then you can run this to delete it:

Get-WMIObject -namespace "root" -query "select * from __NameSpace where name = 'ccm'" | remove-wmiobject

If you had already installed the CM2012 client agent, then you will most likely need to reinstall it after removing the WMI information.

BITS not installed correctly

On a couple of servers it was reporting an issue with BITS, even though it was installed and showing as a feature.

[16:07:47] The state of web site "Default Web Site" is Started.
[16:07:47] The installed certificate has a hash of length 20.
[16:07:47] @@ERR:25051
MSI (s) (AC!24) [16:07:47:727]: Product: ConfigMgr Management Point -- Error 25051. Internet Information Services BITS support is not installed
Error 25051. Internet Information Services BITS support is not installed
CustomAction CcmValidateServerConfig returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 16:07:47: CcmValidateServerConfig. Return value 3.
Action ended 16:07:47: INSTALL. Return value 3.

The solution here was to remove BITS, restart the server, and reinstall BITS.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s