Hi,
When I am trying to schedule the SSIS package and start the job, I am getting the following error. It is not executing properly.
"The job failed. The Job was invoked by User prakash.srinivasan. The last step to run was step 1 (TestSchStep1)."
Pls provide some solution to this.
Thanks in advance.
Regards,
Prakash Srinivasan.
Please see this KB on how to troubleshoot this:
http://support.microsoft.com/kb/918760
|||I had the same problem and replace the user for another one which was domain admin and works properly|||Hi,
I created a package with the username who has admin rights only and tried to schedule it. But I am getting this error.
"The job failed. The Job was invoked by User prakash.srinivasan. The last step to run was step 1 (CopyFile_Step1)
Executed as user: AMR500\sqladmin. The package execution failed. The step failed."
Pls provide some solution for this.
Thanks & Regards,
Prakash Srinivasan.
|||
Hi
Check the service of SQL Server Agent whether it is running in your account.
Regards
H.SRIRAM
|||Prakash - have you reviewed the KB article referenced above? It describes possible problems due to different protection levels, and most importantly how to enable logging and troubleshot this kind of problems.
|||Dear prakash,
Did u check whether the package runs in sql server ?.
if it is not successful then you need to define package protection as donot save sensitive and use SSIS configuration to store database connection in XML or sql server. Once it successful then try for schedule the package.
if schedule fails check your sql server agent services(Control panel- administrative tools-services). By defualt it will be Local Account System change to current user. Try to execute the package It will work.
Sriram
|||Hi,
Did u check whether the package runs in sql server ?.
Yes, it is running in the SQL Server only.
Also, as you mentioned I set the ProtectionLevel as Don't Save Sensitive only and used the Package Configuration for ConnectionString and stored in the XML file.
And I checked the SQL Server Agent services, it was like sqladmin. If I change my username, then other packages will get affected right.
Also guide me how to change the username in the SQL Server Agent Services.
Thanks & Regards,
Prakash Srinivasan
Change the username under which the Agent service runs. You can do this in the good old Services panel.
-Jamie
|||
i am executing as an administrator and running the package as an admnistrator. But still it fails
jas
|||One thing you might want to check is to see if the PC where you developed the application is on the same version as the server where you are running the package.
I had this same problem while I was developing on SQL 2005 SP1 and deploying the package to run on SQL 2005. Once I installed SP1 on the server, the packages started running successfully again.
Hope this helps,
Jarret
No comments:
Post a Comment