July 27, 2017 at 3:56 am
Hi All - Junior Developer here and my first time posting,
I have a TSQLT test case for testing a service end to end which worked fine until recently - it compared my expected results with the actual results with no problems.
A change was made to the service to pull some data produced by the service by a remote SP into a table on another server instead of pushing it (inserting into a table using synonym).
The service continues to work and it is correct after some checking HOWEVER when running the tsqlt test case I get the following error
"The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction."
I know for sure it is this item of code that is causing the test to error as when I run the code down to the original method is works and vice versa. I think it is likely as a result of a distributed transaction but my question is:
Would TSQLT's design of wrapping the test within a transaction be causing some mismatching in the XACT_STATE() and erroring the test?
I have searched online for any known problems with TSQLT and distributed transactions but can find very little. Any help would be very much appreciated.
Thanks,
Matt
July 27, 2017 at 4:16 am
I encountered this error about a week ago when trying to deploy as SSIS project. it turned out the problem was due to a trigger. Do you have any triggers on the destination/table/database that could be causing the problem?
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
July 27, 2017 at 4:21 am
Thanks for the response - Im afraid there are no triggers anywhere in our system. I have double checked to be sure but we just don't use them at the moment!
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply