Replication error - schema

I am getting the error below trying the 1st merge synch to my laptop. The
laptop has MSDE2000 SP3 on it. I tried this synch right after I setup the
database as a publisher. This is the 1st subscriber I have tried to create.
Can anyone help? Thanks.
David
The schema script
'\\LIFEDEV02\d$\sqldata\MSSQL\ReplData\unc\LIFEDEV 02_MCFIData_MCFIData\20051129091321\vw_BillingDeta ilBalance_1465.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: DONAFAYE (Agent); Error number: 0)
------
Invalid object name 'dbo.vw_BillingPaid'.
(Source: DONAFAYE (Data source); Error number: 208)
------
I think that I read somewhere that all objects such as functions, triggers,
procs, etc.. have to be at the subscriber if there is a dependency AND if
they are not in your publication. If the referenced object is not in your
publication then you'll have to add it or manually create it at the
subscriber.
Scott E. Hunley (MCAD)
Measure Twice, Cut Once...
"David" wrote:

> I am getting the error below trying the 1st merge synch to my laptop. The
> laptop has MSDE2000 SP3 on it. I tried this synch right after I setup the
> database as a publisher. This is the 1st subscriber I have tried to create.
> Can anyone help? Thanks.
> David
> The schema script
> '\\LIFEDEV02\d$\sqldata\MSSQL\ReplData\unc\LIFEDEV 02_MCFIData_MCFIData\20051129091321\vw_BillingDeta ilBalance_1465.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: DONAFAYE (Agent); Error number: 0)
> ------
> Invalid object name 'dbo.vw_BillingPaid'.
> (Source: DONAFAYE (Data source); Error number: 208)
> ------
>
>
|||David,
stored procedures use deferred name resolution, so you can get away with
this sort of thing, but in the case of views it doesn't work - you'll need
to have vw_BillingPaid on the subscriber to be able to initialize. You could
drop the subscription, XXX the view into the publication then readd the
subscription. You could alternatively add vw_BillingPaid manually, but this
would have to be done for any other subscribers.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul,
I'm confused. This is the FIRST subscription I am trying to create. The
view that is referred to DOES exist on the Publication. I do not understand
why I am getting this error.
David
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23fvafr09FHA.912@.TK2MSFTNGP11.phx.gbl...
> David,
> stored procedures use deferred name resolution, so you can get away with
> this sort of thing, but in the case of views it doesn't work - you'll need
> to have vw_BillingPaid on the subscriber to be able to initialize. You
> could drop the subscription, XXX the view into the publication then readd
> the subscription. You could alternatively add vw_BillingPaid manually, but
> this would have to be done for any other subscribers.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Paul,
I also looked at the articles being published and ALL views are selected. I
tried dropping and re-creating the subscription, but it did the same thing
at the exact same place. I once had a similar error problem with DTS on a
different database but never was able to resolve it. I also tried your
suggestion to add the view vw_BillingPaid to the subscriber. I did it with
DTS and exported the view and it went over fine. Then I ran the synch
again, but got the exact same error. This is very frustrating. Any ideas
on what else I can do to make this work? I have 7 laptops to setup as
anonymous subscribers, but can't even get the very 1st one to work. Thanks.
David
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23fvafr09FHA.912@.TK2MSFTNGP11.phx.gbl...
> David,
> stored procedures use deferred name resolution, so you can get away with
> this sort of thing, but in the case of views it doesn't work - you'll need
> to have vw_BillingPaid on the subscriber to be able to initialize. You
> could drop the subscription, XXX the view into the publication then readd
> the subscription. You could alternatively add vw_BillingPaid manually, but
> this would have to be done for any other subscribers.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||David,
I think your dependency information is corrupted. If you add the view to the
subscriber manually and meanwhile drop it from the publication it should be
ok. The current problem is that it is still in the publication and is
therefore being dropped.
Alternatively, run sp_depends on the view that errors to check that the
dependency is not acknowledged by SQL Server. If this shows no dependencies
then refresh the view and run it again to check the dependency is
recognised, and once this is the case, the snapshot article order should be
correct.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||You were right. I dropped the pub and subscriber and dropped and re-created
the 2 views and checked their dependencies. Both now appear ok. Then I
tried publication and the create subscriber again and got error on a
different view. Same error. I will remove and recreate everything again!
Is there any way to check all views at once for corrupt dependencies? (I'm
guessing no). Also, any idea how this could happen to so many views?
David
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:O8FdSaQ%23FHA.3340@.TK2MSFTNGP12.phx.gbl...
> David,
> I think your dependency information is corrupted. If you add the view to
> the subscriber manually and meanwhile drop it from the publication it
> should be ok. The current problem is that it is still in the publication
> and is therefore being dropped.
> Alternatively, run sp_depends on the view that errors to check that the
> dependency is not acknowledged by SQL Server. If this shows no
> dependencies then refresh the view and run it again to check the
> dependency is recognised, and once this is the case, the snapshot article
> order should be correct.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||David,
these links show the sort of thing we're talking about:
http://support.microsoft.com/?id=115333
http://support.microsoft.com/?id=201846
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Transactional\Snapshot replication in SQL2005 (the SQL2005 snapshot agent
specifically) is much more resilient to inaccurate\missing information in
sysdepends or sys.sql_dependencies. For Merge replication users, they have
the capability to specify a custom ordering for the articles in SQL2005 to
overcome these kinds of problems.
-Raymond
"David" <dlchase@.lifetimeinc.com> wrote in message
news:OTAXiyR%23FHA.3804@.TK2MSFTNGP14.phx.gbl...
> You were right. I dropped the pub and subscriber and dropped and
> re-created the 2 views and checked their dependencies. Both now appear
> ok. Then I tried publication and the create subscriber again and got
> error on a different view. Same error. I will remove and recreate
> everything again! Is there any way to check all views at once for corrupt
> dependencies? (I'm guessing no). Also, any idea how this could happen to
> so many views?
> David
> "Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
> news:O8FdSaQ%23FHA.3340@.TK2MSFTNGP12.phx.gbl...
>