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