By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,903 Members | 1,977 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,903 IT Pros & Developers. It's quick & easy.

Win2003 SP1 error: "New transaction cannot enlist in the specified transaction coordinator"

P: n/a
I have a web application installed on Windows 2003 Standard Edition
with SP1, it accesses a SQL Servet 2000 database installed on Windows
2000 Server, the two computers are not in the same domain. The web
application uses ASP pages and COM+ components written in VB6.
After the installation of SP1 for Windows 2003 the application does
not work anymore (before the installation of SP1 it worked without
problems). The following error occurs: "New transaction cannot enlist
in the specified transaction coordinator".
If I change in Component Services the componets' Transaction model
from Required to Supported then the application works fine.

Does anybody know if this is a limitation of Windows 2003 SP1 or a bug
or if there is a solution in order to solve the problem.

Thanks,
István
Jul 22 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Hi István

"Vencz Istv?n" <is****@profuse.ro> schrieb im Newsbeitrag
news:f8**************************@posting.google.c om...
I have a web application installed on Windows 2003 Standard Edition
with SP1, it accesses a SQL Servet 2000 database installed on Windows
2000 Server, the two computers are not in the same domain. The web
application uses ASP pages and COM+ components written in VB6.
After the installation of SP1 for Windows 2003 the application does
not work anymore (before the installation of SP1 it worked without
problems). The following error occurs: "New transaction cannot enlist
in the specified transaction coordinator".
If I change in Component Services the componets' Transaction model
from Required to Supported then the application works fine.


have you checked if the SP1 changed the settings for MSDTC under Component
Services?
AFAIK SP1 introduced the option to allow anonymous access to MSDTC (No
authentication required) in the UI - before you had to set it in the
registry to allow web apps to use transactions.
Maybe they also set a different default value - it wouldn't be the first
time ;-)

Helge
Jul 22 '05 #2

P: n/a
Indeed this was the cause of the problem, after the installation of SP1
the implicit value is "mutual authentication required". I was not aware
about this new feature.

Thank you very much for your help,
István

Jul 22 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.