error message initializing merge replication

i've got the following error message, can anybody help me
The merge process could not initialize the subscription.
(Source: Merge Replication Provider (Agent); Error number: -2147201011)
------
Ongeldige cursorstatus
(Source: MWO-SERVER (Data source); Error number: 0)
------
Bruno
@.Assist
Bruno,
can you try increasing the -QueryTimeOut parameter, and also enable logging
to see if we can get a bit more info.
http://support.microsoft.com/?id=312292
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com/default.asp
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||i'v done that, output is about the same. Has it to do with the snapshot ?
The replication is over the internet and has run for serveral week. I had to
change the design of some tables, so i broke the replication, made the change
but when i tried to recreate the the push subscription i get these error.
this is the last part of the log file
[17-4-2005 21:01:20]MWO-SERVER.assist-b2b: {call sp_MSgetversion }
Percent Complete: 2
Connecting to Subscriber 'MWO-SERVER'
Percent Complete: 3
Retrieving publication information
Percent Complete: 4
Retrieving subscription information
Percent Complete: 0
Applying the snapshot to the Subscriber
The merge process could not initialize the subscription.
Percent Complete: 0
The merge process could not initialize the subscription.
Percent Complete: 0
Category:NULL
Source: Merge Replication Provider
Number: -2147201011
Message: The merge process could not initialize the subscription.
Percent Complete: 0
Category:SQLSERVER
Source: MWO-SERVER
Number: 0
Message: Ongeldige cursorstatus
Disconnecting from Subscriber 'MWO-SERVER'
Disconnecting from Publisher 'ANNA'
Disconnecting from Publisher 'ANNA'
Disconnecting from Distributor 'ANNA'
Rgds,
Bruno
"Paul Ibison" schreef:

> Bruno,
> can you try increasing the -QueryTimeOut parameter, and also enable logging
> to see if we can get a bit more info.
> http://support.microsoft.com/?id=312292
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com/default.asp
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||I'd check to see that there isn't something more fundamental wrong here. Can
you create a new merge publication of a test table with a couple of rows in
it and see if this'll initialize. Also, please can you confirm your service
pack / patch level.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com/default.asp
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||microsoft windows 2003
sql server developer edition
version 8.00.760 (sp3)
When i create an new push subscription to another internal sql server, it's
works fine.
"Paul Ibison" schreef:

> I'd check to see that there isn't something more fundamental wrong here. Can
> you create a new merge publication of a test table with a couple of rows in
> it and see if this'll initialize. Also, please can you confirm your service
> pack / patch level.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com/default.asp
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
>
|||Mmmm. Not too sure here. If you have increased -QueryTimeOut then one other
idea I had was blocking. Can you drop all connections to the subscriber
database before initializing to see if this is the issue.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com/default.asp
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||i've created a new database and that also won't work. But the is working the
other way around. i enabled the subscriber as the publisher/distributor and
the original distributor as subscriber and that worked. It's not ideal but
for now its working. I think that some old configuration is still left in the
master database. Can't that be the problem ?
"Paul Ibison" schreef:

> Mmmm. Not too sure here. If you have increased -QueryTimeOut then one other
> idea I had was blocking. Can you drop all connections to the subscriber
> database before initializing to see if this is the issue.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com/default.asp
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
>
>
|||I think it might be some incompatibility between builds, which is one thing
I forgot to ask about, but anyway, I'm glad you have things up and going.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com/default.asp
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)