on pages 148-150 i'm trying to do the exercise and am getting the following error--

[Execute SQL Task] Error: Executing the query "EXEC usp_GetConfigParamValue 'MYAPP','MYPARM','STRING',@MYVALUE OUTPUT" failed with the following error: "The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter 3 ("@MyValue"): Data type 0xE7 has an invalid data length or metadata length.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

i've rechecked everything several times...anyone run into this or know what might be the problem?

thanks

burke

I got the same problem. And if I try the exercise available that you can download from Wrox, it doesn't work either. So the problem seem's to be a difference between the version of SQL 2005 they use to create that exercise, and the way to do it in the final version...

Hi,

I made some test and it work, but not for a string return:

I change the stored proc to this:
ALTER PROCEDURE [dbo].[uspGetConfigParamValue]
    @ApplicationName varchar(30),
    @ParameterName varchar(50),
    @ParameterTypeName varchar(30),
    @ParameterValueVar int OUTPUT
AS
BEGIN
    SET NOCOUNT ON;
    SET @ParameterValueVar = 55
END

and I change the Execute task to this:
SQLStatement: dbo.uspGetConfigParamValue
IsQueryStoredProcedure: True

I declare the 4 variables in the parameter mapping, and I use the same name as in the stored Proc(see http://www.juliankuiters.id.au/artic...put-parameters), like @ParameterValueVar map to MyFile as a Int32 (for the purpose of testing). So I have also 4 variables in the package (MyFile as Int32, MyApp, MyParm and MyType as String).

Now, I change the expression for the connection as:
"C:\\Test" + (DT_STR, 2, 1252) @[User::MyFile] + ".txt"

and it work, it change the name of the file. But when I try to use string type, it give me the same error (data type invalide). So I think that maybe the String type of the variable at the package level is not compatible with the string type in the ADO.NET connection.

I'm getting the same error and have played around with it trying to get it to work - but no luck yet. Anyone else?

Anything Further on this?

Its something i want to use in the Data warehouse i am developing, and it not working is quite frustrating.


Thanks,
Truby Gravatt
Aspex Consulting Ltd
e: [email protected]

I reported this bug last week and they have advised that a fix should appear on the website within the next week.

I'm having the same issue. Where on the website will the fix appear?

Hi Mark,

I received the response from Wiley Customer Support on 1st March.
They said the solution should appear at the following link.

http://www.wrox.com/WileyCDA/WroxTit...764584359.html

Jays

Thanks Jays
I'll keep checking it...

In case anyone is interested. I found a mechanism for getting return values out of parameters when making OLEDB calls to stored procs.
Instead of calling the proc through this mechanism, 'EXEC ? = proc', you call it this way '{? = CALL proc}' it works. You can simply map a parameter to the return value of the proc referencing a parameter called '0'.
There's been a lot written up around this in various places on the web. I found the solution here:
http://msdn.microsoft.com/library/de...qlprovspec.asp