CODEWITHSUNDEEP
sql-serverssisetlscript-component
Mike de H
Mike de H

Reputation: 651

SSIS Data Flow Task Error: Object reference not set to an instance of an object

I am trying to create a package containing several Data Flow tasks in them. The tasks are fairly similar in nature, but contain fairly important differences.

I have tried to copy the task, then change the things which need changing.

When I run the task by itself it runs fine, however when I run it with all the other tasks in the package I get the below error:

Object reference not set to an instance of an object. at ScriptMain.Input0_ProcessInputRow(Input0Buffer Row) at UserComponent.Input0_ProcessInput(Input0Buffer Buffer) at UserComponent.ProcessInput(Int32 InputID, String InputName, PipelineBuffer Buffer, OutputNameMap OutputMap) at Microsoft.SqlServer.Dts.Pipeline.ScriptComponent.ProcessInput(Int32 InputID, PipelineBuffer buffer) at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.ProcessInput(Int32 inputID, PipelineBuffer buffer)

Not the most friendly error message.

Can anyone tell me what this is and how to fix it? I assume that there is some variable or other attribute which is being repeated, but which one?

Note that many of the columns over the several data flow tasks will have the same column names.

Upvotes: 0

Views: 26190

Answers (3)

Gamzosh
Gamzosh

Reputation: 153

I had this issue with my send mail task.

As I was using a file connection for my body of the email, I had to create a new file connection and it worked fine.

Upvotes: 1

Mike de H
Mike de H

Reputation: 651

I figured it out in the end. The reason was that the second level objects need to be explicitly declared.

I had 

public class Level2
{
    public string Somevalue { get; set; }
}
public class RootAttributes
{
    public Level2 lvl2 { get; set; }
    public string Somevalue2 { get; set; }
}

It should have been

public class Level2
{
    public string Somevalue { get; set; }
}
public class RootAttributes
{
    public Level2 lvl2 = new Level2;
    public string Somevalue2 { get; set; }
}

The weird thing was that the top method worked in several other places.

Upvotes: 1

Guru Rajan
Guru Rajan

Reputation: 1

Use the package run report in vs 2012 to identify in which DFT task package got failed. Use the view code option of the package to see the whether all the DFT task having proper input.

Upvotes: 0

Related Questions