March 30, 2009 at 10:53 am
I have a SSIS package that has a Send Mail Task control. When I run the package from Visual Studio the email sends with no problem, but the package fails when I initiate or schedule it from the SQL Server Agent.
I need help solving this issue.
Thanks
March 30, 2009 at 2:06 pm
Does your SMTP connection have any (SSIS) configurations?
March 30, 2009 at 2:53 pm
no...I am not using any configurations. should I?
Thanks
March 30, 2009 at 4:53 pm
can u post your smtp connection string?
March 31, 2009 at 6:22 am
Leland Walker (3/30/2009)
I have a SSIS package that has a Send Mail Task control. When I run the package from Visual Studio the email sends with no problem, but the package fails when I initiate or schedule it from the SQL Server Agent.I need help solving this issue.
Thanks
Can you post what is the error when you execute from SQL Server Agent? Do you use proxy account in SQL Server Agent or you use the default execution account? Most probably the account (which is usually the local system account) doesn't have permissions to access your SMTP server.
April 1, 2009 at 10:23 pm
I guess it has nothing to do with any configurations, When you are running in IDE you use your login credintials, but when you schedule you use Sql service account. you need to look onto this.
go to services(My Computer (right click) > Manage > services and applications (tab) > services) and see on what account this sql server agent is running and the permission it has.
cheers,
Naveen
April 2, 2009 at 6:28 am
I checked a few things out on my end and it appears that the SQL Server Agent can not initiate or run scheduled jobs from the Standard Edition of SQL Server 2005.
I hope there is a work around.
Thanks for the responses.
April 2, 2009 at 6:32 am
Leland Walker (4/2/2009)
I checked a few things out on my end and it appears that the SQL Server Agent can not initiate or run scheduled jobs from the Standard Edition of SQL Server 2005.I hope there is a work around.
Thanks for the responses.
What do you mean by "cannot initiate or run" ? Is the default service account the problem? If that is the case you have to setup and use a proxy account for your package execution.
April 2, 2009 at 6:35 am
As far as i know you can't edit the following, so your going to have to Import the package again, this time, under the:
Protection Level select 'Rely on server storage and roles for access control'
then you will need to edit the job to point that this pakage....
April 2, 2009 at 6:53 am
What I meant was when I try to start the job, by click on Start Job from the SQL Server Agent, it fails....If I schedule the job to run it fails as well.
This is the error message I'm getting.
The task "Send Mail Task" cannot run on this edition of Integration Services.
April 2, 2009 at 7:00 am
Leland Walker (4/2/2009)
What I meant was when I try to start the job, by click on Start Job from the SQL Server Agent, it fails....If I schedule the job to run it fails as well.This is the error message I'm getting.
The task "Send Mail Task" cannot run on this edition of Integration Services.
What edition of SQL Server do you have in use? Btw you can send emails using scripts. Check here for ideas.
April 2, 2009 at 7:34 am
I'm using SQL SERVER 2005 - Standard Edition.
I tried using scripts to send the e-mail and the job failed that way as well.
Thanks for the help.
April 2, 2009 at 7:52 am
Leland Walker (4/2/2009)
I'm using SQL SERVER 2005 - Standard Edition.I tried using scripts to send the e-mail and the job failed that way as well.
Thanks for the help.
I'm not able to find a Microsoft sheet listing what each edition of SQL Server contains, but I think your SQL Server installation is corrupted. You should have Send Mail Task and Script Task available in the Standard Edition. You may have to reinstall your SQL Server + Integration Services.
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply