Share via

SSIS Package Error: The attempt to add a row to the Data Flow tank buffer failed with error code 0x8007000E

Prakash 0 Reputation points
2025-03-21T01:59:02.95+00:00

Hi,

Wet are migrating SSIS Packages from SQL 2008 to SQL 2016 and getting below errors when running SSIS 2016 package through command line (or) scheduling tool . Same package executed successfully if running through SQL Agent.

Error No 1: The attempt to add a row to the Data Flow tank buffer failed with error code 0x8007000E

Error No 2: A buffer failed white allocating 20842848 bytes

Error No 3: The system reports 86 percent memory load. There are 8589328384 bytes of physical memory with 1174040576 bytes free. There are 4294836224 bytes of virtual memory with 298242048 bytes free.

Error No 4: SSIS Error Code DTS_ E_PRIMEOUTPUTFAILED. The PrimeOutput method on Flat File source returned error code 0xC02020C4

I have adjusted DefaultBufferMaxRows to 200000 and DefaultBufferSize to 20971520 and changed ForcedExecutionValuetype to 64 bit biut still getting same error.

SSIS 2016 Server have 16GB of memory and my source file(CSV) have 4.5 million records.SSIS 2016 server is 64 bit and SSIS packages are in 32 bit.

Data flow task have Flat file source, script component and OLEDB Destination. Data access mode in target is, Table of view - Fast load

please provide solution or fix for this issue.

SQL Server Integration Services
SQL Server Integration Services
A Microsoft platform for building enterprise-level data integration and data transformations solutions.
2,681 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Kuruba Gowthami (US) 0 Reputation points
    2025-04-15T14:17:18.29+00:00

    I think you are running into 32-bit memory limitations while dealing with a large flat file (~4.5 million records), especially during command line or SQL Agent execution.

    Even though your Server is 64-bit with 16 GB RAM. You have increased DefaultBufferMaxRows and DefaultBufferSize

    SSIS may still be using the 32-bit runtime.

    Try the below Steps:

    1. Make sure You are Using 64-bit Runtime

    When executing the Command Line: Use dtexec from the 64-bit path

    C:\Program Files\Microsoft SQL Server\130\DTS\Binn\dtexec.exe

    For SQL Agent: Go to Job Step > Execution Options and uncheck 'Use 32-bit runtime'.

    1. Optimize SSIS Buffer Settings

    update as below

    DefaultBufferMaxRows = 100000

    DefaultBufferSize = 10485760 (10 MB)

    Avoid very large buffers (like 20 MB+) as they increase fragmentation risk.

    1. Check Flat File Source Settings

    Ensure correct column delimiter, text qualifier, and row delimiter.

    Consider using a Script Component to better handle parsing if data is messy.

    1. Split the File / Process in Chunks

    If possible, split your 4.5 million row CSV into smaller batches and process them incrementally.

    1. Increase Virtual Memory on the Server

    Sometimes increasing the paging file size manually helps SSIS buffer allocations.

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.