RE: error 29006 - Process could not deliver the snapshot to the su

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



I am showing the message and a few other things. I just didn't copy enough
of my code. Here are some excerpts from my trace. I couldn't find anything
that really stood out.


exec sp_MSadd_merge_anonymous_agent
N'0',N'stBasil',N'SchoolID1',N'',N'handheld','0036007B-0038-0031-4500-350041003000',0

....

exec sp_MSenumcolumns
'07AA7098-2F45-4ED2-A447-C8D675E2A857','713FDD5C-D910-400C-8568-AA32E5E30CCB'

exec sp_MSenumschemachange '07AA7098-2F45-4ED2-A447-C8D675E2A857',0,8000500,0

exec sp_MSadd_merge_history 24,3,N'Applying the snapshot to the
Subscriber',0,0,0,0,0,0,0,0,0,0x00,1,0x01,0x01

exec sp_MSenumschemachange '07AA7098-2F45-4ED2-A447-C8D675E2A857',0,8000500,0

exec sp_MSadd_merge_history 24,2,N'The process could not deliver the
snapshot to the Subscriber.',0,0,0,0,0,0,0,0,0,0x01,1,0x01,0x00

exec sp_MSadd_repl_error 14,0,8,N'Merge Replication
Provider','-2147201001',N'The process could not deliver the snapshot to the
Subscriber.'

Thanks, Scott

"gopal" wrote:


The error handling code only seems to capturing the native error, make sure
you capture the message also. You can check CE BOL for the complete error
handling code

Also what you can do to determine if this is a server or a client side issue
is to run a trace on the server and see if it is doing any work like calling
the proc sp_msinitdynamicsubscriber etc...the server side of the work is
complete as soon as the message file is populated. if that completes fine
then its possibly an issue on the client side

"Scott S." wrote:

I've got the following code that is returning nothing of value:

foreach(System.Data.SqlServerCe.SqlCeError r in
((System.Data.SqlServerCe.SqlCeException)e).Errors)
{
MessageBox.Show(r.NativeError.ToString() + " " + r.Message);
MessageBox.Show("source: " + r.Source);


foreach (string s in r.ErrorParameters)
MessageBox.Show("error param " + s);

}

We turned on the replication logging on IIS and get basically the same
information.

The replication monitor had no merge agents listed and had no other info.

Thanks, Scott


"gopal" wrote:

There should be more detailed information in the error message. The issue
could be on the client side too, make sure the app code loops through the
error collections and returns all the error.

Also look at the error details on the replication monitor...

"Scott S." wrote:

I'm migrating from sql server 2000 and iis on one machine to sql server 2005
on one machine and iis on another. My clients are sql ce 2.0 and I'm getting
the error message "Process could not deliver the snapshot to the subscriber"
when I try to sync. I've checked the permissions multiple times and have
reinstalled sql ce merge replication a couple of times. If anyone has any
ideas it would be much appreciated. Thanks, Scott
.



Relevant Pages

  • Re: How can implement these simple scenario
    ... > Client X wants specific data be download to use/modify offline. ... > changes will then be merged back with the server. ... transactional replication or merge. ... > How do I poll the merge agent on the client to know how many transaction ...
    (microsoft.public.sqlserver.replication)
  • Re: Replication/Sychronization of Disconnected laptops
    ... >>>all Windows servers, as well as being available on WinXP ... >never hand off the task to a client. ... >A dialup account enables indirect replication, ...
    (microsoft.public.access.replication)
  • Re: Intermittant 3167 error/indexing problem
    ... I have a client with a replicated back-end database ... who sporadically suffers from data corruption. ... replication fields) before converting the new back end into a ...
    (microsoft.public.access.replication)
  • Re: Problem with merge replication
    ... subscriber changes before the new snapshot comes down. ... Looking for a SQL Server replication book? ... I use merge replication with windows CE clients and SQL Server 2005. ... If someone collects data in an existing table on the client (the ...
    (microsoft.public.sqlserver.replication)
  • RE: server/connectcomputer from remote offices
    ... I have a replica w2k3 std server config'd as a dc in location B ... I have a number of client workstations in Location B ... We can connect the workstations in Location B to the sbs domain with no ... I have enabled replication of the clients share ...
    (microsoft.public.windows.server.sbs)