Please check this replication error..

I tried to replicate between SVRPOS01 and SVRPOS02.
SVRPOS01 is publisher and distributor.
Replication is Merge replication.
But, after snapshot agent ran, the following error comes out and merge agent doesn't do merge replication.
When configure replication I choose option initialize schema.., and in SVRPOS02 I just create empty DB.
Most of time this works... but not in this time..
SVRPOS02 doesn't have data replicated...
Please reply any idea of following error, and solution if you have any..
Thank you.

<Error message>
The schema script '\\SVRPOS01\C$\Program Files\Microsoft SQL Server\MSSQL\ReplData\unc\SVRPOS01_POS_POSPublicat ion\20040706003309\v_Item_Old_232.sch' could not be propagated to the subscriber.

<Error Detail>
The schema script '\\SVRPOS01\C$\Program Files\Microsoft SQL Server\MSSQL\ReplData\unc\SVRPOS01_POS_POSPublicat ion\20040706003309\v_Item_Old_232.sch' could not be propagated to the subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
----------------------------------
Unable to replicate a view or function because the referenced objects or columns are not present on the Subscriber.
(Source: SVRPOS02 (Agent); Error number: 0)
----------------------------------
Invalid object name 'POSLOC.dbo.BARCODE_MATCH'.
(Source: SVRPOS02 (Data source); Error number: 208)
----------------------------------You have to script the structure of the publishing database and apply to the subscriber before the snapshot agent runs for the first time.|||By any chance, does that view contain some sort of cross-database query? Then you need to make sure that database is also present on the subscriber.

Planning the rebuild of a merge publication (publisher) server

I am currently running a SQL Server 2000, which hosts the replication
publisher & distributor of a large merge publication DB. The current NT 4.0
server is scheduled for complete replacement and upgrade (to Win Server 2003
w/ SQL Server 2000) and I am looking for best practice recommendations for
transferring this database and replication topology from one system to
another. If possible, I would prefer to not to have to perform a complete
rebuild the replication topology. SQL BOL seems to indicate that Backup &
Recovery is not an option. Any ideas?
Thanks, Kevin
Kevin,
you should be able to detach and attach your publication database provided
you migrate master, msdb and the distribution database first, and the new
server name is identical to the old one. If this is too much hassle, then
you'd be better off scripting out the replication settings, tailoring them
with the new server name and then recreating from scratch.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)