• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2094
  • Last Modified:

Msg 7391, Level 16, State 1, Line 2

Can no longer run a distributed transaction since adding a 2K5 instance to a box that had (and still has) 2K on it.  I now get this error:

Msg 7391, Level 16, State 1, Line 2
The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction.
0
carecorejen
Asked:
carecorejen
  • 4
  • 4
1 Solution
 
Kevin3NFCommented:
Check your DTC service on the box, make sure it is running since the upgrade
0
 
carecorejenAuthor Commented:
It is running and I can run select queries, but the update queries no longer work.  

Note:  the update queries only REFERENCE a table on the linked server.  The effected row is local.  Here is the query:

update ld
set ld.COVERED_SINCE = 1
FROM ES_LOADER_DETAIL LD
            JOIN V_COMPANY C ON C.ID = 71
WHERE LOADER_ID = 6162
            AND EXECUTING = 1
            AND LD.COVERED_SINCE < C.PROGRAM_START_DATE

V_Company is a view on a remote server, but as you can see, I am writing to ES_Loader_Detail, a  local table.  Thanks!
0
 
Kevin3NFCommented:
Run this from the instance that has teh ES_Loader_Detail table:

begin distributed transaction

What do you get?
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
carecorejenAuthor Commented:
The command(s) completed successfully.
0
 
Kevin3NFCommented:
try it on the remote box...should have suggested that in the first place...sorry
0
 
carecorejenAuthor Commented:
They are one in the same.  Linked server is to itself to simulate the production environment in test.  It always worked (3+ years) until 2K5 was installed, though.  I feel like it's got something to do with surface area configuration interfering with 2K.  The reason I suspect that is that I can no longer open the MMC for component services to modify the DTC settings.
0
 
pinaldaveCommented:
http://support.microsoft.com/kb/873160

CAUSE
This problem occurs for one or more of the following reasons:
•      Microsoft Distributed Transaction Coordinator (MSDTC) is disabled for network transactions.
•      Windows Firewall is enabled on the computer. By default, Windows Firewall blocks the MSDTC program.

Note This problem may occur even when Windows Firewall is turned off.

Read workaround on MS Site.

What you can do is insert the values in the Temp Table and then run your update from Temp Table your error will go away.
Regards,
---Pinal
0
 
carecorejenAuthor Commented:
Neither machine is XP.  It is a Win2K server with SQl 2K and SQL2K5 both installed. The linked server is from the SQL2K instance to itself.  Thanks, though.
0
 
Kevin3NFCommented:
>>The reason I suspect that is that I can no longer open the MMC for component services to modify the DTC settings.<<

I would hit this issue first, as it does seem that the component may have gotten messed up when 2005 was installed
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now