dbTalk Databases Forums  

Timeout using merge replication (sp_MSuplineageversion does not respond)

microsoft.public.sqlserver.replication microsoft.public.sqlserver.replication


Discuss Timeout using merge replication (sp_MSuplineageversion does not respond) in the microsoft.public.sqlserver.replication forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Thomas
 
Posts: n/a

Default Timeout using merge replication (sp_MSuplineageversion does not respond) - 11-05-2009 , 06:19 PM






Hello,

I use merge replication for several projects. In general it runs fine, but
in one project the replication process generates a timeout since today. I
tried to stop und restart the synchronization process, but this didn't help.
There are no records with genstatus 0 in MSmerge_genhistory, so obviously
there's nothing to be replicated. Anyway the merge agent generates a timeout
while downloading changes to the subscriber. I also increased the timeout
value to 1200. The result was that while synchronizing the following message
appeared (translated from the german version): "The process waits for a
response of the query '{call sp_MSuplineageversion(?, ?, ?)}'.

Does anyone have any idea what to do? Thank you very much.

Kind regards

Thomas

Reply With Quote
  #2  
Old   
Paul Ibison
 
Posts: n/a

Default Re: Timeout using merge replication (sp_MSuplineageversion does not respond) - 11-08-2009 , 11:42 AM






You could check the service pack level of all the subscribers. Assuming this
is OK, then perhaps use DBCC INPUTBUFFER and sp_who2 on the subscriber to
see if you can check exactly what the problem is. Possibly it involves some
sort of blocking. Another option is to use profiler if the previous route
doesn't sole the issue. Sorry these are generalist approaches but I haven't
seen this error message before and can find no previous references.
HTH,
Paul Ibison

Reply With Quote
  #3  
Old   
Thomas
 
Posts: n/a

Default Re: Timeout using merge replication (sp_MSuplineageversion does not respond) - 11-08-2009 , 01:04 PM



Hi Paul

thank you for your response. This problem already occured two times within
one month. It's really annoying, because the only "solution" I figured out
so far is to delete the subscription and to set it up from scratch again.

Blocking is obviously involved in some way. When the problem occured one
table on the publisher side (only on this side) was blocked. After I had
stopped synchronisation the lock was released. After I had restarted
synchronisation the table was blocked again. I will try to identitfy the
problem in detail next time using the mentioned commands.

I checked the service pack level of the publisher and the subscriber and
noticed that on the subscriber side SQL Server 2008 SP1 has been installed
while on the publisher side only some SQL Server 2008 and some cumulative
updates have been installed. So the subscriber's service pack version is
higher. I know that problems can occur, if the subscriber's version is
higher, but I thought this only holds for a major version like 2008. Does it
also hold für service packs?

Kind regards
Thomas

"Paul Ibison" <Paul.Ibison (AT) ReplicationAnswers (DOT) Com.(donotspam)> schrieb im
Newsbeitrag news:EC71FD8B-2F2E-43E8-8BCF-44CC5FE370D7 (AT) microsoft (DOT) com...
Quote:
You could check the service pack level of all the subscribers. Assuming
this is OK, then perhaps use DBCC INPUTBUFFER and sp_who2 on the
subscriber to see if you can check exactly what the problem is. Possibly
it involves some sort of blocking. Another option is to use profiler if
the previous route doesn't sole the issue. Sorry these are generalist
approaches but I haven't seen this error message before and can find no
previous references.
HTH,
Paul Ibison

Reply With Quote
  #4  
Old   
Paul Ibison
 
Posts: n/a

Default Re: Timeout using merge replication (sp_MSuplineageversion does not respond) - 11-08-2009 , 01:16 PM



I don't think you'll get a definitive answer to this for a specific
technology combination as there are too many posibilities for the MS folks
to keep track of. If you ring PSS though they will expect the Pub/Dist =>
Sub in terms of service pack level as a matter of course. Worth doing it and
then posting back if the problem still exists....
Cheers,
Paul

Reply With Quote
  #5  
Old   
Thomas
 
Posts: n/a

Default Re: Timeout using merge replication (sp_MSuplineageversion does not respond) - 11-09-2009 , 03:45 AM



Thank you Paul for your very good support in this newsgroup here. I
installed the latest SP on the publisher and I will let you know, if the
problem occurs again. However it may take some weeks until the problem shows
up.

Kind regards
Thomas

"Paul Ibison" <Paul.Ibison (AT) ReplicationAnswers (DOT) Com.(donotspam)> schrieb im
Newsbeitrag news:u5O2IgKYKHA.1372 (AT) TK2MSFTNGP02 (DOT) phx.gbl...
Quote:
I don't think you'll get a definitive answer to this for a specific
technology combination as there are too many posibilities for the MS folks
to keep track of. If you ring PSS though they will expect the Pub/Dist =
Sub in terms of service pack level as a matter of course. Worth doing it
and then posting back if the problem still exists....
Cheers,
Paul

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.