Re: Unable to merge replication table
- From: "Jonathan Lafontaine" <jlafontaine@xxxxxxxxxxxxx>
- Date: Mon, 9 Jan 2006 13:49:07 -0500
Thanks for your quick answer.
This table never had more than 255 fields, in fact, it has never been bigger
than it is right now.
I can't post the error message because there isn't one.
The only thing I get is a HRESULT of 0x80004005 and native error of 0.
According to Hilary Cotter, this is the generic access denied error message.
I've checked persmission/authorization and nothing seems wrong to me.
The other tables from that database replicate just fine in the same
publication as long as this table isn't part of it.
"Paul Ibison" <Paul.Ibison@xxxxxxxxxxxxx> a écrit dans le message de news:
OpCe%23qUFGHA.344@xxxxxxxxxxxxxxxxxxxxxxx
> Jonathan,
> works fine for me. Are you perhaps using a table that previously had a lot
> of columns (>255) and subsequently had some columns deleted? If so you
> could be running into the issue from a thread last week ("Problem with
> tables where the Column_id > 255"). BTW please could you post up the error
> message if this is not the issue.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
.
- Follow-Ups:
- Re: Unable to merge replication table
- From: Paul Ibison
- Re: Unable to merge replication table
- References:
- Unable to merge replication table
- From: Jonathan Lafontaine
- Re: Unable to merge replication table
- From: Jonathan Lafontaine
- Re: Unable to merge replication table
- From: Paul Ibison
- Unable to merge replication table
- Prev by Date: Re: SQL 2000 Replication and MS Great Plains v. 7.x
- Next by Date: Re: Unable to merge replication table
- Previous by thread: Re: Unable to merge replication table
- Next by thread: Re: Unable to merge replication table
- Index(es):
Relevant Pages
|