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
>
Showing posts with label subscriber. Show all posts
Showing posts with label subscriber. Show all posts
Friday, March 23, 2012
Monday, March 19, 2012
Invalid Descriptor Index
Hi,
I have setup snapshot pull replication between SQL2000 (publisher) and
MSDE2000 (subscriber).
The following error "Invalid Descriptor Index" is occuring on the
subscriber. Would someone please tell me what this error means and how to
get around it?
Thanks
reapply sp3 on the subscriber.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"mm" <postto@.news.com> wrote in message
news:u8luytqlEHA.2492@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I have setup snapshot pull replication between SQL2000 (publisher) and
> MSDE2000 (subscriber).
> The following error "Invalid Descriptor Index" is occuring on the
> subscriber. Would someone please tell me what this error means and how to
> get around it?
> Thanks
>
I have setup snapshot pull replication between SQL2000 (publisher) and
MSDE2000 (subscriber).
The following error "Invalid Descriptor Index" is occuring on the
subscriber. Would someone please tell me what this error means and how to
get around it?
Thanks
reapply sp3 on the subscriber.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"mm" <postto@.news.com> wrote in message
news:u8luytqlEHA.2492@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I have setup snapshot pull replication between SQL2000 (publisher) and
> MSDE2000 (subscriber).
> The following error "Invalid Descriptor Index" is occuring on the
> subscriber. Would someone please tell me what this error means and how to
> get around it?
> Thanks
>
Labels:
andmsde2000,
database,
descriptor,
error,
following,
index,
invalid,
microsoft,
mysql,
oracle,
publisher,
pull,
replication,
server,
setup,
snapshot,
sql,
sql2000,
subscriber
Monday, March 12, 2012
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
>
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
>
Friday, March 9, 2012
invalid cab file after snapshot via FTP
I was able to successfuly retrieve a snapshot via FTP but the subscriber says
the snapshot .cab within the folder is invalid. What would make the file
invalid?
Jeffrey, this looks rather strange indeed. Which version of SQL server are
you running? Is the cab file marked read-only by any chance? Can you browse
the content of snapshot.cab directly in Explorer? Were there any strange
error messages in the snapshot agent history table? Does the problem go away
if you regenerate the snapshot?
-Raymond
"Jeffrey K. Ericson" wrote:
> I was able to successfuly retrieve a snapshot via FTP but the subscriber says
> the snapshot .cab within the folder is invalid. What would make the file
> invalid?
the snapshot .cab within the folder is invalid. What would make the file
invalid?
Jeffrey, this looks rather strange indeed. Which version of SQL server are
you running? Is the cab file marked read-only by any chance? Can you browse
the content of snapshot.cab directly in Explorer? Were there any strange
error messages in the snapshot agent history table? Does the problem go away
if you regenerate the snapshot?
-Raymond
"Jeffrey K. Ericson" wrote:
> I was able to successfuly retrieve a snapshot via FTP but the subscriber says
> the snapshot .cab within the folder is invalid. What would make the file
> invalid?
Subscribe to:
Posts (Atom)