Output from rs_helproute at the Source Replication Server

Describes the rs_helproute output when it is executed at the source Replication Server while a route is being created.

rs_helproute Output at the Source Server
Message	Explanation	Suggested Actions
Route is being created. Source RS has not yet attempted to send the protocol message to the destination RS.	The source Replication Server cannot execute the rs_marker stored procedure against its Replication Server System Database (RSSD).	Restart the Replication Server. If restarting does not fix the route, 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 created. Either (1) RS is waiting for a route protocol message from the RSSD Replication Agent or (2) the RSSD Replication Agent inbound queue is not being processed.	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 created. Create route protocol message is waiting to be delivered to the destination.	The sending Replication Server is not processing its outbound queue.	Resume the route, if: The Replication Server Interface (RSI) experienced problems connecting to the destination Replication Server. The route was suspended. Verify whether: The destination Replication Server is up. The RSI for the destination Replication Server running at the source Replication Server.
Route is being created. Destination has not yet finished creating system table subscriptions.	The destination Replication Server is still creating subscriptions to system tables.	Make sure the destination Replication Server is running. Resume the route, if: The RSI experienced problems connecting to the destination Replication Server. The source could not send messages to the destination. The system suspends the route due to an error or the user explicitly suspends it. Check the list of system table subscriptions that still need to be created.