Question

I want to send SMS using GSM modem’s AT-Commands from SQL Server 2008, so I wrote a Visual C# SQL CLR Database Project and a stored procedure.

But when I execute that stored procedure I received this error:

Request for the permission of type
‘System.Security.Permissions.SecurityPermission, mscorlib,
Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089’
failed.

The source codes of stored procedure and the class for sending sms are these:

[Microsoft.SqlServer.Server.SqlProcedure]
public static void SendSMS2(string phone, string message)
{
    SMSManagement.SM2S ss = new SMSManagement.SM2S();
    ss.SendMessage(phone, message);
}

public void SendMessage(string PhoneNumber, string Message)
{
    try
    {
        SerialPort port = new SerialPort();

        port.PortName = "COM5";                
        port.BaudRate = 115200;                  
        port.DataBits = 8;                
        port.StopBits = StopBits.One;     
        port.Parity = Parity.None;        
        port.ReadTimeout = 300;           
        port.WriteTimeout = 300;          

        // Error occurred in here.
        port.Open();
        port.DtrEnable = true;
        port.RtsEnable = true;

        SMS sms = new SMS();
        sms.Direction = SMSDirection.Submited;
        sms.PhoneNumber = PhoneNumber;
        sms.ValidityPeriod = new TimeSpan(4, 0, 0, 0);
        sms.Message = Message;

        Message = sms.Compose(SMS.SMSEncoding.UCS2);

        ExecCommand(port, "AT", 300, "No phone connected");
        ExecCommand(port, "AT+CMGF=0", 300, "Failed to set pdu format.");
        ExecCommand(port, "AT+CMGS=1", 300, "Failed to set message length.");
        string command = Message + char.ConvertFromUtf32(26);
        ExecCommand(port, command, 6000, "Failed to send message"); 

        port.Close();
    }
    catch (Exception ex)
    {
        SqlContext.Pipe.Send(ex.Message);
    }
}

The version of Visual Studio and SQL Server is 2010 SP1 and 2008 R2.
The CLR project framework is 2.0 .

Answer 1

You didn’t mention how you installed your assembly into SQL Server. If you just deployed straight from Visual Studio – what permission level did you specify??

The default value is Safe, which is okay as long as you only work within SQL Server – regex matching or things like that.

If you want to “reach out” from SQL Server and communicate with the world, you must set the Permission Level to Unsafe before you deploy your assembly into SQL Server.