locked
Error: .NET Framework execution was aborted by escalation policy because of out of memory. RRS feed

  • Question

  • we are seeing this error in our production sql server. sql is 2008 R2 with sp3  64 bit and never had this error before, no change in memory 118 G, total server memory is 125 G or anything else configuration side. so, wanna a know without restart, how can we resolve this issue?

    Checked each and everything in setting but when we run this code in SSMS new query window, it is not even taking a second to think and returned this error.

    .NET Framework execution was aborted by escalation policy because of out of memory.

    declare
    @p_strap [varchar] (25)
    , @p_doc_tp [varchar] (2) --Only hearing evidence doc types will be processed ('HE','HS','SE')
    , @p_file_name [varchar] (200)



    , @src_file varchar(1000)
    , @src_status int
    , @src_size int
    , @src_created datetime
    , @src_written datetime
    , @src_attributes int
    , @dest_file varchar(1000)
    , @file_ext char(4)
    , @src_path varchar(2000)
    , @dest_path varchar(2000)


    select
    @p_strap = 'xxxxxxxxxxxxxxxxxxxxxxx'
    , @p_doc_tp = 'xx'
    , @p_file_name = 'xxxxxxxxx.pdf'


    select 
    @src_file = @p_file_name
    , @dest_file = @p_file_name

    set @src_path = 
    set @dest_path = 


    exec get_file_details @src_path, @src_file, @src_size output, @src_created output, @src_written output, @src_attributes output

    Please help!

    Tuesday, May 17, 2016 3:43 PM

Answers

  • Please see the responses to the posting right before this one, "SQL Server 2014: "Out of memory happened while accessing a critical resource".

    Although memory isn't managed exactly the same way in SQL Server 2008 R2 (not as much SQLCLR memory is covered by max_server_memory in earlier versions), the concept of reducing max_server_memory (for SQL Server memory pools) a bit to allow other applications and SQLCLR to allocate memory outside max_server_memory is similar.

    Once it runs out of memory, restarting SQL Server should clear the condition, but that's not something you want/need to do in a well-configured environment.

    The queries in the other posting should allow you to monitor the memory pools as well.

    Tuesday, May 17, 2016 5:23 PM