Create Peer-to-Peer Topology Error Message

I have been trying for several days to create a peer-to-peer
replication among three servers. I first created the publication on
Server A, enabled it for peer-to-peer to peer on the publication
properties dialog then backed up the database and restored it to
servers B and C. Once restored, I tried to Configure Peer-to-Peer
Topology from the right click menu on the publication in SQL Management
Studio (2005). When I click OK, the wizard gives expected warning
messages that the log reader agent already exists. The wizard then
quits with the following error:

TITLE: Configure Peer-To-Peer Topology Wizard
------------------------------

SQL Server could not create a subscription for Subscriber 'SERVERB'.

------------------------------
ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or
batch. (Microsoft.SqlServer.ConnectionInfo)

------------------------------

The publication 'MyP2P20060510-02' does not exist.
Could not update the distribution database subscription table. The
subscription status could not be changed.
The subscription could not be created.
The subscription could not be found.
Changed database context to 'MYDB'. (Microsoft SQL Server, Error:
20026)

For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=20026&LinkId=20476

------------------------------
BUTTONS:

OK
------------------------------

Since I can see the publication under the replication folder on each of
the other two servers, I have no idea what the message really means. I
(and the ID for the replication agent) have full access to the
distribution database, the publication database, and everything else I
can think of!
Any help would be greatly appreciated.
Randy

.

Relevant Pages

  • Configure Peer-to-Peer Wizard Error
    ... replication among three servers. ... enabled it for peer-to-peer to peer on the publication ... SQL Server could not create a subscription for Subscriber 'SERVERB'. ...
    (microsoft.public.sqlserver.replication)
  • MSSQL 2000 - Merge Replication Issues
    ... I have 9 SQL servers, one is publisher and other 8 are subscribers. ... The subscription to publication 'EMAG4_CUSTOMERS_VP' is invalid. ...
    (microsoft.public.sqlserver.replication)
  • Re: SQL 2005 Peer-To-Peer - How to configure failover (If possible
    ... I originally wanted to configure Peer-To-Peer replication ... configure failover for active applications. ... I currently implemented Mirroring in which, when dealing with Web Apps ... and to delegate the loads across multiple SQL servers vs. 1 but is there a ...
    (microsoft.public.sqlserver.replication)
  • Re: SQL 2005 Peer-To-Peer - How to configure failover (If possible)
    ... Peer-to-peer is not doing that, it is only about replication of data. ... need to control the list of active nodes from your web application (and do ... and to delegate the loads across multiple SQL servers vs. 1 but is there a ...
    (microsoft.public.sqlserver.replication)
  • Distribution executable running at 100% cpu but doesnt process any transactions
    ... I added a new publication to handle some other tables. ... Both publications had push subscriptions to our Production and ... Development SQL servers. ... As a result no transactions are getting through to the ...
    (microsoft.public.sqlserver.replication)