Author Topic: New Transaction cannot enlist in the specified transaction  (Read 181 times)

0 Members and 1 Guest are viewing this topic.

Offline JusticeLeague

  • Sr. Member
  • *
  • Posts: 359
  • Karma: +1/-0
    • View Profile
New Transaction cannot enlist in the specified transaction
« on: August 23, 2008, 05:33:26 PM »
I have two machines with Windows 2003 server:
I hope somebody is kind enough to help me.
Here\'s my scenario.

One is using Enterprise Edition
The other is using Web Edition

The server with Enterprise edition has a SQL Server 2000.

Well, i have in a Web Edition an application constructed with VB6 Components for COM+ and ASP.

Then When I run it\'s application, I receive the message:

"New Transaction cannot enlist in the specified transaction coordinator"

Distributed Transaction Coordinator running on each SQL server in this case...

I tried to reinstall the Windows 2003 Enterprise in the application server, but, the problem still persists.

Any idea how to solve this?

Techronnati | where technology never sleeps

New Transaction cannot enlist in the specified transaction
« on: August 23, 2008, 05:33:26 PM »

Mountain View

Offline h2obubbler

  • Full Member
  • *
  • Posts: 228
  • Karma: +0/-0
  • Life is like a box of chocolate.
    • View Profile
Re: New Transaction cannot enlist in the specified transaction
« Reply #1 on: August 23, 2008, 05:57:24 PM »
we had the same error few years back when we were doing the setup. You can try this one out. In the Component Services, you see the new properties for the class in the component. In the Activation Tab are new properties. On the Activation Context we did some modifications, and the problem had a solution.

 

Posting Disclaimer: Any individual may post a message in this forum and may do so anonymously. Therefore, the sole author is exclusively and entirely responsible for all opinions in that message. They do not represent the official opinions of Techronnati, its administrators or moderators or the Techronnati Management. Techronnati is merely acting as an impartial conduit for constitutionally protected free speech and is not responsible and will not be held liable for the content of such messages. All images and service logos are trademarks of their respective owners.