SYMPTOMS: The package when executes individually runs successfully. But when executing the package through sql server job it crashes with error in the job history.

SOLUTION: The solution is simple there is a problem with your command line option for the job step. Modify it to get the package running.

EXAMPLE: Until now you may be unclear that what i am talking about. Let me illustrate with an example. I created an SSIS package which executes successfully without a job. But when i make it a part of job it crashes with the above mentioned error.

The auto-generated command line when i select the data sources was

/SQL “\DVA_PNC_DTS” /SERVER “SERVER01″ /CONNECTION “Database Connection ADO”;”\”Data Source=SERVER03;User ID=User;Initial Catalog=”"DB1″”;Persist Security Info=True;” /CONNECTION “Database Connenction”;”\”Data Source=SERVER04;User ID=User;Initial Catalog=DB2;Provider=SQLNCLI.1;Persist Security Info=True;Auto Translate=False;” /CONNECTION “Input Connection”;”C:\Schema.csv” /CONNECTION Output;”C:\Output.txt” /MAXCONCURRENT ” -1 ” /CHECKPOINTING OFF

I manually edit the command line and remove some extra quotes and backslashes and it started working perfectly It looks like this:

/SQL “\DVA_PNC_DTS” /SERVER SERVER01  /CONNECTION “Database Connection ADO”;”Data Source=SERVER03;User ID=User;Initial Catalog=DB1;Persist Security Info=True;” /CONNECTION “Database Connenction”;”Data Source=SERVER04;User ID=User;Initial Catalog=DB2;Provider=SQLNCLI.1;Persist Security Info=True;Auto Translate=False;” /CONNECTION “Input Connection”;”C:\Schema.csv” /CONNECTION Output;”C:\Output.txt” /MAXCONCURRENT ” -1 ” /CHECKPOINTING OFF /REPORTING E

Hope this may help anyone.