Click here to Skip to main content
15,917,795 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
Please see the error log file:-
i am using sysadmin permission to access the assembly.
2013-12-20 17:42:47.35 spid59 Unsafe assembly 'rmsdotnet, version=0.0.0.0, culture=neutral, publickeytoken=null, processorarchitecture=msil' loaded into appdomain 4 (RMS.dbo[runtime].3).
2013-12-20 17:42:47.36 spid59 Unsafe assembly 'rmsdotnet, version=0.0.0.0, culture=neutral, publickeytoken=null, processorarchitecture=msil' loaded into appdomain 4 (RMS.dbo[runtime].3).
2013-12-20 17:42:47.51 spid59 Unsafe assembly 'system.web, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=x86' loaded into appdomain 4 (RMS.dbo[runtime].3).
2013-12-20 17:42:47.53 spid59 Using 'dbghelp.dll' version '4.0.5'
2013-12-20 17:42:47.54 spid59 **Dump thread - spid = 0, EC = 0x41A50028
2013-12-20 17:42:47.54 spid59 *
2013-12-20 17:42:47.54 spid59 * User initiated stack dump. This is not a server exception dump.
2013-12-20 17:42:47.54 spid59 *
2013-12-20 17:42:47.54 spid59 ***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\LOG\SQLDump0018.txt
2013-12-20 17:42:47.54 spid59 * *******************************************************************************
2013-12-20 17:42:47.54 spid59 *
2013-12-20 17:42:47.54 spid59 * BEGIN STACK DUMP:
2013-12-20 17:42:47.54 spid59 * 12/20/13 17:42:47 spid 59
2013-12-20 17:42:47.54 spid59 *
2013-12-20 17:42:47.54 spid59 * FIRST OCCURRENCE: 2013-12-20 17:42:47.35 spid59 Unsafe assembly 'rmsdotnet, version=0.0.0.0, culture=neutral, publickeytoken=null, processorarchitecture=msil' loaded into appdomain 4 (RMS.dbo[runtime].3).
2013-12-20 17:42:47.36 spid59 Unsafe assembly 'rmsdotnet, version=0.0.0.0, culture=neutral, publickeytoken=null, processorarchitecture=msil' loaded into appdomain 4 (RMS.dbo[runtime].3).
2013-12-20 17:42:47.51 spid59 Unsafe assembly 'system.web, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=x86' loaded into appdomain 4 (RMS.dbo[runtime].3).
2013-12-20 17:42:47.53 spid59 Using 'dbghelp.dll' version '4.0.5'
2013-12-20 17:42:47.54 spid59 **Dump thread - spid = 0, EC = 0x41A50028
2013-12-20 17:42:47.54 spid59 *
2013-12-20 17:42:47.54 spid59 * User initiated stack dump. This is not a server exception dump.
2013-12-20 17:42:47.54 spid59 *
2013-12-20 17:42:47.54 spid59 ***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\LOG\SQLDump0018.txt
2013-12-20 17:42:47.54 spid59 * *******************************************************************************
2013-12-20 17:42:47.54 spid59 *
2013-12-20 17:42:47.54 spid59 * BEGIN STACK DUMP:
2013-12-20 17:42:47.54 spid59 * 12/20/13 17:42:47 spid 59
2013-12-20 17:42:47.54 spid59 *
2013-12-20 17:42:47.54 spid59 * FIRST OCCURRENCE: Common Language Runtime escalation on critical resource.
2013-12-20 17:42:47.54 spid59 *
2013-12-20 17:42:47.54 spid59 * Input Buffer 255 bytes -on critical resource.
2013-12-20 17:42:47.54 spid59 *
2013-12-20 17:42:47.54 spid59 * Input Buffer 255 bytes -
Posted
Updated 20-Dec-13 18:41pm
v2

1 solution

 
Share this answer
 
Comments
kalisiddayya 21-Dec-13 0:38am    
I am accessing sql authentication user name 'sa'.sa is having sysadmin permission
Ron Beyer 21-Dec-13 1:12am    
What Mike is saying is that you have an assembly that uses unsafe code. It doesn't matter how you access the database, the application is running under the user account. If the user account doesn't have permission to run unsafe code, then it will throw a CLR error.
kalisiddayya 30-Dec-13 1:39am    
user having serveradmin permission

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900