Comments by stretchtack

stretchtack 28-Jun-12 1:02am View

True... this might be tough to recreate. It all depends on what the actual issue is. I'm not going to read any further. I'm going to move the transaction into SQL before I bang my head any further on this. I was hoping someone would shed some light on this, but after 50 views here and only 1 person posting a message... it seems clear that most don't want to touch this... including me. ;) I got other work to do. Thanks.

stretchtack 27-Jun-12 20:53pm View

I can look at that but I'm using SQL Server 2008R2. It's not supposed to be an issue with 2008. I read plenty about older versions and their issues.

stretchtack 27-Jun-12 20:00pm View

The message above in my original post - "Communication with the underlying transaction manager has failed." is the exception message. If you'd like the stack trace or similar I can post that. The try/catch is up a level in the routine that called this one.

stretchtack 27-Jun-12 18:39pm View

The error I mentioned is an exception on the DeleteProfileExecCmd. The problem occurs when I try to use the second datacontext within the TransactionScope. If I remove the TransactionScope it works.

stretchtack 26-Jun-12 23:00pm View

Are telling me that all 4 of the articles apply to fixing my problem? Are you telling me not to use LINQ? I've spent the better part of 2 days reading... 'scouring' as I put it. I'm not using DataAdapters. I know how to do a transaction and I know how to use TransactionScope. I can't get it to work with 2 connections each to a different database.

Comments by stretchtack (Top 5 by date)