Crash occurs when you call Automation procedures from CLR Objects in SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, and SQL Server 2012


Assume that you are running Microsoft SQL Server 2005, Microsoft SQL Server 2008, Microsoft SQL Server 2008 R2, or Microsoft SQL Server 2012. You call some Automation procedures from a SQL Server common language runtime (CLR) object, such as sp_OACreate. In this situation, SQL Server may unexpectedly crash. Additionally, an error message that resembles the following is logged in the application event log: 

Information <Time stamp>Windows Error Reporting 1001 None
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: sqlservr.exe
P2: 2009.100.4000.0
P3: 4fecc5ba
P4: StackHash_b620
P5: 6.1.7601.17725
P6: 4ec4aa8e
P7: c0000374
P8: 00000000000c40f2

Note This issue also occurs when a CLR object calls a Transact-SQL procedure that calls Automation procedures.


To work around this issue, do not directly or indirectly call Automation procedures from any SQL Server CLR objects.

More Information

When an application calls Automation procedures, a message that resembles the following is logged in the SQL Server log:

When an application calls the SQL Server CLR, a message that resembles the following is logged in the SQL Server log:

Note The previous messages do not indicate that CLR objects call Automation procedures.


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

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!