Re: Distributor SQLSERVERAgent Account

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Hilary Cotter (hilary.cotter_at_gmail.com)
Date: 02/09/05 

Date: Wed, 9 Feb 2005 07:43:34 -0500

Is this pull? If so, your subscriber's sql server agent should be running
under the same account as the publisher's SQL Server agent, or an account
that is part of the local admin group on the publisher.

If this is not possible the SQL Server agent account on the subscriber
should have rigths to read the snapshot share and underlying files and
folders. You will probably have to craft another snapshot share on the
publisher for this.

For push subscriptions you should not have to worry about this unless you
have a remote distributor. 

-- 
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
<richerwin@ubs-europe.org> wrote in message
news:1107929613.327118.195320@l41g2000cwc.googlegroups.com...
>
> What account should the SqlServerAgent run under at the distributor
> (dist. and publisher are same machine)?
>
> Mine is running under .\sqladmin but I keep getting
> Error: The schema script
> '\\WSCLAN08\ReplData\unc\WSCLAN08_TMS_TMS\20050209054316\Ltab_Years_1.sch'
> could not be propagated to the subscriber.
>
> At subscriber, SqlServerAgent is running under LocalSystem.
>
> \\WSCLAN08\ReplData\ is public share and user has permissions (incl.
> sqladmin).
>
> Also, user is in PAL of publication (incl. sqladmin).
>
> Thanks.
>

Relevant Pages

  • Re: Browsing for Publication error message
    ... what is going on with the description you gave previously but I would guess that the subscriber SQL Server Agent service account was somehow added to the publication access list of the publication on the DMZ. ... select from the MSpublication_access table in the distribution database and see if the account for your Subscriber's SQL Server Agent service account shows up. ...
    (microsoft.public.sqlserver.replication)
  • Re: Newbie to Replication Subscriptions
    ... (even though on the network share in question "Everyone" had full rights) ... they'd get in that way but not with the localsystem account that is used by ... > publisher reads the files and bcp's them to the subscriber. ... > you are using NT authentication, the SQL Server agent ...
    (microsoft.public.sqlserver.replication)
  • Re: OS error 53 for SQL servers VPN replication?
    ... The Distributor and Publisher SQL ... Server is in the NARC domain and Agent login account as NARC\Administrator. ... And the subscriber is in the HOT domain and Agent Login account is ... > This error is generally caused by the fact that the SQL Server Agent ...
    (microsoft.public.sqlserver.replication)
  • Re: OS error 53 for SQL servers VPN replication?
    ... The Distributor and Publisher SQL ... Server is in the NARC domain and Agent login account as NARC\Administrator. ... And the subscriber is in the HOT domain and Agent Login account is ... > This error is generally caused by the fact that the SQL Server Agent ...
    (microsoft.public.sqlserver.connect)
  • RE: OS error 53 for SQL servers VPN replication?
    ... This error is generally caused by the fact that the SQL Server Agent ... subscription so the SQL Server Agent startup account at the subscriber must ... be a local admin on the publisher. ...
    (microsoft.public.sqlserver.connect)