We have SQL 2008 Enterprise Edition (64-bit) 10.50.1600.1 RTM. It seems I have all rights and permissions there as well. I tried different methods to run a job but it’s always failed with the message: The job failed. Unable to determine if the owner (Domain\MyLogin) of job MyJob has server access (reason: Could not obtain information about Windows NT group/user ‘Domain\MyLogin’, error code 0x5. [SQLSTATE 42000] (Error 15404)). It seems I’m trying to do all things advised from different sources: - Save package with a Server Roles - Change the package role to db_ssisadmin Then another approach: Create a special login on a server with all SQLAgent permission Create Credential Create Proxy account But, somehow I cannot make it work. Could anybody advise a simple straightforward way of doing it? I remember our admin on my previous job did it in some very simple way but I didn’t document it. Please, help.

Are you trying to run this package as an SQL Server Agent job? If so try using a domain account for the SQL Server Agent.Arthur My Blog

Thanks for your reply, ArthurZ. How I could do it? Should I create a login/account in the company Directory first, e.g. SQLAgent, then add this log in as a new login into a Server/Security/Logins? So, it could be Domain\SQLAgent. Or I could just create a new log in on a server without having it in the company directory so it could be SQLAgent without the 'domain\...'. Please, advise. It seems as I tried to create a login on a server without having it in the company directory and it didn't work. Or it doesn't matter if the login in the company directory or not?

Hi, no I suspect your SQL Server Agent is running under an account that does not have the needed privileges. So run it (service) instead under a domain account that has the admin rights. Check if the package works.Arthur My Blog

Thanks again. Please, advise how I could do it.

I’ve done the following steps: Created a new log in on a server Security/Logins called SQLAgent Entered my login password as a password. I believe it could be any one. Gave Server Roles as sysadmin, serveradmin, processadmin, and public Gave access to a datawarehouse db as db_owner , db_dsatareader, db_datawriter, public Gave access to other db on a server I’m using inn SSIS as db_datareader and public Gave access to the msdb as db_ssisadmin, db_ssisitduse, db_ssisoperator, SQLAgentUserRole, SQLAgentOperatorRole, SQLAgentReaderRole What should I do next? Please, advise.

Could anybody advise anything on it further?

That error message doesn't indicate anything wrong at all with your SSIS package, or Agent setup. What it does indicate is that your server can't communicate with your domain controller to access Active Directory to check if that account exists - let alone what rights it might or might not have. If the account didn't have permission to run the job, you'd be getting different messages about connection managers being unable to connect, or being unable to decrypt the package. If the server could contact the DC, but the account didn't exist or you had the credentials wrong, you'd see a different error message about bad credentials. But the message you're getting clearly states that it "could not obtain information". I think you'd have this problem regardless of what kind of job step you tried to run (when using a proxy). I don't know much about AD, domains, etc - but that's where I'd start to look. Talk to me now on

Hello, Here below are some usefull checkpoints.. make sure to check whether ur login have access permession or not. Check at the MSDB database role related to SQL Server agent. Also add ur login name/username to your WINDOWS/NT domain account. After creating the job make sure to add the login name as the owner to the job.

Hello, sunny_pachi, Thanks for your response. I looked at the msdb Database Roles in the SystemDatabase. There are SQLAgentOperatorRole, SQLAgenReaderRole, SQLAgentUserRole. The Role Members (in the Member of this Role part) exists for all those roles and I'm there with my domain\user. However, there is no any checkmarks in the Owned Sheemas part that is probably Ok. I could put a checkmark into a Owned Scheema for the appropriate role there I did for the SQLAgentOperatorRole but it becames gray and I cannot undo it. And I'm not sure if it's a right thing to do.

Thank you, Todd. That's right it cannot recognize my domain\user. But, I have all permissions on the server. You're right I did go through several scenarios with the proxy, creating credential, etc. But, the problem again the credential is using my identity that most likely cannot be recognized. I tried to create a separate login on the server ,e.g. DWSQLServerAgent. I did it giving all permissions as sysadmin, and for the SQLAgenRoles. Then, what's next. Should this login be in the Win directory as domain\DWSQLServerAgent or just a server login? Should I make this login as a job owner? etc. I don't now how to make it works if I need to go through this way that I remember our administrator did before and I remember that procedure should be very simple not as I'm going through many complexities.

If you are able to create a user and give him a SA previlages why dont you chose sql authentication and use sa for that...Let me know Thanks BB

The problem isn't with anything you're configuring on the SQL Server with regards to roles or permissions. Quite simply, your SQL Server can't talk to AD to even see if the user you've specified exists. Talk to me now on

I made the server login I created before as a job owner and it did go through. Thanks so much to everybody for your help.