Can you check and see how the articles are configured.

I think by default, the article is dropped and recreate from publisher when you push a snapshot.

You may find that with the table that is missing, the article has been set to either delete the destination data or truncate it.. and that is causing it to break.

if you have the replication error, you can browse the replication system tables to actually see what the snapshot script is trying to do.

i.e.

use distribution

go

select * from MSrepl_commands

where command_id = 1

and article_id = 47 -- table name from publisher

and xact_seqno = 0x00156D9100019C6D001300000000 -- this is normally found in the error on replication monitor

-- based on above information result, populate below

sp_browsereplcmds @xact_seqno_start = '00156D9100019C6D001300000000'

--,@xact_seqno_end = '00156D9100019C6D001300000000'

--,@originator_id = 1

,@publisher_database_id = 21 -- publishing database ID

,@article_id = 26 -- Publishing Table ID

,@command_id = 1

if the table is missing, script it from publisher and create it on the subscribing end and see if you can progress to the next error