Prev: Invalid object name 'dbo.sysmergepublications'
Next: Replication/Subscription error
From: John F. on 22 Feb 2006 16:08
Raymond - FYI all SQL services are running under the Local System account on
the publisher box. The subscription creates but the snapshot agent still
wont start now with the 'cant get proxy info' error.
--
John F.


"Raymond Mak [MSFT]" wrote:

> This looks really strange, the original error message came from
> SQLServerAgent which basically said 'flowersj' doesn't have access to the
> proxy account that you have configured for the snapshot agent, yet
> subsequent attempts to grant 'flowersj' access to the proxy account resulted
> in errors which basically say 'flowersj' already has access (which is as it
> should be). Is SQLServerAgent running under a low-privileged account (e.g.
> NetworkService)? And are you running Win2K3 or Win2k(which may require
> additional OS privilege to be granted to the proxy account)? Of course, if
> nothing works, you can always run the snapshot agent executable outside of
> SQL Server Agent but I am guessing that you want to have integrated
> scheduling support provided by SQLServerAgent.
>
> -Raymond
> "John F." <juantana(a)newsgroups.microsoft.com> wrote in message
> news:986692AB-536A-4DE1-9B82-CE5D6544BD2E(a)microsoft.com...
> > Thanks Raymond - I tried what you suggest above and get this -
> >
> > 'flowersj' is a member of sysadmin server role and cannot be granted to or
> > revoked from the proxy. Members of sysadmin server role are allowed to use
> > any proxy.
> > Msg 14531, Level 16, State 1, Procedure sp_grant_proxy_to_subsystem, Line
> > 48
> > Permission to access proxy already granted. Verify current permissions
> > assignments.
> >
> > all logins Ive used are 'sa' rights - as far as the replication goes its
> > just a simple snapshot scenario, pull subscription, distributor running on
> > the publisher, & Im trying to start the snapshot agent to get the initial
> > sync. We are on the RTM of SQL2005. Both servers in the same domain. Is
> > there a folder I should share or something? Any help is greatly
> > appreciated
> > - thanks!
> > --
> > John F.
> >
> >
> > "Raymond Mak [MSFT]" wrote:
> >
> >> Hi John,
> >>
> >> You may want to try the following to grant login 'flowersj' and the
> >> Snapshot
> >> subsystem access to proxy id = 1(?):
> >>
> >> use msdb
> >> exec sp_grant_login_to_proxy @login_name = N'flowersj', @proxy_id = 1
> >> exec sp_grant_proxy_to_subsystem @proxy_id = 1, @subsystem_name =
> >> N'Snapshot'
> >>
> >> If that works, I am sort of curious to know how your system got to the
> >> state
> >> that it is currently in. It would be great if you can post some details
> >> on
> >> the nature of the flowersj login, whether you are using a remote
> >> distributor
> >> (snapshot jobs should be owned by distributor_admin), and which edition
> >> of
> >> SQL Server you are using.
> >>
> >> Thanks much.
> >>
> >> -Raymond
> >>
> >> "John F." <juantana(a)newsgroups.microsoft.com> wrote in message
> >> news:AEF0BFB6-16CA-4869-83C7-085EACBFBBC0(a)microsoft.com...
> >> >I have tried both SQL logins with sa permissions and then windows logins
> >> >also
> >> > with sa permissions to both servers as well and I still get this
> >> > message
> >> > and
> >> > the Snapshot Agent won't start - any ideas?
> >> >
> >> > Replication-Replication Snapshot Subsystem: agent NPRPROD-NPR-NPR-1
> >> > failed.
> >> > Unable to start execution of step 2 (reason: JobOwner flowersj doesn't
> >> > have
> >> > permissions to use proxy 1 for subsystem Snapshot). The step failed.
> >> > --
> >> > John F.
> >>
> >>
> >>
>
>
>
From: Raymond Mak [MSFT] on 22 Feb 2006 17:47
If you have configured the snapshot agent to run under an explicit domain
proxy account, SQL Server Agent can have many different ways of failing to
get the proxy account info if it is running as LocalSystem. So in the
interest of narrowing down problem to whether this is a proxy account issue,
you may want to try configuring the snapshot agent to run under the same
account as SQLServerAgent (right click publication->properties->Agent
Security->Security Settings... button for snapshot agent->Run under the SQL
ServerAgent service account (This is not a recommended security best
practice) radio button and see if you can start the snapshot agent at all.

-Raymond
"John F." <juantana(a)newsgroups.microsoft.com> wrote in message
news:08BE8929-5E84-43EF-8270-EB2BE118E20F(a)microsoft.com...
> Raymond - FYI all SQL services are running under the Local System account
> on
> the publisher box. The subscription creates but the snapshot agent still
> wont start now with the 'cant get proxy info' error.
> --
> John F.
>
>
> "Raymond Mak [MSFT]" wrote:
>
>> This looks really strange, the original error message came from
>> SQLServerAgent which basically said 'flowersj' doesn't have access to the
>> proxy account that you have configured for the snapshot agent, yet
>> subsequent attempts to grant 'flowersj' access to the proxy account
>> resulted
>> in errors which basically say 'flowersj' already has access (which is as
>> it
>> should be). Is SQLServerAgent running under a low-privileged account
>> (e.g.
>> NetworkService)? And are you running Win2K3 or Win2k(which may require
>> additional OS privilege to be granted to the proxy account)? Of course,
>> if
>> nothing works, you can always run the snapshot agent executable outside
>> of
>> SQL Server Agent but I am guessing that you want to have integrated
>> scheduling support provided by SQLServerAgent.
>>
>> -Raymond
>> "John F." <juantana(a)newsgroups.microsoft.com> wrote in message
>> news:986692AB-536A-4DE1-9B82-CE5D6544BD2E(a)microsoft.com...
>> > Thanks Raymond - I tried what you suggest above and get this -
>> >
>> > 'flowersj' is a member of sysadmin server role and cannot be granted to
>> > or
>> > revoked from the proxy. Members of sysadmin server role are allowed to
>> > use
>> > any proxy.
>> > Msg 14531, Level 16, State 1, Procedure sp_grant_proxy_to_subsystem,
>> > Line
>> > 48
>> > Permission to access proxy already granted. Verify current permissions
>> > assignments.
>> >
>> > all logins Ive used are 'sa' rights - as far as the replication goes
>> > its
>> > just a simple snapshot scenario, pull subscription, distributor running
>> > on
>> > the publisher, & Im trying to start the snapshot agent to get the
>> > initial
>> > sync. We are on the RTM of SQL2005. Both servers in the same domain.
>> > Is
>> > there a folder I should share or something? Any help is greatly
>> > appreciated
>> > - thanks!
>> > --
>> > John F.
>> >
>> >
>> > "Raymond Mak [MSFT]" wrote:
>> >
>> >> Hi John,
>> >>
>> >> You may want to try the following to grant login 'flowersj' and the
>> >> Snapshot
>> >> subsystem access to proxy id = 1(?):
>> >>
>> >> use msdb
>> >> exec sp_grant_login_to_proxy @login_name = N'flowersj', @proxy_id = 1
>> >> exec sp_grant_proxy_to_subsystem @proxy_id = 1, @subsystem_name =
>> >> N'Snapshot'
>> >>
>> >> If that works, I am sort of curious to know how your system got to the
>> >> state
>> >> that it is currently in. It would be great if you can post some
>> >> details
>> >> on
>> >> the nature of the flowersj login, whether you are using a remote
>> >> distributor
>> >> (snapshot jobs should be owned by distributor_admin), and which
>> >> edition
>> >> of
>> >> SQL Server you are using.
>> >>
>> >> Thanks much.
>> >>
>> >> -Raymond
>> >>
>> >> "John F." <juantana(a)newsgroups.microsoft.com> wrote in message
>> >> news:AEF0BFB6-16CA-4869-83C7-085EACBFBBC0(a)microsoft.com...
>> >> >I have tried both SQL logins with sa permissions and then windows
>> >> >logins
>> >> >also
>> >> > with sa permissions to both servers as well and I still get this
>> >> > message
>> >> > and
>> >> > the Snapshot Agent won't start - any ideas?
>> >> >
>> >> > Replication-Replication Snapshot Subsystem: agent NPRPROD-NPR-NPR-1
>> >> > failed.
>> >> > Unable to start execution of step 2 (reason: JobOwner flowersj
>> >> > doesn't
>> >> > have
>> >> > permissions to use proxy 1 for subsystem Snapshot). The step
>> >> > failed.
>> >> > --
>> >> > John F.
>> >>
>> >>
>> >>
>>
>>
>>


From: John F. on 23 Feb 2006 10:40
still struggling this a.m. with this, Raymond, and I certainly apprecaite
your help. All services on the box in question run under the LocalSystem
account, so I tried to change the Snapshot Agent to use this acct as well.
it still wont start and in looking at all replication job histories I see
this error now - its really strange as the box is both Publisher and
Distributor and the snapshot agent is trying to start on this same box as
well - any ideas? Does the snapshot agent have to run on the publisher? I
wonder if I could do a pull subscription from the subscriber as that box
seems to run smoother with fewer issues. any info or doc on how to setup
Replication in 2005 is greatly appreciated.

2006-02-23 15:22:53.98 Connecting to Distributor 'NPRPROD'
2006-02-23 15:22:54.09 The replication agent had encountered an exception.
2006-02-23 15:22:54.09 Source: Replication
2006-02-23 15:22:54.09 Exception Type:
Microsoft.SqlServer.Replication.ReplicationAgentSqlException
2006-02-23 15:22:54.09 Exception Message: The remote server "NPRPROD" does
not exist, or has not been designated as a valid Publisher, or you may not
have permission to see available Publishers.
2006-02-23 15:22:54.09 Message Code: 14080
--
John F.


"Raymond Mak [MSFT]" wrote:

> If you have configured the snapshot agent to run under an explicit domain
> proxy account, SQL Server Agent can have many different ways of failing to
> get the proxy account info if it is running as LocalSystem. So in the
> interest of narrowing down problem to whether this is a proxy account issue,
> you may want to try configuring the snapshot agent to run under the same
> account as SQLServerAgent (right click publication->properties->Agent
> Security->Security Settings... button for snapshot agent->Run under the SQL
> ServerAgent service account (This is not a recommended security best
> practice) radio button and see if you can start the snapshot agent at all.
>
> -Raymond
> "John F." <juantana(a)newsgroups.microsoft.com> wrote in message
> news:08BE8929-5E84-43EF-8270-EB2BE118E20F(a)microsoft.com...
> > Raymond - FYI all SQL services are running under the Local System account
> > on
> > the publisher box. The subscription creates but the snapshot agent still
> > wont start now with the 'cant get proxy info' error.
> > --
> > John F.
> >
> >
> > "Raymond Mak [MSFT]" wrote:
> >
> >> This looks really strange, the original error message came from
> >> SQLServerAgent which basically said 'flowersj' doesn't have access to the
> >> proxy account that you have configured for the snapshot agent, yet
> >> subsequent attempts to grant 'flowersj' access to the proxy account
> >> resulted
> >> in errors which basically say 'flowersj' already has access (which is as
> >> it
> >> should be). Is SQLServerAgent running under a low-privileged account
> >> (e.g.
> >> NetworkService)? And are you running Win2K3 or Win2k(which may require
> >> additional OS privilege to be granted to the proxy account)? Of course,
> >> if
> >> nothing works, you can always run the snapshot agent executable outside
> >> of
> >> SQL Server Agent but I am guessing that you want to have integrated
> >> scheduling support provided by SQLServerAgent.
> >>
> >> -Raymond
> >> "John F." <juantana(a)newsgroups.microsoft.com> wrote in message
> >> news:986692AB-536A-4DE1-9B82-CE5D6544BD2E(a)microsoft.com...
> >> > Thanks Raymond - I tried what you suggest above and get this -
> >> >
> >> > 'flowersj' is a member of sysadmin server role and cannot be granted to
> >> > or
> >> > revoked from the proxy. Members of sysadmin server role are allowed to
> >> > use
> >> > any proxy.
> >> > Msg 14531, Level 16, State 1, Procedure sp_grant_proxy_to_subsystem,
> >> > Line
> >> > 48
> >> > Permission to access proxy already granted. Verify current permissions
> >> > assignments.
> >> >
> >> > all logins Ive used are 'sa' rights - as far as the replication goes
> >> > its
> >> > just a simple snapshot scenario, pull subscription, distributor running
> >> > on
> >> > the publisher, & Im trying to start the snapshot agent to get the
> >> > initial
> >> > sync. We are on the RTM of SQL2005. Both servers in the same domain.
> >> > Is
> >> > there a folder I should share or something? Any help is greatly
> >> > appreciated
> >> > - thanks!
> >> > --
> >> > John F.
> >> >
> >> >
> >> > "Raymond Mak [MSFT]" wrote:
> >> >
> >> >> Hi John,
> >> >>
> >> >> You may want to try the following to grant login 'flowersj' and the
> >> >> Snapshot
> >> >> subsystem access to proxy id = 1(?):
> >> >>
> >> >> use msdb
> >> >> exec sp_grant_login_to_proxy @login_name = N'flowersj', @proxy_id = 1
> >> >> exec sp_grant_proxy_to_subsystem @proxy_id = 1, @subsystem_name =
> >> >> N'Snapshot'
> >> >>
> >> >> If that works, I am sort of curious to know how your system got to the
> >> >> state
> >> >> that it is currently in. It would be great if you can post some
> >> >> details
> >> >> on
> >> >> the nature of the flowersj login, whether you are using a remote
> >> >> distributor
> >> >> (snapshot jobs should be owned by distributor_admin), and which
> >> >> edition
> >> >> of
> >> >> SQL Server you are using.
> >> >>
> >> >> Thanks much.
> >> >>
> >> >> -Raymond
> >> >>
> >> >> "John F." <juantana(a)newsgroups.microsoft.com> wrote in message
> >> >> news:AEF0BFB6-16CA-4869-83C7-085EACBFBBC0(a)microsoft.com...
> >> >> >I have tried both SQL logins with sa permissions and then windows
> >> >> >logins
> >> >> >also
> >> >> > with sa permissions to both servers as well and I still get this
> >> >> > message
> >> >> > and
> >> >> > the Snapshot Agent won't start - any ideas?
> >> >> >
> >> >> > Replication-Replication Snapshot Subsystem: agent NPRPROD-NPR-NPR-1
> >> >> > failed.
> >> >> > Unable to start execution of step 2 (reason: JobOwner flowersj
> >> >> > doesn't
> >> >> > have
> >> >> > permissions to use proxy 1 for subsystem Snapshot). The step
> >> >> > failed.
> >> >> > --
> >> >> > John F.
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>
From: Raymond Mak [MSFT] on 23 Feb 2006 12:41
The following message certainly looks a lot better as the snapshot agent was
able to run whereas the previous messages you got indicated that
SQLServerAgent wasn't able to start the job at all so progress is being made
albeit in a painfully slow manner. I now suspect that the LocalSystem
account probably doesn't have quite enough privilege to query information
from system catalogue and to verify whether this is the case, you may want
to try using the *SQL Server Configuration Manager (Start->All
Programs->Microsoft SQL Server 2005->Configuration Tools->SQL Server
Configuration Manager)* to configure SQLServerAgent to run under a domain
account that you know have relatively high privilege on the
Publisher\Distributor SQL Server instance (can see all rows in sys.servers
for example) and then restart the snapshot agent job again. You can even try
a bit of validation upfront by starting a cmd.exe window under the domain
account that you intend for running SQLServerAgent and then run the snapshot
agent executable (%ProgramFiles%\Microsoft SQL Server\90\COM\snapshot.exe)
manually from there using the command line obtained from msdb..sysjobsteps
(you should be able to find detail instructions on how to run the
replication agent executable by searching this newsgroup). Once you are
satisified that you can run the snapshot agent executable under a specific
account, you can go back and tackle the problem of starting the snapshot
agent job from SQLServerAgent.

If this is indeed an access permission configuration issue as suggested by
the evidence we have so far, running the snapshot agent anywhere else other
than the distributor machine won't help not to mention that this is an
unsupported configuration that will likely result in suboptimal network
bandwidth utilization.

HTH

-Raymond
"John F." <juantana(a)newsgroups.microsoft.com> wrote in message
news:BFDE84F4-FBA9-4574-83EF-ACA7C32D0315(a)microsoft.com...
> still struggling this a.m. with this, Raymond, and I certainly apprecaite
> your help. All services on the box in question run under the LocalSystem
> account, so I tried to change the Snapshot Agent to use this acct as well.
> it still wont start and in looking at all replication job histories I see
> this error now - its really strange as the box is both Publisher and
> Distributor and the snapshot agent is trying to start on this same box as
> well - any ideas? Does the snapshot agent have to run on the publisher?
> I
> wonder if I could do a pull subscription from the subscriber as that box
> seems to run smoother with fewer issues. any info or doc on how to setup
> Replication in 2005 is greatly appreciated.
>
> 2006-02-23 15:22:53.98 Connecting to Distributor 'NPRPROD'
> 2006-02-23 15:22:54.09 The replication agent had encountered an exception.
> 2006-02-23 15:22:54.09 Source: Replication
> 2006-02-23 15:22:54.09 Exception Type:
> Microsoft.SqlServer.Replication.ReplicationAgentSqlException
> 2006-02-23 15:22:54.09 Exception Message: The remote server "NPRPROD" does
> not exist, or has not been designated as a valid Publisher, or you may not
> have permission to see available Publishers.
> 2006-02-23 15:22:54.09 Message Code: 14080
> --
> John F.
>
>
> "Raymond Mak [MSFT]" wrote:
>
>> If you have configured the snapshot agent to run under an explicit domain
>> proxy account, SQL Server Agent can have many different ways of failing
>> to
>> get the proxy account info if it is running as LocalSystem. So in the
>> interest of narrowing down problem to whether this is a proxy account
>> issue,
>> you may want to try configuring the snapshot agent to run under the same
>> account as SQLServerAgent (right click publication->properties->Agent
>> Security->Security Settings... button for snapshot agent->Run under the
>> SQL
>> ServerAgent service account (This is not a recommended security best
>> practice) radio button and see if you can start the snapshot agent at
>> all.
>>
>> -Raymond
>> "John F." <juantana(a)newsgroups.microsoft.com> wrote in message
>> news:08BE8929-5E84-43EF-8270-EB2BE118E20F(a)microsoft.com...
>> > Raymond - FYI all SQL services are running under the Local System
>> > account
>> > on
>> > the publisher box. The subscription creates but the snapshot agent
>> > still
>> > wont start now with the 'cant get proxy info' error.
>> > --
>> > John F.
>> >
>> >
>> > "Raymond Mak [MSFT]" wrote:
>> >
>> >> This looks really strange, the original error message came from
>> >> SQLServerAgent which basically said 'flowersj' doesn't have access to
>> >> the
>> >> proxy account that you have configured for the snapshot agent, yet
>> >> subsequent attempts to grant 'flowersj' access to the proxy account
>> >> resulted
>> >> in errors which basically say 'flowersj' already has access (which is
>> >> as
>> >> it
>> >> should be). Is SQLServerAgent running under a low-privileged account
>> >> (e.g.
>> >> NetworkService)? And are you running Win2K3 or Win2k(which may require
>> >> additional OS privilege to be granted to the proxy account)? Of
>> >> course,
>> >> if
>> >> nothing works, you can always run the snapshot agent executable
>> >> outside
>> >> of
>> >> SQL Server Agent but I am guessing that you want to have integrated
>> >> scheduling support provided by SQLServerAgent.
>> >>
>> >> -Raymond
>> >> "John F." <juantana(a)newsgroups.microsoft.com> wrote in message
>> >> news:986692AB-536A-4DE1-9B82-CE5D6544BD2E(a)microsoft.com...
>> >> > Thanks Raymond - I tried what you suggest above and get this -
>> >> >
>> >> > 'flowersj' is a member of sysadmin server role and cannot be granted
>> >> > to
>> >> > or
>> >> > revoked from the proxy. Members of sysadmin server role are allowed
>> >> > to
>> >> > use
>> >> > any proxy.
>> >> > Msg 14531, Level 16, State 1, Procedure sp_grant_proxy_to_subsystem,
>> >> > Line
>> >> > 48
>> >> > Permission to access proxy already granted. Verify current
>> >> > permissions
>> >> > assignments.
>> >> >
>> >> > all logins Ive used are 'sa' rights - as far as the replication goes
>> >> > its
>> >> > just a simple snapshot scenario, pull subscription, distributor
>> >> > running
>> >> > on
>> >> > the publisher, & Im trying to start the snapshot agent to get the
>> >> > initial
>> >> > sync. We are on the RTM of SQL2005. Both servers in the same
>> >> > domain.
>> >> > Is
>> >> > there a folder I should share or something? Any help is greatly
>> >> > appreciated
>> >> > - thanks!
>> >> > --
>> >> > John F.
>> >> >
>> >> >
>> >> > "Raymond Mak [MSFT]" wrote:
>> >> >
>> >> >> Hi John,
>> >> >>
>> >> >> You may want to try the following to grant login 'flowersj' and the
>> >> >> Snapshot
>> >> >> subsystem access to proxy id = 1(?):
>> >> >>
>> >> >> use msdb
>> >> >> exec sp_grant_login_to_proxy @login_name = N'flowersj', @proxy_id =
>> >> >> 1
>> >> >> exec sp_grant_proxy_to_subsystem @proxy_id = 1, @subsystem_name =
>> >> >> N'Snapshot'
>> >> >>
>> >> >> If that works, I am sort of curious to know how your system got to
>> >> >> the
>> >> >> state
>> >> >> that it is currently in. It would be great if you can post some
>> >> >> details
>> >> >> on
>> >> >> the nature of the flowersj login, whether you are using a remote
>> >> >> distributor
>> >> >> (snapshot jobs should be owned by distributor_admin), and which
>> >> >> edition
>> >> >> of
>> >> >> SQL Server you are using.
>> >> >>
>> >> >> Thanks much.
>> >> >>
>> >> >> -Raymond
>> >> >>
>> >> >> "John F." <juantana(a)newsgroups.microsoft.com> wrote in message
>> >> >> news:AEF0BFB6-16CA-4869-83C7-085EACBFBBC0(a)microsoft.com...
>> >> >> >I have tried both SQL logins with sa permissions and then windows
>> >> >> >logins
>> >> >> >also
>> >> >> > with sa permissions to both servers as well and I still get this
>> >> >> > message
>> >> >> > and
>> >> >> > the Snapshot Agent won't start - any ideas?
>> >> >> >
>> >> >> > Replication-Replication Snapshot Subsystem: agent
>> >> >> > NPRPROD-NPR-NPR-1
>> >> >> > failed.
>> >> >> > Unable to start execution of step 2 (reason: JobOwner flowersj
>> >> >> > doesn't
>> >> >> > have
>> >> >> > permissions to use proxy 1 for subsystem Snapshot). The step
>> >> >> > failed.
>> >> >> > --
>> >> >> > John F.
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>


From: Wanwen Qi [MSFT] on 23 Feb 2006 17:26
Hi John,

In case you still stuck with
Replication-Replication Snapshot Subsystem: agent NPRPROD-NPR-NPR-1 failed.
Unable to start execution of step 2 (reason: JobOwner flowersj doesn't have
permissions to use proxy 1 for subsystem Snapshot).

Could you please run the following query and post back the results?
select * from sys.credentials

select * from msdb..sysproxies

select * from msdb..sysproxylogin

select * from msdb..sysproxysubsystem

Thanks

--
[ This posting is provided "as is" with no warranties and confers no
rights. ]

"John F." <juantana(a)newsgroups.microsoft.com> wrote in message
news:BFDE84F4-FBA9-4574-83EF-ACA7C32D0315(a)microsoft.com...
> still struggling this a.m. with this, Raymond, and I certainly apprecaite
> your help. All services on the box in question run under the LocalSystem
> account, so I tried to change the Snapshot Agent to use this acct as well.
> it still wont start and in looking at all replication job histories I see
> this error now - its really strange as the box is both Publisher and
> Distributor and the snapshot agent is trying to start on this same box as
> well - any ideas? Does the snapshot agent have to run on the publisher?
> I
> wonder if I could do a pull subscription from the subscriber as that box
> seems to run smoother with fewer issues. any info or doc on how to setup
> Replication in 2005 is greatly appreciated.
>
> 2006-02-23 15:22:53.98 Connecting to Distributor 'NPRPROD'
> 2006-02-23 15:22:54.09 The replication agent had encountered an exception.
> 2006-02-23 15:22:54.09 Source: Replication
> 2006-02-23 15:22:54.09 Exception Type:
> Microsoft.SqlServer.Replication.ReplicationAgentSqlException
> 2006-02-23 15:22:54.09 Exception Message: The remote server "NPRPROD" does
> not exist, or has not been designated as a valid Publisher, or you may not
> have permission to see available Publishers.
> 2006-02-23 15:22:54.09 Message Code: 14080
> --
> John F.
>
>
> "Raymond Mak [MSFT]" wrote:
>
>> If you have configured the snapshot agent to run under an explicit domain
>> proxy account, SQL Server Agent can have many different ways of failing
>> to
>> get the proxy account info if it is running as LocalSystem. So in the
>> interest of narrowing down problem to whether this is a proxy account
>> issue,
>> you may want to try configuring the snapshot agent to run under the same
>> account as SQLServerAgent (right click publication->properties->Agent
>> Security->Security Settings... button for snapshot agent->Run under the
>> SQL
>> ServerAgent service account (This is not a recommended security best
>> practice) radio button and see if you can start the snapshot agent at
>> all.
>>
>> -Raymond
>> "John F." <juantana(a)newsgroups.microsoft.com> wrote in message
>> news:08BE8929-5E84-43EF-8270-EB2BE118E20F(a)microsoft.com...
>> > Raymond - FYI all SQL services are running under the Local System
>> > account
>> > on
>> > the publisher box. The subscription creates but the snapshot agent
>> > still
>> > wont start now with the 'cant get proxy info' error.
>> > --
>> > John F.
>> >
>> >
>> > "Raymond Mak [MSFT]" wrote:
>> >
>> >> This looks really strange, the original error message came from
>> >> SQLServerAgent which basically said 'flowersj' doesn't have access to
>> >> the
>> >> proxy account that you have configured for the snapshot agent, yet
>> >> subsequent attempts to grant 'flowersj' access to the proxy account
>> >> resulted
>> >> in errors which basically say 'flowersj' already has access (which is
>> >> as
>> >> it
>> >> should be). Is SQLServerAgent running under a low-privileged account
>> >> (e.g.
>> >> NetworkService)? And are you running Win2K3 or Win2k(which may require
>> >> additional OS privilege to be granted to the proxy account)? Of
>> >> course,
>> >> if
>> >> nothing works, you can always run the snapshot agent executable
>> >> outside
>> >> of
>> >> SQL Server Agent but I am guessing that you want to have integrated
>> >> scheduling support provided by SQLServerAgent.
>> >>
>> >> -Raymond
>> >> "John F." <juantana(a)newsgroups.microsoft.com> wrote in message
>> >> news:986692AB-536A-4DE1-9B82-CE5D6544BD2E(a)microsoft.com...
>> >> > Thanks Raymond - I tried what you suggest above and get this -
>> >> >
>> >> > 'flowersj' is a member of sysadmin server role and cannot be granted
>> >> > to
>> >> > or
>> >> > revoked from the proxy. Members of sysadmin server role are allowed
>> >> > to
>> >> > use
>> >> > any proxy.
>> >> > Msg 14531, Level 16, State 1, Procedure sp_grant_proxy_to_subsystem,
>> >> > Line
>> >> > 48
>> >> > Permission to access proxy already granted. Verify current
>> >> > permissions
>> >> > assignments.
>> >> >
>> >> > all logins Ive used are 'sa' rights - as far as the replication goes
>> >> > its
>> >> > just a simple snapshot scenario, pull subscription, distributor
>> >> > running
>> >> > on
>> >> > the publisher, & Im trying to start the snapshot agent to get the
>> >> > initial
>> >> > sync. We are on the RTM of SQL2005. Both servers in the same
>> >> > domain.
>> >> > Is
>> >> > there a folder I should share or something? Any help is greatly
>> >> > appreciated
>> >> > - thanks!
>> >> > --
>> >> > John F.
>> >> >
>> >> >
>> >> > "Raymond Mak [MSFT]" wrote:
>> >> >
>> >> >> Hi John,
>> >> >>
>> >> >> You may want to try the following to grant login 'flowersj' and the
>> >> >> Snapshot
>> >> >> subsystem access to proxy id = 1(?):
>> >> >>
>> >> >> use msdb
>> >> >> exec sp_grant_login_to_proxy @login_name = N'flowersj', @proxy_id =
>> >> >> 1
>> >> >> exec sp_grant_proxy_to_subsystem @proxy_id = 1, @subsystem_name =
>> >> >> N'Snapshot'
>> >> >>
>> >> >> If that works, I am sort of curious to know how your system got to
>> >> >> the
>> >> >> state
>> >> >> that it is currently in. It would be great if you can post some
>> >> >> details
>> >> >> on
>> >> >> the nature of the flowersj login, whether you are using a remote
>> >> >> distributor
>> >> >> (snapshot jobs should be owned by distributor_admin), and which
>> >> >> edition
>> >> >> of
>> >> >> SQL Server you are using.
>> >> >>
>> >> >> Thanks much.
>> >> >>
>> >> >> -Raymond
>> >> >>
>> >> >> "John F." <juantana(a)newsgroups.microsoft.com> wrote in message
>> >> >> news:AEF0BFB6-16CA-4869-83C7-085EACBFBBC0(a)microsoft.com...
>> >> >> >I have tried both SQL logins with sa permissions and then windows
>> >> >> >logins
>> >> >> >also
>> >> >> > with sa permissions to both servers as well and I still get this
>> >> >> > message
>> >> >> > and
>> >> >> > the Snapshot Agent won't start - any ideas?
>> >> >> >
>> >> >> > Replication-Replication Snapshot Subsystem: agent
>> >> >> > NPRPROD-NPR-NPR-1
>> >> >> > failed.
>> >> >> > Unable to start execution of step 2 (reason: JobOwner flowersj
>> >> >> > doesn't
>> >> >> > have
>> >> >> > permissions to use proxy 1 for subsystem Snapshot). The step
>> >> >> > failed.
>> >> >> > --
>> >> >> > John F.
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>


First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: Invalid object name 'dbo.sysmergepublications'
Next: Replication/Subscription error