"Joe Mine" <huytuanattpgdotcomdotau> wrote in message
news:u9ThB04$DHA.2216@TK2MSFTNGP10.phx.gbl...
> Thanks Rand,
> Yes that's right the two SQL servers are in different
> non-trusted domains connected through VPN. 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
> HOT\Administrator. No trusted can be established between them. What must I
> do to achieved successful pull subscription??? How do I allow permissions
in
> the NARC domain for HOT\Administrator if there's no trusted???? What about
> independent SQL server logins to access shares in NARC domain(How do I set
> it up if possible)???
> Thanks
>
>
> "Rand Boyd [MSFT]" <rboyd@onlinemicrosoft.com> wrote in message
> news:fjJVvoV$DHA.3712@cpmsftngxa06.phx.gbl...
> > This error is generally caused by the fact that the SQL Server Agent
> > startup account on either the publisher or subscriber is not a local
> > administrator on one or both of the machines.
> >
> > The default location for the snapshot folder is an administrative share
> and
> > as such the SQL Server Agent acount must be a local adminsitrator to
> access
> > it. From the error I am going to presume that you are creating a pull
> > subscription so the SQL Server Agent startup account at the subscriber
> must
> > be a local admin on the publisher. You can verify if this is the problem
> by
> > logging on to the subscriber using the SQL Server Agent startup account
> and
> > try to map a drive to the snap shot folder on the publisher:
> >
> > \\MERCURY\G$\
> >
> > If that fails with the same error then you have your reason for the
> failure.
> >
> > Rand
> > This posting is provided "as is" with no warranties and confers no
rights.
> >
>
>

"Rand Boyd [MSFT]" <rboyd@onlinemicrosoft.com> wrote in message
news:fjJVvoV$DHA.3712@cpmsftngxa06.phx.gbl...
> This error is generally caused by the fact that the SQL Server Agent
> startup account on either the publisher or subscriber is not a local
> administrator on one or both of the machines.
>
> The default location for the snapshot folder is an administrative share
and
> as such the SQL Server Agent acount must be a local adminsitrator to
access
> it. From the error I am going to presume that you are creating a pull
> subscription so the SQL Server Agent startup account at the subscriber
must
> be a local admin on the publisher. You can verify if this is the problem
by
> logging on to the subscriber using the SQL Server Agent startup account
and
> try to map a drive to the snap shot folder on the publisher:
>
> \\MERCURY\G$\
>
> If that fails with the same error then you have your reason for the
failure.
>
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>

"Paul Ibison" <Paul.Ibison@Pygmalion.Com> wrote in message
news:eLNYLS8$DHA.2212@TK2MSFTNGP10.phx.gbl...
> Joe,
> I haven't got Rand's post available here, but I would advise to either use
> SQL security or use pass-through authentication. Both are described in the
> link in my earlier post.
> Regards,
> Paul Ibison
>
>
> "Joe Mine" <huytuanattpgdotcomdotau> wrote in message
> news:u9ThB04$DHA.2216@TK2MSFTNGP10.phx.gbl...
> > Thanks Rand,
> > Yes that's right the two SQL servers are in
different
> > non-trusted domains connected through VPN. 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
> > HOT\Administrator. No trusted can be established between them. What must
I
> > do to achieved successful pull subscription??? How do I allow
permissions
> in
> > the NARC domain for HOT\Administrator if there's no trusted???? What
about
> > independent SQL server logins to access shares in NARC domain(How do I
set
> > it up if possible)???
> > Thanks
> >
> >
> > "Rand Boyd [MSFT]" <rboyd@onlinemicrosoft.com> wrote in message
> > news:fjJVvoV$DHA.3712@cpmsftngxa06.phx.gbl...
> > > This error is generally caused by the fact that the SQL Server Agent
> > > startup account on either the publisher or subscriber is not a local
> > > administrator on one or both of the machines.
> > >
> > > The default location for the snapshot folder is an administrative
share
> > and
> > > as such the SQL Server Agent acount must be a local adminsitrator to
> > access
> > > it. From the error I am going to presume that you are creating a pull
> > > subscription so the SQL Server Agent startup account at the subscriber
> > must
> > > be a local admin on the publisher. You can verify if this is the
problem
> > by
> > > logging on to the subscriber using the SQL Server Agent startup
account
> > and
> > > try to map a drive to the snap shot folder on the publisher:
> > >
> > > \\MERCURY\G$\
> > >
> > > If that fails with the same error then you have your reason for the
> > failure.
> > >
> > > Rand
> > > This posting is provided "as is" with no warranties and confers no
> rights.
> > >
> >
> >
>
>