SQL Server Performance Forum – Threads Archive

Transactional Replication – Pull Subscription Prob

Good morning, I am almost through my first attempt at configuring transactional replication in sql server 2005. My publisher is in the Northeast, and my subscriber is in Atlanta. They are not in the same domain. I have a remote distributer. All are fully patched Win 2003 server. I am running my agents under a domain account that has sysadmin priviliges on all 3 boxes. The problem is that I can push subscriptions from distributor to subscriber, but cannot pull subscriptions from distributor to subscriber. I get an authentication failure. When I go to the publisher and launch the Replication Monitor, I see 5 subscriptions (3 push and 2 pull). The 3 publications involved in the push subscriptions show the subscription status in the All Subscriptions tab, and they are working. The two involved in pull subscriptions show nothing in the All Subscriptions tab. An attempt to insert a tracer token says it can’t do it till the publication has 1 or more subscriptions. Under the Replication node in Management Console, the 3 pushes show subscriptions under them, and the 2 pull do not. Obviously I have some sort of permissions foul up. Thanks for any advice. daustinash daustinash
[email protected]

what is the exact error your are getting.
check the replication history —————————————-

Date8/24/2006 7:44:19 PM
LogJob History (PULL-publishersql3-CPS-SystemTables-subscribersql3_CPS) Step ID1
Serversubscribersql3
Job NamePULL-publishersql3_CPS-SystemTables-subscribersql3_CPS
Step NameRun agent.
Duration13:26:28
Sql Severity0
Sql Message ID0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted0 Message
2006-08-25 13:10:42.907 Microsoft SQL Server Replication Agent: distrib
2006-08-25 13:10:42.907
2006-08-25 13:10:42.907 The timestamps prepended to the output lines are expressed in terms of UTC time.
2006-08-25 13:10:42.907 User-specified agent parameter values:
-Publisher publishersql3
-PublisherDB cps
-Publication SystemTables
-Distributor replication3
-SubscriptionType 1
-Subscriber subscribersql3
-SubscriberSecurityMode 1
-SubscriberDB cps
-Continuous
-XJOBID 0xF67C04CCB7487C4FBEEBD00739393FA9
-XJOBNAME PULL-publishersql3-cps-SystemTables-subscribersql3-cps
-XSTEPID 1
-XSUBSYSTEM Distribution
-XSERVER subscribersql3
-XCMDLINE 0
-XCancelEventHandle 0000039C
2006-08-25 13:10:42.907 Startup Delay: 4080 (msecs)
2006-08-25 13:10:47.000 Connecting to Subscriber ‘subscribersql3’
2006-08-25 13:10:47.141 Connecting to Distributor ‘replication3’
2006-08-25 13:10:47.141 Agent message code 20084. The process could not connect to Distributor ‘replication3’.
daustinash
[email protected]

<blockquote id="quote">quote:<hr height="1" noshade id="quote">Originally posted by daustinash Under the Replication node in Management Console, the 3 pushes show subscriptions under them, and the 2 pull do not. <hr height="1" noshade id="quote"></blockquote id="quote"> Execute sp_helpsubscription to list subscription information associated with a particular publication, article, Subscriber, or set of subscriptions. Execute sp_helppullsubscription to display information about one or more subscriptions at the Subscriber. Execute sp_helpsubscriberinfo to display information about the Subscriber. Another, Check for permissions and sql agent account runs at subscriber [<img src=’/community/emoticons/emotion-1.gif’ alt=’

‘ />] Distribution Agent for a Pull Subscription —————————————— The Windows account under which the agent runs is used when making connections to the Subscriber. This account must at minimum be a member of the db_owner fixed database role in the subscription database. The account used to connect to the Distributor must: - Be a member of the PAL. (Publication Access List) - Have read permissions on the snapshot share. ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/rpldata9/html/6d09fc8d-843a-4a7a-9812-f093d99d8192.htm Deepak Kumar MVP, MCDBA – SQL Server Disclaimer: This post is provided as is with no rights & warranty for accuracy, for the sake of knowledge sharing only.

Checking the permissions for the Service account is the first thing to check in this case, as it may fall over due to that issue. Satya SKJ
Microsoft SQL Server MVP
Contributing Editor & Forums Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing.

]]>