Post reply

process is running and is waiting for a response from one of backend connections

  • June 27, 2006 at 4:23 pm

    #191120

    People i problem never comes alone

    After i resolve my last post,now i'm getting :"process is running and is waiting for a response from one of backend connections" in distribution agent at my snapshot replication.

    I used google and i find that dba think that:

    "The backend connections message just means that the distribution agent has

    started a process and has not communicated back with the replication

    subsystem yet. Setting QueryTimeout to a larger value will prevent the agent

    from being marked suspect and eventually failing. This could be a normally

    message. "

    Is that true??

    It was the fist time I get this message!!

    My DB has around 400 MB.

    Thanks for any feedback

    Claudia

     

    Regards,

    Cláudia Rego

    www.footballbesttips.com

  • June 27, 2006 at 4:26 pm

    #646246

    http://www.replicationanswers.com is a good wesbsite from Paul Ibison.

    There are a lot of commonly observed error messages and a possible fix.

    ******************
    Dinakar Nethi
    Life is short. Enjoy it.
    ******************

  • June 27, 2006 at 8:54 pm

    #646268

    The error is common when your subscriber (for a PUSH subscription) or publisher (for a PULL subscription) is busy with processing long-runnning queries containing the articles that you are replicating.

    As you correctly stated, the common approach to resolve this issue is to increase the agent timeout. To do this, from replication monitor, select the publication, then right click on the problematic agent and select 'Agent Profile'. You have three options: (a) modify the '-LongTimeout' property of your existing profile; (b) select the profile 'LongTimeout' and make changes to the other properties as appropriate; or (c) create a new profile and change the properties as appropriate.

    Lastly, you might like to look at the reason for the timeouts from the perspective of the database, and try fixing this instead. One last thing to look at in future is the replication topology, and whether it meets the current (and future) needs of your growing business.

  • June 28, 2006 at 4:19 am

    #646323

    Hi

    I created a new profile where i define LoginTimeout = 150

    But it happens the same after that time..

    I wonder why this situation is happening, because its the 1st time..

    Thanks

    CLaudia

    Regards,

    Cláudia Rego

    www.footballbesttips.com

  • June 28, 2006 at 7:31 pm

    #646537

    My apologies, I meant a longer QueryTimeout period, say 90000!

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply