November 1, 2013 at 12:55 pm
I get this error when executing a job on server.
The job failed. Unable to determine if the owner (domain\username) of job jobname has server access (reason: Could not obtain information about Windows NT group/user 'domain\username', error code 0x6e. [SQLSTATE 42000] (Error 15404)).
I typed command
EXECUTE AS LOGIN='domain\username'
user name is a valid user name. sql server agent account not able to impersonate domain loginname to execute job
I also tried
EXECUTE AS LOGIN=SQLagentserviceaccount
This command does not fail.
It was working before till today and one fine day it broke.
Can anybosy shed light on what could have happened?
November 1, 2013 at 1:19 pm
I haven't looked up the error code, but at a guess, I'd say the server was unable to get information from your domain controller.
The best thing to do is to change the job owner to SA. That way, the job will never fail due to permissions like this.
November 1, 2013 at 2:19 pm
We have jobs that run get text files or drop text files over the server and those fail. even if I have sa.
November 1, 2013 at 2:30 pm
That sounds like a permissions issue with the folder where you're trying to put the text files. We're doing something similar and we have a shared folder set up with permissions for the SQL Server agent account to be able to write to that directory. Actually, the network admin has the permissions set to allow everyone to write to the folder, which it probably shouldn't be set to...
Anyway, take a look at the permissions on that folder. Try changing the permissions to give everyone full control to see if that fixes the problem. If it does, you can dial the permissions back to just the SQL Server account. If it doesn't, then it's not a permissions issue on that folder.
July 10, 2015 at 11:10 am
It's post two years ago, not sure anyone else has this issue recently? I experienced this error couple of days ago but I can't find any proper answer.
I have two jobs have been running couple of months, but the same error happened last week, I have to change the job owner to 'sa', job can run successfully, but it's not what we want.
After some test and research, I am pretty sure it's not problem of network or security setting. I found system error on server, see below for details, it's from source NETLOGON. I believe it's the reason. the service RPC cannot restart manually, that why we have to restart the box to resolve the problem.
(Sorry don't know how to change the color for more clear reading)
This computer was not able to set up a secure session with a domain controller in domain XXXXXX due to the following:
The RPC server is unavailable.
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.
ADDITIONAL INFO
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
And the system error below can be found:
The processing of Group Policy failed. Windows could not obtain the name of a domain controller. This could be caused by a name resolution failure. Verify your Domain Name System (DNS) is configured and working correctly.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply