Microsoft sql server 2005 merge replication

Did you use IIS on a seperate box too? Much obliged to your info. When a normal snapshot runs, it invalidates all the dynamic snapshots. Also if the snapshot is expired due to retention or other admin actions then the snapshot needs to be run to make the syncs succeed. What do you mean by application has been re-installed?

On what server, and what does it mean to the subscriber? We are having the exact same message. We currently have 5 mobile devices subscribing to one publication using IIS as the proxy as well. The differences I see between our production and others is we do not generate the snapshot daily and our retention policy has been increased to 30 days.

Mahesh I noticed you were talking about permission issues but this domain account never changes. You were also referencing the replisapi. Shouldn't it be the sqlcesa This is becoming a big concern as we are planning on having over 40 devices soon. Yes, For device virtual directory it is sqlcesa From what I gather you have a few partitions, run regular snapshot, run the dynamc snapshots for the partitions, everything runs fine, and suddenly some of them start failing.

Now, I also read in above posts, that some of the devices are re-installed. Now this means that the new device can come with a new id or a new partition. In this case, you need to make sure that the new device coming in comes with the same partition that was there previously or a new dynamic snapshot for this partition is generated.

And any symptoms under which these problems show up will definitely help us in diagnosing the problem better. Now if this device gets reinstalled it may get a different id and hence a new partition id. So when it tries to sync, the previously generated snapshot is not valid any longer and it needs a new dynamic snapshot. Another question I would have is do you see these errors out of the blue or when a new subscriber is tried to sync the first time or a re-initialization of an existing one. Error Code: Message : Minor Err.

Error Code: C Message : An error occurred while reading the. Minor Err. Error Code: Message : The merge process was unable to deliver the snapshot to the Subscriber. I'm getting the same error messages, but I'm not using any filters. Was all working fine, the only recent change was that I had added a new table to the publication articles with the "Highlighted table is download-only" option set.

I generated a new snapshot after adding the table as advised. Later I removed the "download-only" option and reinitialised all subscriptions as advised , with "generate a new snapshot" and "upload unsynchronized change" checked. After that, every subscriber got those error messages when trying to synch. I tried the following to resolve the problem:. None of these worked, I still got those error messages.

The only thing which worked was 4 reinitialise subscription with "upload changes" option unchecked, after that all worked fine, so I don't think it was a permissions problem. I think I might have caused some problems by adding the "download-only" table, but it seems that whenever I add a new table to the publication I have problems with synchronisation, especially if the new table has some foreign key references to existing tables.

Does anyone know if there is a special process I need to follow when adding a table in order to avoid these synch problems? The resolution 4 above is equivalent to deleting the db on the device so not really a satisfactory option. Than I dropped and recrated related user's partition and ran the user's dynamic snapshot job which completed successfully.

But when I retried to sync i've got the same error. The result was intersting each table was downloading times. Here is another shot, this times times. We had avoided this error by using auto generated dynamic partiton by referencing below article which does not exist anymore.

I think this new issue is related with an another thread, and it has been fixed:. There was a known issue with replication that meant for each generation of changes, you would get a copy of the data. Basically the stored procedure that runs when you initialise was getting run once for each generation per subscriber. I beleive that SP1 fixed this. However, that is secondary to the issue of the subscription running fine then just falling over.

Select Create a snapshot immediately , clear Schedule the snapshot agent to run at the following times , and select Next :. On the Agent Security page, select Security Settings. After the publication is created, select Close. Under the Replication node in Object Explorer , right-click Local Publications and select Refresh to view your new merge replication.

The current status of the Snapshot Agent job for the publication appears. Ensure that the snapshot job has succeeded before you continue to the next lesson. Select OK again. In this section, you add a subscription to the merge publication that you created previously.

You then set permissions on the subscription database and manually generate the filtered data snapshot for the new subscription. Expand the Replication folder, right-click the Local Subscriptions folder, and then select New Subscriptions. The New Subscription Wizard starts:.

In the Connect to Server dialog box, enter the name of the publisher instance in the Server name box, and select Connect. On the Subscribers page, select the instance name of the subscriber server.

Under Subscription Database , select New Database from the list. Select OK , and then select Next. On the Merge Agent Security page, select the ellipsis … button. Select OK , select Next , and then select Next again.

Select Next to proceed to the Subscription Type page, and select the appropriate subscription type. This tutorial uses Client. The more you tell us the more we can help. Can you help us improve? Resolved my issue. Clear instructions. Easy to follow. No jargon. Pictures helped.

Didn't match my screen. I will use the publisher as the subscriber also. After that, manage the replication articles, data, and database objects by choosing the objects to be replicated. Then add filters to the published tables to optimize performance and then configure the snapshot agent.

Choose one or more subscriber databases.