publisher malfunction

Hi,
Has anyone seen a problem like this:
when trying to add an article to an existing publication (i.e. running
sp_addarticle) I get the following error if I run it from my workstation:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
(CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
the error is a bit more descriptive when running from the server console:
Server: Msg 8526, Level 16, State 2, Procedure sp_helpdistributor, Line 79
Cannot go remote while the session is enlisted in a distributed transaction
that has an active savepoint.
Connection Broken
Any input would be appreciated
run a dbcc opentrans and see if there is an open or orphaned transaction.
use dbcc inputbuffer to evaluate whether you can kill it or not. If so, kill
it and try to run the sp_addarticle command again.
Also is this with a remote distributor?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Mor DeRor" <MorDeRor@.discussions.microsoft.com> wrote in message
news:55DBD5B3-15F1-4130-8BB8-F3B2FA7294BC@.microsoft.com...
> Hi,
> Has anyone seen a problem like this:
> when trying to add an article to an existing publication (i.e. running
> sp_addarticle) I get the following error if I run it from my workstation:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
> (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
> the error is a bit more descriptive when running from the server console:
> Server: Msg 8526, Level 16, State 2, Procedure sp_helpdistributor, Line 79
> Cannot go remote while the session is enlisted in a distributed
> transaction
> that has an active savepoint.
> Connection Broken
> Any input would be appreciated
|||Thanks Hilary, but it does not look like there is an open transaction. here
is the oputput of DBCC OPENTRAN:
Replicated Transaction Information:
Oldest distributed LSN : (2215838:4377:1)
Oldest non-distributed LSN : (0:0:0)
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
"Hilary Cotter" wrote:

> run a dbcc opentrans and see if there is an open or orphaned transaction.
> use dbcc inputbuffer to evaluate whether you can kill it or not. If so, kill
> it and try to run the sp_addarticle command again.
> Also is this with a remote distributor?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Mor DeRor" <MorDeRor@.discussions.microsoft.com> wrote in message
> news:55DBD5B3-15F1-4130-8BB8-F3B2FA7294BC@.microsoft.com...
>
>
|||I found a solution, in case anyone else is interested. It had to do with
"remote proc trans" option being turned on. Here is a link to the forum where
I found it:
http://www.sql-server-performance.com/forum/topic.asp?TOPIC_ID=18530
"Mor DeRor" wrote:
[vbcol=seagreen]
> Thanks Hilary, but it does not look like there is an open transaction. here
> is the oputput of DBCC OPENTRAN:
> Replicated Transaction Information:
> Oldest distributed LSN : (2215838:4377:1)
> Oldest non-distributed LSN : (0:0:0)
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
>
> "Hilary Cotter" wrote: