SSIS 2012 heap corruption in connection string in the project level connection manager

SSIS 2012 heap corruption in connection string in the project level connection manager by JunChen

Closed

Type:	Bug
ID:	779018
Opened:	2/11/2013 7:32:51 PM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

In SSIS 2012, if the packages uses project level shared connection managers, and the packages contains several "execute package task" running in parallel (running in-process), heap corruption may occur on copying connection string from the shared project level connection manager.

Details (expand)

English

SQL Server 2012 - Enterprise Edition

Integration Services (DTS)

Windows Server 2008 R2 (all editions)

English

We have a repro environment, but it is too large to share (5GB)

1. The main package has a container which have two "execute package task" calling ChildPackage1 and ChildPackage2 in parallel.
2. In ChildPackage1, it contains 16 "execute package task"s running in parallel. And each child package contains a simple "Execute SQL Task" following by a data flow. In the data flow, it just gets some data from SQL Source and add a derived column, and then output to the destination SQL table (using fast load).
3. In ChildPackage2, it has the similar as ChildPackage1.
4. All packages share the same project level connection manager.
5. From SSMS execute the main package.

During the validation phase, an error is reported. The error says heap corruption detected.

If we enable full page heap, we will see dump files generated, and it is related to copying the connection string in the project level connection manager.

See the dumps attached.

The package runs successfully.

File Name	Submitted By	Submitted On	File Size
ErrorDumps.rar	JunChen	2/11/2013	2.39 MB

Hello JunChen. Thanks for bringing this to our attention. This problem has been fixed. The correction will be included in a future release for SQL Server. -Walter A Jokiel, Program Manager, SQL Server (wajokiel@microsoft.com)