|
I get this error:
This happens when I start my SQL 2008 Agent job that I created. The job is owned by my domain account, I have full sysadmin rights on the SQL 08 install. This is running on my local machine (for dev/testing). There is 1 step which runs a PowerShell script:
It runs as a proxy account. This proxy account is allowed to use the PowerShell subsystem only and as my domain account is part of sysadmin I have not assigned it to the proxy account principals list. The proxy account uses a credential that is just my own domain account. If I use the SQL Agent account to run the script the job does NOT fail, but the script itself cannot execute and returns the error:
Which is why I assigned a proxy to run, a proxy that has access to that part of the network for testing. Suggestions on how I can correct this? I've seen pages that say this error may be due to the service account not being enabled for delegation. Could that be the cause of this problem? I am not familiar with the details of delegation so if that is the reason behind it a brief explanation would be greatly appreciated. Thank you!
(comments are locked)
|
|
Based on the URL you are attempting to access an administrative share on the server. Try creating a non-administrative share and assign it permissions for your SQL Agent ID and/or Proxy account then try again. Ah of course! Wasn't even thinking there, I'll try that now and post back. Thanks for pointing that out :) However, what about my proxy account? That account is my domain account which is admin on the local machine, why does that fail for my proxy account? My original issue of "reason: Error authenticating proxy domainuser, system error: Logon failure: unknown user name or bad password." ?
Nov 20 '09 at 02:21 PM
Maxer
I also had the SA account disabled so enabling that allowed Mixed Mode auth to work it seemed, then all was well.
Dec 01 '09 at 11:35 AM
Maxer
(comments are locked)
|
|
The URL was part of the issue and it turns out that I had the SA account disabled and it appears that needs to be enabled for mixed auth to work. After doing that it seemed to work properly.
(comments are locked)
|

