subscription to publication 'XXXX' is invalid

subscription to publication 'XXXX' is invalid

Post by Peter Hiros » Sat, 08 Jun 2002 05:30:05


I am working with a SQL Server 2000 on Windows 2000 Server and I am
attempting (for test purposes) create a publication and then push that
publication as a subscription to another SQL Server 2000( Workstation
running xp).

I set up the publication and subscription as outlined in the steps
below. Prior to setting up for the subscription I enable the remote
server on the publisher to "Enable Subscriptions".

Everything appears to work fine. I can see the snapshot agent run as
part of creating the subscription. After completing the Push
Subscription wizard, I can see the merge agent starting and it seems to
have properly initialized the remote database schema and copied the data
to it. What's odd is the Merge Agent errors out with the following

Last Command:

{call sp_MSgetreplicainfo(?,?,?,?,?,?,?)}

Error Message:
    The subscription to publication 'XXXX' is invalid.

Error Details:

The subscription to publication 'XXXXX' is invalid.
(Source: Merge Replication Provider (Agent); Error number: -2147201019)
The remote server is not defined as a subscription server.
(Source: yyyyy (Data source); Error number: 14010)

I checked to make sure that on the publisher I had subscriptions enabled
for the server that I was attempting to push to. Given the error message
I don't know what else to check given that it appears that all the data
seems to be copied down...

Ideas? What does it mean that the subscription is invalid? Do we have an
authenication error of sorts? If so, why is happening so late in the

Peter Hiross
The New HP

Steps used to configure publication:

Setup the Merge replication with the Windows 2000 Server as the central
publisher for the database.   The Synchronization and Subscription Merge
Agents will run on the Distributor also located on this Server.  The
Merge Agent should be configured to update the subscriptions
continuously. Additionally the subscriptions should be configured such
that they initialize the Publication including the schema and data at
each subscription site. Finally, A single publication will be used for
the database in which all tables, stored procedures, functions etc. are
published as replicable articles.  

This is accomplished as follows:
a. Under Replication folder select new publication; The Create
Replication Wizard will announce itself. Select advanced options.
b. Select XXXXX database as the publication database.
c. Select Immediate updating as the update model (option is only showed
if Advanced option selected in first screen of wizard).
d. Select Merge Replication as publication type
e. Select appropriate server model (assume All Servers running SQL
Server 2000).
f. Select PUBLISH ALL for all tables, stored procedures, views and user
defined functions associated with the XXXXX database.
g. Take default associated with Article Issued (Next)
h. Take default associated with Publication name and description
i. Take default associated with Customizing Properties of Publication (
Select No, create publication as specified).
j. Select Finish. 56 articles will comprise the publication.

Enable the Other server (Windows XP box running SQL Server 2000) as a
subscriber.  Right click on the Subscription Folder
(Replication\Subscriptions) and the server.

To Push a subscription to XP box. This can be accomplished as follows:
a. Right clicking the Compaq Remote Gateway publication under the
Replication\Publication folder of the Enterprise Manager. The Push
Subscriptions Wizard will be displayed. Select Show advanced options
b. Select the appropriate server(s) that you wish to push subscriptions
c. Select the Browse or Create button and then select the Create New
button to create the XXXX database on the other server (you are pushing
a subscription) and are assuming that the database has not yet been
created. Use XXXXX as the database name. Additionally you can specify
the location of the log file and data files.
d. Select run the agent on the distributor
e. Select Continuous for the Merge agent replication schedule.
f. Select Yes to initialize the subscription
g. Select Publisher as the proxy for resolving conflicts
h. Take Default for starting required services (next).
i. Wait for the merge agent to complete.

*** Sent via Developersdex ***
Don't just participate in USENET...get rewarded for it!


subscription to publication 'XXXX' is invalid

Post by George Li [M » Sun, 09 Jun 2002 12:21:29

Please run sp_helpserver on both of your subscriber and publisher. The id
column for local server should be 0; if it not zero, please run
sp_dropserver to drop the server entry, then run sp_addserver to re-add it:

sp_dropserver 'localservername'
sp_addserver 'localservername',local

This posting is provided "AS IS" with no warranties, and confers no rights.

Best Regards,

George Li

Microsoft Support


1. Subscription of Publication 'DATABASE' is invalid

Hi there,

I'm planning to use SQL's Merge replication feature to solve synchronization
issues. However, I got stucked at some errors. Let's say I configured
publisher and distributor at Server A. Publication created at Server A named
DataPub1. Then, I create push new subscription to Server B using Merge type.
It will initialize the schemas and everything is working properly. But, when
it comes to Synchronization process, it is failed. The error is
"Subscription of Publication 'DataPub1' is invalid". Anyone has any idea
about this?

Best regards,


2. Format function substitute?

3. Subscription to publication 'x' is invalid

4. VB 6.0 Career Opportunity

5. The subscription to publication <'publication name'> is invalid

6. NewEra

7. The subscription to publication 'publication name' is invalid

8. Add more than one value in a value list [checkbox]

9. Can't Setup a Pull Subscription to an Snapshot Publication using SQLDMO

10. Please Help: Duplicate DatabaseName : 'xxxx' error

11. Database 'xxxx', OID yyyyy, has disappeared from pg_database

12. HELP!Screen Builder PICT'XXXX.....'

13. Database 'xxxx', OID yyyyy, has disappeared from pg_database