Sometimes the replication agent folders get messed up and either to not show
"Kath" <Kat@community.nospam> wrote in message
news:6721DAD4-B8AD-48C1-B157-05CB0237A3AC@microsoft.com...
> Hi,
>
> Thanks for your reply. If I look at the jobs (Management/SQL Server
> Agent/Jobs) I can't see one that seems to match this merge agent. I know
> the
> subscription job appears in this folder on the subscriber, is this the job
> folder you meant?
>
> The replication jobs are:
> Reinitialise subscriptions having data validation failures (alert
> response)
> Distribution clean up
> Agent history clean up
> RNASERVER-GlimpsePub2-GlimpsePub2-12 (snapshot)
> Expired subscription clean up
>
> What do you mean by a phantom agent?
>
> It isn't created by an ActiveX control. I simply created the replication
> (publisher and subscriber) using the wizards in EM.
>
> Thanks,
> Kath
>
>
>
>
> "Hilary Cotter" wrote:
>
>> Something is wrong here. Perhaps the agent is a phantom agent or an agent
>> created by an ActiveX Control. Drill down in your jobs folder and see if
>> you
>> can identify the job there, You should be able to edit it here and make
>> the
>> necessary changes.
>>
>> --
>> Hilary Cotter
>> Looking for a SQL Server replication book?
>>
http://www.nwsu.com/0974973602.html >>
>> Looking for a FAQ on Indexing Services/SQL FTS
>>
http://www.indexserverfaq.com >>
>> "Kath" <Kat@community.nospam> wrote in message
>> news:A0A1FD8C-7357-40CB-8780-6AD740E329A3@microsoft.com...
>> > Hi,
>> > I am using SQL Server 2000 SP4, running merge replication with one
>> > subscriber. We were previously using transactional replication but
>> > encountered a number of problems with the queue reader, and we think
>> > merge
>> > replication may suit our situation better and be more reliable. When we
>> > had
>> > transactional rep, we had verbose logging on the q and log reader
>> > agents,
>> > and
>> > I would like to turn on this logging for the merge agent. Publication
>> > machine
>> > is also the distributor.
>> >
>> > When I try to open the merge agent properties (right click), EM says
>> > 'establishing connection to SQL Server' and then after a while fails
>> > with
>> > the
>> > msg 'a connection could not be established to <myRemoteSQLServer> ...
>> > SQL
>> > Server does not exist or access denied ...'
>> >
>> > I cannot connect to my remote SQLServer because it is a remote laptop
>> > (connected to internet via 3G/GPRS/wifi, and via VPN to my publication
>> > server), and is not on the same domain as my publication server.
>> >
>> > Why does SQL Server want to connect directly to my subscription laptop
>> > to
>> > view the properties of an agent that resides on the publication
>> > machine? I
>> > never had this with the q or log reader agents when using transactional
>> > rep.
>> > Is this just a unique 'feature' of the merge agent? How can I view/edit
>> > the
>> > agent properties to allow logging of errors (can I perhaps enable this
>> > through T-SQL?). I want to go to run agent step and set -Output
>> > C:\Temp\MERGEOUTPUT.txt -Outputverboselevel 2
>> >
>> > Thanks,
>> > Kath
>>
>>
>>