Hey,

Thanks for everyone's input, problem fixed.. my declaration for a variable was bogus, i thought i had varbinary, but it was varchar 😛

Bump... Anyone?

This is very weird haha i'm sure it's something really stupid, i just can't see it :S

Column1 of table1 is indeed of varbinary type.

dbo.eProcedure as the following definition:

CREATE PROCEDURE [dbo].[eProcedure]

-- Add the parameters for the stored procedure here

@cT varchar(MAX) = NULL,

@et varbinary(MAX) OUTPUT

AS

BEGIN

....

as @value1 is...