Solved

Execute stored procedure (linked server) within another stored procedure

Posted on 2007-03-30
10
641 Views
Last Modified: 2012-05-05
I have 2 linked servers and need to call a stored procedure on 1 linked server within a stored procedure of another server.  Everytime I attempt this i get the following error:
[OLE/DB provider returned message: New transaction cannot enlist in the specified transaction coordinator. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB' ITransactionJoin::JoinTransaction returned 0x8004d00a].
The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction.

I know the 2 servers are linked because i can execute the remote stored procedure in a sql editor but not within another stored procedure.  I also followed all steps outlined in: http://support.microsoft.com/kb/816701  but continue to get this exception. Any help would be greatly appreciated.

Thanks
0
Comment
Question by:egdigital
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 3
10 Comments
 
LVL 11

Expert Comment

by:Otana
ID: 18822783
My guess is that both stored procedures use a transaction. If you execute one inside the other, those transactions will interfere. Try removing the use of transactions from at least one of them.
0
 
LVL 3

Expert Comment

by:popa_duhu
ID: 18822789
First, you should check that MSDTC service is up and running
0
 
LVL 3

Expert Comment

by:popa_duhu
ID: 18822806
Then, in linked server properties / server options, check the RPC and RPC out, after all you try to run a stored proc on another comp.
0
What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

 
LVL 3

Expert Comment

by:popa_duhu
ID: 18822811
can you post the piece of code that troubles you ?
0
 
LVL 3

Expert Comment

by:popa_duhu
ID: 18822883
sorry :D
i did not read all
ok.
so you did as in the article.

but then,
you still have to make some configs on both servers.
i assume that you have win2003

so, you have to go to:
Administrative Tools / Component services / Computer / My Computer

Right click on My Computer / Properties
And there is MSDTC tab.

There you should see Transaction Configuration and a button Security Configuration.

Clik the button, and in the window that appears, there are some options:
You check all "Allow/Enable" options
And there are 3 choices for Authentication, and you choose "No Authentication required."
0
 

Author Comment

by:egdigital
ID: 18822947
otana -
Im not sure what u mean by removing a transaction from one of the procedures.

popa duhu -
RPC and RPC Out are both checked in the server options of the linked server.  I do not see MSDTC in the list of services however it enabled under the application server (Enable network DTC access - checked)

The code that is causing a problem is this:

Procedure x (on server b2)
   ..... some code
   Insert Into #Temp
                EXEC j19.location.eg.sp_LocTagSearch @Tags
  .... some more code
end

Now when on server b2 in sql editor I can execute:
EXEC j19.location.eg.sp_LocTagSearch 'X'
And this returns results as expected.

0
 

Author Comment

by:egdigital
ID: 18823085
popa duhu -

I set all all/enable options as well as the no authentication required on both servers and still receive:
[OLE/DB provider returned message: New transaction cannot enlist in the specified transaction coordinator. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB' ITransactionJoin::JoinTransaction returned 0x8004d00a].
The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction.
0
 
LVL 3

Expert Comment

by:popa_duhu
ID: 18823505
sorry,
when i said MSDTC i meant Distributed Transaction Coordinator (msdtc.exe is the file name)
So, there should be a service named Distributed Transaction Coordinator

After you checked everything on both servers in Component Services, you should restart the DTC service on both servers.
0
 

Author Comment

by:egdigital
ID: 18823685
That was running on both servers but I restarted anyway and still get the same error
0
 
LVL 3

Accepted Solution

by:
popa_duhu earned 500 total points
ID: 18828249
well...
maybe i miss something
but i know that i've solved once this problem.

check this link: http://support.microsoft.com/kb/873160
0

Featured Post

On Demand Webinar: Networking for the Cloud Era

Did you know SD-WANs can improve network connectivity? Check out this webinar to learn how an SD-WAN simplified, one-click tool can help you migrate and manage data in the cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Why is this different from all of the other step by step guides?  Because I make a living as a DBA and not as a writer and I lived through this experience. Defining the name: When I talk to people they say different names on this subject stuff l…
In the first part of this tutorial we will cover the prerequisites for installing SQL Server vNext on Linux.
Via a live example, show how to set up a backup for SQL Server using a Maintenance Plan and how to schedule the job into SQL Server Agent.
Viewers will learn how the fundamental information of how to create a table.

688 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question