Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
bazdunk
Starting Member
6 Posts |
 Posted - 2012-03-14 : 11:04:53
|
| We currently have 4 load balanced web servers connecting to a SQL 2005 database server. On the web servers is IIS 6 which has our Dot Net web services installed and Dot Net COM+ components also in Dot Net 4. MSDTC is used on each web server and on the SQL server for transaction of several SQL queries that have to run as a unit. Occasionally we get the following error recorded in all 4 web servers but not on the SQL server (in the windows event viewer application log):System.Runtime.InteropServices.COMException (0x8004E002): The root transaction wanted to commit, but transaction aborted (Exception from HRESULT: 0x8004E002)Have found a couple of articles where folks have suggested increasing the time-out limits but unfortunately we are unable to do this due to time constraints in communicating with customer requests.We would just like to know what the root cause of this problem could possibly be |
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2012-03-14 : 11:16:38
|
| Have you checked why it is taking so long? Blocking? Missing indexes?Does this really need to be a distributed transaction? I've seen a lot of transactions initialized by web servers that could easily be written as single stored procedures without a transaction, or at least without a distributed transaction. |
 |
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2012-03-14 : 11:20:40
|
| Also, saw this?http://www.dotnet247.com/247reference/msgs/1/6795.aspx |
|
|
|
|
|
|
MSDTC - COM Exception