Quantcast
Channel: SQL Server Replication forum
Viewing all articles
Browse latest Browse all 4054

Can't synchronize my subscription

$
0
0

Ok so I was able to establish the new subscription and set database permissions at the subscriber. However, when I went to view the subscription status I got a message:

TITLE: View Synchronization Status
------------------------------

The agent could not be started.

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=12.0.2000.8&EvtSrc=Microsoft.SqlServer.Management.UI.ReplUtilitiesErrorSR&EvtID=CantStartAgent&LinkId=20476

------------------------------
ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

------------------------------

SQLServerAgent Error: Request to run job BCC-CH-DS01P-Ignition-HandAddsProductTrans-WIN-T6S43L3VKK9-3 (from User sa) refused because the job is already running from a request by Start Sequence 0.
Changed database context to 'Ignition'. (Microsoft SQL Server, Error: 22022)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=12.00.5000&EvtSrc=MSSQLServer&EvtID=22022&LinkId=20476

------------------------------
BUTTONS:

OK
------------------------------

I received a similar message before and then I went into the publisher and enabled named pipes which was disabled there and enabled at the subscriber. After restarting the server I started synchronization and it seemed to have worked because a green loading icon was processing and then next time I checked synchronization status it said synchronization complete but however the same error persists. I've verfied the tcp/ip being enabled, both servers are running, browser is running for both, remote connection is verified for both, I can ping one to the other and vice versa. However, I don't understand how to troubleshoot via the powershell or what settings I should be looking for in firewall? I have not done anything in log file viewer it might be a possibility. I've also checked job history in the publlisher but don't know where to look everything just says job succeeded. Any Suggestions?


Viewing all articles
Browse latest Browse all 4054

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>