Reinstating Replication on a subscriber automatically

Hi all

I am setting up a system using SQL Server 2005 replicating to both SQL Express and MSDE clients. My question is this - if a client PC has been rebuilt - i.e. new hard disk etc, how can I automatically make that machine realise that it is already a subscriber of a SQL Server database and for it to automatically get a snapshot?

I hope this makes sense, thanks for your help.

D

If the subscriber has the same name as the old one, the SQL Server version of the subscriber is the same as the old one, and the history or distribution retention period has not passed you merely need to restore the subscriber database and the distributor will backfill the missing commands.

If this is not the case you should try to do a no-sync and then a validation to determine what is missing, or how out of sync you are. At that point you might want to evaluate re-initializing.sql

reinstall of the subscriber server

We are using SQL 2K std with s4 and are using Push subscription method.
We need to upgrade some hardware in the subscriber server which will require
us to do a total reinstall of the OS and SQL server software. Since we are
using push subscription, most of the replication settings are on the
publishing server. When we do the server upgrade, I will stop the
distribution agent so it won't do any transfer until the server is up. I
like to know if I back up the subscriber database and restore it on the same
upgraded server. Will the replication work like as usual? Are there any
steps I need to consider?
wingman
As long as the server name, database name, and IP address are identical this
will work.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Wingman" <Wingman@.discussions.microsoft.com> wrote in message
news:9E5E069D-1FBD-4A37-8DA3-C09BCCE53F8E@.microsoft.com...
> We are using SQL 2K std with s4 and are using Push subscription method.
> We need to upgrade some hardware in the subscriber server which will
> require
> us to do a total reinstall of the OS and SQL server software. Since we
> are
> using push subscription, most of the replication settings are on the
> publishing server. When we do the server upgrade, I will stop the
> distribution agent so it won't do any transfer until the server is up. I
> like to know if I back up the subscriber database and restore it on the
> same
> upgraded server. Will the replication work like as usual? Are there any
> steps I need to consider?
> wingman
|||As long as the distribution agent was stopped and you restore the database
ensuring that you keep replication settings, then you should be able to
simply resume the distribution agent and it will catch up. In the event
that it fails for some reason, you will have to reinitialize it.
"Wingman" <Wingman@.discussions.microsoft.com> wrote in message
news:9E5E069D-1FBD-4A37-8DA3-C09BCCE53F8E@.microsoft.com...
> We are using SQL 2K std with s4 and are using Push subscription method.
> We need to upgrade some hardware in the subscriber server which will
> require
> us to do a total reinstall of the OS and SQL server software. Since we
> are
> using push subscription, most of the replication settings are on the
> publishing server. When we do the server upgrade, I will stop the
> distribution agent so it won't do any transfer until the server is up. I
> like to know if I back up the subscriber database and restore it on the
> same
> upgraded server. Will the replication work like as usual? Are there any
> steps I need to consider?
> wingman
|||Z,
Thanks for the suggestion. I need some clarification of your statement
"ensuring that you keep replication settiings". Since we are using the
'Push' subscription, as far as I know, all replication settings are in the
publishing computer. Are there other settings in the subscriber server that
I should know about? Also, if I restore the subscriber database from the
backup, should the settings (if any) be restored as well?
wingman
"Z" wrote:

> As long as the distribution agent was stopped and you restore the database
> ensuring that you keep replication settings, then you should be able to
> simply resume the distribution agent and it will catch up. In the event
> that it fails for some reason, you will have to reinitialize it.
> "Wingman" <Wingman@.discussions.microsoft.com> wrote in message
> news:9E5E069D-1FBD-4A37-8DA3-C09BCCE53F8E@.microsoft.com...
>
>
|||Thanks.
One quick follow-up question. I understand the idea of the purpose of the
log reader agent and I don't need to shut it down for what I am planning to
do. I noticed that if I want to delete a subscriber database, I need to shut
the log reader agent down because the log reader agent is running a command
"rplcmds' and is connected to the subscriber database. First of all, is my
finding correct? Secondly, can you explain what this command does?
wingman
"Hilary Cotter" wrote:

> As long as the server name, database name, and IP address are identical this
> will work.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Wingman" <Wingman@.discussions.microsoft.com> wrote in message
> news:9E5E069D-1FBD-4A37-8DA3-C09BCCE53F8E@.microsoft.com...
>
>
|||You don't need to shut down the log reader to delete the subscription
database, rather you need to shut down the distribution agent. The log
reader is connected to the publication database and the distribution
database. I am unfamiliar with the rplcmds command.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Wingman" <Wingman@.discussions.microsoft.com> wrote in message
news:1F21FF5C-083A-43CB-9EA6-59EC9A103AA2@.microsoft.com...[vbcol=seagreen]
> Thanks.
> One quick follow-up question. I understand the idea of the purpose of the
> log reader agent and I don't need to shut it down for what I am planning
> to
> do. I noticed that if I want to delete a subscriber database, I need to
> shut
> the log reader agent down because the log reader agent is running a
> command
> "rplcmds' and is connected to the subscriber database. First of all, is
> my
> finding correct? Secondly, can you explain what this command does?
> wingman
> "Hilary Cotter" wrote:

Reinitializing SQL Server 2005 CE subscriber results in a hang

I'm having an issue when I'm using merge replication between SQL Server 2000
sp4 and .NET client using SQL Server 2005 Compact Edition (v3.1). The client
is based on the sample code from MSDN library listed on the
SQLCeReplication.BeginReplication page that fires events to show each stage
of replication that happens.
The inital snapshot is pulled down and the database is created successfully.
When I change data in the SQL Server 2000 database, subsequent replications
work ok and the client successfully pulls down the changes.
However, when the subscription is reinitialized (either at the server, or
client), the app hangs. I believe it may be to do with the size of the
database as it works fine with smaller subsets of the data.
In my case, the app successfully completes the inital conversation with SQL
Server 2000 (the OnSynchronization event reports that SyncProgres is 100%)
and the PublisherChanges property says that there are over 2,000,000 changes
to be made. With an empty database, the app goes on to download each
published table in turn. However, when the subscription is marked for
reinitialization, the app just seems to hang - CPU is up to 90-95% and the
local database grows by 50% but then it does not seem to go any further.
Is this a known limitation with SQL Server 2005 CE? Are there any
workarounds, eg so can I identify in advance whether my subscription has been
marked for reinialization, so that I can drop my existing subscription
(deleting the database) and recreate it again using the latest snapshot?
Thanks
Stuart
Hi,
From your description, I understand that after your subscription was
initialized your application hanged. You would like to know if this was a
known limitation with SQL Server 2005 CE or if you can know in advance that
your subscription is in re-initialization.
If I have misunderstood, please let me know.
From my research, there is not a known limitation regarding this issue. We
can query its status via the stored procedure sp_helpmergesubscription,
however it cannot be judged whether or not a subscription is in
reinitializing. You may check whether or not this issue also occurs on
other subscribers with other SQL Server 2005 Editions.
Anyway I will try to consult the product team on this issue to get further
suggestions. Also I appreciate your understanding that this issue seems was
performance related. To track the root cause and workaround this issue,
dump analysis may be required, however this work can only be done by
Microsoft Customer Support Services (CSS). If I could not get an effective
answer from product team, effectively and immediately I recommend that you
contact CSS via telephone so that a dedicated Support Professional can
assist you in a more efficient manner. Please be advised that contacting
phone support will be a charged call.
To obtain the phone numbers for specific technology request please take a
look at the web site listed below.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
If you are outside the US please see http://support.microsoft.com for
regional support phone numbers.
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||Hi Stuart,
This is a quick note to let you know that I have not got the response from
the product team. I will try to follow up them now. However since the
process may need a long time, I recommend that you leave me
(changliw_at_microsoft_dot_com) an email response so that I can timely
update you when I got the response. If this issue is urgent to your
business, I recommend that you contact CSS via telephone for the best
support.
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====

Re-initializing an anonymous subscription from the server - error

Hi,

I'm trying to force an anonymous subscription to re-intialize on it's next sync attempt. I can do this from the subscriber no problems, and from the publisher using 'Re-initalize All Subscriptions', but I can't seem to re-intialize only a single subscription from the publisher.

To do this I'm trying to execute sp_reinitmergesubscription using the subscriber details found in the sysmergesubscriptions table. This executes ok and when the subscriber starts to sync it does try to re-initialize starting with generating a new snapshot, but after processing for a while it throws the following error messages:

Error messages:
The merge process could not allocate memory for an operation; your system may be running low on virtual memory. Restart the Merge Agent. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147198720)
Get help: http://help/MSSQL_REPL-2147198720
An error occurred while reading the .bcp data file for the 'CDP_TableDates' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199428)
Get help: http://help/MSSQL_REPL-2147199428
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. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)

There doesn't appear to be any shortage of memory on the server. There is no problem regenerating the snapshot from the publisher, and there's no problem with syncing through the web using delta syncs or re-initializing from the subscriber, so I can't see any obvious cause from those error messages.

I'm using SQL Server 2005 SP2 on the publisher, and SQL ServerCE 3.1 on the subscriber.

Any ideas or alternatives?

Cheers

With an anonymous subscription the publisher is unable to connect to the subsciber so I would guess that actions like forcing a re-init cannot be done from the publisher.

Your root message is saying that the process could not deliver the snapshot to the subscriber. It is trying to connect to the subscriber but cannot as it is anonymous.

Martin

|||Thanks for the response.

I thought that SQL Server 2005 was supposed to remove a lot of the limitations of anonymous subscribers. In this case, as the subscriber can receive the snapshot when the re-init is initiated on the subscriber, I don't understand why it can't receive it when intiated on the publisher. The client obviously recognises that a re-init is required, surely from then the process should be the same?

Any other ideas?
|||

Has anybody successfully forced an anonymous subscriber to re-initiliaze from the publisher? I would have thought this was a fairly common requirement.

|||

Are you using push or pull subscription? If you are using push, can you try to use pull instead and see if that would work for you?

Regards,
Gary

|||

I'm using a pull subscription. As far as I know, SQL Server CE only supports anonymous pull subscriptions.

I've since been advised from a support engineer (via MSC) that SQL Server 2005 can't re-initialise anonymous subscribers from the publisher, only from the subscriber. I can't see why this limitation would be in place, but it is consistent with the errors I'm getting.

The workaround will be to build into the application a pre-sync check which connects to the publisher and checks a re-init flag, then re-inits from the subscriber based on that flag.

If anyone else can suggest an alterantive (or challenge the assertion that anonymous subscriptions can't be re-init from the publisher) I'm keen to hear it.

Thanks

|||

Steve, you should be able to reinitialize your mobile subscriber from the publisher.

exec pubdb..sp_reinitmergesubscription '<PublicationName>', @.subscriber='mysubscriber - aaaaaaaaaaaa', @.subscriber_db='D:\myPathToMobileDatabase.sdf'

I got the subscriber and subscriber_db from the publisher server's sysmergesubscriptions.

I executed the above at the publisher and the subscriber upon next sync was able to reinitialize.

Let me know if you are not seeing this and I would be interested to find out what issue you are encountering.

Note that I tried this on a desktop installation of mobile.

|||

I am using the same process. I grabbed the details out of the sysmergesubscriptions table and then executed the sp_reinitmergesubscription procedure. When the subscriber starts to sync, it recognises that a re-init is necessary and begins that process. If an up-to-date snapshot is not available it generates one otherwise it immediatly starts to transfer the data. At this point it stops with the following error messages:

The merge process could not allocate memory for an operation; your system may be running low on virtual memory. Restart the Merge Agent. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147198720)
Get help: http://help/MSSQL_REPL-2147198720
An error occurred while reading the .bcp data file for the 'CDP_TableDates' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199428)
Get help: http://help/MSSQL_REPL-2147199428
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. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)

The set up I'm using is SQL Server 2005 on Windows Server 2003 and SQL CE 3.1 on Windows XP (ie not mobile). The desktop is our target setup (although most clients are on Windows 2000).

I've also tried doing this in different combinations ie with both the SQL CE and the SQL Server 2005 databases on the Windows 2003 server, and with both running on the win xp desktop, but all get the same errors. In none of these situations is re-initialising from the subscriber an issue.

Any ideas on how to progress this?

|||

Further testing has uncovered an interesting way to get this work. For some reason if I validate all subscribers after using sp_reinitmergesubscription to re-intialise a single subscriber, the subscriber syncs and reinitialises fine. This is obviously not ideal, as forcing all subscribers to validate creates unnecassary overhead, but the result is that I don't get errors from the subscriber re-initialisation.

So my current steps are:

exec sp_reinitmergesubscription

kick off the dynamic snapshot job for the subscriber

exec sp_validatemergepublication

Re-initializing an anonymous subscription from the server - error

Hi,

I'm trying to force an anonymous subscription to re-intialize on it's next sync attempt. I can do this from the subscriber no problems, and from the publisher using 'Re-initalize All Subscriptions', but I can't seem to re-intialize only a single subscription from the publisher.

To do this I'm trying to execute sp_reinitmergesubscription using the subscriber details found in the sysmergesubscriptions table. This executes ok and when the subscriber starts to sync it does try to re-initialize starting with generating a new snapshot, but after processing for a while it throws the following error messages:

Error messages:
The merge process could not allocate memory for an operation; your system may be running low on virtual memory. Restart the Merge Agent. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147198720)
Get help: http://help/MSSQL_REPL-2147198720
An error occurred while reading the .bcp data file for the 'CDP_TableDates' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199428)
Get help: http://help/MSSQL_REPL-2147199428
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. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)

There doesn't appear to be any shortage of memory on the server. There is no problem regenerating the snapshot from the publisher, and there's no problem with syncing through the web using delta syncs or re-initializing from the subscriber, so I can't see any obvious cause from those error messages.

I'm using SQL Server 2005 SP2 on the publisher, and SQL ServerCE 3.1 on the subscriber.

Any ideas or alternatives?

Cheers

With an anonymous subscription the publisher is unable to connect to the subsciber so I would guess that actions like forcing a re-init cannot be done from the publisher.

Your root message is saying that the process could not deliver the snapshot to the subscriber. It is trying to connect to the subscriber but cannot as it is anonymous.

Martin

|||Thanks for the response.

I thought that SQL Server 2005 was supposed to remove a lot of the limitations of anonymous subscribers. In this case, as the subscriber can receive the snapshot when the re-init is initiated on the subscriber, I don't understand why it can't receive it when intiated on the publisher. The client obviously recognises that a re-init is required, surely from then the process should be the same?

Any other ideas?
|||

Has anybody successfully forced an anonymous subscriber to re-initiliaze from the publisher? I would have thought this was a fairly common requirement.

|||

Are you using push or pull subscription? If you are using push, can you try to use pull instead and see if that would work for you?

Regards,
Gary

|||

I'm using a pull subscription. As far as I know, SQL Server CE only supports anonymous pull subscriptions.

I've since been advised from a support engineer (via MSC) that SQL Server 2005 can't re-initialise anonymous subscribers from the publisher, only from the subscriber. I can't see why this limitation would be in place, but it is consistent with the errors I'm getting.

The workaround will be to build into the application a pre-sync check which connects to the publisher and checks a re-init flag, then re-inits from the subscriber based on that flag.

If anyone else can suggest an alterantive (or challenge the assertion that anonymous subscriptions can't be re-init from the publisher) I'm keen to hear it.

Thanks

|||

Steve, you should be able to reinitialize your mobile subscriber from the publisher.

exec pubdb..sp_reinitmergesubscription '<PublicationName>', @.subscriber='mysubscriber - aaaaaaaaaaaa', @.subscriber_db='D:\myPathToMobileDatabase.sdf'

I got the subscriber and subscriber_db from the publisher server's sysmergesubscriptions.

I executed the above at the publisher and the subscriber upon next sync was able to reinitialize.

Let me know if you are not seeing this and I would be interested to find out what issue you are encountering.

Note that I tried this on a desktop installation of mobile.

|||

I am using the same process. I grabbed the details out of the sysmergesubscriptions table and then executed the sp_reinitmergesubscription procedure. When the subscriber starts to sync, it recognises that a re-init is necessary and begins that process. If an up-to-date snapshot is not available it generates one otherwise it immediatly starts to transfer the data. At this point it stops with the following error messages:

The merge process could not allocate memory for an operation; your system may be running low on virtual memory. Restart the Merge Agent. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147198720)
Get help: http://help/MSSQL_REPL-2147198720
An error occurred while reading the .bcp data file for the 'CDP_TableDates' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199428)
Get help: http://help/MSSQL_REPL-2147199428
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. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)

The set up I'm using is SQL Server 2005 on Windows Server 2003 and SQL CE 3.1 on Windows XP (ie not mobile). The desktop is our target setup (although most clients are on Windows 2000).

I've also tried doing this in different combinations ie with both the SQL CE and the SQL Server 2005 databases on the Windows 2003 server, and with both running on the win xp desktop, but all get the same errors. In none of these situations is re-initialising from the subscriber an issue.

Any ideas on how to progress this?

|||

Further testing has uncovered an interesting way to get this work. For some reason if I validate all subscribers after using sp_reinitmergesubscription to re-intialise a single subscriber, the subscriber syncs and reinitialises fine. This is obviously not ideal, as forcing all subscribers to validate creates unnecassary overhead, but the result is that I don't get errors from the subscriber re-initialisation.

So my current steps are:

exec sp_reinitmergesubscription

kick off the dynamic snapshot job for the subscriber

exec sp_validatemergepublication

Re-initializing an anonymous subscription from the server - error

Hi,

I'm trying to force an anonymous subscription to re-intialize on it's next sync attempt. I can do this from the subscriber no problems, and from the publisher using 'Re-initalize All Subscriptions', but I can't seem to re-intialize only a single subscription from the publisher.

To do this I'm trying to execute sp_reinitmergesubscription using the subscriber details found in the sysmergesubscriptions table. This executes ok and when the subscriber starts to sync it does try to re-initialize starting with generating a new snapshot, but after processing for a while it throws the following error messages:

Error messages:
The merge process could not allocate memory for an operation; your system may be running low on virtual memory. Restart the Merge Agent. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147198720)
Get help: http://help/MSSQL_REPL-2147198720
An error occurred while reading the .bcp data file for the 'CDP_TableDates' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199428)
Get help: http://help/MSSQL_REPL-2147199428
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. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)

There doesn't appear to be any shortage of memory on the server. There is no problem regenerating the snapshot from the publisher, and there's no problem with syncing through the web using delta syncs or re-initializing from the subscriber, so I can't see any obvious cause from those error messages.

I'm using SQL Server 2005 SP2 on the publisher, and SQL ServerCE 3.1 on the subscriber.

Any ideas or alternatives?

Cheers

With an anonymous subscription the publisher is unable to connect to the subsciber so I would guess that actions like forcing a re-init cannot be done from the publisher.

Your root message is saying that the process could not deliver the snapshot to the subscriber. It is trying to connect to the subscriber but cannot as it is anonymous.

Martin

|||Thanks for the response.

I thought that SQL Server 2005 was supposed to remove a lot of the limitations of anonymous subscribers. In this case, as the subscriber can receive the snapshot when the re-init is initiated on the subscriber, I don't understand why it can't receive it when intiated on the publisher. The client obviously recognises that a re-init is required, surely from then the process should be the same?

Any other ideas?
|||

Has anybody successfully forced an anonymous subscriber to re-initiliaze from the publisher? I would have thought this was a fairly common requirement.

|||

Are you using push or pull subscription? If you are using push, can you try to use pull instead and see if that would work for you?

Regards,
Gary

|||

I'm using a pull subscription. As far as I know, SQL Server CE only supports anonymous pull subscriptions.

I've since been advised from a support engineer (via MSC) that SQL Server 2005 can't re-initialise anonymous subscribers from the publisher, only from the subscriber. I can't see why this limitation would be in place, but it is consistent with the errors I'm getting.

The workaround will be to build into the application a pre-sync check which connects to the publisher and checks a re-init flag, then re-inits from the subscriber based on that flag.

If anyone else can suggest an alterantive (or challenge the assertion that anonymous subscriptions can't be re-init from the publisher) I'm keen to hear it.

Thanks

|||

Steve, you should be able to reinitialize your mobile subscriber from the publisher.

exec pubdb..sp_reinitmergesubscription '<PublicationName>', @.subscriber='mysubscriber - aaaaaaaaaaaa', @.subscriber_db='D:\myPathToMobileDatabase.sdf'

I got the subscriber and subscriber_db from the publisher server's sysmergesubscriptions.

I executed the above at the publisher and the subscriber upon next sync was able to reinitialize.

Let me know if you are not seeing this and I would be interested to find out what issue you are encountering.

Note that I tried this on a desktop installation of mobile.

|||

I am using the same process. I grabbed the details out of the sysmergesubscriptions table and then executed the sp_reinitmergesubscription procedure. When the subscriber starts to sync, it recognises that a re-init is necessary and begins that process. If an up-to-date snapshot is not available it generates one otherwise it immediatly starts to transfer the data. At this point it stops with the following error messages:

The merge process could not allocate memory for an operation; your system may be running low on virtual memory. Restart the Merge Agent. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147198720)
Get help: http://help/MSSQL_REPL-2147198720
An error occurred while reading the .bcp data file for the 'CDP_TableDates' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199428)
Get help: http://help/MSSQL_REPL-2147199428
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. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)

The set up I'm using is SQL Server 2005 on Windows Server 2003 and SQL CE 3.1 on Windows XP (ie not mobile). The desktop is our target setup (although most clients are on Windows 2000).

I've also tried doing this in different combinations ie with both the SQL CE and the SQL Server 2005 databases on the Windows 2003 server, and with both running on the win xp desktop, but all get the same errors. In none of these situations is re-initialising from the subscriber an issue.

Any ideas on how to progress this?

|||

Further testing has uncovered an interesting way to get this work. For some reason if I validate all subscribers after using sp_reinitmergesubscription to re-intialise a single subscriber, the subscriber syncs and reinitialises fine. This is obviously not ideal, as forcing all subscribers to validate creates unnecassary overhead, but the result is that I don't get errors from the subscriber re-initialisation.

So my current steps are:

exec sp_reinitmergesubscription

kick off the dynamic snapshot job for the subscriber

exec sp_validatemergepublication

Re-initializing an anonymous subscription from the server - error

Hi,

I'm trying to force an anonymous subscription to re-intialize on it's next sync attempt. I can do this from the subscriber no problems, and from the publisher using 'Re-initalize All Subscriptions', but I can't seem to re-intialize only a single subscription from the publisher.

To do this I'm trying to execute sp_reinitmergesubscription using the subscriber details found in the sysmergesubscriptions table. This executes ok and when the subscriber starts to sync it does try to re-initialize starting with generating a new snapshot, but after processing for a while it throws the following error messages:

Error messages:
The merge process could not allocate memory for an operation; your system may be running low on virtual memory. Restart the Merge Agent. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147198720)
Get help: http://help/MSSQL_REPL-2147198720
An error occurred while reading the .bcp data file for the 'CDP_TableDates' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199428)
Get help: http://help/MSSQL_REPL-2147199428
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. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)

There doesn't appear to be any shortage of memory on the server. There is no problem regenerating the snapshot from the publisher, and there's no problem with syncing through the web using delta syncs or re-initializing from the subscriber, so I can't see any obvious cause from those error messages.

I'm using SQL Server 2005 SP2 on the publisher, and SQL ServerCE 3.1 on the subscriber.

Any ideas or alternatives?

Cheers

With an anonymous subscription the publisher is unable to connect to the subsciber so I would guess that actions like forcing a re-init cannot be done from the publisher.

Your root message is saying that the process could not deliver the snapshot to the subscriber. It is trying to connect to the subscriber but cannot as it is anonymous.

Martin

|||Thanks for the response.

I thought that SQL Server 2005 was supposed to remove a lot of the limitations of anonymous subscribers. In this case, as the subscriber can receive the snapshot when the re-init is initiated on the subscriber, I don't understand why it can't receive it when intiated on the publisher. The client obviously recognises that a re-init is required, surely from then the process should be the same?

Any other ideas?
|||

Has anybody successfully forced an anonymous subscriber to re-initiliaze from the publisher? I would have thought this was a fairly common requirement.

|||

Are you using push or pull subscription? If you are using push, can you try to use pull instead and see if that would work for you?

Regards,
Gary

|||

I'm using a pull subscription. As far as I know, SQL Server CE only supports anonymous pull subscriptions.

I've since been advised from a support engineer (via MSC) that SQL Server 2005 can't re-initialise anonymous subscribers from the publisher, only from the subscriber. I can't see why this limitation would be in place, but it is consistent with the errors I'm getting.

The workaround will be to build into the application a pre-sync check which connects to the publisher and checks a re-init flag, then re-inits from the subscriber based on that flag.

If anyone else can suggest an alterantive (or challenge the assertion that anonymous subscriptions can't be re-init from the publisher) I'm keen to hear it.

Thanks

|||

Steve, you should be able to reinitialize your mobile subscriber from the publisher.

exec pubdb..sp_reinitmergesubscription '<PublicationName>', @.subscriber='mysubscriber - aaaaaaaaaaaa', @.subscriber_db='D:\myPathToMobileDatabase.sdf'

I got the subscriber and subscriber_db from the publisher server's sysmergesubscriptions.

I executed the above at the publisher and the subscriber upon next sync was able to reinitialize.

Let me know if you are not seeing this and I would be interested to find out what issue you are encountering.

Note that I tried this on a desktop installation of mobile.

|||

I am using the same process. I grabbed the details out of the sysmergesubscriptions table and then executed the sp_reinitmergesubscription procedure. When the subscriber starts to sync, it recognises that a re-init is necessary and begins that process. If an up-to-date snapshot is not available it generates one otherwise it immediatly starts to transfer the data. At this point it stops with the following error messages:

The merge process could not allocate memory for an operation; your system may be running low on virtual memory. Restart the Merge Agent. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147198720)
Get help: http://help/MSSQL_REPL-2147198720
An error occurred while reading the .bcp data file for the 'CDP_TableDates' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199428)
Get help: http://help/MSSQL_REPL-2147199428
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. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)

The set up I'm using is SQL Server 2005 on Windows Server 2003 and SQL CE 3.1 on Windows XP (ie not mobile). The desktop is our target setup (although most clients are on Windows 2000).

I've also tried doing this in different combinations ie with both the SQL CE and the SQL Server 2005 databases on the Windows 2003 server, and with both running on the win xp desktop, but all get the same errors. In none of these situations is re-initialising from the subscriber an issue.

Any ideas on how to progress this?

|||

Further testing has uncovered an interesting way to get this work. For some reason if I validate all subscribers after using sp_reinitmergesubscription to re-intialise a single subscriber, the subscriber syncs and reinitialises fine. This is obviously not ideal, as forcing all subscribers to validate creates unnecassary overhead, but the result is that I don't get errors from the subscriber re-initialisation.

So my current steps are:

exec sp_reinitmergesubscription

kick off the dynamic snapshot job for the subscriber

exec sp_validatemergepublication

Re-initializing an anonymous subscription from the server - error

Hi,

I'm trying to force an anonymous subscription to re-intialize on it's next sync attempt. I can do this from the subscriber no problems, and from the publisher using 'Re-initalize All Subscriptions', but I can't seem to re-intialize only a single subscription from the publisher.

To do this I'm trying to execute sp_reinitmergesubscription using the subscriber details found in the sysmergesubscriptions table. This executes ok and when the subscriber starts to sync it does try to re-initialize starting with generating a new snapshot, but after processing for a while it throws the following error messages:

Error messages:
The merge process could not allocate memory for an operation; your system may be running low on virtual memory. Restart the Merge Agent. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147198720)
Get help: http://help/MSSQL_REPL-2147198720
An error occurred while reading the .bcp data file for the 'CDP_TableDates' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199428)
Get help: http://help/MSSQL_REPL-2147199428
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. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)

There doesn't appear to be any shortage of memory on the server. There is no problem regenerating the snapshot from the publisher, and there's no problem with syncing through the web using delta syncs or re-initializing from the subscriber, so I can't see any obvious cause from those error messages.

I'm using SQL Server 2005 SP2 on the publisher, and SQL ServerCE 3.1 on the subscriber.

Any ideas or alternatives?

Cheers

With an anonymous subscription the publisher is unable to connect to the subsciber so I would guess that actions like forcing a re-init cannot be done from the publisher.

Your root message is saying that the process could not deliver the snapshot to the subscriber. It is trying to connect to the subscriber but cannot as it is anonymous.

Martin

|||Thanks for the response.

I thought that SQL Server 2005 was supposed to remove a lot of the limitations of anonymous subscribers. In this case, as the subscriber can receive the snapshot when the re-init is initiated on the subscriber, I don't understand why it can't receive it when intiated on the publisher. The client obviously recognises that a re-init is required, surely from then the process should be the same?

Any other ideas?
|||

Has anybody successfully forced an anonymous subscriber to re-initiliaze from the publisher? I would have thought this was a fairly common requirement.

|||

Are you using push or pull subscription? If you are using push, can you try to use pull instead and see if that would work for you?

Regards,
Gary

|||

I'm using a pull subscription. As far as I know, SQL Server CE only supports anonymous pull subscriptions.

I've since been advised from a support engineer (via MSC) that SQL Server 2005 can't re-initialise anonymous subscribers from the publisher, only from the subscriber. I can't see why this limitation would be in place, but it is consistent with the errors I'm getting.

The workaround will be to build into the application a pre-sync check which connects to the publisher and checks a re-init flag, then re-inits from the subscriber based on that flag.

If anyone else can suggest an alterantive (or challenge the assertion that anonymous subscriptions can't be re-init from the publisher) I'm keen to hear it.

Thanks

|||

Steve, you should be able to reinitialize your mobile subscriber from the publisher.

exec pubdb..sp_reinitmergesubscription '<PublicationName>', @.subscriber='mysubscriber - aaaaaaaaaaaa', @.subscriber_db='D:\myPathToMobileDatabase.sdf'

I got the subscriber and subscriber_db from the publisher server's sysmergesubscriptions.

I executed the above at the publisher and the subscriber upon next sync was able to reinitialize.

Let me know if you are not seeing this and I would be interested to find out what issue you are encountering.

Note that I tried this on a desktop installation of mobile.

|||

I am using the same process. I grabbed the details out of the sysmergesubscriptions table and then executed the sp_reinitmergesubscription procedure. When the subscriber starts to sync, it recognises that a re-init is necessary and begins that process. If an up-to-date snapshot is not available it generates one otherwise it immediatly starts to transfer the data. At this point it stops with the following error messages:

The merge process could not allocate memory for an operation; your system may be running low on virtual memory. Restart the Merge Agent. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147198720)
Get help: http://help/MSSQL_REPL-2147198720
An error occurred while reading the .bcp data file for the 'CDP_TableDates' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199428)
Get help: http://help/MSSQL_REPL-2147199428
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. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)

The set up I'm using is SQL Server 2005 on Windows Server 2003 and SQL CE 3.1 on Windows XP (ie not mobile). The desktop is our target setup (although most clients are on Windows 2000).

I've also tried doing this in different combinations ie with both the SQL CE and the SQL Server 2005 databases on the Windows 2003 server, and with both running on the win xp desktop, but all get the same errors. In none of these situations is re-initialising from the subscriber an issue.

Any ideas on how to progress this?

|||

Further testing has uncovered an interesting way to get this work. For some reason if I validate all subscribers after using sp_reinitmergesubscription to re-intialise a single subscriber, the subscriber syncs and reinitialises fine. This is obviously not ideal, as forcing all subscribers to validate creates unnecassary overhead, but the result is that I don't get errors from the subscriber re-initialisation.

So my current steps are:

exec sp_reinitmergesubscription

kick off the dynamic snapshot job for the subscriber

exec sp_validatemergepublication

Re-initializing an anonymous subscription from the server - error

Hi,

I'm trying to force an anonymous subscription to re-intialize on it's next sync attempt. I can do this from the subscriber no problems, and from the publisher using 'Re-initalize All Subscriptions', but I can't seem to re-intialize only a single subscription from the publisher.

To do this I'm trying to execute sp_reinitmergesubscription using the subscriber details found in the sysmergesubscriptions table. This executes ok and when the subscriber starts to sync it does try to re-initialize starting with generating a new snapshot, but after processing for a while it throws the following error messages:

Error messages:
The merge process could not allocate memory for an operation; your system may be running low on virtual memory. Restart the Merge Agent. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147198720)
Get help: http://help/MSSQL_REPL-2147198720
An error occurred while reading the .bcp data file for the 'CDP_TableDates' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199428)
Get help: http://help/MSSQL_REPL-2147199428
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. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)

There doesn't appear to be any shortage of memory on the server. There is no problem regenerating the snapshot from the publisher, and there's no problem with syncing through the web using delta syncs or re-initializing from the subscriber, so I can't see any obvious cause from those error messages.

I'm using SQL Server 2005 SP2 on the publisher, and SQL ServerCE 3.1 on the subscriber.

Any ideas or alternatives?

Cheers

With an anonymous subscription the publisher is unable to connect to the subsciber so I would guess that actions like forcing a re-init cannot be done from the publisher.

Your root message is saying that the process could not deliver the snapshot to the subscriber. It is trying to connect to the subscriber but cannot as it is anonymous.

Martin

|||Thanks for the response.

I thought that SQL Server 2005 was supposed to remove a lot of the limitations of anonymous subscribers. In this case, as the subscriber can receive the snapshot when the re-init is initiated on the subscriber, I don't understand why it can't receive it when intiated on the publisher. The client obviously recognises that a re-init is required, surely from then the process should be the same?

Any other ideas?
|||

Has anybody successfully forced an anonymous subscriber to re-initiliaze from the publisher? I would have thought this was a fairly common requirement.

|||

Are you using push or pull subscription? If you are using push, can you try to use pull instead and see if that would work for you?

Regards,
Gary

|||

I'm using a pull subscription. As far as I know, SQL Server CE only supports anonymous pull subscriptions.

I've since been advised from a support engineer (via MSC) that SQL Server 2005 can't re-initialise anonymous subscribers from the publisher, only from the subscriber. I can't see why this limitation would be in place, but it is consistent with the errors I'm getting.

The workaround will be to build into the application a pre-sync check which connects to the publisher and checks a re-init flag, then re-inits from the subscriber based on that flag.

If anyone else can suggest an alterantive (or challenge the assertion that anonymous subscriptions can't be re-init from the publisher) I'm keen to hear it.

Thanks

|||

Steve, you should be able to reinitialize your mobile subscriber from the publisher.

exec pubdb..sp_reinitmergesubscription '<PublicationName>', @.subscriber='mysubscriber - aaaaaaaaaaaa', @.subscriber_db='D:\myPathToMobileDatabase.sdf'

I got the subscriber and subscriber_db from the publisher server's sysmergesubscriptions.

I executed the above at the publisher and the subscriber upon next sync was able to reinitialize.

Let me know if you are not seeing this and I would be interested to find out what issue you are encountering.

Note that I tried this on a desktop installation of mobile.

|||

I am using the same process. I grabbed the details out of the sysmergesubscriptions table and then executed the sp_reinitmergesubscription procedure. When the subscriber starts to sync, it recognises that a re-init is necessary and begins that process. If an up-to-date snapshot is not available it generates one otherwise it immediatly starts to transfer the data. At this point it stops with the following error messages:

The merge process could not allocate memory for an operation; your system may be running low on virtual memory. Restart the Merge Agent. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147198720)
Get help: http://help/MSSQL_REPL-2147198720
An error occurred while reading the .bcp data file for the 'CDP_TableDates' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199428)
Get help: http://help/MSSQL_REPL-2147199428
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. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)

The set up I'm using is SQL Server 2005 on Windows Server 2003 and SQL CE 3.1 on Windows XP (ie not mobile). The desktop is our target setup (although most clients are on Windows 2000).

I've also tried doing this in different combinations ie with both the SQL CE and the SQL Server 2005 databases on the Windows 2003 server, and with both running on the win xp desktop, but all get the same errors. In none of these situations is re-initialising from the subscriber an issue.

Any ideas on how to progress this?

|||

Further testing has uncovered an interesting way to get this work. For some reason if I validate all subscribers after using sp_reinitmergesubscription to re-intialise a single subscriber, the subscriber syncs and reinitialises fine. This is obviously not ideal, as forcing all subscribers to validate creates unnecassary overhead, but the result is that I don't get errors from the subscriber re-initialisation.

So my current steps are:

exec sp_reinitmergesubscription

kick off the dynamic snapshot job for the subscriber

exec sp_validatemergepublication

Re-initializing an anonymous subscription from the server - error

Hi,

I'm trying to force an anonymous subscription to re-intialize on it's next sync attempt. I can do this from the subscriber no problems, and from the publisher using 'Re-initalize All Subscriptions', but I can't seem to re-intialize only a single subscription from the publisher.

To do this I'm trying to execute sp_reinitmergesubscription using the subscriber details found in the sysmergesubscriptions table. This executes ok and when the subscriber starts to sync it does try to re-initialize starting with generating a new snapshot, but after processing for a while it throws the following error messages:

Error messages:
The merge process could not allocate memory for an operation; your system may be running low on virtual memory. Restart the Merge Agent. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147198720)
Get help: http://help/MSSQL_REPL-2147198720
An error occurred while reading the .bcp data file for the 'CDP_TableDates' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199428)
Get help: http://help/MSSQL_REPL-2147199428
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. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)

There doesn't appear to be any shortage of memory on the server. There is no problem regenerating the snapshot from the publisher, and there's no problem with syncing through the web using delta syncs or re-initializing from the subscriber, so I can't see any obvious cause from those error messages.

I'm using SQL Server 2005 SP2 on the publisher, and SQL ServerCE 3.1 on the subscriber.

Any ideas or alternatives?

Cheers

With an anonymous subscription the publisher is unable to connect to the subsciber so I would guess that actions like forcing a re-init cannot be done from the publisher.

Your root message is saying that the process could not deliver the snapshot to the subscriber. It is trying to connect to the subscriber but cannot as it is anonymous.

Martin

|||Thanks for the response.

I thought that SQL Server 2005 was supposed to remove a lot of the limitations of anonymous subscribers. In this case, as the subscriber can receive the snapshot when the re-init is initiated on the subscriber, I don't understand why it can't receive it when intiated on the publisher. The client obviously recognises that a re-init is required, surely from then the process should be the same?

Any other ideas?
|||

Has anybody successfully forced an anonymous subscriber to re-initiliaze from the publisher? I would have thought this was a fairly common requirement.

|||

Are you using push or pull subscription? If you are using push, can you try to use pull instead and see if that would work for you?

Regards,
Gary

|||

I'm using a pull subscription. As far as I know, SQL Server CE only supports anonymous pull subscriptions.

I've since been advised from a support engineer (via MSC) that SQL Server 2005 can't re-initialise anonymous subscribers from the publisher, only from the subscriber. I can't see why this limitation would be in place, but it is consistent with the errors I'm getting.

The workaround will be to build into the application a pre-sync check which connects to the publisher and checks a re-init flag, then re-inits from the subscriber based on that flag.

If anyone else can suggest an alterantive (or challenge the assertion that anonymous subscriptions can't be re-init from the publisher) I'm keen to hear it.

Thanks

|||

Steve, you should be able to reinitialize your mobile subscriber from the publisher.

exec pubdb..sp_reinitmergesubscription '<PublicationName>', @.subscriber='mysubscriber - aaaaaaaaaaaa', @.subscriber_db='D:\myPathToMobileDatabase.sdf'

I got the subscriber and subscriber_db from the publisher server's sysmergesubscriptions.

I executed the above at the publisher and the subscriber upon next sync was able to reinitialize.

Let me know if you are not seeing this and I would be interested to find out what issue you are encountering.

Note that I tried this on a desktop installation of mobile.

|||

I am using the same process. I grabbed the details out of the sysmergesubscriptions table and then executed the sp_reinitmergesubscription procedure. When the subscriber starts to sync, it recognises that a re-init is necessary and begins that process. If an up-to-date snapshot is not available it generates one otherwise it immediatly starts to transfer the data. At this point it stops with the following error messages:

The merge process could not allocate memory for an operation; your system may be running low on virtual memory. Restart the Merge Agent. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147198720)
Get help: http://help/MSSQL_REPL-2147198720
An error occurred while reading the .bcp data file for the 'CDP_TableDates' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199428)
Get help: http://help/MSSQL_REPL-2147199428
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. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)

The set up I'm using is SQL Server 2005 on Windows Server 2003 and SQL CE 3.1 on Windows XP (ie not mobile). The desktop is our target setup (although most clients are on Windows 2000).

I've also tried doing this in different combinations ie with both the SQL CE and the SQL Server 2005 databases on the Windows 2003 server, and with both running on the win xp desktop, but all get the same errors. In none of these situations is re-initialising from the subscriber an issue.

Any ideas on how to progress this?

|||

Further testing has uncovered an interesting way to get this work. For some reason if I validate all subscribers after using sp_reinitmergesubscription to re-intialise a single subscriber, the subscriber syncs and reinitialises fine. This is obviously not ideal, as forcing all subscribers to validate creates unnecassary overhead, but the result is that I don't get errors from the subscriber re-initialisation.

So my current steps are:

exec sp_reinitmergesubscription

kick off the dynamic snapshot job for the subscriber

exec sp_validatemergepublication

reinitialize deleted data

hi
i have sql 2000 sp3 and a merge publication with a filter. additional i
have a client with msde also sp3 with is subscriber to the
server-publication.
the replication worked just fine for weeks. on one day i made a sync
with lots of data. while synchronizing the computer shutdown into
standby. after waking up i had a error message from the sql server that
he lost connection or something. til here no problem. so i just tried
again to synchronize. i received the error "merge process could not
initialize publisher XXX"
so i clicked on "reinitialize" on the subscriber. he said then that he
would do it when the merge agent starts the next time. so i synchronized
again and it worked very fast. a bit too fast because ALL data in the
table he should have synchronized has gone. obviously deleted...
can i restore this data again without backup :-)
is this the correct behavour of a reinitialize? if yes, what should i
have done else? if no, what happend then?
thanx for every hint
jazper
You should be able to restore the subscriber from the subscriber backup.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Jazper Manto" <ejazper@.hotmail.com> wrote in message
news:uy8gN83aFHA.2900@.TK2MSFTNGP15.phx.gbl...
> hi
> i have sql 2000 sp3 and a merge publication with a filter. additional i
> have a client with msde also sp3 with is subscriber to the
> server-publication.
> the replication worked just fine for weeks. on one day i made a sync
> with lots of data. while synchronizing the computer shutdown into
> standby. after waking up i had a error message from the sql server that
> he lost connection or something. til here no problem. so i just tried
> again to synchronize. i received the error "merge process could not
> initialize publisher XXX"
> so i clicked on "reinitialize" on the subscriber. he said then that he
> would do it when the merge agent starts the next time. so i synchronized
> again and it worked very fast. a bit too fast because ALL data in the
> table he should have synchronized has gone. obviously deleted...
> can i restore this data again without backup :-)
> is this the correct behavour of a reinitialize? if yes, what should i
> have done else? if no, what happend then?
> thanx for every hint
> jazper
|||hi hilary
what is a "subscriber backup"?
is this the correct behavour of a reinitialize?
jazper

registration and Replicatons

Is registration of the subscriber required to configure replications.
I am configuring replications over the internet using a VPN connection
and do not want the Publisher/Distributor (Publisher and Distributor
are the same) to have the Subscriber registered. I know you can add a
subscriber using the system stored procedure but I was wondering if
registration of the subscriber was a requirement to perform
replication.
Thank you in advance for your help.
It is required.
You must register the servers in your hosts file, client configuration utility, and EM. Then you must enable your subscriber using SQL Server authentication.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Gent" wrote:

> Is registration of the subscriber required to configure replications.
> I am configuring replications over the internet using a VPN connection
> and do not want the Publisher/Distributor (Publisher and Distributor
> are the same) to have the Subscriber registered. I know you can add a
> subscriber using the system stored procedure but I was wondering if
> registration of the subscriber was a requirement to perform
> replication.
> Thank you in advance for your help.
>