Have there been any instances found where the DbContextManager opens a second connection? I have one client where im getting the exception
An error has occurred. Csla.DataPortalException: DataPortal.Update failed (The underlying provider failed on Open.) ---> Csla.Reflection.CallMethodException: EditableCategory.DataPortal_Update method call failed ---> System.Data.EntityException: The underlying provider failed on Open. ---> System.Transactions.TransactionManagerCommunicationException: Network access for Distributed Transaction Manager (MSDTC) has been disabled. Please enable DTC for network access in the security configuration for MSDTC using the Component Services Administrative tool. ---> System.Runtime.InteropServices.COMException: The transaction manager has disabled its support for remote/network transactions. (Exception from HRESULT: 0x8004D024)
It looks like the DTC is being used, but I have take care to make sure all database updates, deletes, inserts occur within a using block like below
using (var cntx = DbContextManager<DataContext>.GetManager())
{
}
Also, in my dev environment I dont get this exception when running the same code and the DTC service is definitely disabled.
Also, we have another client who doesnt have the DTC service enabled and they do not get this error.
I understand that the DbContextManager is most likely solid in that it does what it says, but just thought I post here to see if maybe there was a bug or if anyone else has found a similar issue.
I've posted the code in this question
http://stackoverflow.com/questions/18278994/transaction-escalated-to-dtc-no-multiple-connections
Any help is greatly appreciated.
Thanks.
