Re: SQL2000 - Merge Replication - Timeout error

Can you use the regular profile, a large timeout -3600 is probably
right, and then set packet size to the max (32767).

Run profiler on the subscriber to see what is going on? What is your
retention period? Is this the first time this subscriber has been
cleaned up?

In some cases like this out of frustration I have reinitialized the
subscription with upload to get through errors like this.
On Feb 1, 2:36 am, "Des Norton" <d...@xxxxxxxxxxxxxxxxx> wrote:
Hi NG

We have merge replication running successfully between 2 SQL2000 boxes via
VPN.  The agent profile is "Slow Link".  On Tuesday, the replication stopped
working.  Verbose logging indicated a timeout issue.  I created a new
profile with exactly the same parameters as the "Slow link" profile, and
upped the QueryTimeout from 300 seconds to 600 seconds.  Still the same
errors.

I have continually increased this timeout, and it is now at 3600 seconds (1
hour), and we still get the same errors.

Any help is greatly appreciated.
Des Norton

************************************************************************

[2/1/2008 4:00:13 AM]GENHS001.MFP_Collections: set nocount on declare
@dbname sysname select @dbname = db_name() declare @collation nvarchar(255)
select @collation = convert(nvarchar(255), databasepropertyex(@dbname,
N'COLLATION')) select collationproperty(@collation, N'CODEPAGE') as
'CodePage', collationproperty(@collation, N'LCID') as 'LCID',
collationproperty(@collation, N'COMPARISONSTYLE') as 'ComparisonStyle'
Connecting to Publisher 'GENHS001.MFP_Collections'

Server: GENHS001
DBMS: Microsoft SQL Server
Version: 08.00.0760
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288

[2/1/2008 4:00:13 AM]GENHS001.MFP_Collections: {call sp_MSgetversion }
Percent Complete: 3
Retrieving publication information
Percent Complete: 4
Retrieving subscription information
Percent Complete: 4
The merge process is cleaning up meta data in database 'MFP_Collections'.
Percent Complete: 0
The process is running and is waiting for a response from one of the backend
connections.
Percent Complete: 0
The process is running and is waiting for a response from one of the backend
connections.
Percent Complete: 0
The process is running and is waiting for a response from one of the backend
connections.
Percent Complete: 0
The process is running and is waiting for a response from one of the backend
connections.
Percent Complete: 0
The process is running and is waiting for a response from one of the backend
connections.
Percent Complete: 0
The process is running and is waiting for a response from one of the backend
connections.
The merge process could not perform retention-based meta data cleanup in
database 'MFP_Collections'.
Percent Complete: 0
The merge process could not perform retention-based meta data cleanup in
database 'MFP_Collections'.
Percent Complete: 0
Category:NULL
Source:  Merge Replication Provider
Number:  -2147199467
Message: The merge process could not perform retention-based meta data
cleanup in database 'MFP_Collections'.
Percent Complete: 0
Category:COMMAND
Source:  Failed Command
Number:  0
Message: {call sp_mergemetadataretentioncleanup(?, ?, ?)}
Percent Complete: 0
Category:SQLSERVER
Source:  GENHS001
Number:  0
Message: The merge process timed out while executing a query. Reconfigure
the QueryTimeout parameter and retry the operation.
Disconnecting from Subscriber 'MFPAS1'
Disconnecting from Publisher 'GENHS001'
Disconnecting from Publisher 'GENHS001'
Disconnecting from Distributor 'GENHS001'
Microsoft SQL Server Merge Agent 8.00.760
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent:
GENHS001-MFP_Collections-MFP_Collections-MFPAS1-MFP_Collections- 0

************************************************************************

.

Relevant Pages

  • Re: changing merge agent profile for HTTPS - mergeSubscriberType = anonymous
    ... Looking for a SQL Server replication book? ... Just to confirm, for dim old me, if I want to change the profile for one ... subscriber, I need to change it at the subscriber in my RMO code - ... get the agent at the publisher/distributer use a slower profile - I've ...
    (microsoft.public.sqlserver.replication)
  • Re: SqlExpress Merge Agent slow Profiles & one way Rep
    ... I have a publishing subscriber which publishes to SQLExpress. ... You are saying that if I set "slow profile" on the publisher SQLExpress will ... Surely the profiles exist where the Agent runs, which for a Merge agent is ...
    (microsoft.public.sqlserver.replication)
  • Re: Network traffic with transactional replication with immediate updates (SQL 2005)
    ... I do not need to wait until off-hours to run a trace on the subscriber. ... Specifies whether the agent attempts to poll replicated transactions ... profile for distributor agents has as profile parameters one called ... I cannot find a way to explain why Distributor Agents are to ...
    (microsoft.public.sqlserver.replication)
  • Re: changing merge agent profile for HTTPS - mergeSubscriberType = anonymous
    ... Just to confirm, for dim old me, if I want to change the profile for one ... subscriber, I need to change it at the subscriber in my RMO code - ... Looking for a SQL Server replication book? ... get the agent at the publisher/distributer use a slower profile - I've ...
    (microsoft.public.sqlserver.replication)