Re: Distribution Agent not Visible

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Hi Hilary,

Thank you for the response.

I have not done any scripting as you described. I had only done what was
listed in my initial posting.

I have since deleted the one publication and have disabled publishing and
distribution on that server.

Starting from scratch, I have again set up publishing and distribution on
that server. Looking in the "Distribution Agents" directory it says "There
are no items to show in this view." I have recreated the publication. In
an attempt to push the publication to the desired subscriber, at the end of
setting up the "push", I receive this message:

"Subscriptions were created successfully at the following Subscribers:
<subscriber_server_name>
The subscription at Subscriber '<subscriber_server_name>' cannot be
initialized immediately because the snapshot for this publication is not yet
available. To initialize the subscription, start the Distribution Agent
after the snapshot is available."

I had specified for the snapshot to be generated immediately, but apparently
it did not happen. The snapshot shows as "Never started". Right-clicking
on it and selecting "Start Agent" appears to do absolutely nothing.

I do see the distribution agent now. But I don't think it is useful without
any snapshot.

I would appreciate more guidance from anyone!

Thanks,
Jim







"Hilary Cotter" <hilary.cotter@xxxxxxxxx> wrote in message
news:uPlK2pCrGHA.4240@xxxxxxxxxxxxxxxxxxxxxxx
If you have a publication on a database, and you script it out, modify the
publication database name in the script and run the script in a different
database you can cause these agents to disappear. You need to remove the
references to the distribution, log reader and snapshot agents within the
script.

Check to see if they are in the jobs folder. The quick way to fix this is
drop the other publication, and recreate it manually.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.

This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.

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



"Jim" <please.reply@group> wrote in message
news:uJHN7OCrGHA.4508@xxxxxxxxxxxxxxxxxxxxxxx
Server 1--Publisher/Distributor:
Both Windows Server 2003 SP1
Both SQL Server 2000 SP4
Used "Configure Publishing and Distribution Wizard".
Used "Create Publication Wizard".
Used ToolsàReplicationàPush Subscription to Others.


Server 2--Subscriber:
Both Windows Server 2003 SP1
Both SQL Server 2000 SP4

On Server 1, in EM, I see the publication in the "Publications" sub
directory of the database. I also see the database named "distribution".
The "Replication" and "Replication Monitor" directories (and their
subdirectories) are present.

At the end of running "Push Subscription to Others.", I received the
notice:
"The subscription at Subscriber '<subscriber_name>' cannot be initialized
immediately because the snapshot for this publication is not yet
available. To initialize the subscription, start the Distribution
Agent after the snapshot is available."Looking on the
Distributor/Publisher under "Replication Monitor-->Agents-->Distribution
Agents", there are no agents. It reads "There are no items to show in
this view."Why don't I see a Distribution Agent, as is displayed in some
helpful tutorials on the web?Thanks!Jim





.



Relevant Pages

  • Re: Subscription Impact on Production Server
    ... The replication distributor was setup on the 2005 server. ... the way I am configuring distribution and publication. ... setup the server's distribution and publication incorrectly. ...
    (microsoft.public.sqlserver.replication)
  • Distribution Agent not Visible
    ... Both Windows Server 2003 SP1 ... Used "Configure Publishing and Distribution Wizard". ... Used "Create Publication Wizard". ... At the end of running "Push Subscription to Others.", ...
    (microsoft.public.sqlserver.replication)
  • Re: replication monitor
    ... publication and distribution which is why i was thinking it was related to ... > BTW - did you script out your publications and then re-rerun them. ... >>> I have the below and tried registring the distribution server. ...
    (microsoft.public.sqlserver.replication)
  • Re: replication monitor
    ... The distribution and log agents seem to be down because they couldn't connect ... > I have the below and tried registring the distribution server. ... > nothing appears under the server when expanding the monitor. ...
    (microsoft.public.sqlserver.replication)
  • RE: Synchronisation failing on SQL CE Database
    ... There is also an error on the publication in the Replication monitor. ... Server SERVER, Level 0, State 1, Procedure sp_MSprepare_mergearticle, Line 78 ... I am having a problem setting up merge replication between SQL 2005 and SQL ...
    (microsoft.public.sqlserver.replication)