Reenable current subscriptions

From: Alan (Alan_at_discussions.microsoft.com)
Date: 09/14/04


Date: Tue, 14 Sep 2004 08:19:05 -0700

Hi.
Here is a problem:
We had 5 laptops with SQL personal edition that are subscribed to Enterprise
SQL Server on our main server.
Occasionally these laptops ran synchronization with main SQL Server and the
database was up-to-date.
Then we had to move all services from old server to new one.
In order to detach/attach database we had to stop Publication service on SQL
Server.
After that move we can not attach our old subscribers to either new or old
server.
We are getting message:
***************************
connecting to Publisher 'serverName'
1% complete
The initial snapshot for publication 'databaseName' is not yet available.
The initial snapshot for publication 'databaseName' is not yet available.
plSQLMerge -> Initialize() failed
Merge Replication Provider: The initial snapshot for publication
'databaseName' is not yet available.
***************************
We talked with vendor - they said that Publisher doesn't recognize old
subscribers anymore and all old subscriptions are lost.
There was not anything else vendor can help with.

I will appreciate if you could give me some directions what needs to be done.
1. I was wondering how I can create new subscription to existing Publisher
on new server. Where and how can I get original snapshot.
I was thinking in such scenario we will loose data on laptops (subscribers)
entered after last synchronization.
OR
2. Is there any way to attach current subscribers to Publisher on new server.
Vendor said it is not possible.

Again - any suggestions will be greatly appreciated.

Thanks,
Alan.



Relevant Pages

  • Re: Upgrade scenario
    ... > (only other updateable option in SQL Server 7.0). ... Recreate any SQL Agent jobs that should be setup on the 2005 server ... You have moved all of your subscribers over ... Applications congtinue to run during the upgrade ...
    (microsoft.public.sqlserver.replication)
  • Re: Identity values is checnges by initial snapshot
    ... > If you do not want to use SQL server identity range handling, ... > in merge replication - if you have publisher and two subscribers, ... Then after aplying snapshot you should ... We are not using identity ranges. ...
    (microsoft.public.sqlserver.replication)
  • Re: distribution database does not seem to shrink
    ... The distribution database that resides on the same server as 4 other published dbs seems to be choking on entries for just one of the publishers. ... All of the subscribers seem to be current.. ...
    (microsoft.public.sqlserver.replication)
  • Re: Merge Meta Data
    ... Looking for a SQL Server replication book? ... The main publisher has eight subscribers, ... the uploads, its genhistory was 1.1 million rows. ...
    (microsoft.public.sqlserver.replication)
  • Re: Merge Meta Data
    ... Looking for a SQL Server replication book? ... The main publisher has eight subscribers, ... entered in ten databases and change each row so that users cannot make any ... the uploads, its genhistory was 1.1 million rows. ...
    (microsoft.public.sqlserver.replication)