locked
Primary to CAS replication 'Link is being configured' RRS feed

  • Question

  • A new primary site has been added to our hierarchy at the beginning of the week and the status of the replication link is still 'Link is being configured' for site data. Global data is active in both directions.

    Looking at the Initialization and replication detail on the new primary everything has green ticks next to it and looks good, but looking at the CAS, Hardware_Inventory has a question mark next to it in the initialization detail.

    There are no errors in rcmctrl.log on the primary but the CAS rcmctrl.log has the following lines once a minute:

    Checking if initialization request is needed for replication group Hardware_Inventory from site FIA. SMS_REPLICATION_CONFIGURATION_MONITOR 14/08/2015 11:34:37 8196 (0x2004)
    Table Add_Remove_Programs_64_DATA_RCM doesn't exist yet, wait for it get created and will check DRS stored procedure in next cycle. SMS_REPLICATION_CONFIGURATION_MONITOR 14/08/2015 11:34:37 8196 (0x2004)
    Error: Could not create Drs initialization stored procedures or functions for table Add_Remove_Programs_64_DATA, will retry on next cycle. SMS_REPLICATION_CONFIGURATION_MONITOR 14/08/2015 11:34:37 8196 (0x2004)
    Processing Replication success. SMS_REPLICATION_CONFIGURATION_MONITOR 14/08/2015 11:34:38 9096 (0x2388)

    If I run the replication link analyser I get the message that replication initialization is in progress for the replication group Hardware_Inventory and it might take several hours, but this has been going on for several days and the new primary so far only has two clients installed.

    Any ideas what to do?

    Friday, August 14, 2015 11:01 AM

Answers

  • In the end we fixed it doing the following:

    -Remove distributed views from the UK primary-CAS link (This caused both links to fail)

    -Build new CAS and do site recovery using UK primary as the source site

    Replication then started working for links to both primary sites.

    We were then able to do the R2 SP1 install.

    • Marked as answer by adbar Friday, September 18, 2015 10:42 AM
    Friday, September 18, 2015 10:42 AM

All replies

  • These issues are kind of hard to troubleshoot without having information about your setup.

    I suggest that you read this FAQ, it has a lot of useful of information go through various troubleshooting options :

    http://blogs.technet.com/b/umairkhan/archive/2014/03/25/configmgr-2012-drs-troubleshooting-faqs.aspx

    http://blogs.technet.com/b/sudheesn/archive/2012/10/21/drs-initialization-in-configuration-manager-2012.aspx


    Benoit Lecours | Blog: System Center Dudes


    Friday, August 14, 2015 11:05 AM
  • Thanks, I've been looking through those two links already and I feel like I've gone as far as I can with them.

    The RLA shows that replication is initializing for Hardware_Inventory (this has been going on for several days) It does not suggest anything else.

    The replication detail in the console (on the CAS and the affected primary) looks good other than a question mark next to Hardware_Inventory in the Initialization detail on the CAS console. Everything else shows as 100% initialized.

    RMCtrl.log shows no errors on the primary. On the CAS it shows the errors I already mentioned:

     Table Add_Remove_Programs_64_DATA_RCM doesn't exist yet, wait for it get created and will check DRS stored procedure in next cycle.

     Error: Could not create Drs initialization stored procedures or functions for table Add_Remove_Programs_64_DATA, will retry on next cycle. 

    (The table Add_Remove_Programs_64_DATA_RCM doesn't seem to exist on the CAS or either of our primaries)

    If there is any more information I can give you about our setup let me know, but briefly we have a CAS and Primary in the UK that have been running for a while and we have recently added another primary in the USA. The UK primary is set up to use distributed views for hardware inventory but the US one is not.

    Friday, August 14, 2015 12:36 PM
  • What's the link speed between US and UK ? What SCCM version are you using ? I've already seen this kind of issues between a CAS and Primary with slow links. The initial replication took days to complete.

    Benoit Lecours | Blog: System Center Dudes

    Friday, August 14, 2015 12:57 PM
  • It's a fairly fast link and the looking at the initialization detail for all of the other replication groups the status went to 'Succeeded' very quickly. Nothing much seems to be going on in the RCM inbox. Have you got any idea how to fix the error message about Add_Remove_Programs_64_DATA and Add_Remove_Programs_64_DATA_RCM ? I think they are part of the Hardware_Inventory group that will not finish initialising. This appears once a minute:


    • Edited by adbar Tuesday, August 18, 2015 8:24 AM
    Tuesday, August 18, 2015 8:23 AM
  • I forgot to reply to your other question - we are running R2 cu5. I'd like to upgrade to sp1 once we know everything is working as it should. We also have another site to set up .
    Tuesday, August 18, 2015 8:29 AM
  • Looking through VLogs, it seems that it is the failure to create the Add_Remove_Programs_64_DATA stored proc that is stopping hardware_inventory from initializing.:

    ERROR: Could not create initialization stored procedures or functions for table Add_Remove_Programs_64_DATA. Failed to create init request for replication group Hardware_Inventory for subscriber CAS. Will retry on next cycle.

    Tuesday, August 18, 2015 2:44 PM
  • Yes, I know this is an old post, but I’m trying to clean them up. Did you solve this problem, if so what was the solution?


    Garth Jones | My blogs: Enhansoft and Old Blog site | Twitter: @GarthMJ

    Saturday, August 29, 2015 5:17 PM
  • Since no one has answer this post, I recommend opening  a support case with Microsoft Customer Support Services (CSS) as they can work with you to solve this problem.


    Garth Jones | My blogs: Enhansoft and Old Blog site | Twitter: @GarthMJ

    • Proposed as answer by Garth JonesMVP Saturday, September 5, 2015 4:14 PM
    Saturday, September 5, 2015 4:14 PM
  • In the end we fixed it doing the following:

    -Remove distributed views from the UK primary-CAS link (This caused both links to fail)

    -Build new CAS and do site recovery using UK primary as the source site

    Replication then started working for links to both primary sites.

    We were then able to do the R2 SP1 install.

    • Marked as answer by adbar Friday, September 18, 2015 10:42 AM
    Friday, September 18, 2015 10:42 AM