I get a distributed transaction error the first time I call my MTS components after that they create just fine. Does anyone has any idea or have seen this before?
could it be a time-out ? its been quite a well known problem that MTS is slow in serving its very first component activation.
we've worked around this by:
1. lengthening the time-out in MTS and IIS
2. unsetting the time-out for idling components
3. have a refresh meta definition in our IIS ASP that activates the MTS component every 2 minutes
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.