Maybe someone can give me a hint on this.

--

Right-clicking on the distribution agent offers an option, "run agent
on subscriber". I want to try that.

Box comes up that says "Subscriber must be prepared ..." and with a
button that says it will verify subscriber. I click that and get an
error message:

Server 'SQLTEST1" is not prepared to run the offloaded agent.
Error 1040: The agent failed to connect to the Distributor due to the
following error. 'Login failed for user '(null)'. Reason: Not
associated with a trusted SQL Server connection.

--

Oh, yeah?

In BOL, there's a section on Remote Agent Activation that suggests you
have to go to the subscriber (SQLTEST1) and run DCOMCNFG.exe, only the
instructions don't reflect the DCOMCNFG.exe that exists on Windows
Server 2003.

Anybody have any hints for me what the problem is here?

"user '(null)'"????

SQLAgent is running happily on SQLTEST1 and SQLTEST2 (publisher and
current distributor), using a domain account, and SQLTEST2 is pushing
a transactional replication happily to SQLTEST1, but I want to move
the distributor!

Thanx.

Josh

drill down in component services, computers, my computer, Dcom Config,
locate Microsoft SQL Server Replication Distribution Agent 8.0, right click
on it, select properties, select launch and Activation Permissions, and then
add the account the SQL Server agent runs under on the publisher. Make sure
this account is part of your local administrator group on your publisher.

I think you would be best to use a pull agent running off your subscriber.

--
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html

"jxstern" <jxstern (AT) nowhere (DOT) com> wrote

Usually this eror is returned when you try to use sql server security
(logins) and the server you're connecting to isn't set to allow mixed
authentication. I'm not too sure how this applies in your situation, but
please can you check to see if this is relevant - eg is the distribution
agent set to use sql logins?
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

On Tue, 23 Nov 2004 20:08:47 -0000, "Paul Ibison"
<Paul.Ibison (AT) Pygmalion (DOT) Com> wrote:
AFAIK, they are using domain win logins.

J.

On Tue, 23 Nov 2004 15:06:52 -0500, "Hilary Cotter"
<hilary.cotter (AT) gmail (DOT) com> wrote:

I did the launch, not the activation. Let me try ... dang, I'll have
to wait a while, I'll let you know later.

With a pull subscription, the distributor is still on the publisher,
right? That is, the distribution DATABASE is still on the publisher.
I presume (?) that the distribution database moves to the subscriber,
if you "move the distributor"?!?

As usual, thanks.

J.

By default the distributor will be on the server which you created it on,
likely the publisher. You could park it on the subscriber, or another
seperate server.

If you are using a pull subscription you will have to enable the subscriber
for replication which will involve creating a distribution database on your
subscriber. Your publisher by default will use the distribution database it
is configured for - likely the one on the publisher.

Your pull agent on your subscriber will use its distribution database to
record historical information.

So to reiterate, by default the publisher will use the distribution database
on the publisher. The pull agent on the subscriber will connect to the
publisher's distribution database to get the transactions and apply them on
the subscriber, and will record the historical information on the pull agent
in the subscriber's distribution database.

However you can configure your publisher to use any distribution database:
on the publisher, subscriber, or a seperate server altogether.

I hope I have made this clear to you, if not please post back and Paul or
myself (or someone else) will take another stab at explaining it.
--
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html

"jxstern" <jxstern (AT) nowhere (DOT) com> wrote