Known Issue: Secondary Site installation failure with Cumulative Update 2

Known Issue: Secondary Site installation failure with Cumulative Update 2

  • Comments 9
  • Likes

Updated 7/15/2013 -  We have released a hotfix that resolves this issue.  It is available for download here:  Please follow the instructions in the KB article to install the hotfix.

Updated 7/5/2013 - see manual cleanup procedure

Updated 7/3/2013 - see workaround #1

We have confirmed an issue with Cumulative Update 2 (CU2) for System Center 2012 Configuration Manager Service Pack 1 that affects new secondary site installations.

This issue does not affect upgrades of existing secondary sites, or any other aspects of the Configuration Manager hierarchy. 

Problem Description and Symptoms

  1. You installed System Center 2012 Configuration Manager SP1.
  2. You applied the Cumulative Update 2 (KB2854009) in the hierarchy.
  3. You installed a new secondary site or tried to recover an old secondary site using the Installation Source Files option: “Copy installation source files over the network from the parent site server”.    

The ConfigMgrSetup.log file will contain errors similar to the following after an installation attempt:


INFO: SQL Server Script: Creating object spupdatemessageactivity~

INFO: Configuring database replication tables..

*** [42000][50000][Microsoft][SQL Server Native Client 11.0][SQL Server]Object 'PullDPResponse' does not exist : spConfigureReplication

ERROR: Failed to execute dbo.spConfigureReplication.

ERROR: Failed to configure SQL Server replication tables.



You can use either of the following workarounds to install a secondary site.

  1. Using the Create Secondary Site Wizard, change the Installation Source Files setting to another location, instead of the parent primary site.
    1. Create a shared folder with the System Center 2012 Configuration Manager SP1 CD and Redist folders. Download the prerequisite distributable files for the Configuration Manager installation and copy them to <SP1CDShare>\SMSSETUP\Redist\. (update 7/3/2013:  Copy sqlncli.msi from redist folder to smssetup\bin\x64) For additional instructions see
    2. Run the Create Secondary Site Wizard to install a secondary site.
    3. On the page Installation Source Files, choose “Use the source files at the following network location”, and specify the CD share folder.


  1. Replace the ReplicationConfiguration.xml file on the primary site with the original one from the SP1 CD.
    1. Find ReplicationConfiguration.xml on the SP1 CD, and overwrite the file on your primary site (<SMSROOT>\bin\x64) with the version from the SP1 CD. WARNING: DO NOT EDIT THIS FILE as editing will change the timestamp and prevent future servicing updates to the file.
    2. Restart the SMS_EXECUTIVE service.

 You should be able to deploy the secondary site on a clean machine now.

 If the secondary site installation has failed, you will need to manually clean up the following before you attempt to reinstall.  To do this:

  • Delete the SMS registry key on the secondary site machine - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS
  • Delete the database created on the secondary site machine to ensure the data files are removed.
  • (update 7/5/2013) If the database is a SQL Express version, uninstall the "Microsoft SQL Server 2012 (64-bit)" from Add/Remove Programs (ARP).

Note: you still need to apply the Cumulative Update 2 on your secondary site after the installation.

We will update this blog entry with additional details when available. Thank you for your patience.


--Configuration Manager Sustained Engineering

 This posting is provided "AS IS" with no warranties and confers no rights.


Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Thank you for response!

    I will try secondary workaround :)

  • Thank you very much

  • Can you confirm this is working?

  • Yes! Fully working now. (5+ secondary sites are installed in our hierarchy)

  • There's a different issue after applying CU2 that affects those that have multicast enabled on DP before applying. CU2 fixes the multicast issue where OSD multicast wasn't working if it started when in Windows OS. PXE / boot media it worked fine. CU2 fixes this. However there's an issue that wasn't covered on the CU2 install steps. If you have multicast enabled on DP, apply CU2 you will find that multicast now doesn't work in PXE / boot media or Win OS either. This is because applying CU2 breaks the connection of the multicast account and SQL server. If you go to DP and Multicast settings then check the account used for Multicast then "test connection" you will find the connection to the SQL server and multicast account is broken. You must re-add the multicast account password and then "validate" and "test connection" to SQL server on the DP. Then OSD multicast will work as expected after CU2 in PXE / Boot media and Win OS. I have confirmed this both in my isolated test lab and our production environment. It would have been good to know this up front as it took some time to figure why multicast was not working in any form after CU2. It was because a re-validation of the multicast account to SQL server on the DP setting was required. I hope this helps someone

  • @Leo Bounds.  Thanks for the report.  The issue is actually not specific to CU2.  It unfortunately happens every time the MCS.msi gets updated.  A KB would be good until we can resolve it.

  • I have attempted the above proceedures with NO luck looking for additional assistance.

  • @Leo Bounds, we have just published a post for the multicast issue here:

  • Thank You, Terima Kasih!