help with pull subscription

Jake,
check that the sql server agent's login (of the
subscriber) is in the PAL on the publisher.
HTH,
Paul Ibison (SQL Server MVP
[vbcol=seagreen]
Paul,
These instances are in different domains. Does that make a difference?
What is the PAL? The subscriber agent currently is the system account.
Thanks for the info so far.
Jake
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:0d6f01c4b529$c224ba50$a501280a@.phx.gbl...
> Jake,
> check that the sql server agent's login (of the
> subscriber) is in the PAL on the publisher.
> HTH,
> Paul Ibison (SQL Server MVP
>
|||Jake,
the PAL is the publication access list - have a look at the publisher's
properties to see a list of logins which are allowed to access the
publication.
If the domains are not trusted, then the setup will be slightly different -
have a look at : http://support.microsoft.com/?id=321822
HTH,
Paul Ibison (SQL Server MVP
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul,
Ok I have created a sql account called replicationserver. I have given
it dbo rights to the database on the publisher. The db is called tstReplic.
I have give replicationserver access on the PAL. I have created an alias on
the subscriber and login to EM using the replicationserver account which
works. When I try to do step 1 it wants to try and configure the subscriber
as a distributer. Do I proceed with this?
To pull the subscription, create an alias for the Publisher at the
Subscriber, and then follow these steps:
1. In SQL Enterprise Manager from the Publisher, on the Tools menu, point to
Replication, and then click Configure Publishing, Subscribers, and
Distribution.
Note Because the Subscriber is not configured for the distributor, the
Configure Publishing, Subscribers, and Distribution options are not
available for the Subscriber.
2. Click the Publishers tab.
3. Click the Publisher, and then click the Properties (...) button.
4. Click the General tab, click Using SQL server authentication of this
account to specify that the replication agents use SQL Server
Authentication, and then specify an account that has sufficient permissions
in the publishing database.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:ueYPNLUtEHA.272@.TK2MSFTNGP12.phx.gbl...
> Jake,
> the PAL is the publication access list - have a look at the publisher's
> properties to see a list of logins which are allowed to access the
> publication.
> If the domains are not trusted, then the setup will be slightly
> different -
> have a look at : http://support.microsoft.com/?id=321822
> HTH,
> Paul Ibison (SQL Server MVP
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
>
|||Jake,
Step 1 has nothing to do with setting up a subscription.
If you click on tools, replication, pull subscription...
For this to work, go to the publisher and right-click
replication monitor and select distributor properties. On
the subscribers tab, ensure that the subscriber is
enabled. Sometimes the Enterprise Manager doesn't update
correctly, if you are administering the publisher and
subscriber on the same Enterprise Manager (EM) . If this
is the case and you are trying to pull a subscription and
the publication doesn't appear, unregister the
publisher's sql server from EM and re-register it through
the pull subscription wizard.
HTH,
Paul Ibison (SQL Server MVP
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul,
Thanks for the help so far. I found that the subscriber was not
registered as a subscriber under the distributor properties. I enabled it as
a subscriber(Question about this. What happens if the subscriber is on a
dynamic ip outside the lan?) I then tried to register it and again the
publication didn't show up on the GUI. I am using EM on both machines. I
deleted the registration on the subscriber side. I then selected new server.
I used the replicationserver login and password and still I didn't see the
publication in the GUI. I do still see it if I put on anonymous
subscription. Thanks again for all your suggestions so far. Is there
anything else you can suggest? Will the Guide to SQL merge replication cover
this topic in detail? We are in the testing phase and if this works we need
to setup 5 merge replication using pull subscriptions.
Jake
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:10ff01c4b5b4$c00b6710$a501280a@.phx.gbl...
> Jake,
> Step 1 has nothing to do with setting up a subscription.
> If you click on tools, replication, pull subscription...
> For this to work, go to the publisher and right-click
> replication monitor and select distributor properties. On
> the subscribers tab, ensure that the subscriber is
> enabled. Sometimes the Enterprise Manager doesn't update
> correctly, if you are administering the publisher and
> subscriber on the same Enterprise Manager (EM) . If this
> is the case and you are trying to pull a subscription and
> the publication doesn't appear, unregister the
> publisher's sql server from EM and re-register it through
> the pull subscription wizard.
> HTH,
> Paul Ibison (SQL Server MVP
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Paul,
I got it kinda It seems now after your help with the subscriptions
not being registered on the distributor properties I have a permissions
issue. I gave the replicationserver user all rights and they are able to
connect. Now could you tell me which permissions that user actually needs so
I can lock it down? Thanks truly for all your help.
Jake
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:10ff01c4b5b4$c00b6710$a501280a@.phx.gbl...
> Jake,
> Step 1 has nothing to do with setting up a subscription.
> If you click on tools, replication, pull subscription...
> For this to work, go to the publisher and right-click
> replication monitor and select distributor properties. On
> the subscribers tab, ensure that the subscriber is
> enabled. Sometimes the Enterprise Manager doesn't update
> correctly, if you are administering the publisher and
> subscriber on the same Enterprise Manager (EM) . If this
> is the case and you are trying to pull a subscription and
> the publication doesn't appear, unregister the
> publisher's sql server from EM and re-register it through
> the pull subscription wizard.
> HTH,
> Paul Ibison (SQL Server MVP
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||OK - just to recap: the SQL Server login you want to use
is in the PAL of the publication (exactly same username
and password as on the subscriber), and the subscriber is
enabled on the publisher. For the latter, the agent is
configured to use SQL Server Authentication with
the 'replicationserver' account (elipsis button).
When you create the pull subscription, the account you
use must be sysadmin or db_owner on the subscriber and be
the same account as above in the PAL etc.
If all this is as above and you don't see the publication
then someting is strange. Try running sp_helppublication
in a QA window, logged into the subscriber's data and as
your 'replicationserver' account to see if any records
are returned.
Rgds,
Paul Ibison (SQL Server MVP)
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Jake,
db_owner on the subscriber and in the PAL on the
publisher should be enough for the pull subscription.
HTH,
Paul Ibison (SQL Server MVP)
[vbcol=seagreen]
|||Paul,
Ok I got it to view the publication in the GUI. Now when the job runs I
get the following errors. Any where you can point me to work on the
troubleshooting? In the future what happens if we need to add a column in a
replicated table? Since these databases are in remote locations and we do
not have a vpn should we enable the ftp option to allow for getting the
snapshot? Could you point me to some documentation on that? Thanks again for
the help.
Jake
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:055001c4b5ec$bf207060$a601280a@.phx.gbl...
> Jake,
> db_owner on the subscriber and in the PAL on the
> publisher should be enough for the pull subscription.
> HTH,
> Paul Ibison (SQL Server MVP)
>