sp_addarticle generates "Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements."

• vitor8pinto

  SSC Enthusiast

  Points: 124

  More actions

  March 24, 2009 at 9:51 am

  #207444

  Hi all,

  I'm a newbie with SQL Server so forgive me if this is a somewhat stupid question but I already searched for a answer without much success.

  I have a procedure that builds the SQL statements to build a table, build the keys, indexes and constraints. Once this is executed, the sp_addarticle is executed to add the table to a already setup SQL Server Replication. The procedure does not feature a single commit or rollback. All it does are DML statements.

  Once executed in the Management Studio, it runs without any issues. The problem is when it is executed via .Net WCF it returns the following error:

  "Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 1, current count = 2.

  Uncommittable transaction is detected at the end of the batch. The transaction is rolled back."

  If the sp_addarticle is commented out, it runs without any issue.

  Do you have any clue or tip for me to debug this?

  Thanks for your time in advance.

  Regards,

  Vítor

• ShilpaSunil

  SSC-Addicted

  Points: 445

  More actions

  March 19, 2010 at 5:22 am

  #1136603

  hi,

  Check this link

  http://qa.sqlservercentral.com/Forums/Topic721835-338-1.aspx

• vitor8pinto

  SSC Enthusiast

  Points: 124

  More actions

  March 19, 2010 at 5:41 am

  #1136615

  Thanks for the reply! 🙂

• Paul White

  SSC Guru

  Points: 150457

  More actions

  March 20, 2010 at 10:18 am

  #1137202

  vitor8pinto (3/19/2010)

  ---

  Thanks for the reply! 🙂

  So...did you solve it? Was it a trigger?

  Paul White
  SQLPerformance.com
  SQLkiwi blog
  @SQL_Kiwi