A net framework error occurred during execution of user defined routine or aggregate

I have a database will all CLR functions, I deploy it to a master database and then the rest of the servers get a backup and restore copy of it. For some reason some functionality works in some servers and not in other ones. I am aware the CLR routines
requires external access and that is ok here. The assemblies below had to be manually deployed to make the original database work since I could not figure out how to have them deployed from VS2010 project.

Can somebody guide me on how to make the same CLR database function the same accross multiple servers (most of them are Windows 2008 64 bit, couple test machines are Windows 7 64 bit and we have few Windows 7 32 bit)

Thanks in advance.

Msg 6522, Level 16, State 2, Line 1

A .NET Framework error occurred during execution of user-defined routine or aggregate «GetVolumeInfo_CLR»: 

System.IO.FileLoadException: Could not load file or assembly ‘System.Management, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’ or one of its dependencies. Assembly in host store has a different signature than assembly in GAC. (Exception
from HRESULT: 0x80131050) See Microsoft Knowledge Base article 949080 for more information.

System.IO.FileLoadException: 

   at UtilClr.FileSystemFunctions.GetVolumeInfo()

.

Gokhan Varol

If you are working with CLR in SQLServer you might run into

A .NET Framework error occurred during execution of user-defined routine or aggregate "MyCLRMethod":   System.InvalidOperationException: The context connection is already in use.

I cannot say this is the solution every time but it worked for me.  Look down to the top of the stack (furthest down in the text) and you get some more clues.

Msg 6522, Level 16, State 1, Line 1
A .NET Framework error occurred during execution of user-defined routine or aggregate "MyCLRMethod":
System.InvalidOperationException: The context connection is already in use.
System.InvalidOperationException:
 at System.Data.SqlClient.SqlInternalConnectionSmi.Activate()
 at System.Data.SqlClient.SqlConnectionFactory.GetContextConnection(SqlConnectionString options, Object providerInfo, DbConnection owningConnection)
 at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
 at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
 at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
 at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
 at System.Data.SqlClient.SqlConnection.Open()
 at Elvis.DatabaseCLR.UserDefinedFunctions.GetNextSampleID(DateTime readDate, Int32 meterID, Boolean useNextMeter)
 at Elvis.DatabaseCLR.UserDefinedFunctions.ConsumptionForNewMeter(Int32 sampleID, DateTime readDate, Int32 meterID, Decimal meterCoefficient, Int32 previousMeterConsumption, DateTime presentationDateOfSample)
 at Elvis.DatabaseCLR.UserDefinedFunctions.MyCLRMethod(Int32 sampleID, DateTime presentationDate, DateTime readDate, Int32 meterID, Decimal meterCoefficient, Boolean newMeter)

.

The MyCLRMethod calls two more methods until Open is called.  Playing around I found that I couldn’t open a connection if one already was open.  It sounds right since one of the deals with CLR in SQLServer is that we already have a connection.  The resolution is to tidy up the code so we only open the connection once, or open/closes it over and over again.

Tricks I used:
– When you get the error in your applicaiton copy the SQL string to your query editor and run it from there.
– Press F5 in Visual studio and have Visual studio deploy the CLR for you.  But use the query tool to run the query.  The error message is the same.
– Debug-through-printf, or “throw exception” in this case.  Drop in a throw-exception to find out exactly which Open call is failing.  The F5-and-wait and then run query takes a while.  If you have a logging possibility it is handy now.

Tags: clr in sqlserver, connectio, debugging, dotnet

This entry was posted on Thursday, September 2nd, 2010 at 21:27 and is filed under Code and Development.
You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.

Добрый день!
Есть сборка (это ее часть)

1
2
3
4
5
6
7
8
9
10

 [Microsoft.SqlServer.Server.SqlFunction]
    public static string fn_fk1_getdata(string xml, string url)
    {
 
        ...
 
        StreamWriter sw = File.AppendText(@"C:FK1fk.log");
        sw.WriteLine(str1);
        sw.Close();
        ...

Она построена и опубликована. Создана сборка в SQL Server Management Studio 2008
При вызове сборки из процедуры возникает ошибка
A .NET Framework error occurred during execution of user-defined routine or aggregate «fn_fk1_getdata»: System.Security.SecurityException: Request for the permission of type ‘System.Security.Permissions.FileIOPermission, mscorlib, Version=2.0.0.0, Cult

И еще нюанс: во всех сборках на сервере набор разрешений «неограниченный» , а у моей — «безопасный» и изменить не получается. Ошибка «Unsafe assembly permission was denied on object ‘server’, database ‘master'»

Подскажите, пожалуйста, что делать в такой ситуации???
Спасибо!

This is one of the most common problems we get asked, and it’s also the one we are least equipped to answer, but you are most equipped to answer yourself.

Let me just explain what the error means: You have tried to use a variable, property, or a method return value but it contains null — which means that there is no instance of a class in the variable.
It’s a bit like a pocket: you have a pocket in your shirt, which you use to hold a pen. If you reach into the pocket and find there isn’t a pen there, you can’t sign your name on a piece of paper — and you will get very funny looks if you try! The empty pocket is giving you a null value (no pen here!) so you can’t do anything that you would normally do once you retrieved your pen. Why is it empty? That’s the question — it may be that you forgot to pick up your pen when you left the house this morning, or possibly you left the pen in the pocket of yesterdays shirt when you took it off last night.

We can’t tell, because we weren’t there, and even more importantly, we can’t even see your shirt, much less what is in the pocket!

Back to computers, and you have done the same thing, somehow — and we can’t see your code, much less run it and find out what contains null when it shouldn’t.
But you can — and Visual Studio will help you here. Run your program in the debugger and when it fails, VS will show you the line it found the problem on. You can then start looking at the various parts of it to see what value is null and start looking back through your code to find out why. So put a breakpoint at the beginning of the method containing the error line, and run your program from the start again. This time, VS will stop before the error, and let you examine what is going on by stepping through the code looking at your values.

But we can’t do that — we don’t have your code, we don’t know how to use it if we did have it, we don’t have your data. So try it — and see how much information you can find out!