Intermittent TransactionScope communication failures

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Dagsê

I am having trouble stabilizing the behaviour of TransactionScope.
We get intermittent exceptions with the message "Communication with the
underlying transaction manager has failed". This happens in both the
development and the staging environments.

Infrastructure:
Development consists of a virtual machine with Windows XP SP2 (VMWare
Workstation) running VS 2005 SP1. The SQL Server 2005 SP1 DBMS is
installed on a Windows Server 2003 R2 virtual machine (VMWare Server)
hosted on a different physical machine. The hosts are connected to the
same physical switch. All IP's are served by static DHCP.
No firewall is running on either web or database server.

Configuration:
The MSDTC security settings are set on both servers to allow everything
and authenticate nothing. Everyone has all COM access, activation and
launch permissions.
I can ping the NetBIOS name of either server from the other one.

Transactions are created in an ASP.NET application. I can simulate the
error in the development environment by rebooting the database server.
For the first few transactions after a reboot I get the exception
mentioned above. Then things start to work and I cannot recreate the
behaviour.
In staging testers get this error from time to time independent of the
last reboot.
Usually the transaction rolls back when this error appears, but in at
least one case changes were committed to the database!

Interestingly, DTCPing executes successfully from the web to the
database server but from the database server I get an error "(5) Access
denied".

I have tried a couple of suggestions found on discussion lists but none
of them addresses the case where the failures are intermittent.

Any ideas?

Groete
Hans

.

Relevant Pages

  • Re: commit work not working?
    ... Because he is using straight sql, ... The transaction is made up of the statements that occur ... locks the stock table, updates rows in the stock table ... The database server must perform this sequence of operations either ...
    (comp.databases.informix)
  • Re: commit work not working?
    ... and have Perl talk directly to the database server rather than piping a script to dbaccess. ... Then he/she will have program control of error detection and can make decisions about commit or rollback. ... The transaction is made up of the statements that occur ... locks the stock table, updates rows in the stock table ...
    (comp.databases.informix)
  • COM+ transactions in DMZ zome
    ... The Database Server is in the local network of the Client. ... We are not able to connect to our Database Server from our components, when the TRANSACTION ATTRIBUTE is set to REQUIRES TRANSACTION in COM+. ...
    (microsoft.public.dotnet.framework.component_services)
  • Transaction not created. Do i need to configure my database?
    ... In the following edited code sample my transaction instance is being ... The database server Im using at the moment is an evaluation version of SQL ... IDbConnection Connection = GetConnection; ...
    (microsoft.public.dotnet.framework.adonet)
  • persistence in lisp
    ... it would be nice if it will do serialization code ... transaction stuff isn't what i want - i'll have to rewrite lot of code to do ... and sometimes it does full snapshots. ... reboot it could load latest snapshot and apply logged setters. ...
    (comp.lang.lisp)