Programmatically Reinitializing Merge Subscription From Publisher - SQL 2005

Sep 4, 2007

From the SSMS GUI it is possible to re-initialize one or all subscriptions to a merge publication. This is done at the publisher.

How can I achieve these operations programmatically?

In particular, how do I initialize a single merge subscription from the publisher?


I have looked at the documentation for sp_reinitmergepullsubscription but it says that this proc must be run at the subscriber - which isn't much use when subscribers are disconnected for the majority of the time

I have a large number of merge subscribers and want to reinitialize all except one

aero1


View 3 Replies


ADVERTISEMENT

Replication: Remove Merge Subscription Without Existing Publisher?

Feb 26, 2004

Hi all,
I'm a rather newbie, not only to this forum but also to sql server having a question to the following issue:
Is it possible to drop/remove/delete the "orphan" of a merge subscription on one instance of sql server without having the (former) distributor/publisher (on other instance) available?
The background is: I had a small replication infrastructure with two instances (on two machines), one the publisher and distributor, the other the subscriber. Now it happened that the publisher/distributor machine was completely set up new without having the replication dropped in advance, what remained on the subscriber is now a database with all the merge/replication tables and the guid columns in the user tables.
Moreover this, an entry remained in the subscription saying that a subscription with the former publisher exists...

Can I remove these "orphans" without having to setup the instance again?

Thank you,
Andy

View 4 Replies View Related

Data Loss When Reinitializing Subscription

Aug 22, 2007


we had setup merge replication on 2 db servers. For some reason, the subscription started failing a month back with the error " invalid object sysmergexxxx on the subscriber. I did a reinitialize and now all the changes on the subscriber which werent synced got deleted. I have tried all 3 log recovery tools with no luck. Is there any hope of recovering data. the last backup on the subscriber was a month ago.

View 1 Replies View Related

Reinitializing Push Subscription After It Expired In Transactional Replication

Jan 24, 2007

I am using SQL 2000. How can I get my transactional replication reinitialized after it has failed with several attempts.

I know one way of doing it through enterprise manager and specifying the subscription to reinitialize. But this will apply the snapshot and will take long time.

Is there a fast way of doing it?

-Nipul

View 1 Replies View Related

Merge 2005 - A Row From This Table Will Go To Only One Subscription

Jul 31, 2007

Hello everyone.

We've been using replication since a while now and I just discovered that some user are not getting all the data they should. Let me explain the way the whole thing is configured for us.

We have a few tables that are replicated using the Merge process with filtering on the data using SUSER_SNAME() function. My users are salesrep using Laptop and they are synchronizing on demand. The merge process is configured so that a row will go to only one subscription --> Each rep has their owns customers and related tables informations.

I noticed that some users do not have locally all data (from their customers) from some tables while they should. I didn't checked in details but it is possible that these users are new reps replacing other staff that left the company. Is it possible that the data they do not receive is marked as to be previous reps owner because the replication is set as "A row from this table will go to only one subscription" ? The new rep uses the same laptop, therefore the exactly same computer name, only the username changes.

Because of this, now I'm having a bunch of conflicts when replicating because we're generating some ID based on existing data when the user enter new records in some tables; since the data is not sitting locally for them, the ID generated is not the proper one and we now have two identical ID (one on the server and one locally) which cause the conflicts to occurs.

Any helps would be appreciated. Thanks.

View 1 Replies View Related

Change A Merge Subscriber To Become A Merge Publisher

Aug 16, 2004

Hi,

I'm using merge replication to maintain a backup copy of my main (publisher)MSDE database. A push subscription periodically (1 per minute) updates the backup DB.
It's intended that if the main db goes down then the backup (subscription) db can be configured as a publisher. This must all be performed via scripting.
The initial configuration of the main publisher and subscription is controlled via scripting, which works fine.
The problems occur when I try to configure the subsciber to become a publisher. A script is executed on the subscriber but fails at the point when it's configuring the publisher detail. The error is something like "unable to configure a publication for a database setup as an anonymous subscription".
I'm guessing that there are subscritpion artifacts added to the database which need to be removed before it can be configured as a new publisher.

Please help,
Jez W

View 1 Replies View Related

SQL SERVER 2005 REPLICATION (MERGE AGENT FAILING : PUSH SUBSCRIPTION)

Mar 27, 2006

ERROR MESSAGE:

"Message: Incorrect syntax near 'NoteID'."

Here is a snipet from the output file:

2006-03-27 13:01:49.820 Skipping file 'NotesHistory_21.sch' because it has already been delivered for a previous article or by a previously interrupted snapshot.
2006-03-27 13:01:49.867 OLE DB Subscriber 'LUZERNV4-PDOSQL4': SET ANSI_NULLS ON

2006-03-27 13:01:49.898 OLE DB Distributor 'LARGOS00-SDI': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2006-03-27 13:01:49.945 OLE DB Subscriber 'LUZERNV4-PDOSQL4': SET QUOTED_IDENTIFIER ON

2006-03-27 13:01:50.008 [17%] OLE DB Subscriber 'LUZERNV4-PDOSQL4': CREATE TABLE [dbo].[MSmerge_conflict_EFILE_MERGE_NotesHistory](
[NoteID] [int] NOT NULL,
[CaseRefNum] [int] NOT NULL,
[KeyField] [varchar](500) NOT NULL,
[KeyValue] [varchar](500) NOT NULL,
[Note] [varchar](800) NULL,
[NoteField] [varchar](100) NULL,
[ScanDocID] [int] NULL,
[PDF_ID] [int] NULL,
[RescanCode] [int] NULL,
[RescanNote] [varchar](100) NULL,
[AuditID] [bigint] NOT NULL,
[rowguid] [uniqueidentifier] ROWGUIDCOL NOT NULL
)


ꜽśã¹? êœ?Å›B 27 13:01î–”Å›è›ªç —êœ?Å›é”?Ä€Percent Complete: 17
2006-03-27 13:01:50.086 OLE DB Subscriber 'LUZERNV4-PDOSQL4': SET ANSI_NULLS ON


2006-03-27 13:01:50.117 Preparing table 'NotesHistory' for merge replication
2006-03-27 13:01:50.164 OLE DB Subscriber 'LUZERNV4-PDOSQL4': SET QUOTED_IDENTIFIER ON


2006-03-27 13:01:50.195 OLE DB Distributor 'LARGOS00-SDI': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2006-03-27 13:01:50.258 OLE DB Subscriber 'LUZERNV4-PDOSQL4': if object_id('MSmerge_conflicts_info') is not NULL
alter table [MSmerge_conflict_EFILE_MERGE_NotesHistory] add origin_datasource_id uniqueidentifier NULL

2006-03-27 13:01:50.351 OLE DB Subscriber 'LUZERNV4-PDOSQL4': if object_id('MSmerge_conflicts_info') is not NULL
create nonclustered index [ncMSmerge_conflict_EFILE_MERGE_NotesHistory] on [MSmerge_conflict_EFILE_MERGE_NotesHistory] ([rowguid], origin_datasource_id)

2006-03-27 13:01:50.383 OLE DB Subscriber 'LUZERNV4-PDOSQL4': exec sp_MSsetconflicttable @article = N'NotesHistory', @conflict_table = N'MSmerge_conflict_EFILE_MERGE_NotesHistory'

2006-03-27 13:01:50.430 OLE DB Subscriber 'LUZERNV4-PDOSQL4': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2006-03-27 13:01:50.476 [17%] The merge process was unable to deliver the snapshot to the Subscriber. If using Web synchronization, the merge process may have been unable to create or write to the message file. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write.Percent Complete: 17
2006-03-27 13:01:50.50é”?Ä€
2006-03-27 13:01:50.539 Applied script 'NotesHistory_21.cft'
2006-03-27 13:01:50.586 OLE DB Subscriber 'LUZERNV4-PDOSQL4': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2006-03-27 13:01:50.617 OLE DB Distributor 'LARGOS00-SDI': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2006-03-27 13:01:50.711 Percent Complete: 17
2006-03-27 13:01:50.742 {call sp_MSsetconflicttable (N'NotesHistory', N'MSmerge_conflict_EFILE_MERGE_NotesHistory', N'LARGOS00-SDI', N'EFILE', N'EFILE_MERGE')}
2006-03-27 13:01:50.773 OLE DB Distributor 'LARGOS00-SDI': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2006-03-27 13:01:50.867 Percent Complete: 0
2006-03-27 13:01:50.898 Category:COMMAND
Source: Failed Command
Number: 0
Message: {call sp_MSsetconflicttable (N'NotesHistory', N'MSmerge_conflict_EFILE_MERGE_NotesHistory', N'LARGOS00-SDI', N'EFILE', N'EFILE_MERGE')}
2006-03-27 13:01:50.961 Percent Complete: 0
2006-03-27 13:01:50.992 Category:SQLSERVER
Source: LUZERNV4-PDOSQL4
Number: 102
Message: Incorrect syntax near 'NoteID'.
2006-03-27 13:01:51.039 Percent Complete: 0
2006-03-27 13:01:51.070 Category:NULL
Source: Merge Replication Provider
Number: -2147201001
Message: The merge process was unable to deliver the snapshot to the Subscriber. If using Web synchronization, the merge process may have been unable to create or write to the message file. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write.
2006-03-27 13:01:51.133 Disconnecting from OLE DB Subscriber 'LUZERNV4-PDOSQL4'
2006-03-27 13:01:51.180 Disconnecting from OLE DB Subscriber 'LUZERNV4-PDOSQL4'
2006-03-27 13:01:51.226 Disconnecting from OLE DB Subscriber 'LUZERNV4-PDOSQL4'
2006-03-27 13:01:51.258 Disconnecting from OLE DB Subscriber 'LUZERNV4-PDOSQL4'
2006-03-27 13:01:51.305 Disconnecting from OLE DB Publisher 'LARGOS00-SDI'
2006-03-27 13:01:51.336 Disconnecting from OLE DB Publisher 'LARGOS00-SDI'
2006-03-27 13:01:51.383 Disconnecting from OLE DB Publisher 'LARGOS00-SDI'
2006-03-27 13:01:51.414 Disconnecting from OLE DB Publisher 'LARGOS00-SDI'
2006-03-27 13:01:51.445 Disconnecting from OLE DB Distributor 'LARGOS00-SDI'
2006-03-27 13:01:51.492 Disconnecting from OLE DB Distributor 'LARGOS00-SDI'
2006-03-27 13:01:51.523 The merge process will restart after waiting 60 second(s)...

View 1 Replies View Related

Drop Push Subscription Without Publisher

Apr 11, 2002

There is a push subscription to an immediate-updating transactional publication with a queued failover. The publisher was also the distributor.

The publisher melted down and has been removed from service. The subscriber continues to queue up transactions for the now nonexistent publisher.

How do you remove the push subscription directly from the subscribing machine?

Thanks for your help,
Jim Schweitzer
Anobi Technology

View 1 Replies View Related

Subscription Agent Won't Connect To The Publisher

Aug 9, 2015

in the clustering lab I was setting up transact replication - created the publication ok, but when I setup the subscription, wasn't sure what account it needed to use :/  tried various formats of Administrator and Password;1 etc - but no dice. what account I need to be using?

btw: im trying to set this up on single server.

View 4 Replies View Related

Can't Drop SQL Mobile Subscription At Publisher

Oct 3, 2006

I have a program running on Pocket PCs that synchronizes with a desktop SQL database using SQL Mobile. My problem is that I can't delete old subscriptions from the publication; now the publication has 25 subscriptions and won't accept any more (limit of SQL Workgroup edition). I can delete non-SQL Mobile subcriptions just fine.

Running sp_replmonitorhelpsubscription provides this information:

subscriber: LVCONTACTSMERGE - 5FA305234F0C
subscriber_db: Program FilesPocketLVContactsLVContacts.sdf
publisher_db: LVContacts
publication: LVContactsMerge

So I set up this bit of code:

USE LVContacts
EXEC sp_dropmergesubscription
@publication = 'LVContactsMerge',
@subscriber = 'LVCONTACTSMERGE - 5FA305234F0C',
@subscriber_db = 'Program FilesPocketLVContactsLVContacts.sdf',
@subscription_type='all';
GO

No errors are reported, but the subscription doesn't get deleted.

I've tried shutting down SQL Server Agent (mentioned in another thread); makes no difference.

Any ideas?

--Evan

View 5 Replies View Related

Push And Pull Subscription From Publisher/Distributor?

May 30, 2001

Hi All,

Can push and pull subscriptions be configured on the publisher/distributer server?

We have server A running SQL Server 2000 configured as Publisher/Distributor and also a Push subscription (transactional replication) to Server B configured as Subscriber.

The idea was to have Server B as backup server if Server A goes down. Users will continue to update data in server B till server A is up.

Once server A is up, I want to synchronise the up-to-minuit date from Server B to Server A in the form of Transactional replication configured as "Pull Subscription" from Server A.

Is that possible?

Thanks
Sri

View 1 Replies View Related

Unable To Set The Publisher Login For The Updatable Subscription

Jun 15, 2007

I keep getting this following error when trying to set-up an updateable subscription on SQL 2005 (latest service packs). Server is set for mixed mode auth.
At the final stage of the new subscription wizard I get:
Unable to set the Publisher login for the updatable subscription. You may have to set this up directly on the Subscriber machine using sp_link_publication. (New Subscription Wizard)
The user is not associated with a trusted SQL Server connection
Login failed for user ''. The user is not associated with a trusted SQL Server connection
Error Number: 18456, Severity: 14, State: 1,Line Number: 1


Can anyone recommend a possible way of debugging this? Is it some issue with RPC security?

View 1 Replies View Related

The Publisher Failed To Allocate A New Set Of Identity Ranges For The Subscription

Apr 25, 2006

Hi All,

The following is the report from the SQL Server Mobile Subscription wizzard, Any Ideas?

New Subscription Wizard

- Beginning Synchronization (Success)

- Synchronizing Data (100%) (Error)



Messages

A call to SQL Server Reconciler failed. Try to resynchronize.
HRESULT 0x80004005 (29006)

The Publisher failed to allocate a new set of identity ranges for the subscription. This can occur when a Publisher or a republishing Subscriber has run out of identity ranges to allocate to its own Subscribers or when an identity column data type does not support an additional identity range allocation. If a republishing Subscriber has run out of identity ranges, synchronize the republishing Subscriber to obtain more identity ranges before restarting the synchronization. If a Publisher runs out of identit
HRESULT 0x80045647 (0)

Invalid parameter @subid specified for sys.sp_MSmerge_log_idrange_alloc_on_distributor.
HRESULT 0x0000523F (0)


The operation could not be completed.


- Finalizing Synchronization (Stopped)

- Saving Subscription Properties (Stopped)

Initially i thought it might be that some of the articles had primary keys that were of type nvarchar rather then Int thus resulting in no identity range being able to be assigned to those articles. 

Test 1: I tried removing all articles that had nvarchar primary keys and left only one table that had an identity Int primary key colum.  I then ran the snapshot agent.  I then run through the Subscription Wizzard again and the error was the same.

Test 2: Then reading the error message again i tried those tables that didnt use  identity columns and the wizzard completed successfully.  Any idea what would be wrong with my articles that have identity columns.  The article properties for the identity columns use the Identity Range Management defaults.

Any help would be appreciated.

 

 

 

View 18 Replies View Related

SQL 2012 :: Updatable Subscription - View Pending Log From Subscriber To Publisher

May 7, 2015

I have setup Transnational replication with updatable subscription.

There were around 7000 rows update at subscriber from one query which was executed at subscriber side.

But this update has not taken place at publisher yet and so to other subscribers.

Is there any way i can monitor pending log or where is the issue?

I find so many ways to see pending logs or statistics for - "Publisher to Subscriber" but not for "subscriber to publisher"

What is the way to see subscriber to publisher pending and issues?

View 0 Replies View Related

The Publisher Failed To Allocate A New Set Of Identity Ranges For The Subscription After Another Publication Deletion

Jan 17, 2007

Hi.

First of all, I apologize for my english

I have two publications. Some of the data are the same on the two publications. Both are configured as follow : The identity range management is set to "automatic" and the tracking-level is set to "Column-level tracking". Until there, every things works fine.

But, if i'm deleting one of the publication and if i'm deleting one of the rows that were replicated on the two publications i'm getting the following SQL Exception : "Invalid object name 'dbo.MSmerge_repl_view_1CAD32C4FF904A3CA27518B0C4BFF716_70308DE2261C4EC784C56131902E7D1C'"


If i'm watching the status of the leftover replication through the replication monitor, i get this error message :

"Error messages:
The Publisher failed to allocate a new set of identity ranges for the subscription. This can occur when a Publisher or a republishing Subscriber has run out of identity ranges to allocate to its own Subscribers or when an identity column data type does not support an additional identity range allocation. If a republishing Subscriber has run out of identity ranges, synchronize the republishing Subscriber to obtain more identity ranges before restarting the synchronization. If a Publisher runs out of identit (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199417)
Get help: http://help/MSSQL_REPL-2147199417
The publisher's identity range allocation entry could not be found in MSmerge_identity_range table. (Source: MSSQLServer, Error number: 20663)
Get help: http://help/20663"


I checked the given links but they're useless.


So I tried to reinitialize the subscription with the "use a new snapshot" option enabled without any success either. I did only obtain a new error message :

"The publisher's identity range allocation entry could not be found in MSmerge_identity_range table.

Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK TRANSACTION statement is missing. Previous count = 1, current count = 2.

Failed to pr"


I didnt have any idea to correct this issue, so I would appreciate any help.

Thanks.

David.

View 7 Replies View Related

Programmatically Determining If A Data Driven Subscription Is Running

Apr 17, 2007

Hi,

Quick question: how do I determine programmatically if a data driven subscription is currently running?

More info:
I€™m writing a web application which allows the user to kick off an existing data driven subscription (reporting services 2000), which runs from a table with parameters, paths, etc which the user has populated.
The subscription can take several minutes to run, during which time I need to prevent other users from attempting to run the subscription or alter data on the table driving the subscription.
All I€™ve found in the docs so far is
1. The ActiveState on the subscription.
This seems to have more to do with weather or not it can run than if it is running.
2. The status of the subscription.
This seems to only return €œdone: {0} of {1} with {2} errors€? Parsing this is likely to be too flaky to be acceptable.

I really need to move on this as soon as possible, any help is appreciated.

Thanks

View 3 Replies View Related

How To Speedup Data From Subscriber To Publisher On Merge Replication?

Mar 9, 2007

How to speedup data from subscriber to Publisher on Merge replication?

Is there any we can speed up data from Subscriber to Publisher (uploading).

Subscriber downloading data from publisher running more than 20 hours after drop and recreate subscriber.

Could you please post reply.

Regards
Ponnu

View 2 Replies View Related

SQL Server 2008 :: Merge Replication - Publisher And Subscriber On Same Computer?

Nov 6, 2015

For study effect, can I configure merge replication using just one SQL Server Instance?

View 3 Replies View Related

Disabling Merge Distribution Change My Table Definitions At Publisher

Mar 12, 2007

I have merge replication between sql 2005 SP1, and when I disable distribution from my publisher, my tables with identity columns change the property "Not for replication" to "NO", does somebody knows if this is a known problem ?

Other information : the compatibilty level for database is 2000.

View 1 Replies View Related

URGENT Merge Replication: Missing Rows At Publisher And Subscriber: No Conflicts

Jun 9, 2006

We have SQL Server 2000 with merge replication at a Publisher and subscriber.

We have some records getting deleted at Publisher and Subscriber and no conflicts are logged.

We have tried the compensate_for_errors setting and this has had no effect.

This is causing serious data corruption and has now become an URGENT issue. Out tech team are almost out of ideas.

Has anyone experienced this or have any ideas as to what to check next?

View 3 Replies View Related

Replication :: Check If Web Merge Sync Is Working Between Subscriber And Publisher Thru HTTPS?

May 14, 2015

How to check if web merge sync is working between a subscriber and publisher thru HTTPS ? SQL port 1433 at subscriber is blocked so no direct connection to subscriber.

View 2 Replies View Related

Merge Replication - FTP - PULL Subscription

Dec 18, 2002

Trying to set up Merge Replication using FTP with PULL subscriptions on sql 2000

Are there any issues that anyone is aware of that may affect this working.

View 2 Replies View Related

Replication - Merge Vs Updateable Subscription

Feb 14, 2003

Does anyone have advice as choosing between merge replication and updatable subscriptions? I've read the documentaion, they seem to offer the same functionality, and I don't see any clear guidelines as to why to pick one over the other...any suggestions would be appreciated!

Ed

View 1 Replies View Related

Merge Replication - Uninitialized Subscription

May 7, 2007

I have created a Merge Subscription between two databases. I have set the security setting in the UNC folder of the publisher to allow 'Full Control' for 'Everyone'.

I have done various searches, google, here, etc. But cant seem to find much information to help me out.

When I create the subscription it says it was a success, but when I launch the replication monitor and click the publication it says its subscribers are uninitialized.

Can anyone help?

Cheers

View 1 Replies View Related

Merge Process Could Not Initialize The Subscription

Jul 19, 2007

I am experiencing some replication problems. I have a test server with a test database which has been working just fine with some simple Merge Replication. That old server is now been targeted for decommissioning. I have moved the test database to another test server and have set everything conceivable up the same as it was on the prior server but I am experiencing errors that I have not been able to resolve. I am using the same Domain User account with the same privileges on both systems...



The first error I receive in my SQL Server error logs is:



Message
Error: 14151, Severity: 18, State: 1.



Rapidly followed by the following error message:



Message
Replication-Replication Merge Subsystem: agent SOURCE-DATABASE-MERGE-DESTINATION-16 failed. The merge process could not initialize the subscription. Ensure that the subscription registration exists at the publisher, and reregister the subscription if necessary.



From within the Replication Monitor I look into the subscription and I can see the following error message:



Command attempted:

{call sys.sp_MSmergesubscribedb ('true', 0) }



Error messages:

The merge process could not initialize the subscription. Ensure that the subscription registration exists at the publisher, and reregister the subscription if necessary. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201011)
Get help: http://help/MSSQL_REPL-2147201011



INSERT failed because the following SET options have incorrect settings: 'ANSI_PADDING'. Verify that SET options are correct for use with indexed views and/or indexes on computed columns and/or query notifications and/or xml data type methods. (Source: MSSQLServer, Error number: 1934)
Get help: http://help/1934



I have looked into the help links from above, researched codes and also browsed this forum and others to no avail so far. Any help or suggestions would be greatly appreciated! THANKS!



View 5 Replies View Related

The Merge Process Could Not Initialize The Subscription.

Jul 25, 2007

I met some problems in merge replication with sql server 2005 (sp2).

one user who is using the PDA (SQL Mobile 2005) try to sync with server, the error info is coming.

the error in replication monitor is shown as following:
Error messages:
The merge process could not initialize the subscription. Ensure that the subscription registration exists at the publisher, and reregister the subscription if necessary. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201011)
Get help: http://help/MSSQL_REPL-2147201011
The subscription could not be found. (Source: MSSQLServer, Error number: 20021)
Get help: http://help/20021
The subscription has expired. Mark the subscription for reinitialization and restart the Merge Agent to reinitialize the subscription. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200980)
Get help: http://help/MSSQL_REPL-2147200980

is there anybody who has any idea about it?

View 1 Replies View Related

SQLEXPRESS Merge Pull Subscription

Feb 2, 2007

Hi all I have a question,

I am trying to enable a replication process between a SQL 2005 server and sqlexpress instances and i run into the following problem.

On the publisher a subscription (sp_addmergesubscription) is added for each 'machine' that participates in the replication. Is there a way to get around this?

Because when we distribute the installation we dont know all the machine names. I have made the publication accesible for anynymous access. But when the replication script is installed on the client ,the Error message that the subscription does not exists appears.

The only difference between the instal script for the client is that we do not add a sp_addmergesubscription on the server. Is it possible to let SQL server make an subscription when the client connects for the first time?



To summarize my question: Is there a way to enable the replication with only running a script on the client and not on the server?

If i need to explain it more in detail , just let me know and ill try

View 3 Replies View Related

Transact SQL For Creating Merge Subscription

Sep 13, 2006

I am trying to create a merge publication in sql server 2005 and a merge subscription in sql server 2005 mobile through transact sql using sql server query analyzer.

I am succeeded in creating the publication but not subscription.

I am using sp_addmergepublication and sp_addmergesubscription.

sp_addmergepublication is working fine.

But the problem is in creating sp_addmergesubscription.

Can anyone please guide me how to create subscription to sql server 2005 mobile database using transact sql.

View 1 Replies View Related

Sync'ing A Merge Subscription Before Removal.

Feb 15, 2006

Hi,

is there a way to ensure a merge subscription is synchronised before it is removed from the publisher using SMO? - (it is a push subscription)

I thought I had it as there is a MergeSynchronizationAgent object on the SubscriptionDatabase object, but calling Synchronize() on this throws an exception saying it can't contact the publisher.

Any help would be really appreciated, thanks.

Graham

View 4 Replies View Related

Unable To Subscribe CE Database To Merge Subscription

May 25, 2007

Hi,

On the development environment i've got replication running with no trouble but when deploying in the production environment i get the error below

Has anyone seen this before and solved it?
Another question: How to enable verbose history when using the MS SQL Server Management Studio to create a subscription.

Any help is welcome,

Ralf


TITLE: Microsoft SQL Server Management Studio------------------------------A call to SQL Server Reconciler failed. Try to resynchronize.HRESULT 0x80004005 (29006)The schema script 'd:MSSQL
epldatauncTEST_KANSCE TEST20070522165445 blNaw_2.sch' could not be propagated to the subscriber.HRESULT 0x80070003 (0)The merge process was unable to deliver the snapshot to the Subscriber. If using Web synchronization, the merge process may have been unable to create or write to the message file. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write.HRESULT 0x80045017 (0)------------------------------BUTTONS:OK------------------------------

View 6 Replies View Related

Monitoring Merge Push Subscription From Subscriber

Jul 3, 2007

Hi all!

Is there an option to monitor current state of Merge Push Subscription from the Subscriber, without connecting to the Publisher Server? I have examined many SPs and system tables at Subscriber, but didn't find any reliable method...

View 4 Replies View Related

Merge Replication Subscription Doubles In Size

Jan 29, 2008

I made a DDL change to a published table. To do this, I had to remove the table from the article, modify two field sizes, save the table, and then add the table back to the publication. I did have to rerun the snapshot agent after this even though the new article is exactly the same (yes, I understand all rowguids are dropped and recreated).


So, at the subscription, I begin synchronization and it replicates every article, thus doubling the size of the subscription .sdf file. yes, it can be compacted and it cuts it back in half.

Question is how to prevent this behavior? Is it possible to create the rowguid before publishing the table/article and that way even if you go back and make a schema change that requires republishing you can avoid the nasty behavior of producing a new snapshot and and a doubling of subscription database size?

This particular merge publication is read-only. Every article is marked as 'download only.'

Ideally if schema change is needed to one table, I only want that table/article to require reinitialization.
Actually, if its a simple change like expanding a varchar by some chars I'd like to not have to republish the article at all.
keep dreaming?

View 1 Replies View Related

Initializing A Merge Subscription Without A Snapshot Bugs

Feb 21, 2007

Hello guys,

We have customers that are using web synchronization. Could you, please tell us when service pack for the bugs, discussed in thread http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=689428&SiteID=1 will be reliazed?

What replication participants should apply the service pack in a configuration where Subscriber (MS SQL 2005 Express)  gets synchronized with Publisher/Diustributor (MS SQL 2005 Standard)?

 Thanks.

 Alexander.

View 3 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved