Failed to create AppDomain "master.sys[runtime].X" - by Ole Kristian Bangaas

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


5
0
Sign in
to vote
ID 693184 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 10/5/2011 7:13:50 AM
Access Restriction Public

Description

Executing the following statement:
select format(3.145,'#.00 kr','no')

Causing the following error to be logged:
Msg 6517, Level 16, State 1, Line 1
Failed to create AppDomain "master.sys[runtime].X".
Exception has been thrown by the target of invocation.

X is a number, starting with 1 and increasing with 1 for every execution of the code above.

There is a lot of free memory on the server. This message is also logged in the SQL Server Error Log and in the event log, but there are no additional information there. The server had been in standby for some days prior to this error message.
Sign in to post a comment.
Posted by Microsoft on 12/6/2011 at 10:24 PM
Errors like:

Msg 6517, Level 16, State 1, Line 3
AppDomain "MDS.dbo [runtime] .20" Could not create.
Exception has been thrown by the target of an invocation.

come directly from .NET/CLR itself. It's usually about some inconsistency with the CLR/.NET itself. It means the CLR installation is corrupted (unlikely), or, more likely, a .NET patch was recently installed and the machine is pending a reboot.

Let us know if reboot doesn't fix the problem.

About the upgrade failure from upgrade step 677 to 678: this issue is fixed in Denali RC1.
Posted by Yirkin on 11/17/2011 at 10:54 AM
I get this error in Denali CTP3 on occasion when restoring a database from an earlier version of SQL Server.

It occures during the upgrade step from 677 to 678

Msg 6517, Level 16, State 1, Line 1
Failed to create AppDomain "master.sys[runtime].1".
Exception has been thrown by the target of an invocation.
Posted by Microsoft on 10/18/2011 at 10:32 AM
Thanks for your feedback regarding this issue. Our developer is taking a look at it and we will respond again after the investigation completes.

Robann Mateja
Microsoft