May 30, 2010 at 6:31 pm
Hi All,
I am trying to schedule SSIS package in SQL-Agent. Type is cmdexec. Below is the statement used.
dtexec.exe /FILE "\etworkserver\Package\audit\Audit.dtsx" /CONFIGFILE "\etworkserver\package\Audit\Audit.dtsconfig" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING E
I am getting the error as
"The process could not be created. The system cannot find the file specified". Please let me know what could be wrong?
Thanks.
[font="Arial"]BASKAR BV
http://geekswithblogs.net/baskibv/Default.aspx
In life, as in football, you won’t go far unless you know where the goalposts are.[/font]
June 1, 2010 at 1:16 am
This was removed by the editor as SPAM
June 1, 2010 at 1:29 am
This was removed by the editor as SPAM
June 1, 2010 at 3:19 am
stewartc-708166 (6/1/2010)
Why execute as type os command?a SQL job can execute a step of type "SQL Server Integration Services Package", irrespective of whether the package is stored in SQL Server or on the file system.
There are several reasons to do this:
* if you have a 64-bit server but you want to run the package in 32-bit (needed to process Excel files)
* apparantly, but I have not tested this, the logging is better with an OS command. I had a link to an article that explained this, but it appears to be broken.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
June 1, 2010 at 3:37 am
This was removed by the editor as SPAM
June 2, 2010 at 1:40 pm
I have the same problem but I ran it as SSIS package.
It kept saying it did not recognize the connection on the input file //server/filename.
June 2, 2010 at 1:41 pm
Also when I ran it under Business management studio, the package worked.
It did not work when I ran it in the job.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply