| Author |
Topic |
|
Srain
Starting Member
23 Posts |
Posted - 2008-07-09 : 14:11:21
|
| Hi All,I have created a simple SSIS package which exports the table data to an excel file. The package runs fine. But the package fails with below error while scheduled as a Job.Error - The command line parameters are invalid. The step failed. Job Properties are as specified - Type - SQL Server Integration Services PackageRun As - SQL Agent Service AccountPackage Source - File SystemI couldn't able to find where I made a mistake. Please advise. |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-07-09 : 14:13:32
|
| What protection level did you set? Use rely on server if you don't want password protected.Also does SQL server agent account has access to location of desired Excel file. |
 |
|
|
Srain
Starting Member
23 Posts |
Posted - 2008-07-09 : 14:20:48
|
Hi,I am new to SSIS. Please let me know how do I check the protection level & whether SQL server agent account has access to location of desired Excel file.quote: Originally posted by sodeep What protection level did you set? Use rely on server if you don't want password protected.Also does SQL server agent account has access to location of desired Excel file.
|
 |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-07-09 : 14:24:35
|
| Where is package stored? |
 |
|
|
Srain
Starting Member
23 Posts |
Posted - 2008-07-09 : 14:40:36
|
Package path \Maintenance Plans\Packageprotection level is rely on server.quote: Originally posted by sodeep Where is package stored?
|
 |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-07-09 : 23:20:07
|
| If you export data to remote excel file, sql agent service account needs permission to access that file. That means you have to start sql agent with domain account. |
 |
|
|
Srain
Starting Member
23 Posts |
Posted - 2008-07-10 : 01:27:42
|
The Package is failed with below error message for String type data export "Column ProjName & ProjName can not convert between unicode and non-unicode string data type."Any help would be much appreciated.quote: Originally posted by rmiao If you export data to remote excel file, sql agent service account needs permission to access that file. That means you have to start sql agent with domain account.
|
 |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2008-07-10 : 01:33:27
|
| Are both of them declared as unicode datatype? |
 |
|
|
Srain
Starting Member
23 Posts |
Posted - 2008-07-10 : 05:37:01
|
The String data isssue resolved though but still job is failing.The SSIS package is running fine when executed in BI window. But the same fails in the Job with error "command line parameters are invalid"quote: Originally posted by visakh16 Are both of them declared as unicode datatype?
|
 |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2008-07-10 : 05:44:21
|
quote: Originally posted by Srain The String data isssue resolved though but still job is failing.The SSIS package is running fine when executed in BI window. But the same fails in the Job with error "command line parameters are invalid"quote: Originally posted by visakh16 Are both of them declared as unicode datatype?
Thats means there's some probelm with values passed to parameters in command line. |
 |
|
|
Srain
Starting Member
23 Posts |
Posted - 2008-07-10 : 06:01:31
|
The command line parameters - /SQL "\Maintenance Plans\TEST" /SERVER TEST /CONNECTION "TEST.TESTPROJ";"Data Source=TEST;Initial Catalog=TESTPROJ;Provider=SQLNCLI.1;Integrated Security=SSPI;Auto Translate=False;" /CONNECTION "Excel Connection Manager";"Provider=Microsoft.Jet.OLEDB.4.0;Data Source=X:\Documents\ExportExcel\TEST.xls;Extended Properties=""EXCEL 8.0;HDR=YES"";" /VALIDATEEven if I have added the sql server login still no luck.quote: Originally posted by visakh16
quote: Originally posted by Srain The String data isssue resolved though but still job is failing.The SSIS package is running fine when executed in BI window. But the same fails in the Job with error "command line parameters are invalid"quote: Originally posted by visakh16 Are both of them declared as unicode datatype?
Thats means there's some probelm with values passed to parameters in command line.
|
 |
|
|
|