SQL 2005 error: Replication-Replication Distribution Subsystem: agent (null) failed.

[bourgon]

I'm getting this, after upgrading from 2000 to 2005.

Replication-Replication Distribution Subsystem: agent (null) failed.
The subscription to publication '(null)' has expired or does not
exist.

The only suggestions I've seen are to dump all subscriptions. Since
we have several dozen publications to several servers, is there a
decent way to script it all out, if that's the only suggestion?

Thanks in advance.

[Hilary Cotter]

Drill down on the publication in the replication folder\Local Publications.
Right click on it and select Generate Scripts.

--
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
<bo*****@gmail.comwrote in message
news:11**********************@o11g2000prd.googlegr oups.com...

I'm getting this, after upgrading from 2000 to 2005.

Replication-Replication Distribution Subsystem: agent (null) failed.
The subscription to publication '(null)' has expired or does not
exist.

The only suggestions I've seen are to dump all subscriptions. Since
we have several dozen publications to several servers, is there a
decent way to script it all out, if that's the only suggestion?

Thanks in advance.

[jeff_y]

I get the similar error message, can this be explained in terms of its
possible causes?
My observation is my transactional replication goes well without any
problems, but I keep on finding this annoying error in the sql server log.
Any thoughts on this issue is highly appreciated.

Jeff

<bo*****@gmail.comwrote in message
news:11**********************@o11g2000prd.googlegr oups.com...

I'm getting this, after upgrading from 2000 to 2005.

Replication-Replication Distribution Subsystem: agent (null) failed.
The subscription to publication '(null)' has expired or does not
exist.

The only suggestions I've seen are to dump all subscriptions. Since
we have several dozen publications to several servers, is there a
decent way to script it all out, if that's the only suggestion?

Thanks in advance.

[bourgon]

On Jun 18, 1:06 pm, "jeff_y" <[e-mail]:

I get the similar error message, can this be explained in terms of its
possible causes?
My observation is my transactional replication goes well without any
problems, but I keep on finding this annoying error in the sql server log.
Any thoughts on this issue is highly appreciated.

Jeff, we wound up contacting Microsoft about it. They had us run a
trace on the server (turning on the "errors and warnings"), determined
that it had something to do with subscriptions to a particular
published database, then we removed and recreated them.

We also, once we'd scripted and removed the subscriptions, we ran
sp_removedbreplication. Hope this helps.