Push works / Pull doesn't

When I set up a pull subscription through the wizard, I get the following error when I try to run the distribution agent:
-->
The subscription to publication '(null)' has expired and does not exist. The step failed.
<--
If I set up a push subscription, everything works fine. Any ideas what would cause this issue?
Thanks in advance!
Greg,
there was an issue with this in SQL 7.0:
http://www.kbalertz.com/Feedback_290054.aspx.
Hopefully this is relevant to your case (;-))
Regards,
Paul
|||Here's more info:
I'm using sql server 2000, sp3 on win2kadv server on both publisher and subscriber. It's a Transaction replication publication, no merge or updating back to the publisher. I set up a very simple database with one table that has a primary key and a varchar
(50) column, and 3 rows to isolate the problem. The snapshot runs quick, but the pull distribution agent keeps getting the before mentioned error. If I set up a push subscription, it works.
Any ideas?
|||Greg,
as far as I can tell, this error is raised from
sp_MShelp_distribution_agentid, which is undocumented. The error message
relates to the independant_agent setting when you created the publication.
Please could you run profiler on the subscriber while you try the pull
subscription to check if this is the case. If so please post up the
arguments sent to the procedure and your script which creates the
publication and I'll see if I can get any further.
Regards,
Paul Ibison
|||I figured it out! I set up aliases rather than using ip addresses and it is now working.
http://support.microsoft.com/?id=321822

Pull Subscription for transactional replication

I have setup a pull subscription on the subscriber for transactional replication. The distribution job continues to run, but doesn't do anything because it says: The initial snapshot for publication 'man4' is not yet available.

How can I tell if the snapshot is running, and can I see the snapshot where it was created?The snapshot is set up on the publisher and must be created before any subscriptions are set up.

Publisher, Distribution, Subscriber all on one SQL Server?

Should this work? In production we have one server acting as the
publisher/distributer, and then another as the subscriber.
In the test environment, I'd like to have all of this on the same
server. Will this work? I've run into what I hope is a minor gotcha
(running the drop replication scripts created by enterprise manager
doesn't work, exec sp_dropsubscription returns "The remote server is
not defined as a subscription server").
thanks for any hints.
Sylvia
Hey. I've the same setup at my company for testing. It works fine. I have 2
instances of SQL, one acting as a subscriber and the other acting as a
publisher/distributor for transactional and merge replication. I've 3
publications so far.
For your structure, how is it defined? On your publication, have you defined
the same server as a publisher as well as a subcriber?
|||I even do pull subscriptions using FTP on a single server.
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
"Sylvia" <sylvia@.vasilik.com> wrote in message
news:1130800544.680463.133070@.z14g2000cwz.googlegr oups.com...
> Should this work? In production we have one server acting as the
> publisher/distributer, and then another as the subscriber.
> In the test environment, I'd like to have all of this on the same
> server. Will this work? I've run into what I hope is a minor gotcha
> (running the drop replication scripts created by enterprise manager
> doesn't work, exec sp_dropsubscription returns "The remote server is
> not defined as a subscription server").
> thanks for any hints.
> Sylvia
>