Integrity Violation when syncing with SQL CE, but not MSDE

I'm getting the following error when I do a sync with SQL CE:
Error Code: 80004005 Message : Run
NativeErr.: 28557
Source : Microsoft SQL Server 2000 Windows CE Edition
Err. Par. 0: data source=\Program Files\ThinkShare\Fdm\FdmJournal_eli.sdf; -
Error Code: 80040E2F
Message : The row update or insert cannot be reapplied due to an integrity
violation. [,,,,,]
NativeErr.: 28549 Source : Microsoft SQL Server 2000 Windows CE
We use merge replication and have several join and select filters. What's
interesting is that MSDE will sync just fine using the same publication.
Is it possible to find out what the offending table is and which row(s) is
causing the problem?
Thanks,
Eli
you might look for data types that were automatically converted during the
merge. For instance any nchar types longer tahtn 255 are converted to ntext
(which can't be a key). ther are a few others that I can't remember. they're
listed in online manuals.
Any of the offending columns can be remedied by modifying the article
properties in the publication setup. There you can turn of indexing
.....integrity settings...etc.. for articles in a publication.
i ran into these type of issues a few times and they were very frustrating
to figure out. If the database structure is intact after the faile merge
perhaps you can look at the local sqlce database with the ce query analyzer.
"Eli Tucker" <eli-msdn@.mailinator.com> wrote in message
news:Oz2$3I$gEHA.3320@.TK2MSFTNGP11.phx.gbl...
> I'm getting the following error when I do a sync with SQL CE:
> Error Code: 80004005 Message : Run
> NativeErr.: 28557
> Source : Microsoft SQL Server 2000 Windows CE Edition
> Err. Par. 0: data source=\Program
Files\ThinkShare\Fdm\FdmJournal_eli.sdf; -
> Error Code: 80040E2F
> Message : The row update or insert cannot be reapplied due to an integrity
> violation. [,,,,,]
> NativeErr.: 28549 Source : Microsoft SQL Server 2000 Windows CE
> We use merge replication and have several join and select filters. What's
> interesting is that MSDE will sync just fine using the same publication.
> Is it possible to find out what the offending table is and which row(s) is
> causing the problem?
> Thanks,
> Eli
>
|||I do have several columns that are varchar(256) that get converted to ntext
when syncing with SQL CE, but as far as I can tell none of these columns are
indexed or are keys. In fact, the sync works fine with some instances of
data, but not with others. When you were having the problem, did it happen
the first time you attempted to sync?
Also, could you explain how to turn off indexing/integrity settings of a
publication in more detail? I couldn't quote follow what you wrote below.
Thanks again for your help,
Eli
"mgarner1980" <mgarner@.kbsi.com> wrote in message
news:u34W8jKhEHA.3916@.TK2MSFTNGP11.phx.gbl...
> you might look for data types that were automatically converted during the
> merge. For instance any nchar types longer tahtn 255 are converted to
ntext
> (which can't be a key). ther are a few others that I can't remember.
they're
> listed in online manuals.
> Any of the offending columns can be remedied by modifying the article
> properties in the publication setup. There you can turn of indexing
> ....integrity settings...etc.. for articles in a publication.
> i ran into these type of issues a few times and they were very frustrating
> to figure out. If the database structure is intact after the faile merge
> perhaps you can look at the local sqlce database with the ce query
analyzer.[vbcol=seagreen]
> "Eli Tucker" <eli-msdn@.mailinator.com> wrote in message
> news:Oz2$3I$gEHA.3320@.TK2MSFTNGP11.phx.gbl...
> Files\ThinkShare\Fdm\FdmJournal_eli.sdf; -
integrity[vbcol=seagreen]
What's[vbcol=seagreen]
is
>