4

I have a SQL CLR Function (written in c#.net) that I'm trying to debug. I attach visual studio to the sqlserver process and begin stepping through, but it keeps crashing and ending with the following error message:

.NET Framework execution was aborted. Another query caused the AppDomain DatabaseName.dbo[runtime].4 to be unloaded.

(The number after DatabaseName.dbo[runtime] changes - increments on each crash)

It sometimes even crashes the sql server process & stops the service.

The function works absolutely fine with no errors when I'm not debugging. This only happens when I'm debugging.

Does anyone have any idea what could be causing this?

Thanks

tuseau
  • 1,334
  • 4
  • 17
  • 37
  • Also it's SQL Server 2008 and Visual Studo 2008 I'm working with. – tuseau Sep 14 '11 at 15:04
  • Could it be a different process calling your CLR SP? SQL might have to terminate your debugging process to run the SP again. – Chuck Jul 22 '15 at 17:37

1 Answers1

0

I had exactly the same message today - for me, the reason was the change in the 'max server memory' configuration while the SSIS load was running.

What might have helped here is an extract from the SQL Server Log:

SQL Server Error Log

milivojeviCH
  • 1,580
  • 14
  • 29