Output from rs_helproute at the source Replication Server

Table 4-5 describes the output when rs_helproute is executed at the source Replication Server.

Table 4-5: rs_helproute output at the source Replication Server

Message

What Does It Mean?

Suggested Actions

Route is being dropped. System table subscriptions are being dropped.

The destination Replication Server is trying to drop the system table subscriptions.

Check the list of system table subscriptions that still need to be dropped.

Route is being dropped. Waiting for the system table subscriptions to be dropped.

The system is in this state until the subscriptions are dropped.

The Replication Server should not be in this state for a long period of time. If it is, it may indicate a subscription problem. Refer to Chapter 5, “Subscription Problems”.

Route is being dropped. Source RS has not yet attempted to send the drop route protocol message to the destination RS.

The sender Replication Server could not execute the rs_marker stored procedure against its RSSD.

Restart the Replication Server.Check the RSSD and any related messages in the error logs. There may be a message in the error logs indicating some problem with the RSSD.

Route is being dropped. Drop route protocol message should be either in RSSD Replication Agent queue or in the inbound queue.

A message may be stuck between the RSSD log and the Replication Server inbound queue. The sender Replication Server executed the stored procedure, but the RSSD Replication Agent cannot forward it to the Replication Server.

Check if the RSSD Replication Agent is experiencing problems sending messages to the Replication Server. If not, restart the RSSD Replication Agent.

A message may be stuck between the inbound and outbound queues in the Replication Server.

Check if the Replication Server inbound queues are full or the distributor for the RSSD is not running. If neither of these problems exist, restart the RSSD Replication Agent.

Route is being dropped. Drop route protocol message is waiting to be delivered to the destination.

The sender Replication Server is not processing its outbound queue.

Is the destination Replication Server operating? Did the RSI (Replication Server Interface) experience problems trying to connect to the destination Replication Server? If so, it may be necessary to resume this route.