|Product:||Syniti Data Replication, DBMoto|
|Summary:||Steps to take if a replication involving MS SQL Server does not start|
Take the following steps to verify that everything on the SQL Server side is working fine:
Step 1: Check that the SQL Server Agent is running on the source machine and that it starts every time Windows starts.
- Run Administrative Tools Services panel and search for SQL Server Agent.
- Check that the Status is running and the Startup is Automatic
If the startup is automatic and the service is stopped: This is due to errors in SQL Server agent. You can check them in Event Viewer - Application and Event Viewer - System. You also need to check the SQL Server Agent log file, which is usually located in C:\Program Files\Microsoft SQL Server folder under MSSQL\LOG. The SQL Server Agent must be started to replicate with Syniti DR/DBMoto.
If the startup is manual and the service is stopped: Change the startup method to Automatic and manually start the SQL Server Agent. Next time you start Windows the service will run automatically.
Step 2: Check that the Log Reader Agent is running correctly on the source machine (1 agent for each replicated database).
- Open SQL Server Management Studio.
- Connect to the Publisher for the database.
- View the server node and the Replication folder.
- View the Local Publications folder.
- Right click the publication and choose View Log Reader Agent Status.
- If the Log Reader status is stopped, click Start.
- In the Log Reader Agent dialog, browse the error messages and action messages.
- If these are empty, you probably have an Agent Owner which doesn't allow the agent to start.
- Open the Log Reader Agent Security dialog.
- Change the owner to a SQL Server admininstrator account like "sa", for example.
- Repeat these steps for each publication.
- Ignore any error in Snapshot Agents: Syniti DR/DBMoto does not use snapshot agents.
Step 3: Check the Agents status in the Agents folder in the Replication Manager.
- In the Agents folder, expand the Log Reader Agents folder.
- Check the Properties of the agents listed to see if the changes made in the Publishers folder have been applied here.
- Manually start the agents by selecting the agent, right-clicking, then choosing Start
If the operation is successful and the Log Reader starts, you can start mirroring.
If the SQL Server Agent reports that the replication Agents are not correctly registered, this is an issue for your SQL Server administrator.