Error Pull replication

I have two Win2000 that are in a domain. SQL1(SQL server) acts as the
distributor and publisher. SQL2(MSDE2000) acts as the subscriber. Push merge
replication is running well.
I want to PULL the db from SQL1 to the db on SQL2, failed :The process could
not connect to Distributor. Cannot generate SSPI context.
I changed Merge Agent location from Subsciber to Distributor, message :
Server 'SQLTEST1" is not prepared to run the offloaded agent
Error Unable to activate the agent on the specified remote server because of
security restrictions. Use dcomcnfg on the remote server to allow the local
SQL Server Agent account to activate the agent
1. Where the best location for the Merge Agent
2. What I have to do next
the SSPI error should be addressed first - consult these kb articles for
more info on it.
http://support.microsoft.com/search/...alse&x=11&y=14
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
"Thang Long" <ThangLong@.discussions.microsoft.com> wrote in message
news:CA8EB6A7-F554-4A18-B817-6CE8F3B9A2C6@.microsoft.com...
> I have two Win2000 that are in a domain. SQL1(SQL server) acts as the
> distributor and publisher. SQL2(MSDE2000) acts as the subscriber. Push
merge
> replication is running well.
> I want to PULL the db from SQL1 to the db on SQL2, failed :The process
could
> not connect to Distributor. Cannot generate SSPI context.
> I changed Merge Agent location from Subsciber to Distributor, message :
> Server 'SQLTEST1" is not prepared to run the offloaded agent
> Error Unable to activate the agent on the specified remote server because
of
> security restrictions. Use dcomcnfg on the remote server to allow the
local
> SQL Server Agent account to activate the agent
> 1. Where the best location for the Merge Agent
> 2. What I have to do next
>
|||Thank you for the reply. Now it is running well.
One more question. I want to use dinamic filter, different database name for
each subscriber:
... WHERE CityCode = DB_NAME()
but no record in the subscriber table. Plese advice.
"Hilary Cotter" wrote:

> the SSPI error should be addressed first - consult these kb articles for
> more info on it.
> http://support.microsoft.com/search/...alse&x=11&y=14
> --
> 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
> "Thang Long" <ThangLong@.discussions.microsoft.com> wrote in message
> news:CA8EB6A7-F554-4A18-B817-6CE8F3B9A2C6@.microsoft.com...
> merge
> could
> of
> local
>
>
|||I think that db_name will always resolve to msdb - as that is the database
that the job is run in. In this case I think you will need to change your
filtering criteria.
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
"Thang Long" <ThangLong@.discussions.microsoft.com> wrote in message
news:75905A3F-F21F-4131-9FDA-79D6628B79BB@.microsoft.com...
> Thank you for the reply. Now it is running well.
> One more question. I want to use dinamic filter, different database name
for[vbcol=seagreen]
> each subscriber:
> ... WHERE CityCode = DB_NAME()
> but no record in the subscriber table. Plese advice.
>
> "Hilary Cotter" wrote:
http://support.microsoft.com/search/...alse&x=11&y=14[vbcol=seagreen]
Push[vbcol=seagreen]
:[vbcol=seagreen]
because[vbcol=seagreen]
|||what should be the filter?
Please advise.
Thank you.
"Hilary Cotter" wrote:

> I think that db_name will always resolve to msdb - as that is the database
> that the job is run in. In this case I think you will need to change your
> filtering criteria.
> --
> 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
> "Thang Long" <ThangLong@.discussions.microsoft.com> wrote in message
> news:75905A3F-F21F-4131-9FDA-79D6628B79BB@.microsoft.com...
> for
> http://support.microsoft.com/search/...alse&x=11&y=14
> Push
> :
> because
>
>
|||I would like to use instance name as the filtering criteria, it is posible ?
Please advice.
Thank you.
"Hilary Cotter" wrote:

> I think that db_name will always resolve to msdb - as that is the database
> that the job is run in. In this case I think you will need to change your
> filtering criteria.
> --
> 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
> "Thang Long" <ThangLong@.discussions.microsoft.com> wrote in message
> news:75905A3F-F21F-4131-9FDA-79D6628B79BB@.microsoft.com...
> for
> http://support.microsoft.com/search/...alse&x=11&y=14
> Push
> :
> because
>
>

Error number: 2147200953 Article 'TGS_LOG' failed data valid

Hi,
the merge-agent of a mergereplication with a publisher and two subscribers
stops with the message:
Error number: 2147200953 Article 'TGS_LOG' failed data validation.
How can I solve the problem ?
Best regards
Axel Lanser
Did you run a validation? Typically you get this emessage when you run a
validation. You might want to reinitialize to get your data back in sync.
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
"ALN" <ALN@.discussions.microsoft.com> wrote in message
news:CA73A80F-AADD-4933-BE44-D4AD7B0CD1AD@.microsoft.com...
> Hi,
> the merge-agent of a mergereplication with a publisher and two subscribers
> stops with the message:
> Error number: 2147200953 Article 'TGS_LOG' failed data validation.
> How can I solve the problem ?
> Best regards
> Axel Lanser
|||Hi,
I don't run a validation. The validation starts automaticaly. It was the
first start of the merge process after generating the subscriber.
Is it possible to reinitialize only the tables wich produce the error ?
Best regards
Axel Lanser
"Hilary Cotter" wrote:

> Did you run a validation? Typically you get this emessage when you run a
> validation. You might want to reinitialize to get your data back in sync.
> --
> 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
> "ALN" <ALN@.discussions.microsoft.com> wrote in message
> news:CA73A80F-AADD-4933-BE44-D4AD7B0CD1AD@.microsoft.com...
>
>

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 8144 on Transaction Push Replication

Don,
have you changed the schema on the publisher and
subscriber - please can you check the table definitions.
Perhaps this was a nosync initialization and you created
the procedures by hand and they are now out of sync as
you've altered the columns on the publisher? Depending on
the problem it may be possible to run
sp_scriptpublicationcustomprocs to generate new
procedures and then recreate them on the subscriber if
this is the case. I'd only do this if the schemas are
identical.
HTH,
Paul Ibison
(The ONLY sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Paul,
Thank you so much. The developers were upgrading the publication and got the
error message that Dirc Khan-Evans just posted.
Trying to run ALTER TABLE ... get the error message:
Server: Msg 4929, Level 16, State 1, Line 1
Cannot alter the table 'blah' because it is being published for replication.
I had no choice but to delete the publication. I recreated it and pushed a
new subscription and it ran successfully. However, the schema changes did not
carry over to the subscriber. The subsriber table does not have the new
fields. That is why I am getting this error. Should I delete the table on
the subscriber and push a new subscription? Thanks.
Don
the "Paul Ibison" wrote:

> Don,
> have you changed the schema on the publisher and
> subscriber - please can you check the table definitions.
> Perhaps this was a nosync initialization and you created
> the procedures by hand and they are now out of sync as
> you've altered the columns on the publisher? Depending on
> the problem it may be possible to run
> sp_scriptpublicationcustomprocs to generate new
> procedures and then recreate them on the subscriber if
> this is the case. I'd only do this if the schemas are
> identical.
> HTH,
> Paul Ibison
> (The ONLY sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Don,
I'd reinitialize, but first double-check something in the
publication properties. On the article properties
elipsis, snapshot tab, for name conflicts check that it
says 'DROP the existing table'. When you subscribe, be
sure to leave the default which is to initialize. Then it
should all go fine.
HTH,
Paul Ibison
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

>
|||Paul,
Just to let you know how the story ended. I tried to reinitialize, but that
also did not work. I ended up droping the tables on the subscriber that had
schemas different from the publisher. I scripted the tables from the
publisher and recreated them on the subscriber. I then had to recreate the
publications and push the subscriptions. It now seems to be running fine.
Just one thought... the publisher is on SQL 2000 sp2 and the subsciber is on
2000 sp3. I don't know if this was a bug. Thanks for all your help.
Don Saluga
Vector Security Inc.
"Paul Ibison" wrote:

> Don,
> I'd reinitialize, but first double-check something in the
> publication properties. On the article properties
> elipsis, snapshot tab, for name conflicts check that it
> says 'DROP the existing table'. When you subscribe, be
> sure to leave the default which is to initialize. Then it
> should all go fine.
> HTH,
> Paul Ibison
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||Thanks for the update Don - it's always helpful.
Regards,
Paul
"Don" <Don@.discussions.microsoft.com> wrote in message
news:A1286950-DC8C-4DB3-97CC-1C6E06E90565@.microsoft.com...
> Paul,
> Just to let you know how the story ended. I tried to reinitialize, but
that
> also did not work. I ended up droping the tables on the subscriber that
had
> schemas different from the publisher. I scripted the tables from the
> publisher and recreated them on the subscriber. I then had to recreate
the
> publications and push the subscriptions. It now seems to be running fine.
> Just one thought... the publisher is on SQL 2000 sp2 and the subsciber is
on[vbcol=seagreen]
> 2000 sp3. I don't know if this was a bug. Thanks for all your help.
> Don Saluga
> Vector Security Inc.
> "Paul Ibison" wrote:

'Error Message

Hi All
I have the 3 servers, A, B & C. A is the publisher, B is the distributor and
C is the subscriber. I have enabled these servers with their roles. I created
a publication which i try to do a transactional replication and i get an
error like this:
'Error Message:
The process could not create file '\\B\SNAPSHOT\unc'.
Error Details:
The network path was not found.
(Source: (OS); Error number: 53)
I don't know what to do and i need some help. Thank you in advance.
Mitty,
can you log on to the publisher as the sql server agent's login and see if
you can browse to the distribution working folder (\\B\SNAPSHOT\). If you
can, see if you can create a file there. This'll test the existance of the
share, your rights to add a file and also see if there is enough space
there.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)