TSG954
asked on
SQL Agent Job 2008 and SSIS issue
I created a SSIS package in BIDS2008, created a job in sql server agent 2008 that calls the Package.
However I'm getting this error.. I also cretated credentials and a proxy.
Unable to start execution of step 1 (reason: Error authenticating proxy domain\svc_SqlDev, system error: Logon failure: unknown user name or bad password.). The step failed.
Any ideas what this could be?
Thanks,
However I'm getting this error.. I also cretated credentials and a proxy.
Unable to start execution of step 1 (reason: Error authenticating proxy domain\svc_SqlDev, system error: Logon failure: unknown user name or bad password.). The step failed.
Any ideas what this could be?
Thanks,
ASKER
The package is stored as a file.
What rights would be required for the domain\svc_SqlDev?
Thanks,
What rights would be required for the domain\svc_SqlDev?
Thanks,
http://msdn.microsoft.com/en-us/library/ms189064.aspx
"Before SQL Server Agent runs a job step that uses a proxy, SQL Server Agent impersonates the credentials defined in the proxy, and then runs the job step by using that security context."
"Before SQL Server Agent runs a job step that uses a proxy, SQL Server Agent impersonates the credentials defined in the proxy, and then runs the job step by using that security context."
ASKER
Right, I created a credential for it.
therefor you would need to grant sufficient rights on that account to perform whatever the package steps need to do.
ASKER
This is what I had done. I created a user domain\svc_SqlDev in Active Directory.
Then, I created a Credential called SSISProxyCredentials and in the Identity put "domain\svc_SqlDev", and the password the same
I had given to that account.
Where am I going wrong?
Then, I created a Credential called SSISProxyCredentials and in the Identity put "domain\svc_SqlDev", and the password the same
I had given to that account.
Where am I going wrong?
You need to open SSMS and check that the account exists in SQL server under the Security - Logins and that it has sufficient rights against whatever DB objects the package steps need to perform.
ASKER
I checked the Logins in Security and there is an account. My package dosnt connect to any db right now since i'm just in testing mode.
OK, do you have a password for the account?
If not you need to set a password for the Credential that is associated with the proxy. To do this, right click on the credential and select properties. Enter and confirm the password for the account.
If not you need to set a password for the Credential that is associated with the proxy. To do this, right click on the credential and select properties. Enter and confirm the password for the account.
ASKER
Yes, I have done this.
Hm......
Because the package is stored as a file, can you navigate to that folder, double click the DTSX package and try to Execute it?
Because the package is stored as a file, can you navigate to that folder, double click the DTSX package and try to Execute it?
So the proxy is "Active to the following subsystems:" - "SQL Server Integration Server Packages"
AND the job step where you execute the DTSX file is set to "Run as" the proxy account right?
AND the job step where you execute the DTSX file is set to "Run as" the proxy account right?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Switched methods and worked fine
As the package is executed by the SQL Agent asunder the proxy account, does that user "domain\svc_SqlDev" have all requred DB rights in SQL?