June 15, 2009 at 2:57 am
hi,
i am getting below error while exectuing a LINKED SERVER query
please help me
Executed as user: NT AUTHORITY\SYSTEM. The operation could not be performed because OLE DB provider "SQLNCLI" for linked server "INDBA01test\DEV" was unable to begin a distributed transaction. [SQLSTATE 42000] (Error 7391) OLE DB provider "SQLNCLI" for linked server "INDBA01test\DEV" returned message "The partner transaction manager has disabled its support for remote/network transactions.". [SQLSTATE 01000] (Error 7412). The step failed.
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
June 15, 2009 at 3:31 am
was it previously working fine or is it a brand new setup?
have you checked this post? http://social.msdn.microsoft.com/Forums/en-US/adodotnetdataproviders/thread/7172223f-acbe-4472-8cdf-feec80fd2e64
June 15, 2009 at 4:26 am
No this is a new setup .
below is the query , whic is running fine while executing in mgmt studio
but i have put it in JOB , to perform it periodically
so when the job runs , it gives that error
-------------------------------------------------------
declare @SQLCmd varchar(100)
SET @SQLCmd = 'insert into ghi_prod.dbo.account_test SELECT TOP 1 * from mydba.ghi_prod.dbo.account '
EXEC(@SQLCmd) AT [mytesttest\DEV] <------linked server
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
June 15, 2009 at 4:39 am
As first step I'd check the instructions detailed in the link i've posted earlier on.
Also, I'm not 100% sure, but I would look at security issues between the two linked servers: how did you configure the security mappings between the two servers? Also, I don't think that NT AUTHORITY\SYSTEM is a valid account on linked servers as it depends on the machine it's running on (that is, it is on both servers, but it's a "different" account on the two servers - I might be wrong here tho).
Try creating a new Active Directory account with limited privileges, grant it the access level you need on both servers and use that account for the login mapping: hopefully that should sort your issue.
As I said, I'm not 100% sure, but that's the path I would follow to sort this issue 😛
Hope this helps, post again otherwise 🙂
Matt
June 15, 2009 at 4:46 am
also, take a look here first: http://support.microsoft.com/kb/306212
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply