Attempted to read or write protected memory RRS feed

  • Question

  • Hello,

    I'm getting the following error message intermittently when trying to execute SSIS packages. The SSIS packages are hosted on SQL server 2008,10.0.2531, X64 and 100GB f RAM and with more than 10GB available memory on the server.  The package is trying to transfer data from one server to other. The source server is SQL Server 2005,x64,SP3 and destination is SQL Server 2008,10.0.2531,x64.

    when the restart the same SSIS package (SQLAgen job) it works fine.  I do not see any access voilation/memory assertions on the server. I would like to understand and know the root cause of this error message.  Is it related to SSIS or DB engine??. Any tools or troubleshooting techniques would help to isolate the issue..

    I have posted the same question in SSIS forum and reason i posted here is because it is relaetd to memory issue and i'm hoping to get replies from DB engine/performance issues tuning experts..

    any help highly appreciated.....

    ERROR :

    Error: 2013-07-05 1:55:10.77

      Code: 0xC002F210
       Source: SQL - Get Source Logic Execute SQL Task 
       Description: Executing the query "EXECUTE Control.GetSourceLogic ?, ? OUTPUT;" failed with the following error: "Attempted to read or write protected memory. This is often an indication that other memory is corrupt.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
    End Error
    DTExec: The package execution returned DTSER_FAILURE (1).
    Started:  9:53:19 PM
    Finished: 9:55:28 PM
    Elapsed:  128.608 seconds

    Sunday, July 7, 2013 3:13 AM


All replies

  • Hello ,

    Windows error reporting would have generated dump when we hit the above error. Look for dumps in %LOCALAPPDATA%\CrashDumps

    Once you get the dump follow the step in http://mssqlwiki.com/2012/10/16/sql-server-exception_access_violation-and-sql-server-assertion/ and post the stack.

    I will help you to find the cause.

    Thank you,

    Karthick P.K |My blogs|My Scribbles|Twitter|My Facebook Group|


    Please click the Mark as answer button and vote as helpful if this reply solves your problem

    • Proposed as answer by Fanny Liu Friday, July 12, 2013 1:35 AM
    • Marked as answer by Fanny Liu Tuesday, July 23, 2013 6:42 AM
    Monday, July 8, 2013 1:54 PM
  • Thanks Karthick.

    We have this issue again last week, but I DO NOT see any dumps generated at %LOCALAPPDATA%\CrashDumps.

    In fact I do not see CrashDumps folder at all.

    The following is the path for LocalAppData - C:\Users\<service account>\AppData\Local\CrashDumps

    Any other thoughts??/

    Thursday, December 5, 2013 12:14 PM
  • If you are still having problems, the first thing I would suggest is installing the latest service pack and see if the problem is already fixed by MS.  MS is horrible about publicly documenting all fixes in patches. 

    Please see:


    Thursday, December 5, 2013 1:23 PM