Merge Rpl. Pull from subscriber access denied problem

Hi,
I have set up one laptop as the Distributer/Publisher. Went through the
wizard and set up a Publication also, used Pubs. Then registered another
remote laptop that I can see via the network, and it can see me. I went
through the wizard again and set up a Push to that laptop. Said it ran good,
and I can see the tables on the remote laptop now.
I deleted the Push and keep trying to create a Pull at the other laptop,
(subscriber). The wizard sets it up, but when it Starts Syncronizing, it
immediately gets the big Red X.
The error said The schema script
'\\ACER\ReplShare\ReplData\unc\ACER_pubs_pubs_arti cles\20050928212317\stores_1.sch' could not be propagated to the subscriber.
I can see this share from both ends. I have read a ton about the accounts
the agent has to run under in the last 12 hours, but can't see what I am
doing wrong.
Is there a trick here?
Thanks.
Steve,
try logging on to the subscriber laptop using the same account that the sql
server agent uses as a service account. The see if you can browse to the
snapshot folder
\\ACER\ReplShare\ReplData\unc\ACER_pubs_pubs_artic les\20050928212317. If you
can, see if you can copy the contents of this directory locally. I'm
guessing that the first part won't be possible due to permission
restrictions, but please post back with your results.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul,
I had tried some other things prior to being able to read your response.
Here is what I have done that is now working.
I set up new SQL users on both Publisher/Dist. and Subscriber, giving them
the proper roles. I then set up a new Windows login on each box, "Bob", of
type admin. I then changed both the MSSQLSERVICE and SQLAGENTSERVICE on each
to run under "Bob". When it asks for logon credintials for the subscriber, I
use the sa, when it asks for the publisher, I use the new SQL user I had set
up. Probably may have been able to use that for the subscriber instead of
the sa, don't know.
I have tried so many things since yesterday afternoon, I am a little unsure
as to what actually solved it. From all I read over night, having the two
service run under "Bob" was needed.
Thank you for the response,
Steve
"Paul Ibison" wrote:

> Steve,
> try logging on to the subscriber laptop using the same account that the sql
> server agent uses as a service account. The see if you can browse to the
> snapshot folder
> \\ACER\ReplShare\ReplData\unc\ACER_pubs_pubs_artic les\20050928212317. If you
> can, see if you can copy the contents of this directory locally. I'm
> guessing that the first part won't be possible due to permission
> restrictions, but please post back with your results.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||This is OK - what you've set up is known as pass-through authentication.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Is there a better or more preferred method? We have one laptop that acts as
the publisher/distributor, and two other laptops that will be subscribers.
They run over a wireless network. The two subscribers will be able to
initial pull merge replications.
Thanks,
Steve
"Paul Ibison" wrote:

> This is OK - what you've set up is known as pass-through authentication.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||Steve,
are the laptops all on the same domain? If so, you could use a domain
account, which is given rights to the distributor's working folder. If not,
it's either pass-through, FTP, backup and restore or alternative snapshot
locations.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
sql

Merge replication not working (Push or Pull)

I'm trying to setup merge replication between two server (serverA and serverB). serverA houses the publisher DB (pubs) and Distribution DB (distribution), server B has the subscriber DB (subs). I tried first to setup a pull subscription, but the snapshot is never created in the subs db, even though the snapshot agent says everything was successful. The merge agent also never changes from the status 'Never Started'.
So I tried a push subscription. This gets me a little further, it creates the snapshot in the subs DB, but then the merge agent fails with the following error.
The subscription to publication 'pubs_customer_test' is invalid.
(Source: Merge Replication Provider (Agent); Error number: -2147201019)
------
The remote server is not defined as a subscription server.
(Source: BBLABCW03 (Data source); Error number: 14010)
------
Please help. Thanks.After creating a pull subscription to a transactional Publication, the status
of the pull subscription in the Database -> Pull Subscription Folder will
never change from the default of 'Never Started'
The job and the Pull Subscription Agent will show history for the agent, but
the status does not change in this view.
The problem is that the name of the job is greater than 100 characters, and is
trying to be placed into a temporary table that only allows 100 characters for
the job name.
SELECT job_id
FROM msdb.dbo.sysjobs
WHERE (name = N'SQL02-MyProj-DBReplication-SQL01-RptDB-D3E11F67-B38E-4DE4-82AE-9A3358B902AF')
-- Get job ID
-- Run below command with the job id as input
sp_MSenum_replication_job @.job_id = '388BFC85-BB28-434F-A7AE-77EEBB1A3C8B'
-- If you see this error, then you may need to reduce the -- job description name to resolve this issue
Server: Msg 8152, Level 16, State 6, Procedure sp_help_jobhistory, Line 91
String or binary data would be truncated.
NOTE: Then name of the job is a automatically concatenated by SQL of the
Publishing Server Name + Publishing Database + Publication Name + Subscribing Server + Subscribing Database.