Share via


Subscription Error: The current transaction cannot be committed and cannot support operations that write to the log file

Question

Wednesday, November 4, 2015 7:28 PM

After I watch a video for how to create MS SQL Replication, I configure distribution and create the publication. The problem comes from subscription. If I create a "PUSH" subscription, it works fine. However, when I create a "PULL" subscription, I got the following error. I just wonder if anyone know where I should look for solution for this error. Many thanks. 

All replies (5)

Thursday, November 5, 2015 10:11 AM ✅Answered

Hi eg10013,

Please check that  if  there is additional message in the SQL error log.

Additionally, this issue might be caused by that your distribute agent account or subscribe agent account has not enough permission, we need to verify that what’s your distribute agent account,  and we also need to verify that what is the account of Publisher agent and Subscriber agent.

To troubleshoot this issue, when you create the new publication and subscription using SSMS GUI, you can both select the “SQL Server Agent service account” in the Agent security wizard as your Publisher agent and Subscriber agent accounts,  at the same time, set distribute agent account to “SQL Server Agent service account” in distribute agent property, then check if this issue exists.

Regards,
Ice Fan 

Ice Fan
TechNet Community Support


Thursday, November 5, 2015 9:49 PM

Thank you for your tip. It came out the SQL and SQL agent service were running as a local account. After I change to the AD account, the issue is solved.

Can I ask you for another help. Now, I start creating replication in the production servers. I want to replicate a database from a SQL 2008 server to a SQL 2012 server. I followed the same steps. However, the tables will not be created in SQL 2012 database? Both the publisher and subscription seems fine. Any idea what it can be. Thanks again.


Friday, November 6, 2015 1:47 AM

Hi eg10013,

This thread has been closed, I would recommend you open a new thread in the SQL Server Replication forum about your new issue.

Thanks,

Ice Fan 

Ice Fan
TechNet Community Support


Friday, November 6, 2015 3:14 PM

Is your subscriber SQL Server Express? Also check to verify that the account you are using is in the db_owner role in the subscription database.

looking for a book on SQL Server 2008 Administration? http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search? http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941


Friday, November 6, 2015 4:44 PM

No, we have MS SQL 2008 and MS SQL 2012. The last issue on the production server was caused by missing database owner. Problem solved and everything is fine. Thanks all.