SSIS error - Argument "SMTP" for option "connection" is not valid

I have built an SSIS package that works just fine in BIDS.  I would like to schedule the package in SQL Server Agent.  After I set it up I get the following error:

Argument "SMTP" for option "connection" is not valid

I also ran it using using command line DTExec and I get the same error.  Not sure why.  The command line created by DETexecUI is below.

/FILE "D:\SSIS\Packages\SageDataTransfer.dtsx"  /CONNECTION DestinationConnectionOLEDB;"\"Data Source=EVERESTDA;Initial Catalog=AGC_PROD;Provider=SQLNCLI10;Integrated Security=SSPI;Auto Translate=false;\"" /CONNECTION "SMTP Connection Manager";"\"SmtpServer=10.0.8.14;UseWindowsAuthentication=True;EnableSsl=False;\"" /CONNECTION SourceConnectionOLEDB;"\"Data Source=AGCCRMDB;User ID=sa;Initial Catalog=CRM58;Provider=SQLNCLI10.1;Persist Security Info=True;Auto Translate=false;Application Name=SSIS-SageDataTransfer-{7FE010B9-6D29-4D58-9784-448A4CC9F4FE}SourceConnectionOLEDB;\"" /CHECKPOINTING OFF /REPORTING E

Thanks for the help,
Miguel
agcsupportAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Reza RadConsultant, TrainerCommented:
check the account who sql server agent started under that has permission? it can be network service or administrative account
0
agcsupportAuthor Commented:
I thought it would be permissions myself but it is not.  I already cheked.
0
Megan BrooksSQL Server ConsultantCommented:
This is likely a problem with the quotes on the command line. Here's a similar case:
http://www.sqlservercentral.com/Forums/Topic388545-148-1.aspx 
It looks like you have the right idea, but something is slightly off. Just a guess, maybe /CONNECTION "SMTP Connection Manager" should be /CONNECTION "\"SMTP Connection Manager\""? I haven't had to solve one of these quote puzzles in years and I am rusty.
0
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

agcsupportAuthor Commented:
I did google my problem and saw that article.  I made those exact changes and it did not work for me.  
0
Megan BrooksSQL Server ConsultantCommented:
Focus on the part of the command line adjacent to "SMTP Connection Manager." Instead of inserting quotes, you can try removing spaces altogether in various places (e.g. "SMTPConnectionManager"). The resulting command lines won't work, but doing this may clarify where the problem is by producing different error messages.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
agcsupportAuthor Commented:
Thanks rscowden.

I finally eneded up not choosing the connection strings as part of my command line and it worked fine.  My batch file executes the following command and it runs fine.

DTexec /FILE "D:\SSIS\Packages\JDEtoEverest.dtsx" /CHECKPOINTING OFF  /REPORTING EWCDI
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.