Solved

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

Posted on 2006-10-24
2
2,246 Views
Last Modified: 2008-01-09
I have a ton of error log in SQL server 2005:

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

Does anyone know what this error mean?

and how can I fixt it?

The error comes from an application that using CLr stored procedure...
0
Comment
Question by:jung1975
  • 2
2 Comments
 
LVL 20

Expert Comment

by:Sirees
ID: 17797477
Looks like this one is fixed in SP1.

Check this

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=191400&SiteID=1
0
 
LVL 20

Accepted Solution

by:
Sirees earned 500 total points
ID: 17797489
0

Featured Post

NAS Cloud Backup Strategies

This article explains backup scenarios when using network storage. We review the so-called “3-2-1 strategy” and summarize the methods you can use to send NAS data to the cloud

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Slowly Changing Dimension Transformation component in data task flow is very useful for us to manage and control how data changes in SSIS.
Ever needed a SQL 2008 Database replicated/mirrored/log shipped on another server but you can't take the downtime inflicted by initial snapshot or disconnect while T-logs are restored or mirror applied? You can use SQL Server Initialize from Backup…
Via a live example, show how to shrink a transaction log file down to a reasonable size.
Via a live example, show how to setup several different housekeeping processes for a SQL Server.

856 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question