locked
SMS Object Replication Manager Error RRS feed

  • Question

  • I have just upgraded our SCCM 2012 to SP1.

    I am now getting the following error occurring about every half hour

    "Object Replication Manager failed to process Object changes. These changes will be retried on next processing cycle."

    It goes on to say to check the previous status message for more details

    The 2 previoius messages were that the component needed re-installing and the next one was that the component was re-installed successfully.

    I have checked the objreplmgr.log and see no errors or notghing out of the ordinary.

    We are currently running a single Primary site with no child sites so there should be nothing to have to replicate to.

    Has anyone else had this issue or know where else I could look in the Configuration Manager to ferret out a few more details in order to fix this error?

    Thanks

    Wednesday, January 9, 2013 2:13 AM

Answers

  • objreplmgr.log *should* contain additional information. I've never seen a status message without a corresponding line in a logfile.

    Torsten Meringer | http://www.mssccmfaq.de

    • Proposed as answer by Garth JonesMVP Friday, February 6, 2015 1:32 PM
    • Marked as answer by Garth JonesMVP Tuesday, October 27, 2015 5:11 PM
    Wednesday, January 9, 2013 7:26 AM

All replies

  • objreplmgr.log *should* contain additional information. I've never seen a status message without a corresponding line in a logfile.

    Torsten Meringer | http://www.mssccmfaq.de

    • Proposed as answer by Garth JonesMVP Friday, February 6, 2015 1:32 PM
    • Marked as answer by Garth JonesMVP Tuesday, October 27, 2015 5:11 PM
    Wednesday, January 9, 2013 7:26 AM
  • I also have this problem with the two systems I have upgraded to SP1.  Both systems operate a single primary site.  Neither system has a corresponding line in the objreplmgr.log that indicates anything out of the ordinary.

    I'm suspicious this is a bug in SP1.

    Thursday, January 10, 2013 10:06 AM
  • I don't see this error in my lab, so it's not a general issue. Make sure to open a call at Microsoft CSS to let them have a look at it.

    Torsten Meringer | http://www.mssccmfaq.de

    Thursday, January 10, 2013 10:09 AM
  • Looking through the rcmctrl.log I can see that post SP1 install there are a number of entries that start:

    -------------------------------------------------------------

    Connecting to RCM.  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><01-09-2013 16:45:47.746+00><thread=5116 (0x13FC)>
    Initializing RCM.  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><01-09-2013 16:45:47.908+00><thread=5116 (0x13FC)>
    No parent or child sites found, so no replication channels to configure.~~  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><01-09-2013 16:45:48.167+00><thread=5116 (0x13FC)>
    Current number of active threads: 1  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><01-09-2013 16:45:48.212+00><thread=5116 (0x13FC)>
    Current number of active threads: 2  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><01-09-2013 16:45:48.213+00><thread=5116 (0x13FC)>
    AutoUpdate thread is starting...  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><01-09-2013 16:45:48.215+00><thread=4768 (0x12A0)>
    InvokeCloudSync thread is starting...  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><01-09-2013 16:45:48.219+00><thread=4684 (0x124C)>
    No connector role installed  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><01-09-2013 16:45:48.304+00><thread=4684 (0x124C)>
    Rcm control is waiting for file change notification or timeout after 3600 seconds.  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><01-09-2013 16:45:49.231+00><thread=5116 (0x13FC)>
    No connector role installed  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><01-09-2013 16:50:48.354+00><thread=4684 (0x124C)>
    No connector role installed  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><01-09-2013 16:55:49.159+00><thread=4684 (0x124C)>
    No connector role installed  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><01-09-2013 17:00:49.218+00><thread=4684 (0x124C)>
    No connector role installed  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><01-09-2013 17:05:49.276+00><thread=4684 (0x124C)>
    No connector role installed  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><01-09-2013 17:10:49.313+00><thread=4684 (0x124C)>
    No connector role installed  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><01-09-2013 17:15:49.423+00><thread=4684 (0x124C)>
    No connector role installed  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><01-09-2013 17:20:49.460+00><thread=4684 (0x124C)>
    No connector role installed  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><01-09-2013 17:25:49.511+00><thread=4684 (0x124C)>
    No connector role installed  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><01-09-2013 17:30:49.524+00><thread=4684 (0x124C)>
    No connector role installed  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><01-09-2013 17:35:49.585+00><thread=4684 (0x124C)>
    No connector role installed  $$<SMS_REPLICATION_CONFIGURATION_MONITOR><01-09-2013 17:40:49.624+00><thread=4684 (0x124C)>

    -------------------------------------------------------------

    This is brand new behaviour and started immediately after SP1 upgrade on both independent Primary Sites.

    Thursday, January 10, 2013 11:34 AM
  • That's fine as far as I can tell and does not indicate a problem.

    Torsten Meringer | http://www.mssccmfaq.de

    Thursday, January 10, 2013 12:40 PM