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 Agent - Unable to determine if the owner of job has server access. Expand / Collapse
Author
Message
Posted Tuesday, November 20, 2012 4:18 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: 2 days ago @ 9:55 AM
Points: 11, Visits: 250
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
Post #1386815
Posted Wednesday, November 21, 2012 8:25 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Friday, November 22, 2013 10:13 AM
Points: 79, Visits: 200
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.
Post #1387449
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse