RE: Executing a SSIS package from a SQL Job 1

[allyne]

Hi Everyone,

I have an SSIS package that I have imported into our Report Server and I runs fine. I now need to be able to schedule this to run in a job but when I run the job I receive the following error message.

Message
Executed as user: AHS\nextgen. Microsoft (R) SQL Server Execute Package Utility Version 10.50.2500.0 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Argument "ngvrsql.NGProd" for option "connection" is not valid. The command line parameters are invalid. The step failed.

the command line looks something like this:

/SQL "\WellPartner_Enc_Based" /SERVER "SRC-NGReport" /CONNECTION ENCTR;"\\SVH-FS3\Home-SRC\purnec\WellPartner\ENCTR_SVH201201231_1.pipe" /CONNECTION "Flat File Connection Manager";"\\SVH-FS3\Home-SRC\purnec\WellPartner\ENCTR_SVH20121231_1.pipe" /CONNECTION "ngvrsql.NGProd";"\"Data Source=ngvrsql;Initial Catalog=NGProd;Provider=SQLOLEDB.1;Integrated Security=SSPI;\"" /CONNECTION "ngvrsql.NGProd 1";"\"Data Source=ngvrsql;Initial Catalog=NGProd;Provider=SQLNCLI10.1;Integrated Security=SSPI;Application Name=SSIS-WellPartner_Enc_Based_Old-{88C8533F-9FC1-4F43-9B64-710C1C9F9299}ngvrsql.NGProd 1;Auto Translate=False;\"" /CONNECTION "SSH Connection Manager

Any Ideas?

Thanks for your help!

 

[xlbo]

SQL Server agent needs to have same permissions as you to be able to run the package

Rgds, Geoff

We could learn a lot from crayons. Some are sharp, some are pretty and some are dull. Some have weird names and all are different colours but they all live in the same box.

Please read FAQ222-2244 before you ask a question

 

[allyne]

Thanks! That was it!