Does anyone has any idea
I have to resolve this exception:
Communication with the underlying transaction manager has failed
InnerException
"Error HRESULT E_FAIL has been returned from a call to a COM component. (System.Transactions)
------------------------------
Program Location:
at System.Transactions.Oletx.IDtcProxyShimFactory.ReceiveTransaction(UInt32 propgationTokenSize, Byte[] propgationToken, IntPtr managedIdentifier, Guid& transactionIdentifier, OletxTransactionIsolationLevel& isolationLevel, ITransactionShim& transactionShim)
at System.Transactions.TransactionInterop.GetOletxTransactionFromTransmitterPropigationToken(Byte[] propagationToken)
"
I've tried all the solutions from http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=444383&SiteID=1 ...nothing worked .. and on my colleague computers works fine. So, the problem appeared after I changed my computer - on the old one, transactions in transactionScope worked fine. Does anyone know what can be wrong
Thanks a lot,
Ela
Communication with the underlying transaction manager has failed
VarunR
Sounds like the most likely scenario is that name resolution on your computer doesn't work after you changed the computer name. Try adding correct entry to your hosts file.
You can use DTC traces/CM traces which are described in the KB even if your transaction excecuted in a box.
http://support.microsoft.com/kb/899115
They will tell you where the transaction failed or failed before transaction started. If before, CM traces may tell you why the connection failed.
And I want to hear more details from you such as:
1. Is your primary exception InvalidOperationException
2. Do you get the exception everytime you execute transaction or intermittently
3. So you installed COM+ applicatin or some transactional application into your database server and it is called from "Client machine"
eldiener
Ok,
Client machine
XP Pro with SP2
Visual Studio 2005 , SQL Server 2005
Server machine
Windows Server 2003 with SQL Server 2005
DTC Security settings
1. Client and Administration Options [Allow Remote Clients and Allow Remote Administration] are checked
2. Transaction Managed Communication Options [Allow Inbound and Allow Outbound] are checked
3.Option “Mutual Authentication Required” checked
Firewall is off
As I already said, I've already tried all that Florin Lazar mentioned in his blog. - DTC security settings configured ok, firewall off, and what is most important DTCPing. But this last one solution is not so good, because on my colleagues computers the same application connected on the same server is working and on my new computer doesn't. And the message from dtcPing is the same: WARNING:the CID values for both test machines are the same
while this problem won't stop DTCping test, MSDTC will fail for this, from the server to my and their workstation. And I think that this test is not so relevant. Can be a problem the fact that I've changed my workstation and computer name in the network and I am using the same user account Because on first one the transactions were ok. I have no idea about what happened.
Thanks
ACCOUNTINGONLINE.US
I have the same problem. I also have the same configuration as Ela, except for the SQL server at client machine. and the machines are two Virtual PC on different computers.
Addition. I'm totally new to this transaction thing. I decided to learn this transaction thing, so I downloaded 101 Samples for Visual Studio 2005 and started the project Transactions. The problems listed above occured in the section where the application wanting to copy a file with it's own resource manager (or so I think it's trying to do...) The error above is generated in the file TransFile.cs, line 246. The error is not generated when I skip the code in file Form1.cs, line 67-76, the "using sql-connection" part. It seems I can do a sql-operation or a fileCopy operation, but not both.
stratos13
Ela,
Can you provide some more details about your system configuration and settings For both the client and server machines, it would be helpful to have the following:
Also check out http://blogs.msdn.com/florinlazar/archive/2005/09/16/469064.aspx : Florin lists some steps for diagnosing common MSDTC connectivity issues using DTCPing, which is linked from that page.
Chris
m14cus
Thank you for tip :)
I've used traces and in log file I have :
11-23-2006 16:54 32:800: CM Error Value = 0x80004005, Call to SetRpcSecurity failed, d:\qxp_slp\com\com1x\dtc\dtc\cm\src\iomgrclt.cpp (533)
11-23-2006 16:54 32:800: CM Error Value = 0x80004005, SecureBuildContextWrapper call failed. This is usually due to security/network configuration issues., d:\qxp_slp\com\com1x\dtc\dtc\cm\src\iomgrclt.cpp (332)
hope to solve it, but know I really don't know how, I will talk to network admin. If you have any idea....
About the other questions:
1.The first and only exception is the TransactionManagerCommunicatioException :
Communication with the underlying transaction manager has failed.
2.I get this exception only if I try to update/insert/delete more than once in a transaction scope. If I do have only one operation this succeds.
3. Other applications beside SqlServer 2005 we didn't install.It is a test server. Anyway my colleagues have no problem.
Thank you
Ela
KrazyMGA