error message on publisher

SQL 2005 sp1 merge replication. 1 publisher/distributor. 20 SQL
Express(SP1) subscriptions.
Working OK since we set up about 7 weeks ago, today we recieved the
following error when attempting an update on the publisher. The table
is bidirectional, auto identity range mgmt, column level tracking.
Error Executing Database Query. [Macromedia][SQLServer JDBC
Driver][SQLServer]UPDATECOLVBM: The parameter 'colv' is not valid.
The error occurred on line 311.
Can anyone shed any light on this? Where to begin looking? Hopefully
there is a way to correct without losing data at the existing
subscriptions.
TIA,
John G.
Can you enable logging so we can determine which proc this is failing on?
Here is a kbarticle which describes how to do this.
http://support.microsoft.com/default.aspx/kb/312292
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
<jgmeinder@.gmail.com> wrote in message
news:1169493886.403936.320150@.38g2000cwa.googlegro ups.com...
> SQL 2005 sp1 merge replication. 1 publisher/distributor. 20 SQL
> Express(SP1) subscriptions.
> Working OK since we set up about 7 weeks ago, today we recieved the
> following error when attempting an update on the publisher. The table
> is bidirectional, auto identity range mgmt, column level tracking.
> Error Executing Database Query. [Macromedia][SQLServer JDBC
> Driver][SQLServer]UPDATECOLVBM: The parameter 'colv' is not valid.
> The error occurred on line 311.
> Can anyone shed any light on this? Where to begin looking? Hopefully
> there is a way to correct without losing data at the existing
> subscriptions.
> TIA,
> John G.
>
|||Sorry, I wasn't very clear, the error occurs when running a T-SQL
update statement on the publisher database, not when an agent is
running. I executed the SQL outside of our app and got the following
error from the merge upd trigger.
Msg 18750, Level 16, State 1, Procedure
MSmerge_upd_6F87E78AF9BA4EC881AD11085DED1A80, Line 100
UPDATECOLVBM: The parameter 'colv' is not valid.
Msg 3621, Level 16, State 1, Procedure
MSmerge_upd_6F87E78AF9BA4EC881AD11085DED1A80, Line 100
The statement has been terminated.
The SQL:
UPDATE tblAlaska_Facility_Manager SET [organization_establishment] =
'Absolute Fresh Seafoods Inc'
WHERE facilityID = 2732
In the app they updated more columns, but otherwise is exactly the
same.
I can see the line it is referring to in the trigger, but do not
understand the syntax.
Also, I have found rows that the update completes correctly, and some
that error with the same exact error. I am going to try see if there
is anything common between the rows that error and the rows that do
not.
Thanks,
jg
Hilary Cotter wrote:[vbcol=seagreen]
> Can you enable logging so we can determine which proc this is failing on?
> Here is a kbarticle which describes how to do this.
> http://support.microsoft.com/default.aspx/kb/312292
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> <jgmeinder@.gmail.com> wrote in message
> news:1169493886.403936.320150@.38g2000cwa.googlegro ups.com...
|||I could not discover any commonalities between the rows that returned
the error. So we did a simple update at a subscriber, and it worked,
while the same update at the publisher would error. We then did a
sync, and the rows at the publisher 'freed up', so that updates to the
rows work now.
We see this behavior once in a while, and until this time we would drop
the article and re-create it. But in this case our customers with
subscribers could not afford to lose any data that changed at any
subscription.
At least we have a work around, but I wouldn't mind getting an
understanding of what is causing this behavior.
Thanks,
jg

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)

Error Message

Hi,
I got this error from my SQL Server in merge replication:
- Number: -2147200999
- Message: The process could not enumerate changes at the 'Publisher'
I read on Internet that it is a bug. Could you help me to fix it?
Regards
90%+ of the time this error is cleared by simply rerunning the agent. Other
times it can be cleared by following this kb article
http://support.microsoft.com/default...&Product=sql2k
There is a bug associated with some events which generate an error similar
to this one. You will have to enable logging to determine if you are bumping
into this bug.
Follow the instructions in this kb article to enable logging:
http://support.microsoft.com/default...b;EN-US;312292
Then check to see if one of these bugs/problems apply
http://support.microsoft.com/default...&Product=sql2k
http://support.microsoft.com/default...&Product=sql2k
http://support.microsoft.com/default...&Product=sql2k
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Andrea Aiello" <Andrea Aiello@.discussions.microsoft.com> wrote in message
news:E3E782EF-BB4D-4FDF-A53C-E73A3AA8AC7E@.microsoft.com...
> Hi,
> I got this error from my SQL Server in merge replication:
> - Number: -2147200999
> - Message: The process could not enumerate changes at the 'Publisher'
> I read on Internet that it is a bug. Could you help me to fix it?
> Regards
>