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 Push subscription after it expired in Transactional Replication

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

A reinitialize requires reapplying the snapshot. Can you be more clear what you're trying to accomplish? I think what you want to do is just restart the distribution agent, does this work?

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

Reinitializing a subscription

Win 2000 & SQL 2000 SP3
I have a publication that wants to be reinitialized (The
subscription(s) have been marked inactive and must be reinitialized.
NoSync subscriptions will need to be dropped and recreated.). When I
created the push subscription, I did it NoSync, so I know I have to
drop and recreate it. But, my question is this....How can I prevent
from loosing the transactions that are pending? If I drop the
subscription & recreate it, the pending transactions will be
lost...right?!?!? I need these. HELP
TIA,
Larry...
Yes you are correct. The best approach to this sort of problem is to use
sp_browsereplcmds like this
sp_browsereplcmds @.publisher_database_id = 7,@.results_table =
'results_table'
where @.publisher_database_id is your publication database ID.
Then you have the commands stored in your results table. You can run these
on your subscriber. You can also use @.xact_seqno_start to define a start id.
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
<lreames@.gmail.com> wrote in message
news:1112196237.338064.299320@.o13g2000cwo.googlegr oups.com...
> Win 2000 & SQL 2000 SP3
> I have a publication that wants to be reinitialized (The
> subscription(s) have been marked inactive and must be reinitialized.
> NoSync subscriptions will need to be dropped and recreated.). When I
> created the push subscription, I did it NoSync, so I know I have to
> drop and recreate it. But, my question is this....How can I prevent
> from loosing the transactions that are pending? If I drop the
> subscription & recreate it, the pending transactions will be
> lost...right?!?!? I need these. HELP
> TIA,
> Larry...
>

reinitialized subscription - more info

Running - Win 2K / SQL 2K
I am constantly, once a week or so,getting an error on a
transactional publication that I have...
The subscription(s) have been marked inactive and must be
reinitialized. NoSync subscriptions will need to be
dropped and recreated.
This publication is set up to be continious and is
checked daily to verify it is running. I will come in
one morning and there will be an error. There are 15
remote locations using a transactional/continous
publication to move data to the main office.
How can I prevent this from happening?
What is causing this?
Is there some logging option I can turn on to see more
info about the transactions?
Larry....
By default is a publisher and subscriber have not "talked to" each other for
14 days the subscriber is marked inactive and the subscription may be
dropped. You must reinitialize, regenerate and redistribute the snapshot to
clear this condition.
You can set the interval by right clicking on your publication, selecting
properties and in the subscription expiration section, set a long expiration
value.
I normally run scripts that detect whether the distribution agent has
replicated a transaction to the subscriber in the last 24 hours, and if not,
it raises an alert which causes operations to be paged.
This raises the visibility of these errors.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"larry..." <anonymous@.discussions.microsoft.com> wrote in message
news:9b3601c43446$63f03c20$a401280a@.phx.gbl...
> Running - Win 2K / SQL 2K
> I am constantly, once a week or so,getting an error on a
> transactional publication that I have...
> The subscription(s) have been marked inactive and must be
> reinitialized. NoSync subscriptions will need to be
> dropped and recreated.
> This publication is set up to be continious and is
> checked daily to verify it is running. I will come in
> one morning and there will be an error. There are 15
> remote locations using a transactional/continous
> publication to move data to the main office.
> How can I prevent this from happening?
> What is causing this?
> Is there some logging option I can turn on to see more
> info about the transactions?
> Larry....
>

reinitialized subscription

Running - Win 2K / SQL 2K
I am constantly getting an error on a merge
publication/subscription that I have...
The subscription(s) have been marked inactive and must be
reinitialized. NoSync subscriptions will need to be
dropped and recreated.
How can I prevent this from happening?
What is causing this?
Larry...
you normally get this error when your subscribers haven't connected to your
publisher within 14 days for transactional and merge publications.
The way to prevent this is to ensure your subscriber connects to your
publisher within this period.
Exactly how frequently are you getting this error?
"larry" <anonymous@.discussions.microsoft.com> wrote in message
news:89a401c432b4$81e001e0$a401280a@.phx.gbl...
> Running - Win 2K / SQL 2K
> I am constantly getting an error on a merge
> publication/subscription that I have...
> The subscription(s) have been marked inactive and must be
> reinitialized. NoSync subscriptions will need to be
> dropped and recreated.
> How can I prevent this from happening?
> What is causing this?
> Larry...
|||.....Exactly how frequently are you getting this error?
Hilary,
I get this on one of my continous transactional
subscriptions once every couple of weeks. I check
replication every day and in fact, the SQL server agent
gets restarted every night @. 2:00 am.
Larry...

Reinitialize subscriptions in transactional replication

If I have one table in one publication in transactional replication
replication between primary and replicate is broken because subscription is marked as inactive.

If there are 3 rows on replicate and 5 rows on primary , out of which 2 are added after replication is broken

If I do

Reinitialize subscriptions
start the snapshot agent
start the distribution agent

Does this mean that it will only transfer the new 2 rows to replicate sites ? or will it drop everything from replicate site and apply all rows from primary site on to replicate.

Any help is appreciatedIt will drop every article the subscriber subscribes and refresh the DDL and data from the publication.

Reinitialize subscription thru DOS

Hey All,
Is there a way thru which I can reinitialize a subscription using a
batch/ script file. Or force the generation of a snapshot and force
apply the snapshot using a batch/ script file.
Thanks a lot for your help.
Jatin
*** Sent via Developersdex http://www.codecomments.com ***
Jatin,
you need to call the relevant sp_reinit... stored procedure (eg
sp_reinitsubscription), followed by running the snapshot and
distribution/merge agents (sp_start_job). You could have all these as a TSQL
batch file and use OSQL to run the batch file if you need to do it through
DOS (also the OSQL commands could be in a DOS batch file).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Thanks Paul...that is exactly what I ended up doing.
*** Sent via Developersdex http://www.codecomments.com ***

Re-Initialize subscription did not upload changes?

I'm doing a test.
I dropped a subscription on Subscriber-A
I performed some transactions on Subscriber-A.
I pushed a new subscription to it and indicated that it already had schema
and data.
I'm trying to get those new transactions to the publisher. I chose then to
re-initialize the subscription and checked the box to upload changes. But
the publisher never received those new transactions?
What may I try?
bob
It sounds like that you chose not to apply data and structure during
snapshot set up. Do you have the corresponding stored procedures in your
subscribers?
If not, that may be the first step to look at.
"Robert A. DiFrancesco" <bob.difrancesco@.comcash.com> wrote in message
news:OxqVBuswEHA.2876@.TK2MSFTNGP12.phx.gbl...
> I'm doing a test.
> I dropped a subscription on Subscriber-A
> I performed some transactions on Subscriber-A.
> I pushed a new subscription to it and indicated that it already had schema
> and data.
> I'm trying to get those new transactions to the publisher. I chose then
to
> re-initialize the subscription and checked the box to upload changes. But
> the publisher never received those new transactions?
> What may I try?
> bob
>

Reinitialize pull subscription

i am using merge replication for data sync. in the client i have utility
written in vb that use
merge object. Clients get the dynamic snapshots. My question is:
when i run the job and create a new snapshot for a user,
how can i force the client to use this new sanpshot instead of getting
incremental changes?
thanks so much
by the way i use anonymous pull subscription..
"prefect" <uykusuz@.uykusuz.com> wrote in message
news:efuOUegNGHA.3576@.TK2MSFTNGP15.phx.gbl...
> i am using merge replication for data sync. in the client i have utility
> written in vb that use
> merge object. Clients get the dynamic snapshots. My question is:
> when i run the job and create a new snapshot for a user,
> how can i force the client to use this new sanpshot instead of getting
> incremental changes?
> thanks so much
>
|||If you are referring to an existing client, you would have to reinitialize
the subscription. However I don't see why you would want to do this. Please
can you provide a bit more background info.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||for some clients , that do not synchronized for a long time, retention
period expired
therefore some data is lost. so i create a new snapshot with fresh data for
them and i want them to use this new snapshot.
as i said before , they are using a vb utility to synchronize (anonymous
pull subscription).
you know , this utility works like merge agent. i want to do something in
the publisher to make it get the new snapshot.
if the clients remove the utility which deletes the database and install
again , it is working fine. but i dont want them to do that.
thanks so much
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:ekMsamhNGHA.3284@.TK2MSFTNGP14.phx.gbl...
> If you are referring to an existing client, you would have to reinitialize
> the subscription. However I don't see why you would want to do this.
> Please can you provide a bit more background info.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||OK - please take a look at "sp_reinitmergepullsubscription".
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

reinitialization of subscriptions

If I have a subscription to a publication (transactional)
and the Distribution Agent tells me I need to
reinitialize.
What are the steps to do this?
Do I need to delete all the data on the subscriber? If
so, is there a way around this? If not, what is the best
practice of accomplishing this?
What if there are changes made at the subscriber do I
loose them if the subscription is reinitializatized?
Thanks...
Jimmy,
reinitialize means apply a new snapshot, so, you'll need to run the snapshot
agent first then run the distribution agent. When you say will it delete all
the data on the subscriber, I'm not sure why this is a concern. For
transactional replication, the subscriber data is treated as RO data. If
however someone has edited the data, then you could use binary checksums to
see what has changed and then do the same changes on the publisher. If the
subscriber is using updatable transactional replication then the changes are
already on the publisher. If you're using a queue, then be sure to run the
queue reader to send up the changes.
HTH,
Paul Ibison
|||expand your publishing database, right click on your publication, select
properties, click on your subscriber tab, highlight your subscriber, and
click the reinitialize button.
It will delete all the data of the replication objects and their schemas and
then replace them.
"Jimmy" <anonymous@.discussions.microsoft.com> wrote in message
news:9dc801c43447$43f3a5a0$a601280a@.phx.gbl...
> If I have a subscription to a publication (transactional)
> and the Distribution Agent tells me I need to
> reinitialize.
> What are the steps to do this?
> Do I need to delete all the data on the subscriber? If
> so, is there a way around this? If not, what is the best
> practice of accomplishing this?
> What if there are changes made at the subscriber do I
> loose them if the subscription is reinitializatized?
> Thanks...
|||Paul,
You said...
then you could use binary checksums to see what has
changed and then do the same changes on the publisher
How?
Larry...

>--Original Message--
>Jimmy,
>reinitialize means apply a new snapshot, so, you'll need
to run the snapshot
>agent first then run the distribution agent. When you
say will it delete all
>the data on the subscriber, I'm not sure why this is a
concern. For
>transactional replication, the subscriber data is
treated as RO data. If
>however someone has edited the data, then you could use
binary checksums to
>see what has changed and then do the same changes on the
publisher. If the
>subscriber is using updatable transactional replication
then the changes are
>already on the publisher. If you're using a queue, then
be sure to run the
>queue reader to send up the changes.
>HTH,
>Paul Ibison
>
>.
>
|||Larry,
there's a good explanation of BINARY_CHECKSUM in books online (BOL). If you
have any problems with the explanation, please post back.
Regards,
Paul Ibison

Registry Permissions for on demand pull subscription

To configure an on-demand pull subscription, the domain user account used by
the SQL Server Agent service must have full control permissions on the
registry key: HKLM\Software\Microsoft\Microsoft SQL
Server\80\Replication\Subscriptions. When I attempt to use the registry
editor to configure the permissions, the subscriptions portion of the key is
not present. I am running Win 2000 Server and SQL Server 2000. I am logged on
as an administrator, and I have sucessfully created a merge publication and a
push subcription. Any thoughts on what may be my problem? What SQL process
creates the subscriptions entry in the registery?
Tom McAvoy, MCP
The subscriptions portion of the key can be filled in by using reg files,
but the preferred way of doing it is having Windows Synchronization Manager,
or the ActiveX Controls make these changes.
When you create your push (only through the procs), or you pull (procs or
wizards), ensure you select on demand pull. This will register your
subscription and make the necessary registry entries.
If you did not do this, you will have to configure your pull subcription
withing WSM.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Tom McAvoy" <TomMcAvoy@.discussions.microsoft.com> wrote in message
news:7E02406B-F211-49F4-B1FD-41C2B6127F4A@.microsoft.com...
> To configure an on-demand pull subscription, the domain user account used
by
> the SQL Server Agent service must have full control permissions on the
> registry key: HKLM\Software\Microsoft\Microsoft SQL
> Server\80\Replication\Subscriptions. When I attempt to use the registry
> editor to configure the permissions, the subscriptions portion of the key
is
> not present. I am running Win 2000 Server and SQL Server 2000. I am logged
on
> as an administrator, and I have sucessfully created a merge publication
and a
> push subcription. Any thoughts on what may be my problem? What SQL process
> creates the subscriptions entry in the registery?
> --
> Tom McAvoy, MCP
|||Hillary, thank you for the response. I am unable to create the 'on-demand
pull' subscription due to the lack of permissions on the registry key. I
receive an 'access denied error'. I don't have the exact error info
avaialble right now. I'll review the problem on Monday and post more complete
error info.
"Hilary Cotter" wrote:

> The subscriptions portion of the key can be filled in by using reg files,
> but the preferred way of doing it is having Windows Synchronization Manager,
> or the ActiveX Controls make these changes.
> When you create your push (only through the procs), or you pull (procs or
> wizards), ensure you select on demand pull. This will register your
> subscription and make the necessary registry entries.
> If you did not do this, you will have to configure your pull subcription
> withing WSM.
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Tom McAvoy" <TomMcAvoy@.discussions.microsoft.com> wrote in message
> news:7E02406B-F211-49F4-B1FD-41C2B6127F4A@.microsoft.com...
> by
> is
> on
> and a
>
>
|||It seems that you need to be a power user or admin on the machine you are
trying to pull the subscription to.
Also the account which is doing the pulling should be in the PAL.
"Tom McAvoy" <TomMcAvoy@.discussions.microsoft.com> wrote in message
news:8518A10B-BFB3-4C4D-A6E4-8A605F129C22@.microsoft.com...
> Hillary, thank you for the response. I am unable to create the 'on-demand
> pull' subscription due to the lack of permissions on the registry key. I
> receive an 'access denied error'. I don't have the exact error info
> avaialble right now. I'll review the problem on Monday and post more
complete[vbcol=seagreen]
> error info.
> "Hilary Cotter" wrote:
files,[vbcol=seagreen]
Manager,[vbcol=seagreen]
or[vbcol=seagreen]
used[vbcol=seagreen]
registry[vbcol=seagreen]
key[vbcol=seagreen]
logged[vbcol=seagreen]
publication[vbcol=seagreen]
process[vbcol=seagreen]

Registration edit for replication ?

I have a laptop on a LAN and I have pushed a new subscription to it. Now I
want to move the Laptop to its proper location (in another city for example)
and replicate to it via the internet.
Can I simply edit the server registration at the Publisher?
thank you,
bob
Bob,
assuming you don't intend to reinitialize, AFAIK there is no new
configuration necessarily required on the publisher. However, on the
subscriber there are various stipulations:
It'll need to be set up as a pull subscriber.
On the laptop you'll need to set up an alias in the client network utility
and place an entry in the hosts file to recognise the publisher.
For security, the pull agent will need to be set up to use SQL
authentication or passthrough windows authentication.
If you want to subsequently reinitialize, then changes will be necessary on
the publisher. You'll need to set @.enabled_for_internet = true so that FTP
can be used to download the snapshot.
HTH,
Paul Ibison
|||no. The subscriber in this case is probably set up for an push. Exactly how
is the publisher going to find the subscriber over the internet.
To get this to work you would have to update the lmhosts and/or the hosts
file for the new ip address, Client Network Utiltity for the new ip address.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Robert A. DiFrancesco" <bob.difrancesco@.comcash.com> wrote in message
news:eSDh92DZEHA.2408@.tk2msftngp13.phx.gbl...
> I have a laptop on a LAN and I have pushed a new subscription to it. Now
I
> want to move the Laptop to its proper location (in another city for
example)
> and replicate to it via the internet.
> Can I simply edit the server registration at the Publisher?
>
> thank you,
> bob
>