Need help

Hi All,
I tried to update a record on one server and there is an update
trigger to to update another record in another server . But I got this error
and no record is updated. Can anyone please advise me the solution and the
cause? Thanks.
The error message as follow:
update action start
Server: Msg 7391, Level 16, State 1, Procedure something_ins_upd_trg, Line
328
The operation could not be performed because the OLE DB provider 'SQLOLEDB'
was unable to begin a distributed transaction.
[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].
Hi Eric,
Welcome to use MSDN Managed Newsgroup!
From your descriptions, I understood you encounter error message 7391 when
executing query on Linked Server. If I have misunderstood your concern,
please feel free to point it out.
First of all, please make sure you are not encounter the scenario as the
following KB described.
You may receive a 7391 error message in SQL Server 2000 when you run a
distributed transaction against a linked server after you install Windows
Server 2003 or Windows XP Service Pack 2
http://support.microsoft.com/kb/839279
Also, make sure you have made MS DTC correctly configured for network access
You receive error 7391 when you run a distributed transaction against a
linked server
http://support.microsoft.com/kb/329332/en-us
Secondly, I have noticed you mentioned "there is an update trigger to to
update another record in another server". If you are executing the query
that won't active the trigger, will it also reproduce this error message?
Are you executing the stored procedure in a transtion? If you execute the
stored procedure directly, will it reproduce this error message?
If you have any questions or concerns, don't hesitate to let me know. We
are always here to be of assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Thanks for your help, Michael. I am running this trigger on Win2000 SP3 or
SP4. If I remove the trigger there is no error at all and it does involve
store procedure. The following KB apply for Win 2003 only, right? How do
you configure the MS DTC?
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:Tk7Ahv$8FHA.1236@.TK2MSFTNGXA02.phx.gbl...
> Hi Eric,
> Welcome to use MSDN Managed Newsgroup!
> From your descriptions, I understood you encounter error message 7391 when
> executing query on Linked Server. If I have misunderstood your concern,
> please feel free to point it out.
> First of all, please make sure you are not encounter the scenario as the
> following KB described.
> You may receive a 7391 error message in SQL Server 2000 when you run a
> distributed transaction against a linked server after you install Windows
> Server 2003 or Windows XP Service Pack 2
> http://support.microsoft.com/kb/839279
> Also, make sure you have made MS DTC correctly configured for network
> access
> You receive error 7391 when you run a distributed transaction against a
> linked server
> http://support.microsoft.com/kb/329332/en-us
> Secondly, I have noticed you mentioned "there is an update trigger to to
> update another record in another server". If you are executing the query
> that won't active the trigger, will it also reproduce this error message?
> Are you executing the stored procedure in a transtion? If you execute the
> stored procedure directly, will it reproduce this error message?
> If you have any questions or concerns, don't hesitate to let me know. We
> are always here to be of assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
|||Hi Eric,
Thanks for your reply.
Does your two server on the same domain or on the trusted domains? Does the
linked server is also SQL Server or other database? Execute the query
directly on the destination server, will the query work and active the
trigger?
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.