• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2204
  • Last Modified:

New request is not allowed to start because it should come with valid transaction descriptor

New request is not allowed to start because it should come with valid transaction descriptor

.NET 2.0 system.transactions deadlock causes this on every subsequent connection.
0
twinfrey
Asked:
twinfrey
  • 2
  • 2
1 Solution
 
QPRCommented:
0
 
Ved Prakash AgrawalDatabase Consultant/Performance ArchitectCommented:
Hi,
Please check you MSDTC configuration.
MSDTC should enable for transaction.

when you used .Net 2.0 System.transaction and called multiple SP into a single transaction it will promote the transaction to use MSDTC. id MSDTC are not configured then you will get this issue.

0
 
Ved Prakash AgrawalDatabase Consultant/Performance ArchitectCommented:
0
 
twinfreyAuthor Commented:
Thanks guys, but we have been using dtc for a bit.  It was not until the load testing where we received a deadlock where this presented itself.
0
 
twinfreyAuthor Commented:
found solution.  Commerce server was not signing up for the ambient transaction.
0

Featured Post

[Webinar] Improve your customer journey

A positive customer journey is important in attracting and retaining business. To improve this experience, you can use Google Maps APIs to increase checkout conversions, boost user engagement, and optimize order fulfillment. Learn how in this webinar presented by Dito.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now