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 Instance Invalid Connection NT 4.0

When connecting to SQL Server using a Win NT 4.0 client I receive the messag
e:
[DBNETLIB] ConnectionOpen [Invalid Instance ()]Invalid Connection
Another Win NT 4.0 client works fine.
SQL MSDE 2000 release A installed on the server. Another SQL 2000 instance
is running (from another vendor) on the same machine. MDAC 2.7 sp1 refresh
checks out fine in component checker.
Any idea?By default MSDE 2000 SP3 only allows local connections, you have to go in
and enable MSDE to listen on TCP or Named Pipes if you wnat to allow remote
connectivity.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.