Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQL Server Jobs Error: The job failed. Unable to determine if the owner of job has access Expand / Collapse
Author
Message
Posted Friday, November 1, 2013 12:55 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Wednesday, September 10, 2014 6:47 AM
Points: 51, Visits: 143
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?
Post #1510769
Posted Friday, November 1, 2013 1:19 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, October 2, 2014 11:25 AM
Points: 238, Visits: 288
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.
Post #1510783
Posted Friday, November 1, 2013 2:19 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Wednesday, September 10, 2014 6:47 AM
Points: 51, Visits: 143
We have jobs that run get text files or drop text files over the server and those fail. even if I have sa.
Post #1510807
Posted Friday, November 1, 2013 2:30 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, October 2, 2014 11:25 AM
Points: 238, Visits: 288
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.
Post #1510813
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse