| John Bell 2005-08-30, 3:23 am |
| Hi
Unfortunately I am not an expert on replication!
Hilary Cotter who has replied in microsoft.public.sqlserver.replication
knows alot more about replication than I.
John
"steroche" wrote:
> Im afraid not. I have tried everything at this stage and its driving me
> crazy!!!!!
> I have re-published my database about 10times i'd say and i always get
> an error.
> Generally I get one of 2 errors. If i have already created the database
> the errors are:
>
> Message "Row data cannot be set. [,,,,,]"
> NativeError 28572
> and
> Message "Invalid row handle"
> NativeError 0
>
> However if i dont have it created previous to running it and it creates
> it itself I get the error:
>
> message "Run"
> NativeError 28557
>
> Message "The row update or insert cannot be reapplied due to an
> integrity violation. [,,,,,]
> NativeError 28549
>
> What the hell is going on?? I have checked all the tables to make sure
> that the checkbox "Enforce Relationship for replication" IS checked so
> the NOT FOR REPLICATION bug doesn't apply here.
>
> I have checked over all my datatypes and relationships and the data
> that they contain to ensure that there can be no FK conflicts.
>
> I know the table is being created as i can see it on the CE Query
> analyser but it contains no tables so this probably gives rise to the
> second error but why is it not creating the db properly in the first
> place??????
>
> I heard that compacting the db might help - how do i do that??
>
>
|