SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SQL Server Agent - Unable to determine if the owner of job has server access.


SQL Server Agent - Unable to determine if the owner of job has server access.

Author
Message
Dave-993364
Dave-993364
Valued Member
Valued Member (59 reputation)Valued Member (59 reputation)Valued Member (59 reputation)Valued Member (59 reputation)Valued Member (59 reputation)Valued Member (59 reputation)Valued Member (59 reputation)Valued Member (59 reputation)

Group: General Forum Members
Points: 59 Visits: 338
I've read a few posts regarding similar messages, but I don't seem to be able to find a specific answer to my problem. I think it's because we have two domains to work from.

Here's the setup......

I work in an environment where we all login to our PC's using DOMAIN1\User1, yet all our SQL 2008 R2 servers are in DOMAIN2.
The two domains have trust between them, so we login, or RDP, to our DOMAIN2 servers using our DOMAIN1 accounts.

When I create any SQL Agent jobs, it defaults to my DOMAIN1 account, and because of this I've recently had loads of SQL Agent jobs fail with very similar messages....

The job failed. Unable to determine if the owner (DOMAIN1\USER1) of job MaintenancePlan1-BAckup DB has server access (reason: Could not obtain information about Windows NT group/user 'DOMAIN1\USER1', error code 0xffff0002. [SQLSTATE 42000] (Error 15404)).


I have a script I put together to reset all the job owners to the SQL Service account, but I feel this is just a 'get around' and not actually fixing the true problem.

I think that the domains aren't 'trusting' themselves properly, am I correct?

Or should I just keep resetting the Job Owners every time I edit a job?

Thanks
sqlGDBA
sqlGDBA
SSC-Addicted
SSC-Addicted (493 reputation)SSC-Addicted (493 reputation)SSC-Addicted (493 reputation)SSC-Addicted (493 reputation)SSC-Addicted (493 reputation)SSC-Addicted (493 reputation)SSC-Addicted (493 reputation)SSC-Addicted (493 reputation)

Group: General Forum Members
Points: 493 Visits: 315
In my experience, I've had that happen when the SQL Agent service account was locked out.(Another DBA was using the service account for administrative work and typed in the wrong password 3 times). I'd double check domain policies to ensure your SQL Server Agent account never expires or doesnt get locked out.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search