Merge replication error

I have 7 databases in a replication to another server. All have the same settings, but are just different databases.
On 3 of the databases the replication has failed with the message:
"The process could not connect to Distributor 'SERVER'. SQL Server does not exis"
The other 4 databases, which use SERVER as their distributor (again, all settings are the same) are working just fine and replicating.
If I restart the agent on any of the three that are not working, they will eventually result in the above error message.
What do I do?
Thanks.
How do I
Looks like a networking issue; when the error occurs, please try pinging the
distributor from the subscriber, to test your network connectivity and name
resolution.
Regards,
Paul Ibison
|||Paul - Thanks for your response.
The connectivity is fine - which is proven by 4 databases on this same server replicating just fine to the same subscriber.
Another other ideas?
- David
"Paul Ibison" wrote:

> Looks like a networking issue; when the error occurs, please try pinging the
> distributor from the subscriber, to test your network connectivity and name
> resolution.
> Regards,
> Paul Ibison
>
>
|||but the network problem might exist only between this subscriber and
publisher.
I'd try to run a ping -t for a day and then look at the statistics to see if
a hicup occured.
You could run this keep alive script which will tell you exactly when you
get a failure.
save this as c:\keepalive.sql
WHILE 1<>2
BEGIN
SELECT GETDATE()
WAITFOR DELAY '00:00:01'
END
GO
Here is the batch file that I use to run this script:
osql -S hilary2kp -E -i c:\keepalive.sql -n
date /t
time /t
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"DBard" <DBard@.discussions.microsoft.com> wrote in message
news:D10215EC-A700-4E92-8142-D567F8C50E34@.microsoft.com...
> Paul - Thanks for your response.
> The connectivity is fine - which is proven by 4 databases on this same
server replicating just fine to the same subscriber.[vbcol=seagreen]
> Another other ideas?
> - David
> "Paul Ibison" wrote:
the[vbcol=seagreen]
name[vbcol=seagreen]

Merge replication conflicts on Identity Columns

Hi all,
I've set up a merge replication using sql server 2005.
All settings for "Copy Use Triggers" were set to false
All Identity ranges were set to be handled automatically.
There is a table - "Stock" - which has an ident field. An insert
trigger on this table inserts a new record into another table -
"barcodes" - which itself has its own ident field.
When a new "stock" record is inserted on the subscriber I get a merge
conflict which says:
"A row insert at 'xxx.YYYYYYYYY' could not be propagated to
'zzz.YYYYYYYYY'. This failure can be caused by a constraint violation.
Explicit value must be specified for identity column in table
'barcodes' either when IDENTITY_INSERT is set to ON or when a
replication user is inserting into a NOT FOR REPLICATION identity
column."
It suggested I use sp_adjustpublisheridentityrange, which I did on
both tables, but still the conflict won't resolve.
Any suggestions will be most gratefully received
Thanks
Ken
This should resolve itself the next time the merge agent runs. It is
possibly that you have entered so much data on the subscriber that you
identity range is completely out of whack.
Issue a dbcc checkident(''tablename') on your subscriber and note the value
for the current identity value and current column value. If the current
identity value is greater than your current column value set the current
identity value to be the current column value, i.e.
dbcc checkident(''tablename',reseed, 14)
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
<kengillett@.gmail.com> wrote in message
news:1184849805.324095.134260@.w3g2000hsg.googlegro ups.com...
> Hi all,
> I've set up a merge replication using sql server 2005.
> All settings for "Copy Use Triggers" were set to false
> All Identity ranges were set to be handled automatically.
> There is a table - "Stock" - which has an ident field. An insert
> trigger on this table inserts a new record into another table -
> "barcodes" - which itself has its own ident field.
> When a new "stock" record is inserted on the subscriber I get a merge
> conflict which says:
> "A row insert at 'xxx.YYYYYYYYY' could not be propagated to
> 'zzz.YYYYYYYYY'. This failure can be caused by a constraint violation.
> Explicit value must be specified for identity column in table
> 'barcodes' either when IDENTITY_INSERT is set to ON or when a
> replication user is inserting into a NOT FOR REPLICATION identity
> column."
> It suggested I use sp_adjustpublisheridentityrange, which I did on
> both tables, but still the conflict won't resolve.
> Any suggestions will be most gratefully received
> Thanks
> Ken
>