CODEWITHSUNDEEP
c#asp.netsql-serverencryptionalways-encrypted
Mulana Monova
Mulana Monova

Reputation: 41

Operand type clash: varchar is incompatible with varchar(50) trying to insert in encrypted database

I am getting a SqlException:

Operand type clash: varchar is incompatible with varchar(50) encrypted with (encryption_type = 'DETERMINISTIC', encryption_algorithm_name = 'AEAD_AES_256_CBC_HMAC_SHA_256', column_encryption_key_name = 'CEK_Auto1', column_encryption_key_database_name = 'PB') collation_name = 'SQL_Latin1_General_CP1_CI_AS'\r\nIncorrect parameter encryption metadata was received from the client. The error occurred during the invocation of the batch and therefore the client can refresh the parameter encryption metadata by calling sp_describe_parameter_encryption and retry.

My C# code:

using (var connection = new SqlConnection(GetConnectionString()))
{
    using (var cmd = new SqlCommand("Clients_Insert", connection))
    {
        cmd.CommandType = CommandType.StoredProcedure;

        cmd.Parameters.Add("@Email", SqlDbType.VarChar, 50).Value = client.Email;
        cmd.Parameters.Add("@ContactPerson", SqlDbType.VarChar, 400).Value = client.ContactPerson;

        connection.Open();
        cmd.ExecuteNonQuery();
    }
}

And my stored procedure: 

ALTER PROCEDURE [dbo].[Clients_Insert]
    @Email VARCHAR(50),
    @ContactPerson VARCHAR(400)
AS
BEGIN
    INSERT into dbo.Clients(Email, ContactPerson) 
    VALUES (@Email, @ContactPerson);

    SELECT SCOPE_IDENTITY();
END;

I have no problems with inserting data into not encrypted fields.

I found this article

http://dataap.org/sql-2016-ctp/column-level-encryption-using-always-encrypted-in-sql-server-2016/

My issue is similiar but i haven't found the solution.

Upvotes: 4

Views: 26868

Answers (4)

Sachin Sonone
Sachin Sonone

Reputation: 21

Anyone still facing an issue with Entity Framework, you may need to define the property with DB Type and Length in the Entity Map which is inherited from EntityTypeConfiguration

this.Property(t => t.FieldName).HasColumnType("varchar").HasMaxLength(50);

Upvotes: 0

Rony
Rony

Reputation: 311

Anyone who still face this issue and none of the above checks didn't help, make sure the parameter names exactly match (case sensitively) both in the procedure and the code.

Upvotes: -2

devC
devC

Reputation: 1444

If someone is still looking for an answer on this, what worked for me is that you need to use DbType.AnsiStringFixedLength data type in the SqlParameter data type, for the encrypted columns.

Refer this article for more information

Upvotes: 5

Nikhil Vithlani - Microsoft
Nikhil Vithlani - Microsoft

Reputation: 837

There are 2 things you can try,

Ensure that Column encryption setting is enabled in your connection string. This can be done using a SqlConnectionStringBuilder object and setting SqlConnectionStringBuilder.ColumnEncryptionSetting to Enabled as follows

strbldr.ColumnEncryptionSetting = SqlConnectionColumnEncryptionSetting.Enabled;

If your stored procedure was created before you encrypted your column, you will need to refresh metadata for your stored procedure as follows

Use [Database]
GO    
--Do this for all stored procedures
EXEC sys.sp_refresh_parameter_encryption @name = '[dbo].[Clients_Insert]'

Upvotes: 5

Related Questions