The step did not generate any output. Is it a Script Task problem
My SSIS package when executed through SQL Server Job was throwing the below error; The step did not generate any output. The return value was unknown. The process exit code was -532459699. The step failed. After a long trial and error I found that only after adding Script task inside my For each container, I get the above error. What is the actual problem? Can somebody help/ Thanks in advace.
April 13th, 2011 1:39am

Can you execute the package in BIDS successfully?http://www.rad.pasfu.com
Free Windows Admin Tool Kit Click here and download it now
April 13th, 2011 1:50am

Maybe this thread can help: http://social.msdn.microsoft.com/Forums/en/vswpfdesigner/thread/378eae0a-ca38-48a8-875b-917b73ef6660MCTS, MCITP - Please mark posts as answered where appropriate.
April 13th, 2011 1:50am

Can you execute the package in BIDS successfully? http://www.rad.pasfu.com Yes. Yes. I can execute it in BIDS. But, this job is actually created on a different machine. Not on my local.
Free Windows Admin Tool Kit Click here and download it now
April 13th, 2011 2:02am

Maybe this thread can help: http://social.msdn.microsoft.com/Forums/en/vswpfdesigner/thread/378eae0a-ca38-48a8-875b-917b73ef6660 MCTS, MCITP - Please mark posts as answered where appropriate. I already have .Net 3.5 SP1 installed.
April 13th, 2011 2:04am

could you paste script task code here? http://www.rad.pasfu.com
Free Windows Admin Tool Kit Click here and download it now
April 13th, 2011 2:26am

could you paste script task code here? http://www.rad.pasfu.com I get this error if I just place a plain script task with out any code. Otherwise the script task code will look like this: Using System.IO; If(File.Exists(FilePath)) Dts.variables[User::varIsFileExists].Value = 1; else Dts.variables[User::varIsFileExists].Value = 0; This script task is placed inside a For each loop which reads this FilePath from a SQL table one by one.
April 13th, 2011 2:31am

the account which sql server agent service runs under it probably hasn't permission to the FilePath in defined in the script task.http://www.rad.pasfu.com
Free Windows Admin Tool Kit Click here and download it now
April 13th, 2011 2:36am

I have one more finding here. When i create a job on my local machine using the same package, it runs successfully. The error occurs only when i install the packge in another machine and create job in that machine. Cant I install a package to another machine's SQL server from my local machine, by specifying the Server name of tat machine with user id nd password? Can anybody figure out what is creating the problem?
April 13th, 2011 2:42am

My guess is that the problem is around DTS.TaskResult. Script Task is not setting value for DTS.TaskResult. Check your script if it has : DTS.TaskResult = (int)ScriptResults.Failure or DTS.TaskResult = (int)ScriptResults.Success Please vote for answer if it helps you.
Free Windows Admin Tool Kit Click here and download it now
April 13th, 2011 2:45am

I have one more finding here. When i create a job on my local machine using the same package, it runs successfully. The error occurs only when i install the packge in another machine and create job in that machine. Cant I install a package to another machine's SQL server from my local machine, by specifying the Server name of tat machine with user id nd password? Can anybody figure out what is creating the problem? Did you checked the permission to that folder for sql server agent service account as I mentioned in my previous post? http://www.rad.pasfu.com
April 13th, 2011 2:50am

Yes. The proxy I am using has access permission.
Free Windows Admin Tool Kit Click here and download it now
April 13th, 2011 3:30am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics