Hi,
From the verbose mode 2, I got this output. This is the last part of
the log:
A snapshot of 1 article(s) was generated.
Disconnecting from Publisher '********'
Microsoft SQL Server Snapshot Agent 8.00.760
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: *************-Repl-5
Connecting to Distributor '*********'
Connecting to Publisher '*************'
But in the subscriber database, under subscriptions, I got a message
stating:
"SQL Server Agent could not access the replication agent. Use the
DCOMCNFG utility".
I have SP3a installed on both publisher and subscriber, hence it
should not be the bug because of it.
Upon refreshing the same, I got a message stating - "The step did not
generate any output. The step failed".
Any ideas or suggestions will be greatly appreciated!
Thanks,
PS.
[quoted text, click to view] "Hilary Cotter" <hilaryk@att.net> wrote in message news:<#0A$ylbUEHA.4064@TK2MSFTNGP11.phx.gbl>...
> you will get long job names when you are using a pull subscription, and
> short names when you are doing a push subscription.
>
> can you enable logging to see what it reports. Follow the steps in this kb
> article to enable logging.
>
>
http://support.microsoft.com/default.aspx?scid=kb;EN-US;312292 >
>
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
>
http://www.nwsu.com/0974973602.html >
>
> "ps" <ps_sr2001@yahoo.com> wrote in message
> news:1a7be36d.0406131046.2aa8d35e@posting.google.com...
> > Hi,
> > I was trying to pull a subscription to an MSDE machine(subscriber)
> > from a sql server 2000 machine acting as the publisher and
> > distributor. when I configure for the pull, it generates a snapshot
> > immediately which is successfully completed. But then, the pull
> > actually never happens and I get the message saying the pull
> > subscription has 'Never Started'. I found that, if the name of the job
> > exceeds 100 characters, then the problem arises, but my job name is
> > very small and hence, I dont think that is my problem. I tried to
> > manually start and reinitialize all the agents, but that does not
> > solve my problem.
> > Can someone suggest what else could be done?
> >
> > Thanks
