Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 SSIS and Import/Export (2005)
 Job Fails! when I use SSIS

Author  Topic 

karthik_padbanaban
Constraint Violating Yak Guru

263 Posts

Posted - 2008-05-13 : 04:03:51
Hi all.,
I am trying to schedule a SSIS package into SQL Job., for that I created a account with sysadmin role which named karthikm.,
I create a new proxy settings.,
with all the permissions.,

But still the Job fails.,

Error message: The job failed. The Job was invoked byUserkarthikm. The last step to run was step1(Step1).,

any idea to solve this problem.,

visakh16
Very Important crosS Applying yaK Herder

52326 Posts

Posted - 2008-05-13 : 04:16:06
Did you try executing SSIS directly? Did it ran successfully?
Go to Top of Page

karthik_padbanaban
Constraint Violating Yak Guru

263 Posts

Posted - 2008-05-13 : 05:41:14
quote:
Originally posted by visakh16

Did you try executing SSIS directly? Did it ran successfully?



yes its working when i execute the package alone., but its not working when scheduled with job
Go to Top of Page

nr
SQLTeam MVY

12543 Posts

Posted - 2008-05-13 : 07:10:31
Enable looging and look at the log.
What happens when you log on as that user and run the package from the designer?

==========================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
Go to Top of Page

rgombina
Constraint Violating Yak Guru

319 Posts

Posted - 2008-05-13 : 07:10:46
Try job and steps owner karthikm. Also try to use SQL Agent (job and step owner too) if you can and see if it works.
Go to Top of Page

karthik_padbanaban
Constraint Violating Yak Guru

263 Posts

Posted - 2008-05-13 : 07:20:00
quote:
Originally posted by nr

Enable looging and look at the log.
What happens when you log on as that user and run the package from the designer?

==========================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.



when i use the user name karthikm.,
its working fine when I runs that package.,
but still its not working in job
Go to Top of Page

nr
SQLTeam MVY

12543 Posts

Posted - 2008-05-13 : 07:48:13
Is it because you have passwords that aren't being saved with the package?
What does the log say?

==========================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
Go to Top of Page

karthik_padbanaban
Constraint Violating Yak Guru

263 Posts

Posted - 2008-05-13 : 09:58:08
quote:
Originally posted by nr

Is it because you have passwords that aren't being saved with the package?
What does the log say?

==========================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.



now the LOG says:
The job failed. The Job was invoked by User karthikm. The last step to run was step1(Step1).,
executed as User: zsw056\SYSTEM package execution failed the job failed
Go to Top of Page

rgombina
Constraint Violating Yak Guru

319 Posts

Posted - 2008-05-13 : 10:11:30
Try job and steps owner karthikm. Also try to use SQL Agent (job and step owner too) if you can and see if it works.

Test it with an "sa" account and make it work and then mess around with proxy. Go backward and it may help you.

Go to Top of Page

karthik_padbanaban
Constraint Violating Yak Guru

263 Posts

Posted - 2008-05-13 : 10:35:27
quote:
Originally posted by rgombina

Try job and steps owner karthikm. Also try to use SQL Agent (job and step owner too) if you can and see if it works.

Test it with an "sa" account and make it work and then mess around with proxy. Go backward and it may help you.





Now I have changed every thing under "sa" account now also the job failed and log returns,

The job failed. The Job was invoked by Schedule 10(edatesting). The last step to run was step1(Step1).,
executed as User: zsw056\SYSTEM package execution failed the job failed

Go to Top of Page

sumit.microsofttech
Starting Member

6 Posts

Posted - 2008-05-13 : 10:41:09
If you are using any connection to database or any server which requires password, then you have to create configuration file for the package, because everytime the package is executed it needs the password. So to overcome this problem you can create configuration file and add that in SQL Agent Job.

Note: Dont forget to update the passwords in configuration file because SSIS doesnt save the password for you. It leaves the value blank so you have to manually feed the value.

Hope it will solve your problem..
Go to Top of Page

karthik_padbanaban
Constraint Violating Yak Guru

263 Posts

Posted - 2008-05-13 : 10:58:28
quote:
Originally posted by sumit.microsofttech

If you are using any connection to database or any server which requires password, then you have to create configuration file for the package, because everytime the package is executed it needs the password. So to overcome this problem you can create configuration file and add that in SQL Agent Job.

Note: Dont forget to update the passwords in configuration file because SSIS doesnt save the password for you. It leaves the value blank so you have to manually feed the value.

Hope it will solve your problem..


How to create a configuration file for sql agent job.,
and how to add that to it.,
Go to Top of Page

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2008-05-13 : 11:39:56
What protection level you set while deploying package to SQL job? Expand job (+) sign and tell us what you see or if you have set to event log check it.
Go to Top of Page

karthik_padbanaban
Constraint Violating Yak Guru

263 Posts

Posted - 2008-05-14 : 02:55:47
quote:
Originally posted by sodeep

What protection level you set while deploying package to SQL job? Expand job (+) sign and tell us what you see or if you have set to event log check it.



I did not set any protection level while deploying.,
when I expand job,I could see all the job which i have created.,
Go to Top of Page

karthik_padbanaban
Constraint Violating Yak Guru

263 Posts

Posted - 2008-05-14 : 04:31:46
quote:
Originally posted by karthik_padbanaban

quote:
Originally posted by sodeep

What protection level you set while deploying package to SQL job? Expand job (+) sign and tell us what you see or if you have set to event log check it.



I did not set any protection level while deploying.,
when I expand job,I could see all the job which i have created.,



I have solved the problem.,I have used different authentication in connetions., now its clear, thank you for all your comments
Go to Top of Page

amritsandhu
Starting Member

3 Posts

Posted - 2008-05-22 : 06:02:18
Hi Karthik, can you please explain more on how you solved this? I have a similar issue. Or do you have an email I can rech you on?
Amrit

quote:
Originally posted by karthik_padbanaban
I have solved the problem.,I have used different authentication in connetions., now its clear, thank you for all your comments

Go to Top of Page

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2008-05-22 : 10:31:04
she has already given answer. What issue are you having?
Go to Top of Page

amritsandhu
Starting Member

3 Posts

Posted - 2008-05-22 : 11:02:20
I don't understand how she solved the problem. What steps did she take to solve it?
quote:
Originally posted by sodeep

she has already given answer. What issue are you having?

Go to Top of Page

rgombina
Constraint Violating Yak Guru

319 Posts

Posted - 2008-05-22 : 12:43:04
I have solved the problem.,I have used different authentication in connetions., now its clear, thank you for all your comments
Go to Top of Page

amritsandhu
Starting Member

3 Posts

Posted - 2008-05-23 : 03:27:36
I see. I think in that case my problem is slightly different, however I get the same error message.
I have in fact used the same sql server authentication for connections in the packages. I can run the package on it's own, however when I attempt to run it from a job, it fails. I know it has something to do with permissions of the package but I haven't worked out what.

The package essentially grabs data from sql server1 with Sql server 2000. This data is stored on reporting server (sql server 2005). The server with the SSIS job is server 3 with sql server 2005.

Any ideas on this guys?
Go to Top of Page

nr
SQLTeam MVY

12543 Posts

Posted - 2008-05-28 : 04:25:30
Enable logging in the package and see what the log says.

==========================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.
Go to Top of Page
    Next Page

- Advertisement -