Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Ken Blum
Constraint Violating Yak Guru
383 Posts |
 Posted - 2009-02-10 : 06:16:18
|
| I have a pull merge subscription setup using Web synchronization. Recently 5 million+ rows were deleted on the subscriber, and the web synchronization is failing due to a timeout error. I set the timeout on the subscriber to 18,000 which should allow for 5 hours of transfer time, but the duration of the job is still 32 minutes. Here's the error in Job history...Message2009-02-10 06:47:11.312 Thread id 11088 will wait for 20 second(s) before retrying the query on Subscriber 'F8HVGH1'.2009-02-10 06:52:51.187 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.2009-02-10 06:52:51.343 No data needed to be merged.2009-02-10 06:52:51.343 The merge process was unable to create a new generation at the 'Subscriber'. Troubleshoot by restarting the synchronization with verbose history logging and specify an output file to which to write.2009-02-10 06:52:51.343 Category:NULLSource: Merge Replication ProviderNumber: -2147200994Message: The merge process was unable to create a new generation at the 'Subscriber'. Troubleshoot by restarting the synchronization with verbose history logging and specify an output file to which to write.Am I missing another timeout setting somewhere? |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2009-02-10 : 10:11:25
|
| http://social.msdn.microsoft.com/Forums/en-US/sqlreplication/thread/97d91ede-b092-4e42-88ce-331eaa67b2b1/ |
 |
|
|
|
|
|
synchronization timeout issue