"Chandy" <chandy@totalise.co.uk> wrote in message
news:5af0375a.0403310121.81202ff@posting.google.com...
> Hi Hilary,
>
> They exist in the Publisher db, they just start throwing exceptions
> when profiler is active.
>
> Chandy
>
> "Hilary Cotter" <hilaryk@att.net> wrote in message
news:<uuIKbNoFEHA.1396@TK2MSFTNGP11.phx.gbl>...
> > do these procedures exist on the SQL CE database?
> >
> > Can you check the conflicts table for errors about missing replication
> > procs?
> >
> > "Chandy" <chandy@totalise.co.uk> wrote in message
> > news:5af0375a.0403300834.4f2fdc6e@posting.google.com...
> > > We have the following scanario.
> > >
> > > Publisher is SQL 2k SP2, Subscribers are SQL CE 1.1, using merge
> > > replication.
> > >
> > > Everything is fine, until we start SQL Profiler on the Publisher
> > > Database. If the Profiler is running then replication takes 2-3
> > > attempts, failing between times with server errors. SQL records the
> > > following in the log:
> > >
> > > SqlDumpExceptionHandler: Process 64 generated fatal exception c0000005
> > > EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process..
> > >
> > > and points to:
> > >
> > > sp_upd_F280ADE09C6947139B37078469804F9B
> > >
> > > (or similar depending on the subscriber who initialised the merge at
> > > the time)
> > >
> > > Server is a dual-processor PIII 500 with 4GB RAM and plenty of disk.
> > >
> > > Subscribers are iPAQs.
> > >
> > > Any ideas???
> > >
> > > Chandy