Skip to content

HELP!......SMS_REPLICATION_CONFIGURATION_MONITOR

Featured Replies

Hi all, I am very grateful for your valuable support, thanks to you I learned much. Now I have a very important inquiry, I have one primary and several secondary site with replication, all going well, but there is nothing but one is giving me problems with replication apparently connectivity problems, I checked the link channel or constant pinging such a network and packet loss are minimal but well, very little, so this rule because there are other sites with more losses and the replication process is well maintained with them despite the lost, no longer to do because everything is well, if you need advice, no longer to review, here I leave a picture replication Monitor and log RCMCTRL.LOG .. I'm sure that will help me

===============================================================================================================================================================================================================================================================

 

Processing Replication success. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:18:35 AM 4928 (0x1340)

Rcm control is waiting for file change notification or timeout after 120 seconds. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:18:36 AM 4928 (0x1340)

DRS sync started. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:19:08 AM 6672 (0x1A10)

DRS change application started. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:19:08 AM 8656 (0x21D0)

Launching 3 sprocs on queue ConfigMgrDRSQueue and 0 sprocs on queue ConfigMgrDRSSiteQueue. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:19:08 AM 8656 (0x21D0)

There are 3 Drs Activations sprocs running. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:19:08 AM 8656 (0x21D0)

DRS sync started. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:20:08 AM 6672 (0x1A10)

DRS change application started. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:20:09 AM 8656 (0x21D0)

Launching 3 sprocs on queue ConfigMgrDRSQueue and 0 sprocs on queue ConfigMgrDRSSiteQueue. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:20:09 AM 8656 (0x21D0)

The asynchronous command finished with return message: [spDRSActivation finished at 11/3/2012 2:20:05 AM. End execute query finished at 11/3/2012 2:20:05 AM.]. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:20:09 AM 8656 (0x21D0)

The asynchronous command finished with return message: [spDRSActivation finished at 11/3/2012 2:20:06 AM. End execute query finished at 11/3/2012 2:20:06 AM.]. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:20:09 AM 8656 (0x21D0)

There are 3 Drs Activations sprocs running. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:20:09 AM 8656 (0x21D0)

Wait for inbox notification timed out. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:20:36 AM 4928 (0x1340)

Cleaning the RCM inbox if there are any *.RCM files for further change notifications.... SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:20:36 AM 4928 (0x1340)

Initializing RCM. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:20:36 AM 4928 (0x1340)

Processing Replication SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:20:36 AM 4928 (0x1340)

Running configuration EnsureServiceBrokerEnabled. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:20:36 AM 4928 (0x1340)

Running configuration EnsureServiceBrokerQueuesAreEnabled. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:20:36 AM 4928 (0x1340)

Processing replication pattern global_proxy. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:20:36 AM 4928 (0x1340)

Summarizing all replication links for monitoring UI. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:20:37 AM 4928 (0x1340)

The current site status: ReplicationActive. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:20:37 AM 4928 (0x1340)

Processing Replication success. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:20:37 AM 4928 (0x1340)

Rcm control is waiting for file change notification or timeout after 120 seconds. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:20:38 AM 4928 (0x1340)

DRS sync started. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:21:08 AM 6672 (0x1A10)

DRS change application started. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:21:09 AM 8656 (0x21D0)

Launching 3 sprocs on queue ConfigMgrDRSQueue and 0 sprocs on queue ConfigMgrDRSSiteQueue. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:21:09 AM 8656 (0x21D0)

There are 3 Drs Activations sprocs running. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:21:09 AM 8656 (0x21D0)

DRS sync started. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:22:09 AM 6672 (0x1A10)

DRS change application started. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:22:09 AM 8656 (0x21D0)

Launching 3 sprocs on queue ConfigMgrDRSQueue and 0 sprocs on queue ConfigMgrDRSSiteQueue. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:22:09 AM 8656 (0x21D0)

The asynchronous command finished with return message: [spDRSActivation finished at 11/3/2012 2:21:30 AM. End execute query finished at 11/3/2012 2:21:30 AM.]. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:22:09 AM 8656 (0x21D0)

There are 3 Drs Activations sprocs running. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:22:09 AM 8656 (0x21D0)

Wait for inbox notification timed out. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:22:38 AM 4928 (0x1340)

Cleaning the RCM inbox if there are any *.RCM files for further change notifications.... SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:22:38 AM 4928 (0x1340)

Initializing RCM. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:22:38 AM 4928 (0x1340)

Processing Replication SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:22:38 AM 4928 (0x1340)

Running configuration EnsureServiceBrokerEnabled. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:22:38 AM 4928 (0x1340)

Running configuration EnsureServiceBrokerQueuesAreEnabled. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:22:38 AM 4928 (0x1340)

Processing replication pattern global_proxy. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:22:38 AM 4928 (0x1340)

Summarizing all replication links for monitoring UI. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:22:38 AM 4928 (0x1340)

The current site status: ReplicationActive. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:22:39 AM 4928 (0x1340)

Processing Replication success. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:22:39 AM 4928 (0x1340)

Rcm control is waiting for file change notification or timeout after 120 seconds. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:22:40 AM 4928 (0x1340)

DRS sync started. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:23:09 AM 6672 (0x1A10)

DRS change application started. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:23:09 AM 8656 (0x21D0)

Launching 3 sprocs on queue ConfigMgrDRSQueue and 0 sprocs on queue ConfigMgrDRSSiteQueue. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:23:09 AM 8656 (0x21D0)

There are 3 Drs Activations sprocs running. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:23:09 AM 8656 (0x21D0)

DRS sync started. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:24:09 AM 6672 (0x1A10)

DRS change application started. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:24:09 AM 8656 (0x21D0)

Launching 3 sprocs on queue ConfigMgrDRSQueue and 0 sprocs on queue ConfigMgrDRSSiteQueue. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:24:09 AM 8656 (0x21D0)

The asynchronous command finished with return message: [spDRSActivation finished at 11/3/2012 2:23:58 AM. End execute query finished at 11/3/2012 2:23:58 AM.]. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:24:09 AM 8656 (0x21D0)

The asynchronous command finished with return message: [spDRSActivation finished at 11/3/2012 2:23:59 AM. End execute query finished at 11/3/2012 2:23:59 AM.]. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:24:09 AM 8656 (0x21D0)

There are 3 Drs Activations sprocs running. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:24:09 AM 8656 (0x21D0)

Wait for inbox notification timed out. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:24:40 AM 4928 (0x1340)

Cleaning the RCM inbox if there are any *.RCM files for further change notifications.... SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:24:40 AM 4928 (0x1340)

Initializing RCM. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:24:40 AM 4928 (0x1340)

Processing Replication SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:24:40 AM 4928 (0x1340)

Running configuration EnsureServiceBrokerEnabled. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:24:40 AM 4928 (0x1340)

Running configuration EnsureServiceBrokerQueuesAreEnabled. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:24:40 AM 4928 (0x1340)

Processing replication pattern global_proxy. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:24:40 AM 4928 (0x1340)

Summarizing all replication links for monitoring UI. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:24:40 AM 4928 (0x1340)

The current site status: ReplicationActive. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:24:40 AM 4928 (0x1340)

Processing Replication success. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:24:40 AM 4928 (0x1340)

Rcm control is waiting for file change notification or timeout after 120 seconds. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:24:41 AM 4928 (0x1340)

DRS sync started. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:25:09 AM 6672 (0x1A10)

DRS change application started. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:25:10 AM 8656 (0x21D0)

Launching 3 sprocs on queue ConfigMgrDRSQueue and 0 sprocs on queue ConfigMgrDRSSiteQueue. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:25:10 AM 8656 (0x21D0)

There are 3 Drs Activations sprocs running. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:25:10 AM 8656 (0x21D0)

DRS sync started. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:26:09 AM 6672 (0x1A10)

DRS change application started. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:26:10 AM 8656 (0x21D0)

Launching 3 sprocs on queue ConfigMgrDRSQueue and 0 sprocs on queue ConfigMgrDRSSiteQueue. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:26:10 AM 8656 (0x21D0)

The asynchronous command finished with return message: [spDRSActivation finished at 11/3/2012 2:25:25 AM. End execute query finished at 11/3/2012 2:25:25 AM.]. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:26:10 AM 8656 (0x21D0)

There are 3 Drs Activations sprocs running. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:26:10 AM 8656 (0x21D0)

Wait for inbox notification timed out. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:26:42 AM 4928 (0x1340)

Cleaning the RCM inbox if there are any *.RCM files for further change notifications.... SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:26:42 AM 4928 (0x1340)

Initializing RCM. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:26:42 AM 4928 (0x1340)

Processing Replication SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:26:42 AM 4928 (0x1340)

Running configuration EnsureServiceBrokerEnabled. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:26:42 AM 4928 (0x1340)

Running configuration EnsureServiceBrokerQueuesAreEnabled. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:26:42 AM 4928 (0x1340)

Processing replication pattern global_proxy. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:26:42 AM 4928 (0x1340)

Summarizing all replication links for monitoring UI. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:26:42 AM 4928 (0x1340)

The current site status: ReplicationActive. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:26:42 AM 4928 (0x1340)

Processing Replication success. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:26:42 AM 4928 (0x1340)

Rcm control is waiting for file change notification or timeout after 120 seconds. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:26:43 AM 4928 (0x1340)

DRS sync started. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:27:10 AM 6672 (0x1A10)

DRS change application started. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:27:10 AM 8656 (0x21D0)

Launching 3 sprocs on queue ConfigMgrDRSQueue and 0 sprocs on queue ConfigMgrDRSSiteQueue. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:27:10 AM 8656 (0x21D0)

There are 3 Drs Activations sprocs running. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:27:10 AM 8656 (0x21D0)

DRS sync started. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:28:10 AM 6672 (0x1A10)

DRS change application started. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:28:10 AM 8656 (0x21D0)

Launching 3 sprocs on queue ConfigMgrDRSQueue and 0 sprocs on queue ConfigMgrDRSSiteQueue. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:28:10 AM 8656 (0x21D0)

The asynchronous command finished with return message: [spDRSActivation finished at 11/3/2012 2:27:29 AM. End execute query finished at 11/3/2012 2:27:29 AM.]. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:28:10 AM 8656 (0x21D0)

The asynchronous command finished with return message: [spDRSActivation finished at 11/3/2012 2:27:14 AM. End execute query finished at 11/3/2012 2:27:14 AM.]. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:28:10 AM 8656 (0x21D0)

There are 3 Drs Activations sprocs running. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:28:10 AM 8656 (0x21D0)

Wait for inbox notification timed out. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:28:43 AM 4928 (0x1340)

Cleaning the RCM inbox if there are any *.RCM files for further change notifications.... SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:28:43 AM 4928 (0x1340)

Initializing RCM. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:28:43 AM 4928 (0x1340)

Processing Replication SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:28:44 AM 4928 (0x1340)

Running configuration EnsureServiceBrokerEnabled. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:28:44 AM 4928 (0x1340)

Running configuration EnsureServiceBrokerQueuesAreEnabled. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:28:44 AM 4928 (0x1340)

Running configuration RemoveDuplicateSSBServices. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:28:44 AM 4928 (0x1340)

Processing replication pattern global_proxy. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:28:44 AM 4928 (0x1340)

Summarizing all replication links for monitoring UI. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:28:44 AM 4928 (0x1340)

The current site status: ReplicationActive. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:28:44 AM 4928 (0x1340)

Processing Replication success. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:28:44 AM 4928 (0x1340)

Rcm control is waiting for file change notification or timeout after 120 seconds. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:28:45 AM 4928 (0x1340)

DRS sync started. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:29:10 AM 6672 (0x1A10)

DRS change application started. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:29:10 AM 8656 (0x21D0)

Launching 3 sprocs on queue ConfigMgrDRSQueue and 0 sprocs on queue ConfigMgrDRSSiteQueue. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:29:10 AM 8656 (0x21D0)

There are 3 Drs Activations sprocs running. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:29:10 AM 8656 (0x21D0)

DRS sync started. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:30:10 AM 6672 (0x1A10)

DRS change application started. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:30:11 AM 8656 (0x21D0)

Launching 3 sprocs on queue ConfigMgrDRSQueue and 0 sprocs on queue ConfigMgrDRSSiteQueue. SMS_REPLICATION_CONFIGURATION_MONITOR 11/3/2012 2:30:11 AM 8656 (0x21D0)

The asynchronous command finished with retur :wacko::wacko: :wacko: :wacko: :wacko: :wacko: :wacko:

post-17403-0-13982500-1351956601_thumb.png

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.