|
|
|
date: Thu, 3 Jul 2008 18:54:58 +0200,
group: microsoft.public.sqlserver.replication
back
Time out error synchronizing in one merge push subscriber
Hello!!
I've a Merge Replication with SQL Server 2005. I've one publisher and 12
subscribers, using push subscriptions. All the subscribers are sync fine,
except the last one that I subscribe. This one had no error while applying
the snapshot, but I'm not 100% that first syncs where fine. Some days ago I
saw an error and I set the agent to verbose logging, that I send as an
atachment.
Since it starts synchronizing, it takes near half an hour to give the
error...
Here's the error:
2008-06-30 14:34:06.060 The process is waiting for a response from the query
'{call sys.sp_MSmakegeneration (?)}'
2008-06-30 14:34:06.107 OLE DB Distributor 'PUBLISHER\INSTANCE_NAME': {call
sys.sp_MSadd_merge_history90
(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2008-06-30 14:34:06.185 Percent Complete: 0
2008-06-30 14:34:06.217 The merge process failed to execute a query because
the query timed out. If this failure continues, increase the query timeout
for the process. When troubleshooting, restart the synchronization with
verbose history logging and specify an output file to which to write.
And I've seen that Agent's version is different than Publisher version
(that's also the distributor). Could it be possible? Although I don't think
that this can cause the error.
2008-06-30 14:23:01.140 Microsoft SQL Server Merge Agent 9.00.3042.00
2008-06-30 14:23:02.452 OLE DB Distributor: PUBLISHER\INSTANCE_NAME
DBMS: Microsoft SQL Server
Version: 09.00.3159
This subscriber it's not in a production environtment yet (it should be in 5
days), so if I need to, I've no problem applying the snapshot again or test
whatever I should in the subscriber...
Regards and thank you in advance for any kind of help!!
Josep.
date: Thu, 3 Jul 2008 18:54:58 +0200
author: Josep
Re: Time out error synchronizing in one merge push subscriber
Look for users processes which might be causing this sync to hang.
Also set querytimeout to some thing large, the default IIRC is 60 s.
"Josep" wrote in message
news:evFLH2S3IHA.4584@TK2MSFTNGP02.phx.gbl...
> Hello!!
>
> I've a Merge Replication with SQL Server 2005. I've one publisher and 12
> subscribers, using push subscriptions. All the subscribers are sync fine,
> except the last one that I subscribe. This one had no error while applying
> the snapshot, but I'm not 100% that first syncs where fine. Some days ago
> I saw an error and I set the agent to verbose logging, that I send as an
> atachment.
> Since it starts synchronizing, it takes near half an hour to give the
> error...
>
> Here's the error:
>
> 2008-06-30 14:34:06.060 The process is waiting for a response from the
> query '{call sys.sp_MSmakegeneration (?)}'
> 2008-06-30 14:34:06.107 OLE DB Distributor 'PUBLISHER\INSTANCE_NAME':
> {call sys.sp_MSadd_merge_history90
> (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
> 2008-06-30 14:34:06.185 Percent Complete: 0
> 2008-06-30 14:34:06.217 The merge process failed to execute a query
> because the query timed out. If this failure continues, increase the query
> timeout for the process. When troubleshooting, restart the synchronization
> with verbose history logging and specify an output file to which to write.
>
>
>
> And I've seen that Agent's version is different than Publisher version
> (that's also the distributor). Could it be possible? Although I don't
> think that this can cause the error.
>
> 2008-06-30 14:23:01.140 Microsoft SQL Server Merge Agent 9.00.3042.00
>
> 2008-06-30 14:23:02.452 OLE DB Distributor: PUBLISHER\INSTANCE_NAME
> DBMS: Microsoft SQL Server
> Version: 09.00.3159
>
>
> This subscriber it's not in a production environtment yet (it should be in
> 5 days), so if I need to, I've no problem applying the snapshot again or
> test whatever I should in the subscriber...
>
>
> Regards and thank you in advance for any kind of help!!
>
> Josep.
>
>
date: Thu, 3 Jul 2008 13:39:16 -0400
author: Hilary Cotter
Re: Time out error synchronizing in one merge push subscriber
Thank you,
I tried it, changing the value from 300 to 600. But the result was that the
time before getting the error was doubled, from 30 min. to an hour. And
there was no processes that could cause a block.
Somedays after posting here I got some synchronizations fine (3 or 4) but
then I continued failing. So the value I change could had something to do...
Last week I was in my customer's headquarter and I work more on it and I
realised that during the synchronization one of the 4 CPU (the server is a
Quad) was always on 80 - 90% of usage. Then back I saw that on July 15th
appeared the Cumulative Update 8 for SQL Server 2005 SP2 that was solving a
hang like mine that's because of an infinite loop in sp_MSmakegeneration:
FIX: The synchronization operation of a merge replication times out
in Microsoft SQL Server 2005
Bug number: 50002786
I installed it and it sync all the stuff pending perfectly and it seems to
work perfect now :-)
I hope that information could be usefull so someone else...
Thanks and regards,
Josep
"Hilary Cotter" escribió en el mensaje
news:3ABB272B-4FD6-406E-9858-32CE3E7CADD8@microsoft.com...
> Look for users processes which might be causing this sync to hang.
>
> Also set querytimeout to some thing large, the default IIRC is 60 s.
>
> "Josep" wrote in message
> news:evFLH2S3IHA.4584@TK2MSFTNGP02.phx.gbl...
>> Hello!!
>>
>> I've a Merge Replication with SQL Server 2005. I've one publisher and 12
>> subscribers, using push subscriptions. All the subscribers are sync fine,
>> except the last one that I subscribe. This one had no error while
>> applying the snapshot, but I'm not 100% that first syncs where fine. Some
>> days ago I saw an error and I set the agent to verbose logging, that I
>> send as an atachment.
>> Since it starts synchronizing, it takes near half an hour to give the
>> error...
>>
>> Here's the error:
>>
>> 2008-06-30 14:34:06.060 The process is waiting for a response from the
>> query '{call sys.sp_MSmakegeneration (?)}'
>> 2008-06-30 14:34:06.107 OLE DB Distributor 'PUBLISHER\INSTANCE_NAME':
>> {call sys.sp_MSadd_merge_history90
>> (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
>> 2008-06-30 14:34:06.185 Percent Complete: 0
>> 2008-06-30 14:34:06.217 The merge process failed to execute a query
>> because the query timed out. If this failure continues, increase the
>> query timeout for the process. When troubleshooting, restart the
>> synchronization with verbose history logging and specify an output file
>> to which to write.
>>
>>
>>
>> And I've seen that Agent's version is different than Publisher version
>> (that's also the distributor). Could it be possible? Although I don't
>> think that this can cause the error.
>>
>> 2008-06-30 14:23:01.140 Microsoft SQL Server Merge Agent 9.00.3042.00
>>
>> 2008-06-30 14:23:02.452 OLE DB Distributor: PUBLISHER\INSTANCE_NAME
>> DBMS: Microsoft SQL Server
>> Version: 09.00.3159
>>
>>
>> This subscriber it's not in a production environtment yet (it should be
>> in 5 days), so if I need to, I've no problem applying the snapshot again
>> or test whatever I should in the subscriber...
>>
>>
>> Regards and thank you in advance for any kind of help!!
>>
>> Josep.
>>
>>
>
date: Wed, 23 Jul 2008 13:24:53 +0200
author: Josep
|
|
