Hi there,
Fun problem for a Monday morning (NOT!). Running a stored procedure on
one server (SQL 2000, with latest patches), which is similar to the
example below, in connecting to a linked server to archive data out
from 'SERVER2' to a database on 'SERVER1' (the code below is obviously
a simplified part of the actual code to illustrate the functionality).
The stored procedure is run via a job on 'SERVER1'
This was OK, but recently we upgraded to a new clustered server and
are getting these problems now and again. The DBA informs me all looks
OK for the MSDTC and the Component Services is looking OK. Are there
any tips out there'
Thanks for any ideas.
Rob
--Running on SERVER1
CREATE TABLE #RecordsToDelete
(RefId varchar(100) NOT NULL)
INSERT INTO #RecordsToDelete
SELECT RefID FROM SERVER2.MyDB.dbo.MyTable
WHERE [name] = 'Jo Bloggs'
BEGIN DISTRIBUTED TRAN
INSERT INTO HISTORY.dbo.MyTable mt
SELECT * FROM SERVER2.MyDB.dbo.MyTable mt
JOIN #RecordsToDelete rtd ON rtd.RefID = mt.RefID
DELETE FROM SERVER2.MyDB.dbo.MyTable
WHERE RefID IN (SELECT RefId FROM #RecordsToDelete)
COMMIT> Fun problem for a Monday morning (NOT!). Running a stored procedure on
> one server (SQL 2000, with latest patches), which is similar to the
> example below, in connecting to a linked server to archive data out
> from 'SERVER2' to a database on 'SERVER1' (the code below is obviously
> a simplified part of the actual code to illustrate the functionality).
> The stored procedure is run via a job on 'SERVER1'
If the other server is 7.0, then this article might help:
http://support.microsoft.com/defaul...b;en-us;834849.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com|||"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si> wrote in m
essage news:<e90GmTCsEHA.1164@.TK2MSFTNGP10.phx.gbl>...
> If the other server is 7.0, then this article might help:
> http://support.microsoft.com/defaul...b;en-us;834849.
No, they are both SQL Server 2000, which makes it confusing as the
only explanation/docmentation on this problem is to do with one server
being SQL Server 7.0!
Regards
Rob
Showing posts with label distributed. Show all posts
Showing posts with label distributed. Show all posts
Tuesday, March 27, 2012
Error 8525: Distributed transaction completed. Either enlist this session ... PROBLEM!
Hi there,
Fun problem for a Monday morning (NOT!). Running a stored procedure on
one server (SQL 2000, with latest patches), which is similar to the
example below, in connecting to a linked server to archive data out
from 'SERVER2' to a database on 'SERVER1' (the code below is obviously
a simplified part of the actual code to illustrate the functionality).
The stored procedure is run via a job on 'SERVER1'
This was OK, but recently we upgraded to a new clustered server and
are getting these problems now and again. The DBA informs me all looks
OK for the MSDTC and the Component Services is looking OK. Are there
any tips out there?
Thanks for any ideas.
Rob
--Running on SERVER1
CREATE TABLE #RecordsToDelete
(RefIdvarchar(100) NOT NULL)
INSERT INTO #RecordsToDelete
SELECT RefID FROM SERVER2.MyDB.dbo.MyTable
WHERE [name] = 'Jo Bloggs'
BEGIN DISTRIBUTED TRAN
INSERT INTO HISTORY.dbo.MyTable mt
SELECT * FROM SERVER2.MyDB.dbo.MyTable mt
JOIN #RecordsToDelete rtd ON rtd.RefID = mt.RefID
DELETE FROM SERVER2.MyDB.dbo.MyTable
WHERE RefID IN (SELECT RefId FROM #RecordsToDelete)
COMMIT
> Fun problem for a Monday morning (NOT!). Running a stored procedure on
> one server (SQL 2000, with latest patches), which is similar to the
> example below, in connecting to a linked server to archive data out
> from 'SERVER2' to a database on 'SERVER1' (the code below is obviously
> a simplified part of the actual code to illustrate the functionality).
> The stored procedure is run via a job on 'SERVER1'
If the other server is 7.0, then this article might help:
http://support.microsoft.com/default...;en-us;834849.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
|||"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si > wrote in message news:<e90GmTCsEHA.1164@.TK2MSFTNGP10.phx.gbl>...
> If the other server is 7.0, then this article might help:
> http://support.microsoft.com/default...;en-us;834849.
No, they are both SQL Server 2000, which makes it confusing as the
only explanation/docmentation on this problem is to do with one server
being SQL Server 7.0!
Regards
Rob
Fun problem for a Monday morning (NOT!). Running a stored procedure on
one server (SQL 2000, with latest patches), which is similar to the
example below, in connecting to a linked server to archive data out
from 'SERVER2' to a database on 'SERVER1' (the code below is obviously
a simplified part of the actual code to illustrate the functionality).
The stored procedure is run via a job on 'SERVER1'
This was OK, but recently we upgraded to a new clustered server and
are getting these problems now and again. The DBA informs me all looks
OK for the MSDTC and the Component Services is looking OK. Are there
any tips out there?
Thanks for any ideas.
Rob
--Running on SERVER1
CREATE TABLE #RecordsToDelete
(RefIdvarchar(100) NOT NULL)
INSERT INTO #RecordsToDelete
SELECT RefID FROM SERVER2.MyDB.dbo.MyTable
WHERE [name] = 'Jo Bloggs'
BEGIN DISTRIBUTED TRAN
INSERT INTO HISTORY.dbo.MyTable mt
SELECT * FROM SERVER2.MyDB.dbo.MyTable mt
JOIN #RecordsToDelete rtd ON rtd.RefID = mt.RefID
DELETE FROM SERVER2.MyDB.dbo.MyTable
WHERE RefID IN (SELECT RefId FROM #RecordsToDelete)
COMMIT
> Fun problem for a Monday morning (NOT!). Running a stored procedure on
> one server (SQL 2000, with latest patches), which is similar to the
> example below, in connecting to a linked server to archive data out
> from 'SERVER2' to a database on 'SERVER1' (the code below is obviously
> a simplified part of the actual code to illustrate the functionality).
> The stored procedure is run via a job on 'SERVER1'
If the other server is 7.0, then this article might help:
http://support.microsoft.com/default...;en-us;834849.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
|||"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si > wrote in message news:<e90GmTCsEHA.1164@.TK2MSFTNGP10.phx.gbl>...
> If the other server is 7.0, then this article might help:
> http://support.microsoft.com/default...;en-us;834849.
No, they are both SQL Server 2000, which makes it confusing as the
only explanation/docmentation on this problem is to do with one server
being SQL Server 7.0!
Regards
Rob
Error 8525: Distributed transaction completed. Either enlist this session ... PROBLEM!
Hi there,
Fun problem for a Monday morning (NOT!). Running a stored procedure on
one server (SQL 2000, with latest patches), which is similar to the
example below, in connecting to a linked server to archive data out
from 'SERVER2' to a database on 'SERVER1' (the code below is obviously
a simplified part of the actual code to illustrate the functionality).
The stored procedure is run via a job on 'SERVER1'
This was OK, but recently we upgraded to a new clustered server and
are getting these problems now and again. The DBA informs me all looks
OK for the MSDTC and the Component Services is looking OK. Are there
any tips out there'
Thanks for any ideas.
Rob
--Running on SERVER1
CREATE TABLE #RecordsToDelete
(RefId varchar(100) NOT NULL)
INSERT INTO #RecordsToDelete
SELECT RefID FROM SERVER2.MyDB.dbo.MyTable
WHERE [name] = 'Jo Bloggs'
BEGIN DISTRIBUTED TRAN
INSERT INTO HISTORY.dbo.MyTable mt
SELECT * FROM SERVER2.MyDB.dbo.MyTable mt
JOIN #RecordsToDelete rtd ON rtd.RefID = mt.RefID
DELETE FROM SERVER2.MyDB.dbo.MyTable
WHERE RefID IN (SELECT RefId FROM #RecordsToDelete)
COMMIT> Fun problem for a Monday morning (NOT!). Running a stored procedure on
> one server (SQL 2000, with latest patches), which is similar to the
> example below, in connecting to a linked server to archive data out
> from 'SERVER2' to a database on 'SERVER1' (the code below is obviously
> a simplified part of the actual code to illustrate the functionality).
> The stored procedure is run via a job on 'SERVER1'
If the other server is 7.0, then this article might help:
http://support.microsoft.com/default.aspx?scid=kb;en-us;834849.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com|||"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si> wrote in message news:<e90GmTCsEHA.1164@.TK2MSFTNGP10.phx.gbl>...
> If the other server is 7.0, then this article might help:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;834849.
No, they are both SQL Server 2000, which makes it confusing as the
only explanation/docmentation on this problem is to do with one server
being SQL Server 7.0!
Regards
Rob
Fun problem for a Monday morning (NOT!). Running a stored procedure on
one server (SQL 2000, with latest patches), which is similar to the
example below, in connecting to a linked server to archive data out
from 'SERVER2' to a database on 'SERVER1' (the code below is obviously
a simplified part of the actual code to illustrate the functionality).
The stored procedure is run via a job on 'SERVER1'
This was OK, but recently we upgraded to a new clustered server and
are getting these problems now and again. The DBA informs me all looks
OK for the MSDTC and the Component Services is looking OK. Are there
any tips out there'
Thanks for any ideas.
Rob
--Running on SERVER1
CREATE TABLE #RecordsToDelete
(RefId varchar(100) NOT NULL)
INSERT INTO #RecordsToDelete
SELECT RefID FROM SERVER2.MyDB.dbo.MyTable
WHERE [name] = 'Jo Bloggs'
BEGIN DISTRIBUTED TRAN
INSERT INTO HISTORY.dbo.MyTable mt
SELECT * FROM SERVER2.MyDB.dbo.MyTable mt
JOIN #RecordsToDelete rtd ON rtd.RefID = mt.RefID
DELETE FROM SERVER2.MyDB.dbo.MyTable
WHERE RefID IN (SELECT RefId FROM #RecordsToDelete)
COMMIT> Fun problem for a Monday morning (NOT!). Running a stored procedure on
> one server (SQL 2000, with latest patches), which is similar to the
> example below, in connecting to a linked server to archive data out
> from 'SERVER2' to a database on 'SERVER1' (the code below is obviously
> a simplified part of the actual code to illustrate the functionality).
> The stored procedure is run via a job on 'SERVER1'
If the other server is 7.0, then this article might help:
http://support.microsoft.com/default.aspx?scid=kb;en-us;834849.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com|||"Dejan Sarka" <dejan_please_reply_to_newsgroups.sarka@.avtenta.si> wrote in message news:<e90GmTCsEHA.1164@.TK2MSFTNGP10.phx.gbl>...
> If the other server is 7.0, then this article might help:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;834849.
No, they are both SQL Server 2000, which makes it confusing as the
only explanation/docmentation on this problem is to do with one server
being SQL Server 7.0!
Regards
Rob
Wednesday, March 21, 2012
Error 7391 when distributed transaction started
Node 1:
Windows 2003 Server Standar Edition SP1
SQL Server 2005 Standar Edition
Node 2:
Windows 2000 Server SP4
SQL Server 2000 Standar Edition SP3a
Node 1 have node 2 like "linked server", node 2 have node 1 like "linked
server" too.
Both nodes use Microsoft OLE DB Provider for SQL Server.
Node 1 begins a distributed transaction vs Node 2.
Transaction KO with
"Server: Msg 7391, Level 16, State 1, Line 1
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]."
MS DTS is configured in Node 1 like microsoft said in
http://suppport.microsoftl.com/defa...kb;en-us;329332
If I change Node1 with Windows 2000 Server Standard Edition and SQL Server
2000 SP3a, the distribution transaction run OK.
Thanks a lot.Hi
Windows 2003 has more secure defaults than Windows 2000 therefore it is
probably something that has not been configured that is causing the problem
Check out http://support.microsoft.com/kb/839279/
http://support.microsoft.com/kb/191168/
http://support.microsoft.com/kb/306843/
http://support.microsoft.com/kb/306843/
http://support.microsoft.com/kb/329332
http://support.microsoft.com/kb/306212
You can use DTCPing to check it can communicate with the server
http://download.microsoft.com/downl.../>
dtcping.exe
John
"FRF" wrote:
> Node 1:
> Windows 2003 Server Standar Edition SP1
> SQL Server 2005 Standar Edition
> Node 2:
> Windows 2000 Server SP4
> SQL Server 2000 Standar Edition SP3a
> Node 1 have node 2 like "linked server", node 2 have node 1 like "linked
> server" too.
> Both nodes use Microsoft OLE DB Provider for SQL Server.
> Node 1 begins a distributed transaction vs Node 2.
> Transaction KO with
> "Server: Msg 7391, Level 16, State 1, Line 1
> 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]."
> MS DTS is configured in Node 1 like microsoft said in
> http://suppport.microsoftl.com/defa...kb;en-us;329332
> If I change Node1 with Windows 2000 Server Standard Edition and SQL Server
> 2000 SP3a, the distribution transaction run OK.
> Thanks a lot.
>
Windows 2003 Server Standar Edition SP1
SQL Server 2005 Standar Edition
Node 2:
Windows 2000 Server SP4
SQL Server 2000 Standar Edition SP3a
Node 1 have node 2 like "linked server", node 2 have node 1 like "linked
server" too.
Both nodes use Microsoft OLE DB Provider for SQL Server.
Node 1 begins a distributed transaction vs Node 2.
Transaction KO with
"Server: Msg 7391, Level 16, State 1, Line 1
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]."
MS DTS is configured in Node 1 like microsoft said in
http://suppport.microsoftl.com/defa...kb;en-us;329332
If I change Node1 with Windows 2000 Server Standard Edition and SQL Server
2000 SP3a, the distribution transaction run OK.
Thanks a lot.Hi
Windows 2003 has more secure defaults than Windows 2000 therefore it is
probably something that has not been configured that is causing the problem
Check out http://support.microsoft.com/kb/839279/
http://support.microsoft.com/kb/191168/
http://support.microsoft.com/kb/306843/
http://support.microsoft.com/kb/306843/
http://support.microsoft.com/kb/329332
http://support.microsoft.com/kb/306212
You can use DTCPing to check it can communicate with the server
http://download.microsoft.com/downl.../>
dtcping.exe
John
"FRF" wrote:
> Node 1:
> Windows 2003 Server Standar Edition SP1
> SQL Server 2005 Standar Edition
> Node 2:
> Windows 2000 Server SP4
> SQL Server 2000 Standar Edition SP3a
> Node 1 have node 2 like "linked server", node 2 have node 1 like "linked
> server" too.
> Both nodes use Microsoft OLE DB Provider for SQL Server.
> Node 1 begins a distributed transaction vs Node 2.
> Transaction KO with
> "Server: Msg 7391, Level 16, State 1, Line 1
> 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]."
> MS DTS is configured in Node 1 like microsoft said in
> http://suppport.microsoftl.com/defa...kb;en-us;329332
> If I change Node1 with Windows 2000 Server Standard Edition and SQL Server
> 2000 SP3a, the distribution transaction run OK.
> Thanks a lot.
>
Error 7391 when distributed transaction started
Node 1:
Windows 2003 Server Standar Edition SP1
SQL Server 2005 Standar Edition
Node 2:
Windows 2000 Server SP4
SQL Server 2000 Standar Edition SP3a
Node 1 have node 2 like "linked server", node 2 have node 1 like "linked
server" too.
Both nodes use Microsoft OLE DB Provider for SQL Server.
Node 1 begins a distributed transaction vs Node 2.
Transaction KO with
"Server: Msg 7391, Level 16, State 1, Line 1
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]."
MS DTS is configured in Node 1 like microsoft said in
http://suppport.microsoftl.com/defau...b;en-us;329332
If I change Node1 with Windows 2000 Server Standard Edition and SQL Server
2000 SP3a, the distribution transaction run OK.
Thanks a lot.
Hi
Windows 2003 has more secure defaults than Windows 2000 therefore it is
probably something that has not been configured that is causing the problem
Check out http://support.microsoft.com/kb/839279/
http://support.microsoft.com/kb/191168/
http://support.microsoft.com/kb/306843/
http://support.microsoft.com/kb/306843/
http://support.microsoft.com/kb/329332
http://support.microsoft.com/kb/306212
You can use DTCPing to check it can communicate with the server
http://download.microsoft.com/downlo...c1/dtcping.exe
John
"FRF" wrote:
> Node 1:
> Windows 2003 Server Standar Edition SP1
> SQL Server 2005 Standar Edition
> Node 2:
> Windows 2000 Server SP4
> SQL Server 2000 Standar Edition SP3a
> Node 1 have node 2 like "linked server", node 2 have node 1 like "linked
> server" too.
> Both nodes use Microsoft OLE DB Provider for SQL Server.
> Node 1 begins a distributed transaction vs Node 2.
> Transaction KO with
> "Server: Msg 7391, Level 16, State 1, Line 1
> 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]."
> MS DTS is configured in Node 1 like microsoft said in
> http://suppport.microsoftl.com/defau...b;en-us;329332
> If I change Node1 with Windows 2000 Server Standard Edition and SQL Server
> 2000 SP3a, the distribution transaction run OK.
> Thanks a lot.
>
sql
Windows 2003 Server Standar Edition SP1
SQL Server 2005 Standar Edition
Node 2:
Windows 2000 Server SP4
SQL Server 2000 Standar Edition SP3a
Node 1 have node 2 like "linked server", node 2 have node 1 like "linked
server" too.
Both nodes use Microsoft OLE DB Provider for SQL Server.
Node 1 begins a distributed transaction vs Node 2.
Transaction KO with
"Server: Msg 7391, Level 16, State 1, Line 1
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]."
MS DTS is configured in Node 1 like microsoft said in
http://suppport.microsoftl.com/defau...b;en-us;329332
If I change Node1 with Windows 2000 Server Standard Edition and SQL Server
2000 SP3a, the distribution transaction run OK.
Thanks a lot.
Hi
Windows 2003 has more secure defaults than Windows 2000 therefore it is
probably something that has not been configured that is causing the problem
Check out http://support.microsoft.com/kb/839279/
http://support.microsoft.com/kb/191168/
http://support.microsoft.com/kb/306843/
http://support.microsoft.com/kb/306843/
http://support.microsoft.com/kb/329332
http://support.microsoft.com/kb/306212
You can use DTCPing to check it can communicate with the server
http://download.microsoft.com/downlo...c1/dtcping.exe
John
"FRF" wrote:
> Node 1:
> Windows 2003 Server Standar Edition SP1
> SQL Server 2005 Standar Edition
> Node 2:
> Windows 2000 Server SP4
> SQL Server 2000 Standar Edition SP3a
> Node 1 have node 2 like "linked server", node 2 have node 1 like "linked
> server" too.
> Both nodes use Microsoft OLE DB Provider for SQL Server.
> Node 1 begins a distributed transaction vs Node 2.
> Transaction KO with
> "Server: Msg 7391, Level 16, State 1, Line 1
> 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]."
> MS DTS is configured in Node 1 like microsoft said in
> http://suppport.microsoftl.com/defau...b;en-us;329332
> If I change Node1 with Windows 2000 Server Standard Edition and SQL Server
> 2000 SP3a, the distribution transaction run OK.
> Thanks a lot.
>
sql
Error 7391 when distributed transaction started
Node 1:
Windows 2003 Server Standar Edition SP1
SQL Server 2005 Standar Edition
Node 2:
Windows 2000 Server SP4
SQL Server 2000 Standar Edition SP3a
Node 1 have node 2 like "linked server", node 2 have node 1 like "linked
server" too.
Both nodes use Microsoft OLE DB Provider for SQL Server.
Node 1 begins a distributed transaction vs Node 2.
Transaction KO with
"Server: Msg 7391, Level 16, State 1, Line 1
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]."
MS DTS is configured in Node 1 like microsoft said in
http://suppport.microsoftl.com/default.aspx?scid=kb;en-us;329332
If I change Node1 with Windows 2000 Server Standard Edition and SQL Server
2000 SP3a, the distribution transaction run OK.
Thanks a lot.Hi
Windows 2003 has more secure defaults than Windows 2000 therefore it is
probably something that has not been configured that is causing the problem
Check out http://support.microsoft.com/kb/839279/
http://support.microsoft.com/kb/191168/
http://support.microsoft.com/kb/306843/
http://support.microsoft.com/kb/306843/
http://support.microsoft.com/kb/329332
http://support.microsoft.com/kb/306212
You can use DTCPing to check it can communicate with the server
http://download.microsoft.com/download/d/0/0/d00c8f6b-135d-4441-a97b-9de16a1935c1/dtcping.exe
John
"FRF" wrote:
> Node 1:
> Windows 2003 Server Standar Edition SP1
> SQL Server 2005 Standar Edition
> Node 2:
> Windows 2000 Server SP4
> SQL Server 2000 Standar Edition SP3a
> Node 1 have node 2 like "linked server", node 2 have node 1 like "linked
> server" too.
> Both nodes use Microsoft OLE DB Provider for SQL Server.
> Node 1 begins a distributed transaction vs Node 2.
> Transaction KO with
> "Server: Msg 7391, Level 16, State 1, Line 1
> 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]."
> MS DTS is configured in Node 1 like microsoft said in
> http://suppport.microsoftl.com/default.aspx?scid=kb;en-us;329332
> If I change Node1 with Windows 2000 Server Standard Edition and SQL Server
> 2000 SP3a, the distribution transaction run OK.
> Thanks a lot.
>
Windows 2003 Server Standar Edition SP1
SQL Server 2005 Standar Edition
Node 2:
Windows 2000 Server SP4
SQL Server 2000 Standar Edition SP3a
Node 1 have node 2 like "linked server", node 2 have node 1 like "linked
server" too.
Both nodes use Microsoft OLE DB Provider for SQL Server.
Node 1 begins a distributed transaction vs Node 2.
Transaction KO with
"Server: Msg 7391, Level 16, State 1, Line 1
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]."
MS DTS is configured in Node 1 like microsoft said in
http://suppport.microsoftl.com/default.aspx?scid=kb;en-us;329332
If I change Node1 with Windows 2000 Server Standard Edition and SQL Server
2000 SP3a, the distribution transaction run OK.
Thanks a lot.Hi
Windows 2003 has more secure defaults than Windows 2000 therefore it is
probably something that has not been configured that is causing the problem
Check out http://support.microsoft.com/kb/839279/
http://support.microsoft.com/kb/191168/
http://support.microsoft.com/kb/306843/
http://support.microsoft.com/kb/306843/
http://support.microsoft.com/kb/329332
http://support.microsoft.com/kb/306212
You can use DTCPing to check it can communicate with the server
http://download.microsoft.com/download/d/0/0/d00c8f6b-135d-4441-a97b-9de16a1935c1/dtcping.exe
John
"FRF" wrote:
> Node 1:
> Windows 2003 Server Standar Edition SP1
> SQL Server 2005 Standar Edition
> Node 2:
> Windows 2000 Server SP4
> SQL Server 2000 Standar Edition SP3a
> Node 1 have node 2 like "linked server", node 2 have node 1 like "linked
> server" too.
> Both nodes use Microsoft OLE DB Provider for SQL Server.
> Node 1 begins a distributed transaction vs Node 2.
> Transaction KO with
> "Server: Msg 7391, Level 16, State 1, Line 1
> 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]."
> MS DTS is configured in Node 1 like microsoft said in
> http://suppport.microsoftl.com/default.aspx?scid=kb;en-us;329332
> If I change Node1 with Windows 2000 Server Standard Edition and SQL Server
> 2000 SP3a, the distribution transaction run OK.
> Thanks a lot.
>
Error 7391 running distributed transaction
When attempting to run a distributed transaction I get the following
error:
Server: Msg 7391, Level 16, State 1, Line 4
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].
I have two servers.
ServerA
Windows 2003
SQL Server 2000 SP3a
MDAC 2.8 RTM
ServerB
Windows 2000
SQL Server 2000 SP3a
MDAC 2.8 RTM
When I open Query Analyzer on ServerA and execute the following
statement, I get the error.
begin distributed transaction
exec ServerB.master.dbo.sp_helpdb
I've already enabled network access for Component Services:
http://support.microsoft.com/default.aspx?kbid=329332
Didn't fix the issue.
Any ideas?
Thanks,
MarkMake sure that the DTC Service is running on both machines as well..
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Mark Newton" <mark.newton@.bdsmarketing.com> wrote in message
news:0ia5sv0ifue6po44fbc1j3aipvpas38put@.4ax.com...
> When attempting to run a distributed transaction I get the following
> error:
> Server: Msg 7391, Level 16, State 1, Line 4
> 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].
>
> I have two servers.
> ServerA
> Windows 2003
> SQL Server 2000 SP3a
> MDAC 2.8 RTM
> ServerB
> Windows 2000
> SQL Server 2000 SP3a
> MDAC 2.8 RTM
> When I open Query Analyzer on ServerA and execute the following
> statement, I get the error.
> begin distributed transaction
> exec ServerB.master.dbo.sp_helpdb
>
> I've already enabled network access for Component Services:
> http://support.microsoft.com/default.aspx?kbid=329332
> Didn't fix the issue.
> Any ideas?
> Thanks,
> Mark|||MSDTC is running on both machines.
On Tue, 25 Nov 2003 05:45:42 -0500, "Wayne Snyder"
<wsnyder@.computeredservices.com> wrote:
>Make sure that the DTC Service is running on both machines as well..
error:
Server: Msg 7391, Level 16, State 1, Line 4
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].
I have two servers.
ServerA
Windows 2003
SQL Server 2000 SP3a
MDAC 2.8 RTM
ServerB
Windows 2000
SQL Server 2000 SP3a
MDAC 2.8 RTM
When I open Query Analyzer on ServerA and execute the following
statement, I get the error.
begin distributed transaction
exec ServerB.master.dbo.sp_helpdb
I've already enabled network access for Component Services:
http://support.microsoft.com/default.aspx?kbid=329332
Didn't fix the issue.
Any ideas?
Thanks,
MarkMake sure that the DTC Service is running on both machines as well..
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Mark Newton" <mark.newton@.bdsmarketing.com> wrote in message
news:0ia5sv0ifue6po44fbc1j3aipvpas38put@.4ax.com...
> When attempting to run a distributed transaction I get the following
> error:
> Server: Msg 7391, Level 16, State 1, Line 4
> 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].
>
> I have two servers.
> ServerA
> Windows 2003
> SQL Server 2000 SP3a
> MDAC 2.8 RTM
> ServerB
> Windows 2000
> SQL Server 2000 SP3a
> MDAC 2.8 RTM
> When I open Query Analyzer on ServerA and execute the following
> statement, I get the error.
> begin distributed transaction
> exec ServerB.master.dbo.sp_helpdb
>
> I've already enabled network access for Component Services:
> http://support.microsoft.com/default.aspx?kbid=329332
> Didn't fix the issue.
> Any ideas?
> Thanks,
> Mark|||MSDTC is running on both machines.
On Tue, 25 Nov 2003 05:45:42 -0500, "Wayne Snyder"
<wsnyder@.computeredservices.com> wrote:
>Make sure that the DTC Service is running on both machines as well..
error 7391 in distributed transaction
I have a procedure running locally on my server A. This procedure does an
insert into a table after getting a return value from a select done on
another server say B . Server B is set up as linked server on server A. th
error i get shows as
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].
Has anyone seen this before? Is there any solution to this or any setting
that needs to be changed to get this working? any help will be greatly
appreciated.
TIA
Message posted via http://www.webservertalk.comFor distributed transaction you need to have a Primary key on updated table.
So pLease add primary key to resolve your issue. Please let me know if
doesn't work.
Regards,
Jagan Mohan
MCDBA
"ishaan99 via webservertalk.com" wrote:
> I have a procedure running locally on my server A. This procedure does an
> insert into a table after getting a return value from a select done on
> another server say B . Server B is set up as linked server on server A. th
> error i get shows as
> 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].
> Has anyone seen this before? Is there any solution to this or any setting
> that needs to be changed to get this working? any help will be greatly
> appreciated.
> TIA
> --
> Message posted via http://www.webservertalk.com
>|||I've had this same error, mine only happened during times when transactions
were high on the system, I think there is a setting to increase the number o
f
concurrent distributed transactions, don't know what else you could do, I
know it has to do with MSDTC.
"ishaan99 via webservertalk.com" wrote:
> I have a procedure running locally on my server A. This procedure does an
> insert into a table after getting a return value from a select done on
> another server say B . Server B is set up as linked server on server A. th
> error i get shows as
> 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].
> Has anyone seen this before? Is there any solution to this or any setting
> that needs to be changed to get this working? any help will be greatly
> appreciated.
> TIA
> --
> Message posted via http://www.webservertalk.com
>sql
insert into a table after getting a return value from a select done on
another server say B . Server B is set up as linked server on server A. th
error i get shows as
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].
Has anyone seen this before? Is there any solution to this or any setting
that needs to be changed to get this working? any help will be greatly
appreciated.
TIA
Message posted via http://www.webservertalk.comFor distributed transaction you need to have a Primary key on updated table.
So pLease add primary key to resolve your issue. Please let me know if
doesn't work.
Regards,
Jagan Mohan
MCDBA
"ishaan99 via webservertalk.com" wrote:
> I have a procedure running locally on my server A. This procedure does an
> insert into a table after getting a return value from a select done on
> another server say B . Server B is set up as linked server on server A. th
> error i get shows as
> 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].
> Has anyone seen this before? Is there any solution to this or any setting
> that needs to be changed to get this working? any help will be greatly
> appreciated.
> TIA
> --
> Message posted via http://www.webservertalk.com
>|||I've had this same error, mine only happened during times when transactions
were high on the system, I think there is a setting to increase the number o
f
concurrent distributed transactions, don't know what else you could do, I
know it has to do with MSDTC.
"ishaan99 via webservertalk.com" wrote:
> I have a procedure running locally on my server A. This procedure does an
> insert into a table after getting a return value from a select done on
> another server say B . Server B is set up as linked server on server A. th
> error i get shows as
> 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].
> Has anyone seen this before? Is there any solution to this or any setting
> that needs to be changed to get this working? any help will be greatly
> appreciated.
> TIA
> --
> Message posted via http://www.webservertalk.com
>sql
Error 7391 for distributed transaction between SQL Server and Oracle
Hi,
I am using SQL server 2000 on Windows 2003 SP1.I am trying to insert a
row into SQL server and Oracle through a Stored Proc.
If i run the sql statement using Query Analyzer with openrowset,i am
able to insert the row fine.
But when it is done through SP it throws this error.
Server: Msg 7391, Level 16, State 1, Procedure
SP_AutoInsertIncentive_oracle, Line 19
The operation could not be performed because the OLE DB provider
'MSDAORA' was unable to begin a distributed transaction.
OLE DB error trace [OLE/DB Provider 'MSDAORA'
ITransactionJoin::JoinTransaction returned 0x8004d01b].
Thanks a lot in advance for your help.
AJHi,
You can try this
[url]http://support.microsoft.com/default.aspx?scid=kb;en-us;306212&Product=sql2k.[/url
]
Hope it helps.
Danijel Novak
<aj70000@.hotmail.com> wrote in message
news:1137444337.934408.326330@.g47g2000cwa.googlegroups.com...
> Hi,
> I am using SQL server 2000 on Windows 2003 SP1.I am trying to insert a
> row into SQL server and Oracle through a Stored Proc.
> If i run the sql statement using Query Analyzer with openrowset,i am
> able to insert the row fine.
> But when it is done through SP it throws this error.
>
> Server: Msg 7391, Level 16, State 1, Procedure
> SP_AutoInsertIncentive_oracle, Line 19
> The operation could not be performed because the OLE DB provider
> 'MSDAORA' was unable to begin a distributed transaction.
> OLE DB error trace [OLE/DB Provider 'MSDAORA'
> ITransactionJoin::JoinTransaction returned 0x8004d01b].
> Thanks a lot in advance for your help.
> AJ
>
I am using SQL server 2000 on Windows 2003 SP1.I am trying to insert a
row into SQL server and Oracle through a Stored Proc.
If i run the sql statement using Query Analyzer with openrowset,i am
able to insert the row fine.
But when it is done through SP it throws this error.
Server: Msg 7391, Level 16, State 1, Procedure
SP_AutoInsertIncentive_oracle, Line 19
The operation could not be performed because the OLE DB provider
'MSDAORA' was unable to begin a distributed transaction.
OLE DB error trace [OLE/DB Provider 'MSDAORA'
ITransactionJoin::JoinTransaction returned 0x8004d01b].
Thanks a lot in advance for your help.
AJHi,
You can try this
[url]http://support.microsoft.com/default.aspx?scid=kb;en-us;306212&Product=sql2k.[/url
]
Hope it helps.
Danijel Novak
<aj70000@.hotmail.com> wrote in message
news:1137444337.934408.326330@.g47g2000cwa.googlegroups.com...
> Hi,
> I am using SQL server 2000 on Windows 2003 SP1.I am trying to insert a
> row into SQL server and Oracle through a Stored Proc.
> If i run the sql statement using Query Analyzer with openrowset,i am
> able to insert the row fine.
> But when it is done through SP it throws this error.
>
> Server: Msg 7391, Level 16, State 1, Procedure
> SP_AutoInsertIncentive_oracle, Line 19
> The operation could not be performed because the OLE DB provider
> 'MSDAORA' was unable to begin a distributed transaction.
> OLE DB error trace [OLE/DB Provider 'MSDAORA'
> ITransactionJoin::JoinTransaction returned 0x8004d01b].
> Thanks a lot in advance for your help.
> AJ
>
Error 7391 for distributed transaction between SQL Server and Oracle
Hi,
I am using SQL server 2000 on Windows 2003 SP1.I am trying to insert a
row into SQL server and Oracle through a Stored Proc.
If i run the sql statement using Query Analyzer with openrowset,i am
able to insert the row fine.
But when it is done through SP it throws this error.
Server: Msg 7391, Level 16, State 1, Procedure
SP_AutoInsertIncentive_oracle, Line 19
The operation could not be performed because the OLE DB provider
'MSDAORA' was unable to begin a distributed transaction.
OLE DB error trace [OLE/DB Provider 'MSDAORA'
ITransactionJoin::JoinTransaction returned 0x8004d01b].
Thanks a lot in advance for your help.
AJHi,
You can try this
http://support.microsoft.com/default.aspx?scid=kb;en-us;306212&Product=sql2k.
Hope it helps.
--
Danijel Novak
<aj70000@.hotmail.com> wrote in message
news:1137444337.934408.326330@.g47g2000cwa.googlegroups.com...
> Hi,
> I am using SQL server 2000 on Windows 2003 SP1.I am trying to insert a
> row into SQL server and Oracle through a Stored Proc.
> If i run the sql statement using Query Analyzer with openrowset,i am
> able to insert the row fine.
> But when it is done through SP it throws this error.
>
> Server: Msg 7391, Level 16, State 1, Procedure
> SP_AutoInsertIncentive_oracle, Line 19
> The operation could not be performed because the OLE DB provider
> 'MSDAORA' was unable to begin a distributed transaction.
> OLE DB error trace [OLE/DB Provider 'MSDAORA'
> ITransactionJoin::JoinTransaction returned 0x8004d01b].
> Thanks a lot in advance for your help.
> AJ
>
I am using SQL server 2000 on Windows 2003 SP1.I am trying to insert a
row into SQL server and Oracle through a Stored Proc.
If i run the sql statement using Query Analyzer with openrowset,i am
able to insert the row fine.
But when it is done through SP it throws this error.
Server: Msg 7391, Level 16, State 1, Procedure
SP_AutoInsertIncentive_oracle, Line 19
The operation could not be performed because the OLE DB provider
'MSDAORA' was unable to begin a distributed transaction.
OLE DB error trace [OLE/DB Provider 'MSDAORA'
ITransactionJoin::JoinTransaction returned 0x8004d01b].
Thanks a lot in advance for your help.
AJHi,
You can try this
http://support.microsoft.com/default.aspx?scid=kb;en-us;306212&Product=sql2k.
Hope it helps.
--
Danijel Novak
<aj70000@.hotmail.com> wrote in message
news:1137444337.934408.326330@.g47g2000cwa.googlegroups.com...
> Hi,
> I am using SQL server 2000 on Windows 2003 SP1.I am trying to insert a
> row into SQL server and Oracle through a Stored Proc.
> If i run the sql statement using Query Analyzer with openrowset,i am
> able to insert the row fine.
> But when it is done through SP it throws this error.
>
> Server: Msg 7391, Level 16, State 1, Procedure
> SP_AutoInsertIncentive_oracle, Line 19
> The operation could not be performed because the OLE DB provider
> 'MSDAORA' was unable to begin a distributed transaction.
> OLE DB error trace [OLE/DB Provider 'MSDAORA'
> ITransactionJoin::JoinTransaction returned 0x8004d01b].
> Thanks a lot in advance for your help.
> AJ
>
Error 7391 for distributed transaction between SQL Server and Oracle
Hi,
I am using SQL server 2000 on Windows 2003 SP1.I am trying to insert a
row into SQL server and Oracle through a Stored Proc.
If i run the sql statement using Query Analyzer with openrowset,i am
able to insert the row fine.
But when it is done through SP it throws this error.
Server: Msg 7391, Level 16, State 1, Procedure
SP_AutoInsertIncentive_oracle, Line 19
The operation could not be performed because the OLE DB provider
'MSDAORA' was unable to begin a distributed transaction.
OLE DB error trace [OLE/DB Provider 'MSDAORA'
ITransactionJoin::JoinTransaction returned 0x8004d01b].
Thanks a lot in advance for your help.
AJ
Hi,
You can try this
http://support.microsoft.com/default...Product=sql2k.
Hope it helps.
Danijel Novak
<aj70000@.hotmail.com> wrote in message
news:1137444337.934408.326330@.g47g2000cwa.googlegr oups.com...
> Hi,
> I am using SQL server 2000 on Windows 2003 SP1.I am trying to insert a
> row into SQL server and Oracle through a Stored Proc.
> If i run the sql statement using Query Analyzer with openrowset,i am
> able to insert the row fine.
> But when it is done through SP it throws this error.
>
> Server: Msg 7391, Level 16, State 1, Procedure
> SP_AutoInsertIncentive_oracle, Line 19
> The operation could not be performed because the OLE DB provider
> 'MSDAORA' was unable to begin a distributed transaction.
> OLE DB error trace [OLE/DB Provider 'MSDAORA'
> ITransactionJoin::JoinTransaction returned 0x8004d01b].
> Thanks a lot in advance for your help.
> AJ
>
I am using SQL server 2000 on Windows 2003 SP1.I am trying to insert a
row into SQL server and Oracle through a Stored Proc.
If i run the sql statement using Query Analyzer with openrowset,i am
able to insert the row fine.
But when it is done through SP it throws this error.
Server: Msg 7391, Level 16, State 1, Procedure
SP_AutoInsertIncentive_oracle, Line 19
The operation could not be performed because the OLE DB provider
'MSDAORA' was unable to begin a distributed transaction.
OLE DB error trace [OLE/DB Provider 'MSDAORA'
ITransactionJoin::JoinTransaction returned 0x8004d01b].
Thanks a lot in advance for your help.
AJ
Hi,
You can try this
http://support.microsoft.com/default...Product=sql2k.
Hope it helps.
Danijel Novak
<aj70000@.hotmail.com> wrote in message
news:1137444337.934408.326330@.g47g2000cwa.googlegr oups.com...
> Hi,
> I am using SQL server 2000 on Windows 2003 SP1.I am trying to insert a
> row into SQL server and Oracle through a Stored Proc.
> If i run the sql statement using Query Analyzer with openrowset,i am
> able to insert the row fine.
> But when it is done through SP it throws this error.
>
> Server: Msg 7391, Level 16, State 1, Procedure
> SP_AutoInsertIncentive_oracle, Line 19
> The operation could not be performed because the OLE DB provider
> 'MSDAORA' was unable to begin a distributed transaction.
> OLE DB error trace [OLE/DB Provider 'MSDAORA'
> ITransactionJoin::JoinTransaction returned 0x8004d01b].
> Thanks a lot in advance for your help.
> AJ
>
Monday, March 19, 2012
Error 627:Cannot use SAVE TRANSACTION within a distributed transac
Information:
SQL Server 2000 Enterprise Edition
Server Pack 3a
Server Edition is Windows 2000 Advanced Server
Replication Type is Transactional
I am trying to drop a publication. I am getting the error:
Error 627:Cannot use SAVE TRANSACTION within a distributed transaction
This error also is generated when trying to drop the individual subscription.
Can anyone provide insight as to what could be causing this error?
Thank you in advance.
Robert M.Check the "remote proc trans" value from sp_configure. If it's 1, you need
to change it to 0.
"Robert M." <RobertM@.discussions.microsoft.com> wrote in message
news:28E165FE-67B2-44F1-98DC-1F2CB3EA0B7E@.microsoft.com...
> Information:
> SQL Server 2000 Enterprise Edition
> Server Pack 3a
> Server Edition is Windows 2000 Advanced Server
> Replication Type is Transactional
> I am trying to drop a publication. I am getting the error:
> Error 627:Cannot use SAVE TRANSACTION within a distributed transaction
> This error also is generated when trying to drop the individual
subscription.
> Can anyone provide insight as to what could be causing this error?
> Thank you in advance.
> Robert M.
>|||I am assuming that the 'remote proc trans' setting needs to be set to zero on
the publisher (i have separate servers for distributor/publisher/subscriber).
Thanks...Robert M.
"Richard Ding" wrote:
> Check the "remote proc trans" value from sp_configure. If it's 1, you need
> to change it to 0.
>
> "Robert M." <RobertM@.discussions.microsoft.com> wrote in message
> news:28E165FE-67B2-44F1-98DC-1F2CB3EA0B7E@.microsoft.com...
> > Information:
> > SQL Server 2000 Enterprise Edition
> > Server Pack 3a
> > Server Edition is Windows 2000 Advanced Server
> > Replication Type is Transactional
> >
> > I am trying to drop a publication. I am getting the error:
> > Error 627:Cannot use SAVE TRANSACTION within a distributed transaction
> >
> > This error also is generated when trying to drop the individual
> subscription.
> >
> > Can anyone provide insight as to what could be causing this error?
> >
> > Thank you in advance.
> >
> > Robert M.
> >
> >
>
>|||Actually, I believe it should be set to 0 on the subscriber. No need to
touch the values on publisher or distributor.
"Robert M." <RobertM@.discussions.microsoft.com> wrote in message
news:4A56EC3F-0537-441C-990E-0C7D43BD972C@.microsoft.com...
> I am assuming that the 'remote proc trans' setting needs to be set to zero
on
> the publisher (i have separate servers for
distributor/publisher/subscriber).
> Thanks...Robert M.
> "Richard Ding" wrote:
> > Check the "remote proc trans" value from sp_configure. If it's 1, you
need
> > to change it to 0.
> >
> >
> > "Robert M." <RobertM@.discussions.microsoft.com> wrote in message
> > news:28E165FE-67B2-44F1-98DC-1F2CB3EA0B7E@.microsoft.com...
> > > Information:
> > > SQL Server 2000 Enterprise Edition
> > > Server Pack 3a
> > > Server Edition is Windows 2000 Advanced Server
> > > Replication Type is Transactional
> > >
> > > I am trying to drop a publication. I am getting the error:
> > > Error 627:Cannot use SAVE TRANSACTION within a distributed transaction
> > >
> > > This error also is generated when trying to drop the individual
> > subscription.
> > >
> > > Can anyone provide insight as to what could be causing this error?
> > >
> > > Thank you in advance.
> > >
> > > Robert M.
> > >
> > >
> >
> >
> >
SQL Server 2000 Enterprise Edition
Server Pack 3a
Server Edition is Windows 2000 Advanced Server
Replication Type is Transactional
I am trying to drop a publication. I am getting the error:
Error 627:Cannot use SAVE TRANSACTION within a distributed transaction
This error also is generated when trying to drop the individual subscription.
Can anyone provide insight as to what could be causing this error?
Thank you in advance.
Robert M.Check the "remote proc trans" value from sp_configure. If it's 1, you need
to change it to 0.
"Robert M." <RobertM@.discussions.microsoft.com> wrote in message
news:28E165FE-67B2-44F1-98DC-1F2CB3EA0B7E@.microsoft.com...
> Information:
> SQL Server 2000 Enterprise Edition
> Server Pack 3a
> Server Edition is Windows 2000 Advanced Server
> Replication Type is Transactional
> I am trying to drop a publication. I am getting the error:
> Error 627:Cannot use SAVE TRANSACTION within a distributed transaction
> This error also is generated when trying to drop the individual
subscription.
> Can anyone provide insight as to what could be causing this error?
> Thank you in advance.
> Robert M.
>|||I am assuming that the 'remote proc trans' setting needs to be set to zero on
the publisher (i have separate servers for distributor/publisher/subscriber).
Thanks...Robert M.
"Richard Ding" wrote:
> Check the "remote proc trans" value from sp_configure. If it's 1, you need
> to change it to 0.
>
> "Robert M." <RobertM@.discussions.microsoft.com> wrote in message
> news:28E165FE-67B2-44F1-98DC-1F2CB3EA0B7E@.microsoft.com...
> > Information:
> > SQL Server 2000 Enterprise Edition
> > Server Pack 3a
> > Server Edition is Windows 2000 Advanced Server
> > Replication Type is Transactional
> >
> > I am trying to drop a publication. I am getting the error:
> > Error 627:Cannot use SAVE TRANSACTION within a distributed transaction
> >
> > This error also is generated when trying to drop the individual
> subscription.
> >
> > Can anyone provide insight as to what could be causing this error?
> >
> > Thank you in advance.
> >
> > Robert M.
> >
> >
>
>|||Actually, I believe it should be set to 0 on the subscriber. No need to
touch the values on publisher or distributor.
"Robert M." <RobertM@.discussions.microsoft.com> wrote in message
news:4A56EC3F-0537-441C-990E-0C7D43BD972C@.microsoft.com...
> I am assuming that the 'remote proc trans' setting needs to be set to zero
on
> the publisher (i have separate servers for
distributor/publisher/subscriber).
> Thanks...Robert M.
> "Richard Ding" wrote:
> > Check the "remote proc trans" value from sp_configure. If it's 1, you
need
> > to change it to 0.
> >
> >
> > "Robert M." <RobertM@.discussions.microsoft.com> wrote in message
> > news:28E165FE-67B2-44F1-98DC-1F2CB3EA0B7E@.microsoft.com...
> > > Information:
> > > SQL Server 2000 Enterprise Edition
> > > Server Pack 3a
> > > Server Edition is Windows 2000 Advanced Server
> > > Replication Type is Transactional
> > >
> > > I am trying to drop a publication. I am getting the error:
> > > Error 627:Cannot use SAVE TRANSACTION within a distributed transaction
> > >
> > > This error also is generated when trying to drop the individual
> > subscription.
> > >
> > > Can anyone provide insight as to what could be causing this error?
> > >
> > > Thank you in advance.
> > >
> > > Robert M.
> > >
> > >
> >
> >
> >
Subscribe to:
Posts (Atom)