Applies To: SQL Server 2016
|Product Name||SQL Server|
|Component||SQL Server Database Engine|
|Message Text||Agent shutdown. For more information, see the SQL Server Agent job history for job '%s'.|
A replication agent has shut down without writing a reason to the appropriate history table, or the agent was shut down while in the middle of a process.
Restart the agent to see whether it will now run without failures. For more information, see Start and Stop a Replication Agent (SQL Server Management Studio) and Replication Agent Executables Concepts.
Check the agent history and job history for other errors that occurred around the same time. For information about how to view agent status and error details in Replication Monitor, see the following topics:
For the Snapshot Agent, Log Reader Agent, and Queue Reader Agent, see View Information and Perform Tasks for the Agents Associated With a Publication (Replication Monitor).
For the Distribution Agent and Merge Agent, see View Information and Perform Tasks for the Agents Associated With a Subscription (Replication Monitor).
Verify that basic connectivity is working between the computers that are accessed by the agent, and then connect to each computer by using a utility, such as the sqlcmd utility. When you connect, use the same account under which the agent makes connections. For more information about the permissions that are required by each agent account, see Replication Agent Security Model.
If the error occurs while you are creating or applying a snapshot, check the files in the snapshot directory for errors.
If the error continues to occur, increase the logging of the agent and specify an output file for the log. Depending on the context of the error, this could provide the steps leading up to the error and additional error messages. For more information about how to configure logging for replication, see the Microsoft Knowledge Base article 312292.