error when changing published article at the subscriber

Hi

Using merge replication - the stored procs are published articles.

When trying to change the article at the subscriber (sql express) I get the following errors:

Msg 21531, Level 16, State 1, Procedure sp_MSmerge_alterschemaonly, Line 45
The DDL statement cannot be performed at the Subscriber or Republisher.

Msg 21530, Level 16, State 1, Procedure sp_MSmerge_ddldispatcher, Line 181
The DDL operation failed inside merge DDL replication manipulation.

Msg 3609, Level 16, State 2, Procedure usp_Anniversary_upd, Line 21
The transaction ended in the trigger. The batch has been aborted.

Does this mean it can only be changed at the publisher ?

Bruce

correct. If you want to make schema changes at the subscriber, you need to set @.replicate_ddl to false in sp_addmergepublication.|||

Schema changes cannot be made at the subscriber. They have to come from the Publisher.

Message: correct. If you want to make schema changes at the subscriber, you need to set @.replicate_ddl to false in sp_addmergepublication.

I believe Greg meant "publisher only" instead of "subscriber" in the above statement.

|||

Hi

Just to clarify this.....

1. You cannot change it at the subscriber, irrespective of whether @.replicate_ddl is set to 0 or 1 ?

2. If @.replicate_ddl is set to 1, then changing the proc on the publisher will result in the proc being changed at the subscriber next time it is synchronised (if a published article)

Is this correct ?

I ask, because @.replicate_ddl is set to 1, but I get that error mentioned earlier if I try and change it at the subscriber.....

Thanks
Bruce

|||

1. you're correct, i was wrong in my earlier post.

2. correct.

Error trying to websync

Hello,

We dropped an article and then made a change to a column. We then added the article back in. Generated a snapshot and reinitialized all subscriptions without uploading data changes. After we did this we still continue to get this error. Any ideas? Thanks.

John

The Merge Agent failed after detecting that retention-based metadata cleanup has deleted metadata at the Publisher for changes not yet sent to the Subscriber. You must reinitialize the subscription (without upload).

John,

After you drop the article and before you add the article in, did you run the marge agent? Also, what version of SQL Server are you using?

|||

Yi,

No we didn't run merge agent manually. Were we supposed to? It's SQL 2k5

John

|||

The error message is telling that some metadata that is needed to enumerate what rows need to sent to the subscriber has been cleaned up. Hence you will need to reinitialize the subscription.

And you need not run the merge agent in between dropping and adding the article.

You might have encoutnered this scenario because the merge agent may not have synchronized with the publisher for a long time (time longer than the retention period)

Please reinitialize without upload, run the merge agent and report back if you still see failures.

Error trying to websync

Hello,

We dropped an article and then made a change to a column. We then added the article back in. Generated a snapshot and reinitialized all subscriptions without uploading data changes. After we did this we still continue to get this error. Any ideas? Thanks.

John

The Merge Agent failed after detecting that retention-based metadata cleanup has deleted metadata at the Publisher for changes not yet sent to the Subscriber. You must reinitialize the subscription (without upload).

John,

After you drop the article and before you add the article in, did you run the marge agent? Also, what version of SQL Server are you using?

|||

Yi,

No we didn't run merge agent manually. Were we supposed to? It's SQL 2k5

John

|||

The error message is telling that some metadata that is needed to enumerate what rows need to sent to the subscriber has been cleaned up. Hence you will need to reinitialize the subscription.

And you need not run the merge agent in between dropping and adding the article.

You might have encoutnered this scenario because the merge agent may not have synchronized with the publisher for a long time (time longer than the retention period)

Please reinitialize without upload, run the merge agent and report back if you still see failures.

Error to manually add subscription to an article

When trying to add an article back to an existing publication thats active
in transactional replication I get the following error
Server: Msg 14100, Level 16, State 1, Procedure sp_addsubscription, Line 240
Specify all articles when subscribing to a publication using concurrent
snapshot processing.
Apparently concurrent snapshot is enabled and when I did issue the
sp_addsubscription and specified the @.article parameter with the table name
, it didnt like it and threw the above error..
It wanted 'all' .. and I was afraid it would do some reinitializing,etc..
Just curious to know why we need that 'all'.. Seems kinda buggy
Interesting. I remember seeing this on Vyas's blog:
http://vyaskn.tripod.com/sqlblog/. He didn't report a solution and I'll also
take a look.
Rgds,
Paul Ibison
|||I just substituted all and it worked. It did take care of just the
respective articles.. Thank God..
With that Im thinking, should we just use all even if we dont have
concurrent snapshot enabled . Will it just take care of just those articles
we want to add manually. I'll try it out and let u know
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23zcnRGXSFHA.1528@.TK2MSFTNGP09.phx.gbl...
> Interesting. I remember seeing this on Vyas's blog:
> http://vyaskn.tripod.com/sqlblog/. He didn't report a solution and I'll
also
> take a look.
> Rgds,
> Paul Ibison
>
>

Error setting up Custom Security Extension

I am trying to set up a custom security extension. I've followed the setup
from the msdn article as well as the Microsoft Reporting Services in Action
sample. I keep getting an error when I try to start the ReportServer Service
after changing the config file. Can anyone help?
Thanks in Advance!
P.S. I looked in the log file and this looks like the first error:
ReportingServicesService!library!4!6/28/2005-16:21:10:: i INFO: Counter not
created. Category: RS Windows Service, Counter: Active Database Connections,
Instance: MSSQLSERVER. Error Message: Counter 'active database connections'
does not exist in category 'rs windows service'.Scott,
here I will suggest to restore original config files and reconfigure
them. Else please send me file, I will try to fig out the problem.
Mahesh