Cannot start Log Reader Agent and Snapshot Agent

I am testing peer to peer replication in our environment. I simulated a three node peer to peer topology and a local distributor.

For some wierd reason I cannot get the Log Reader Agent and snapshot agent to start. The domain account under which SQL Server Agent runs has administrator previlage on the box. I also use a domain account for SQL Server Service. (none of the passwords changed).

This is the error I am getting - "Executed as user: abc. A required privilege is not held by the client. The step failed"

Any ideas?

Also this domain account is a member of

SQLServer2005MSSQLUsers$ServerName$MSSQLSERVER

SQLServer2005MSAgentUser$ServerName$MSSQLSERVER

open the properties of each job and change the owner to sa and it should work fine.|||I tried it. No luck...it gives the same error message

cannot set name conflicts

For a snapshot replication.
I set the Name conflicts from the defualt-DROP the existing tables and
re-create it
to Delete All data in the existing table.
and set check in Include declared refertial integrity in Copy objects to
destination secton.
After I close these perperties window and reopen the publiction property
window to check the property on snapshop tab on article properties. I found
both the properties goes back to default values again
I am unable to repro your problem. Is this on SQL 2000 or SQL 7? Also which
sp?
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
"Chen" <mxchen100@.hotmail.com> wrote in message
news:%231XSwgo2FHA.1572@.TK2MSFTNGP10.phx.gbl...
> For a snapshot replication.
> I set the Name conflicts from the defualt-DROP the existing tables and
> re-create it
> to Delete All data in the existing table.
> and set check in Include declared refertial integrity in Copy objects to
> destination secton.
> After I close these perperties window and reopen the publiction property
> window to check the property on snapshop tab on article properties. I
found
> both the properties goes back to default values again
>
>
|||on SQL 2000
Table
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%236uJRJu2FHA.476@.TK2MSFTNGP15.phx.gbl...
> I am unable to repro your problem. Is this on SQL 2000 or SQL 7? Also
which[vbcol=seagreen]
> sp?
> --
> 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
> "Chen" <mxchen100@.hotmail.com> wrote in message
> news:%231XSwgo2FHA.1572@.TK2MSFTNGP10.phx.gbl...
property
> found
>
>
|||which sp? can you do a select @.@.version from QA?
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
"Chen" <mxchen100@.hotmail.com> wrote in message
news:uUXNF7w2FHA.2292@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> on SQL 2000
> Table
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:%236uJRJu2FHA.476@.TK2MSFTNGP15.phx.gbl...
> which
to
> property
>
>

Cannot run snapshot agent from command line

I have a transactional replication running and it's running well.
But now i'm writing a script so I can start the Snapshot Agent from
distance. therefore I want to run it from the command prompt.
I'm using this command: C:\Program Files\Microsoft SQL Server\80\COM
\snapshot.exe -Publisher <server> -PublisherDB <pubDB> -Publication
<pub> -DistributorLogin <login> -DistributorPassword <pwd>
And this is my output:
==== Output start ======
Microsoft SQL Server Snapshot Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
The process could not create file '\\<server>\ReplData\unc'.
Finished with exit code 2
==== Output end ======
When I start the agent from SQL Server itself it works fine.
the location of the snapshot folder is defined as '\\<server>
\ReplData' and (for testing now) this folder has full access.
Can somebody tell mee what;s going wrong and what I can do about it?
Can you create your command as text in a batch file then use RunAs (or log on
again if RunAs is disabled). The user to select is the sql server agent
login...
HTH,
Paul Ibison
|||You need to check to ensure that the share permissions are full for the
account which the SQL Server Agent runs under, or the account the snapshot
agent is proxied under, and the underlying security is full for the path and
all child objects.
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
"acsnaterse" <snaterse@.gmail.com> wrote in message
news:1184079506.481076.126000@.22g2000hsm.googlegro ups.com...
>I have a transactional replication running and it's running well.
> But now i'm writing a script so I can start the Snapshot Agent from
> distance. therefore I want to run it from the command prompt.
> I'm using this command: C:\Program Files\Microsoft SQL Server\80\COM
> \snapshot.exe -Publisher <server> -PublisherDB <pubDB> -Publication
> <pub> -DistributorLogin <login> -DistributorPassword <pwd>
> And this is my output:
> ==== Output start ======
> Microsoft SQL Server Snapshot Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> The process could not create file '\\<server>\ReplData\unc'.
> Finished with exit code 2
> ==== Output end ======
> When I start the agent from SQL Server itself it works fine.
> the location of the snapshot folder is defined as '\\<server>
> \ReplData' and (for testing now) this folder has full access.
> Can somebody tell mee what;s going wrong and what I can do about it?
>
|||On 10 jul, 17:58, Paul Ibison <Paul.Ibi...@.Pygmalion.Com> wrote:
> Can you create your command as text in a batch file then use RunAs (or log on
> again if RunAs is disabled). The user to select is the sql server agent
> login...
> HTH,
> Paul Ibison
Hi,
Thanks! With the runas commando it works great!
Hint: in combination with Sanur (http://www.commandline.co.uk/
sanur_unsupported/index3.html) you can automate the password fill-in.