March 16, 2011 at 1:28 am
Hi,
I have created a package which loops through a folder containing Excel inputs and loads in to the SQL server database. I have deployed the package in SQL server and it is executing as expected when through the execute package utility.
I have created a job to schedule this package. But the job fails with the below error message...
Executed as user: ******. Microsoft (R) SQL Server Execute Package Utility Version 10.50.1600.1 for 32-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Option "8.0;HDR=NO;IMEX=1;;" is not valid. The command line parameters are invalid. The step failed.
The command line in the SQL job is:
/SQL "\PMT_Import" /SERVER ****** /CONNECTION "Config_Conn";"\"Data Source=******;Initial Catalog=*****;Provider=SQLNCLI10.1;Integrated Security=SSPI;Auto Translate=False;\"" /CONNECTION "Test_Conn";"\"Data Source=*****;Initial Catalog=*****;Provider=SQLNCLI10.1;Integrated Security=SSPI;Application Name=SSIS-Package1-{93CFDE27-19E5-4FBF-AB4C-FE3231560B20}******;Auto Translate=False;\"" /CONNECTION "PMTFiles_Conn";"\"Provider=Microsoft.Jet.OLEDB.4.0;Data Source=F:\Test1.xls;Extended Properties=""EXCEL 8.0;HDR=NO;IMEX=1;"";\"" /X86 /CHECKPOINTING OFF /REPORTING E
I'm unable to understand why the job is failing when the same package is working as expected when running through the execute package utility. Kindly suggest...
Regards,
Krishna Chaitanya.
March 16, 2011 at 5:12 am
March 16, 2011 at 5:34 am
KrishnaChaitanya (3/16/2011)
Hi,I have created a package which loops through a folder containing Excel inputs and loads in to the SQL server database. I have deployed the package in SQL server and it is executing as expected when through the execute package utility.
I have created a job to schedule this package. But the job fails with the below error message...
Executed as user: ******. Microsoft (R) SQL Server Execute Package Utility Version 10.50.1600.1 for 32-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Option "8.0;HDR=NO;IMEX=1;;" is not valid. The command line parameters are invalid. The step failed.
The command line in the SQL job is:
/SQL "\PMT_Import" /SERVER ****** /CONNECTION "Config_Conn";"\"Data Source=******;Initial Catalog=*****;Provider=SQLNCLI10.1;Integrated Security=SSPI;Auto Translate=False;\"" /CONNECTION "Test_Conn";"\"Data Source=*****;Initial Catalog=*****;Provider=SQLNCLI10.1;Integrated Security=SSPI;Application Name=SSIS-Package1-{93CFDE27-19E5-4FBF-AB4C-FE3231560B20}******;Auto Translate=False;\"" /CONNECTION "PMTFiles_Conn";"\"Provider=Microsoft.Jet.OLEDB.4.0;Data Source=F:\Test1.xls;Extended Properties=""EXCEL 8.0;HDR=NO;IMEX=1;"";\"" /X86 /CHECKPOINTING OFF /REPORTING E
I'm unable to understand why the job is failing when the same package is working as expected when running through the execute package utility. Kindly suggest...
Regards,
Krishna Chaitanya.
Looks like it might be a problem with the space character between EXCEL and 8.0 - as the 'EXCEL' bit does not appear in the error message. Maybe you need another set of quotes in there (somewhere:w00t:) to resolve that.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply