SQL Cluster passive node suddenly won't run replication jobs

  • I have been running a SQL Cluster and I have failed over plenty of times. Today when I did so the passive node started yelling about proxy users not being able to authenticate ( I use domain accounts to run the replication agents).

    Not sure why this is happening, anyone have a clue. I would say roughly 50% of the replication jobs in replication monitor fail when I fail over.

  • Can you log onto the server/ remote it using one of the domain accounts that are failing? (when failed over)

    If that works then maybe the password(s) on the proxy user/credentials is out of date?

    also there were some interesting points in here [/url]

    Oraculum

  • We believe that the sheer volume of jobs reconnecting flooded the AD server requests and timed out the jobs.

    Starting the agents manually solved it. Like I said, this server is overloaded with replication agent jobs.

Viewing 3 posts - 1 through 2 (of 2 total)

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