erikd (7/10/2013)
Hi,We already have SQL running with a domain account called clients\SQLService, which I'm told has every permission in the book allowed to it. The server proxy account in SSMS is indeed blank, so it should be using clients\SQLService. Both the SQL service and the server itself have been rebooted in the last 12 hours, so I know it's not using any of the old values that were replaced some weeks ago. I can go back and ask my pocket sysadmin if he's sure about the permissions for that account.
I read one post that mentioned having the account actually log in to the server once so it gets its permissions set from AD. Does that sound like a fix or a time waster?
Thanks
So it is a domain account, good. However, even though it might have lots of local permissions or even at the domain level you STILL have to verify that THAT user has rights to the share you are trying to reach AND the underlying files. This is the next step.
You do not need to set the proxy in this case I believe. Keep in mind the proxy account is only used when a non-sysadmin user has been allowed to call xp_cmdshell. If you are logging into SQL with a sysadmin level user then this is not in play.
CEWII