Invalid object name 'dbo.MSmerge_tombstone'

Running SQL 2005/Win 2003 (publisher/distributor) & SQL 2000/Win 2003
(subscriber).
Lat night around 6:30, 7 of my 15 subscriptions to one publication
started to fail with the message below. I am not using merge
anywhere, currently, though I have had a merge publication in the past
that all 15 subscrivers, subscribed to. The publication is currently
a phamtom one that I cannot delete. They do not appear in the local
publications folder, but only in the replicaiton monitor for the
original publisher.
I do not know if these are related, but any help will be appreciated.
Larry...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Command attempted:
if @.@.trancount > 0 rollback tran
(Transaction sequence number: 0x0000147E0000451A001900000000, Command
ID: 1)
Error messages:
Invalid object name 'dbo.MSmerge_tombstone'. (Source: MSSQLServer,
Error number: 208)
Get help: http://help/208
Invalid object name 'dbo.MSmerge_tombstone'. (Source: MSSQLServer,
Error number: 208)
Get help: http://help/208
Could not use view or function 'tsvw_842FD9495DB74084823D364E97EB6D70'
because of binding errors. (Source: MSSQLServer, Error number: 4413)
Get help: http://help/4413
Invalid object name 'dbo.MSmerge_tombstone'. (Source: MSSQLServer,
Error number: 208)
Get help: http://help/208
Could not use view or function 'tsvw_842FD9495DB74084823D364E97EB6D70'
because of binding errors. (Source: MSSQLServer, Error number: 4413)
Get help: http://help/4413
Invalid object name 'dbo.MSmerge_tombstone'. (Source: MSSQLServer,
Error number: 208)
Get help: http://help/208
check to see if you have a merge replication trigger on one of the
subscriber tables. Looks like merge replication was not completely removed.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"LPR-3rd" <lreames@.gmail.com> wrote in message
news:1170175947.713622.18830@.v45g2000cwv.googlegro ups.com...
> Running SQL 2005/Win 2003 (publisher/distributor) & SQL 2000/Win 2003
> (subscriber).
> Lat night around 6:30, 7 of my 15 subscriptions to one publication
> started to fail with the message below. I am not using merge
> anywhere, currently, though I have had a merge publication in the past
> that all 15 subscrivers, subscribed to. The publication is currently
> a phamtom one that I cannot delete. They do not appear in the local
> publications folder, but only in the replicaiton monitor for the
> original publisher.
> I do not know if these are related, but any help will be appreciated.
> Larry...
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Command attempted:
> if @.@.trancount > 0 rollback tran
> (Transaction sequence number: 0x0000147E0000451A001900000000, Command
> ID: 1)
> Error messages:
> Invalid object name 'dbo.MSmerge_tombstone'. (Source: MSSQLServer,
> Error number: 208)
> Get help: http://help/208
> Invalid object name 'dbo.MSmerge_tombstone'. (Source: MSSQLServer,
> Error number: 208)
> Get help: http://help/208
> Could not use view or function 'tsvw_842FD9495DB74084823D364E97EB6D70'
> because of binding errors. (Source: MSSQLServer, Error number: 4413)
> Get help: http://help/4413
> Invalid object name 'dbo.MSmerge_tombstone'. (Source: MSSQLServer,
> Error number: 208)
> Get help: http://help/208
> Could not use view or function 'tsvw_842FD9495DB74084823D364E97EB6D70'
> because of binding errors. (Source: MSSQLServer, Error number: 4413)
> Get help: http://help/4413
> Invalid object name 'dbo.MSmerge_tombstone'. (Source: MSSQLServer,
> Error number: 208)
> Get help: http://help/208
>

Invalid cursor state

Hi! I want to build up a transactional replication between 2 SQL Server 2000. The Publisher is also the distributor.
I used all the wizards and after i made the subscriber, I get an error at the distribution agent:
Invalid cursor state
(Source: ODBC Driver Manager (ODBC); Error number: 24000)
What should i do now?
Please help, thank you!!
Is this error reproducible? For instance if you restart your Distribution
Agent do you get it again?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"oselinge" <oselinge@.discussions.microsoft.com> wrote in message
news:98B5BAD5-2551-4279-9B74-40A6481FF3E1@.microsoft.com...
> Hi! I want to build up a transactional replication between 2 SQL Server
2000. The Publisher is also the distributor.
> I used all the wizards and after i made the subscriber, I get an error at
the distribution agent:
> Invalid cursor state
> (Source: ODBC Driver Manager (ODBC); Error number: 24000)
> What should i do now?
> Please help, thank you!!
|||Yes, I get it again! I often tried to restart, but everytime i got this error.
"Hilary Cotter" wrote:

> Is this error reproducible? For instance if you restart your Distribution
> Agent do you get it again?
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "oselinge" <oselinge@.discussions.microsoft.com> wrote in message
> news:98B5BAD5-2551-4279-9B74-40A6481FF3E1@.microsoft.com...
> 2000. The Publisher is also the distributor.
> the distribution agent:
>
>
|||Oselinge,
usually this is an MDAC/ODBC error - hopefully this
article applies to your case:
http://support.microsoft.com/default.aspx?kbid=831997
HTH,
Paul Ibison
|||I think this is not the reason for this error.
Any other ideas?
"Paul Ibison" wrote:

> Oselinge,
> usually this is an MDAC/ODBC error - hopefully this
> article applies to your case:
> http://support.microsoft.com/default.aspx?kbid=831997
> HTH,
> Paul Ibison
>

Invalid column name 'rowguiedcol' - error number 207

"The process could not deliver the snapshot to the Subscriber"
I added a new database to the same server as the publisher and distributor.
The error ocurred when pushing a new subscription to it.
I did indicate that the subscriber already has the schema and data.
Any ideas for correcting?
thanks,
bob
Sounds like the table you are replicating to has an extra column in it which
is not in the publisher. Look for a column called rowguidcol and delete it.
If you get an error message complaining that this table is published for
replication or a similar message, verify that this table is not published,
or published to.
If it is you might have to do the following:
exec sp_configure N'allow updates', 1
go
reconfigure with override
go
UPDATE syscolumns set colstat = colstat & ~4096 WHERE colstat &4096 <>0
GO
UPDATE sysobjects set replinfo=0
GO
and then issue a sp_MSunmarkreplinfo against the problem table
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Robert A. DiFrancesco" <bob.difrancesco@.comcash.com> wrote in message
news:umf1ACevEHA.2520@.TK2MSFTNGP15.phx.gbl...
> "The process could not deliver the snapshot to the Subscriber"
> I added a new database to the same server as the publisher and
distributor.
> The error ocurred when pushing a new subscription to it.
> I did indicate that the subscriber already has the schema and data.
> Any ideas for correcting?
> thanks,
> bob
>