Replication problem

I'm getting this error with a transactional replication
publication I'm working with, I think my distribution
database is hosed, I got another error cannot find object
syspublications, I'm just kind of wondering how it got
that way and how I can fix it...
TIA
SQL Server Enterprise Manager encountered errors creating
push subscriptions for the following Subscribers:
MNCOROLAPTST-V1: Error 2601: Cannot insert duplicate key
row in object 'MSsubscriptions' with unique
index 'ucMSsubscriptions'.
Could not update the distribution database subscription
table. The subscription status could not be changed.
The subscription could not be created.
The statement has been terminated.
BTW, has anyone noticed that the msnews.microsoft.com
server was down to day, or is that just me...?
Its just you
Your problem though sounds very unusual. How are you creating your
subscriptions? Via a script?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Dan" <anonymous@.discussions.microsoft.com> wrote in message
news:112301c4a1b3$ae62e070$a301280a@.phx.gbl...
> I'm getting this error with a transactional replication
> publication I'm working with, I think my distribution
> database is hosed, I got another error cannot find object
> syspublications, I'm just kind of wondering how it got
> that way and how I can fix it...
> TIA
>
> SQL Server Enterprise Manager encountered errors creating
> push subscriptions for the following Subscribers:
> MNCOROLAPTST-V1: Error 2601: Cannot insert duplicate key
> row in object 'MSsubscriptions' with unique
> index 'ucMSsubscriptions'.
> Could not update the distribution database subscription
> table. The subscription status could not be changed.
> The subscription could not be created.
> The statement has been terminated.
>
> BTW, has anyone noticed that the msnews.microsoft.com
> server was down to day, or is that just me...?
|||Hello Hilary,
We typically use Enterprise Manager Replication >
Publications > Publication [Context Menu] Push New
subscription.. This was working without any problems
before our tech ops guys restored a database that happens
to contain the articles for the publication on the
server...
Can I blow away the distribution database and start
over...? Right now I cannot delete any pubs create any
subscriptions or anything else with replication it's
totally useless on this box..
Thanks, I appreciate your help!!
Dan

>--Original Message--
>Its just you
>Your problem though sounds very unusual. How are you
creating your
>subscriptions? Via a script?
>--
>Hilary Cotter
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>"Dan" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:112301c4a1b3$ae62e070$a301280a@.phx.gbl...
object[vbcol=seagreen]
creating[vbcol=seagreen]
key
>
>.
>
|||Now it all makes sense. An easy way around this is to recreate your
publications with a different name.
However, you will probably be best to disable replication (tools,
replication, disable publishing) and then by re-enabling your server for
replication.
"Dan" <anonymous@.discussions.microsoft.com> wrote in message
news:034201c4a1bc$28d8b1b0$a501280a@.phx.gbl...[vbcol=seagreen]
> Hello Hilary,
> We typically use Enterprise Manager Replication >
> Publications > Publication [Context Menu] Push New
> subscription.. This was working without any problems
> before our tech ops guys restored a database that happens
> to contain the articles for the publication on the
> server...
> Can I blow away the distribution database and start
> over...? Right now I cannot delete any pubs create any
> subscriptions or anything else with replication it's
> totally useless on this box..
> Thanks, I appreciate your help!!
> Dan
>
> creating your
> message
> object
> creating
> key
|||That's exactly what I was looking for...
Thanks!!!
Dan

>--Original Message--
>Now it all makes sense. An easy way around this is to
recreate your
>publications with a different name.
>However, you will probably be best to disable replication
(tools,
>replication, disable publishing) and then by re-enabling
your server for
>replication.
>"Dan" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:034201c4a1bc$28d8b1b0$a501280a@.phx.gbl...
happens[vbcol=seagreen]
replication[vbcol=seagreen]
subscription
>
>.
>