replication error skipping file because it has already been delivered

Article
04/30/2014

Question

_{Wednesday, April 30, 2014 6:35 AM}

I've set up Replication, published the database, set up the subscriber (on a seperate server, within the same domain)

I'm getting an error message stating.

"replication error skipping file because it has already been delivered"

how do i resolve this ?

All replies (4)

_{Wednesday, April 30, 2014 5:06 PM ✅Answered}

You need to re-initialize the subscriptions.

looking for a book on SQL Server 2008 Administration? http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search? http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

_{Wednesday, April 30, 2014 12:12 PM | 1 vote}

Hi Pete Repka:

Based on the error message, i can suggest the below link please check and let me know.

http://blogs.msdn.com/b/repltalk/archive/2010/04/05/how-sql-server-2005-2008-replication-resumes-interrupted-snapshot-delivery.aspx

Thanks,

Satish Kumar.

Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)

_{Wednesday, April 30, 2014 12:53 PM}

As the link that Satish posted states that's not an error.

"how do i resolve this ?"

You don't. There's a reason replication is generating that message and it has to do with another problem while attempting to apply your snapshot. I have the same problem occasionally because one of our developers decided that the best solution to one of his problems on our report server was to create an indexed view.

Well that indexed view is schema bound so anytime I have to make a change to the publication which contains one of the tables the view is dependent on replication lets me know that it cannot drop the table and then begins to reapply the snapshot. Each time it attempts to reapply the snapshot it skips all the scripts that were successfully applied.

To resolve the problem I have to manually drop the indexed view, allow the snapshot agent to move past the application of the schema scripts and then recreate the view once the snapshot agent begins delivering data.

_{Wednesday, April 30, 2014 1:43 PM}

Hi Ed,

the reason why i was posted the above link is --> the page was saying the reasons why the replication do skipping part.

Here in this case i can not predict the reason of failure, hence i shared it. Please let me know on this.