BUG: You may receive an access violation error message when you try to run an SSIS package in SQL Server 2005

Article translations Article translations
Article ID: 924016 - View products that this article applies to.
Bug #: 898 (SQL Hotfix)
Expand all | Collapse all

SYMPTOMS

Consider the following scenario. In Microsoft SQL Server 2005, you try to run a SQL Server Integration Services (SSIS) package. The SSIS package transfers data between two instances of SQL Server 2005. In this scenario, you may receive an access violation error message. When this problem occurs, the Microsoft Windows Application log contains an event that documents the system error message. The system error message resembles the following:
DTExec.EXE - Application Error The exception unknown software exception (0x40000015) occurred in the application at location 0x7ee8bd9e.
Note This problem occurs when Lookup transformations that are in the SSIS package are executed in parallel. This problem does not occur when Lookup transformations that are in the SSIS package are executed sequentially.

CAUSE

This problem occurs when Lookup transformations from multiple data flow tasks share the same cache area. Lookup transformations may share the same cache area when the text in the SQLCommand property of one Lookup transformation that isin a data flow task is the same as the text in the SQLCommand property of a Lookup transformation that is in another data flow task.

WORKAROUND

To work around this problem, use one of the following workarounds:
  • Set the MaxConcurrentExecutables property of the SSIS package to 1.This setting prevents parallel execution of SSIS tasks.
  • Configure the Lookup transformation to use no caching.
  • If the Lookup transformations are in different child packages, set the value of the ExecuteOutOfProcess property of each child package to True
  • Change the text in the SQLCommand property of one SSIS Lookup transformation so that it differs from the text in the SQLCommand property of the second Lookup transformation. The following examples of small modifications show how to perform this workaround:

    Example 1
    1. Set the SQLCommand property of the first Lookup transformation to the following.
      select * from [dbo].[table1] --comment to differentiate the Lookup SQLCommands
    2. Set the SQLCommand property of the second Lookup transformation to the following.
      select * from [dbo].[table1] --different comment
    Example 2
    1. Create two views named View1 and View2. Define both views by using an SQL query that resembles the following.
      select * from [dbo].[Table1]
    2. Set the SQLCommand property of the first Lookup transformation to the following.
      select * from [dbo].[View1]
    3. Set the SQLCommand property ofthe second Lookup transformation to the following.
      select * from [dbo].[View2]

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

For more information about the MaxConcurrentExecutables property, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn2.microsoft.com/en-us/library/microsoft.sqlserver.dts.runtime.package.maxconcurrentexecutables.aspx
For more information about the Lookup transformation in SSIS, visit the following MSDN Web site:
http://msdn2.microsoft.com/en-us/library/ms141821.aspx

Properties

Article ID: 924016 - Last Review: September 17, 2011 - Revision: 3.0
APPLIES TO
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Standard X64 Edition
  • Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Enterprise X64 Edition
  • Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Developer Edition
Keywords: 
kbbug kbtshoot KB924016

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com