Deepak K Agarwal on Wed, 17 Aug 2016 09:44:41
I have 2 SQL Azure DB's (V12) within a single server and wants the transaction to be atomic. Trying to do what is mentioned here.
I get below exception while trying to wrap the transactions in a single transaction scope. The project targets .net version 4.6. What am I missing here?
Error message (in case image doesn't appear on your end): "The service has encountered an error processing your request. Please try again. Error code 8510. A severe error occurred on the current command. The results, if any, should be discarded."
Torsten Grabs (MSFT) on Thu, 25 Aug 2016 20:44:52
You typically get an error like this when you are picking up the wrong .NET version. Are you sure you are running with .NET 4.6.1? An earlier version like version 4.6 (which you mention above) will not work and produce an exception like the one you see.
J.Hook on Tue, 20 Sep 2016 14:29:35
We are getting exact same error while using .NET 4.6.1. Any distributed transaction fails with this error. Puzzling here is that we got MSDTC to work against Azure Paas databases for a while and now every call is failing. Is there any fix we could try?
davidbaxterbrowne on Tue, 20 Sep 2016 14:50:19
Please start a new thread with your question. Including details of your code and the exception you are getting. Also can you clarify what you mean by "we got MSDTC to work"? Elastic Database Transactions don't use MSDTC: one of the databases serves as the transaction coordinator.
naveenduddi on Tue, 07 Feb 2017 06:44:33
Can you please let me know the resolution for the same, is it upgrade to 4.6.1?
davidbaxterbrowne on Wed, 08 Feb 2017 18:15:07
Please start a new thread with your question, and details about the error you are seeing.