Unabletogeterrormessage cannot get error message (6107) (0) Distributed Transaction Tr

Today, I encountered a strange problem. After the business was running for less than one minute, I ran a database error, which was still not fixed. The error content could not be obtained (6107) (0). The English is Unabletogeterrormessage (6107) (0). If you still have this problem, I will help you locate 100% as a result of Distributed Transaction timeout.

Today, I encountered a strange problem. After the business was running for less than one minute, I ran a database error, which was still not fixed. The error content could not be obtained (6107) (0). The English language is Unable to get error message (6107) (0). If you still have this problem, I will help you locate 100% as a result of Distributed Transaction timeout.

Today, I encountered a strange problem. After the business was running for less than one minute, I ran a database error, which was still not fixed. The error content could not be obtained (6107) (0), English is Unable to get error message (6107) (0 ),

If you still have this problem, I will help you identify 100% as a result of Distributed Transaction timeout. Generally, the timeout time needs to be set at the place where the transaction is opened.

 using (TransactionScope transactionScope = new TransactionScope(TransactionScopeOption.Required, new TimeSpan(1, 0, 0)))            {}

My timeout is complicated because there is still a WCF access in the transaction, so the connection timeout of WCF will also affect the distributed transaction and set the WCF time.

In addition, you must set the Web. Config Distributed Transaction timeout for this application.

Finally, if the Machine is disconnected within 10 minutes, you need to set Machine. Config.

C: \ Windows \ Microsoft. NET \ Framework \ v2.0.50727 \ CONFIG