Yeah, unless you look at the title bar you will cancel and run.

I got this error from .NET Framework 3.5 code calling a stored procedure in SQL Server 2005. The same code worked for most of the stored procedures with all sorts of input, out parameters returning result set, not returning result set or returning scalar values.

This stored procedure was different in one way. This had an Xml input parameter.

If you go search for this error, you will get a lot of different suggestions. Here are some sample suggestions I saw:

• Set the correct size for all sql parameters. 
• Set the size of the Xml input to 1. 
• Set the size for varchar and nvarchar parameters.

What I found is that, when you have at least one input that is Xml data type and one output parameter, set the size for the output parameter. It works. 

If I didn’t have that Xml data type input, I don’t need to specify the size for output parameters.