New transaction cannot enlist
-
I've configured several COM components to support transactions, and they are called by my C# serviced component, which is configured to require a new transaction. However my component fails on the first COM call, with an error saying that the new transaction could not enlist in the specified transaction coordinator. Is this a cross machine problem, and if so, would having all components and databases running on one machine under one coordinator solve it? I'm new to this, any help would be appreciated. The DJ's took pills to stay awakwe and play for seven days. - Jim Morrison, Black Polished Chrome.
-
I've configured several COM components to support transactions, and they are called by my C# serviced component, which is configured to require a new transaction. However my component fails on the first COM call, with an error saying that the new transaction could not enlist in the specified transaction coordinator. Is this a cross machine problem, and if so, would having all components and databases running on one machine under one coordinator solve it? I'm new to this, any help would be appreciated. The DJ's took pills to stay awakwe and play for seven days. - Jim Morrison, Black Polished Chrome.
Having the components all on one server isn't the issue. COM+ allows for cross machine transactions, look elsewhere for the solution.