Hi everyone,
We are trying to implement merge replication using a central subscriber
model. When testing this out on 4 test machines, everything seemed fine.
Now, we are running a live test alongside our old system. So far we have the
central subscriber up and running and one publisher. The central subscriber
is using a one-way pull subscription to fetch the data from the publisher.
It pulls data once an hour.
The problem is that after a day or two, things stop working, and the merge
agent keeps failing and retrying to start the merge. The error from the
agent history is:
"Another merge agent for the subscription(s) is running."
Once I stop and start the sql agent service on the publisher, things work
fine for another day or two.
So my question is, why is this happening? I haven't been able to find
anything on the web about this particular error, other than to try using
this:
"select spid from sysprocesses where program_name = 'Your_Agent_Name'"
"Kill <spid>"
The problem with this solution is that I get no results from the select
statement, so there's no process to kill.
We are using MSDE 2000 Release A on Windows 2000 boxes. Any help would be
greatly appreciated.
Thanks,
-Brian
You get this when you are using WSM or the ActiveX controls to manage a pull
subscription and you also have a merge agent running. I have also seen it
when you script out publications and run them in a test environment and
don't change all the parameters.
You have to try to isolate this rouge agent.
"Brian Newtz" <anonymous@.discussions.microsoft.com> wrote in message
news:OP9lCvmEEHA.1128@.TK2MSFTNGP11.phx.gbl...
> Hi everyone,
> We are trying to implement merge replication using a central subscriber
> model. When testing this out on 4 test machines, everything seemed fine.
> Now, we are running a live test alongside our old system. So far we have
the
> central subscriber up and running and one publisher. The central
subscriber
> is using a one-way pull subscription to fetch the data from the publisher.
> It pulls data once an hour.
> The problem is that after a day or two, things stop working, and the merge
> agent keeps failing and retrying to start the merge. The error from the
> agent history is:
> "Another merge agent for the subscription(s) is running."
> Once I stop and start the sql agent service on the publisher, things work
> fine for another day or two.
> So my question is, why is this happening? I haven't been able to find
> anything on the web about this particular error, other than to try using
> this:
> "select spid from sysprocesses where program_name = 'Your_Agent_Name'"
> "Kill <spid>"
> The problem with this solution is that I get no results from the select
> statement, so there's no process to kill.
> We are using MSDE 2000 Release A on Windows 2000 boxes. Any help would be
> greatly appreciated.
> Thanks,
> -Brian
>
>
|||this message is raised after we check the sysprocesses table to see if any
SPID exists for the same application name as the merge agent.
You should try to detemine if the spids are being orphaned even after you
stop the agent, if so we need to determine the cause of that.
thanks
gopal
|||Hilary, Gopal,
I'm not using WSM or ActiveX controls for the pull subscription. What I did
was script out the replication and changed things as necessary in the
scripts to install it on the live servers.
Gopal - like I said, my problem is that when I try to get the spid of the
agent, there are no results returned... so I'm at a loss as to what to try.
Any other suggestions?
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:%23EG3DFnEEHA.3788@.TK2MSFTNGP10.phx.gbl...
> You get this when you are using WSM or the ActiveX controls to manage a
pull
> subscription and you also have a merge agent running. I have also seen it
> when you script out publications and run them in a test environment and
> don't change all the parameters.
> You have to try to isolate this rouge agent.
> "Brian Newtz" <anonymous@.discussions.microsoft.com> wrote in message
> news:OP9lCvmEEHA.1128@.TK2MSFTNGP11.phx.gbl...
> the
> subscriber
publisher.
merge
work
be
>
Thursday, March 8, 2012
Another merge agent for the subscription(s) is running
Labels:
agent,
central,
database,
implement,
machines,
merge,
microsoft,
mysql,
oracle,
replication,
running,
server,
sql,
subscribermodel,
subscription
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment